Getting Event ID error 4015 and 4004

System setup:

Windows 2003 server
AD, DNS, DHCP

Getting these error:

Event Type:      Error
Event Source:      DNS
Event Category:      None
Event ID:      4015
Date:            11/19/2008
Time:            8:33:45 PM
User:            N/A
Computer:      SVR-AEG-03
Description:
The DNS server has encountered a critical error from the Active Directory. Check that the Active Directory is functioning properly. The extended error debug information (which may be empty) is "000020EF: SvcErr: DSID-020800E0, problem 5012 (DIR_ERROR), data -1017". The event data contains the error.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 01 00 00 00               ....    

Event Type:      Error
Event Source:      DNS
Event Category:      None
Event ID:      4004
Date:            11/19/2008
Time:            8:33:45 PM
User:            N/A
Computer:      SVR-AEG-03
Description:
The DNS server was unable to complete directory service enumeration of zone aegera.local.  This DNS server is configured to use information obtained from Active Directory for this zone and is unable to load the zone without it.  Check that the Active Directory is functioning properly and repeat enumeration of the zone. The extended error debug information (which may be empty) is "000020EF: SvcErr: DSID-020800E0, problem 5012 (DIR_ERROR), data -1017". The event data contains the error.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 2a 23 00 00               *#..    

In the DNS snap-in, getting this is the forward lookup zone:

Zone not loaded by DNS Server.

Only 1 AD, DNS on the network.

Now Exchange is down because of this problem.  I was getting the error prior to today but it was still working.   I had to reboot the server tonight and now I am getting problem.  I have to fix this tonight.  Please help.
pctechaegeraAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

mtzmindCommented:
your problem is that active directory is not working  so that DNS  or exchange servers can't read from the active directory
just it
restart the server and everything will be fine
kind regards
mcse+ security
0
pctechaegeraAuthor Commented:
I did restart twice and the problem was not fixed.
0
mtzmindCommented:

Details
Product: Windows Operating System
Event ID: 4004
Source: DNS
Version: 5.2
Symbolic Name: DNS_EVENT_DS_ZONE_ENUM_FAILED
Message: The DNS server was unable to complete directory service enumeration of zone %1. This DNS server is configured to use information obtained from Active Directory for this zone and is unable to load the zone without it. Check that the Active Directory is functioning properly and repeat enumeration of the zone. The extended error debug information (which may be empty) is "%2". The event data contains the error.
   
Explanation
The DNS Server service uses Active Directory to store DNS data, and it encountered a Lightweight Directory Access Protocol (LDAP) error while querying the directory. This error could be caused by either a high load on the domain controller or the failure of other domain controller services.
 
   
User Action
If this message appears repeatedly, restart the DNS Server service, and then look in the event log for other events occurring at the same time that could be causing this problem.
 
 
0
Newly released Acronis True Image 2019

In announcing the release of the 15th Anniversary Edition of Acronis True Image 2019, the company revealed that its artificial intelligence-based anti-ransomware technology – stopped more than 200,000 ransomware attacks on 150,000 customers last year.

mtzmindCommented:

Product: Windows Operating System
Event ID: 4015
Source: DNS
Version: 5.2
Symbolic Name: DNS_EVENT_DS_INTERFACE_ERROR
Message: The DNS server has encountered a critical error from the Active Directory. Check that the Active Directory is functioning properly. The extended error debug information (which may be empty) is "%1". The event data contains the error.
   
Explanation
The DNS Server service uses Active Directory to store DNS data, and it encountered a Lightweight Directory Access Protocol (LDAP) error while querying the directory. This error could be caused by either a time-out or a temporary interruption of service.
 
   
User Action
If this message appears repeatedly, restart the DNS Server service.

For more information about DNS and DNS troubleshooting procedures, see Domain Name System(DNS)Center.
 
FROM MICROSOFT WIBESITE
0
pctechaegeraAuthor Commented:
I did try that and I am still getting the error.  In the event viewer, under DNS, the log are filled with ID 4015 and 4004.
0
mtzmindCommented:
IS THERE ANY LOG EVENTS  OCCURS AT THE SAME TIME
0
pctechaegeraAuthor Commented:
When I restart the DNS service, I am getting error 4015 and 4004 error right away.  There does not seems to have any other error that occur at the same time.

This is the error I am getting when running DCdiag:

C:\Documents and Settings\pctech>dcdiag

Domain Controller Diagnosis

Performing initial setup:
   Done gathering initial info.

Doing initial required tests

   Testing server: Montreal\server03
      Starting test: Connectivity
         The host 828b4244-1eb5-488b-a014-aad182b88d78._msdcs.domain.local could
 not be resolved to an
         IP address.  Check the DNS server, DHCP, server name, etc
         Although the Guid DNS name
         (828b4244-1eb5-488b-a014-aad182b88d78._msdcs.domain.local) couldn't be
         resolved, the server name (server03.domain.local) resolved to the IP
         address (192.168.42.3) and was pingable.  Check that the IP address is
         registered correctly with the DNS server.
         ......................... server03 failed test Connectivity

Doing primary tests

   Testing server: Montreal\server03
      Skipping all tests, because server server03 is
      not responding to directory service requests

   Running partition tests on : DomainDnsZones
      Starting test: CrossRefValidation
         ......................... DomainDnsZones passed test CrossRefValidation

      Starting test: CheckSDRefDom
         ......................... DomainDnsZones passed test CheckSDRefDom

   Running partition tests on : ForestDnsZones
      Starting test: CrossRefValidation
         ......................... ForestDnsZones passed test CrossRefValidation

      Starting test: CheckSDRefDom
         ......................... ForestDnsZones passed test CheckSDRefDom

   Running partition tests on : Schema
      Starting test: CrossRefValidation
         ......................... Schema passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... Schema passed test CheckSDRefDom

   Running partition tests on : Configuration
      Starting test: CrossRefValidation
         ......................... Configuration passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... Configuration passed test CheckSDRefDom

   Running partition tests on : domain
      Starting test: CrossRefValidation
         ......................... domain passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... domain passed test CheckSDRefDom

   Running enterprise tests on : domain.local
      Starting test: Intersite
         ......................... domain.local passed test Intersite
      Starting test: FsmoCheck
         ......................... domain.local passed test FsmoCheck

Regards,
0
mtzmindCommented:
CHECK SERVER 3  tcp/ip configuration and ensure that it has the right ip address and  ensure that it point to your  dns server as the prefered dns server
regards
0
pctechaegeraAuthor Commented:
I double check this and all is properly configured.

Regards,
0
mtzmindCommented:
is  the  tcp/ip is provied by dhcp or manually
if  provided by dhcp  configure  change it to manually configuration
and my last try is to make sure that server 3 have a a   srv record at the dns lookup zone
0
pctechaegeraAuthor Commented:
The IP address is setup manually.  And as I stated, in my initial post, the forward lookup zone is not working, getting a red X with error: Zone not loaded by DNS server.

Regards,
0
meugenCommented:
If you have installed AD using Dcprom , the dcpromo create the .(root) zone and when you need to use the forwords option as Microsoft recommendation for Internet names resolution you will always get the 4004 & 4015 errors in your log. To solve this problem and stop these events do the following:
1. Create a .(root) zone file
2. Right click the .(root) name and select Properties
3. Change the zone into a primary zone instead of the integrated AD zone type
4. Delete the .(root) zone
0
pctechaegeraAuthor Commented:
Keep in mind that DNS are not my field of expertise.  Where do I create the .root zone file, does it matter?

I have only 1 DNS server and only one primary zone define.  When I go in the property of the primary zone, it says Expired???  How can this be with a primary zone???

Regards,
0
pctechaegeraAuthor Commented:
My site is down right now because of this.  Anyone?
0
pctechaegeraAuthor Commented:
When I try to delete the zone I am getting this error:

The zone cannot be deleted.  The active Directory service is not available.

I need help.  My site is down since this morning.  
0
ChiefITCommented:
Upon seeing these two errors together, it is usually the result of a misconfigured multihomed server.

Do you have multiple NICs on this server?
0
ChiefITCommented:
Another thing you should try is this:

go to the server's command prompt and type:

Net stop Netlogon
Net start netlogon
Ipconfig /flushDNS
0
pctechaegeraAuthor Commented:
Therer is only 1 nic on the server.  I also try to start and stop the Netlogon.  Still no go.  The same is true with IPconfig /flushdns.

I also try to delete the nic card and recreate it.  The server is running under Vmware ESX 3.5.  There are about 80 mailbox on the server.  

I cannot do anything with the forward lookup zone.  I had the assistance of a consultant who is an expert.  He also could not found the problem.  We open a case at Microsoft and they told us that they never seen this before.  They are still working on it.  

Really not sure what to do next.  The site as been down all day.  Not looking good for tomorrow.

Regards,
0
ChiefITCommented:
I have also seen this when IPver 6 was on the server and DNS was not configured to handle IPv6.

I am going to provide you a link. Please evaluate your system to determine if you have IP version 6 enabled. If so, stop and get back in touch with me. We will evaluate if your LAN can support IPv6, and if you wish to use IPv6.

http://beta.experts-exchange.com/Networking/Protocols/DNS/Q_23604907.html
0
ChiefITCommented:
If you are NOT running IPv6 and have determined the above solution is not your solution:

Then, let's look at a couple more solutions I was working on that resolved the issues of events 4004 and 4015.

____________________________________________________________
Errors 4015 and 4004 can usually be ignored if these events happen upon startup:

It means DNS was started before AD service. They will go away if this was upon loadup. I just helped someone with these errors.

http://www.experts-exchange.com/Networking/Protocols/DNS/Q_22901131.html
_____________________________________________________________________
If the problem goes unresolved, you may wish to look in your reverse lookup zone, and also check the DHCP service on bot the servers and clients to make sure they are enabled. The below article may help you.

http://www.experts-exchange.com/Operating_Systems/Windows_Server_2003/Q_21213433.html
________________________________________________________________________________

If DHCP client is running and these events continue beyond startup, then look at your reverse lookup zone records for your DC.

Your clients will look at their preferred DNS server IPs, it will go to the reverse lookup zone and try to determine a name for your AD servers. If there is no reverse zone lookup for  your DC, or there is an error in the reverse lookup zone, then you could see these errors you describe.

0
pctechaegeraAuthor Commented:
I finally found the problem.  The AD database was corrupted.  With the help of Microsoft we managed to fix the corruption.  I was then able to reinstall the DNS role on the server and now all is good.

0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
ChiefITCommented:
Guess that will do it too. Glad to see you got it fixed.
0
Lawrence Sullivan, M.D.Commented:
i have the same problem.  how did you fix the corrupted database?
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Active Directory

From novice to tech pro — start learning today.