none
DNS EVENT ID 4015 IN 2012 SERVER RRS feed

  • Question

  • IN DNS 4015 error showing.We restarted the domain & DNS services still error comes.

    Please see the following error & Please help to resolve the issue.

    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 "". The event data contains the error.

    Friday, May 5, 2017 7:46 AM

All replies

  • Hello,

    This could turn out to be a false positive within Event Viewer, have you tried running a DCDIAG on the DC's? Also, try disabling IPV6 if you don't need it enabling.

    Thanks

    Ben

    Friday, May 5, 2017 7:50 AM
  • Dear BEN,

    DCDIAG command gives two errors.

    1. failed test Advertising

    2.  failed test NetLogons.

    What this errors???

    How i resolve this???

    Please Refer following test result,

    Testing server: Default-First-Site-Name\INMU-ADC
       Starting test: Advertising
          Warning: DsGetDcName returned information for
          \\INMU-BOVRDC01.MM001.SIPL.NET, when we were trying to reach INMU-ADC.
          SERVER IS NOT RESPONDING or IS NOT CONSIDERED SUITABLE.
          ......................... INMU-ADC failed test Advertising
       Starting test: FrsEvent
          ......................... INMU-ADC passed test FrsEvent
       Starting test: DFSREvent
          ......................... INMU-ADC passed test DFSREvent
       Starting test: SysVolCheck
          ......................... INMU-ADC passed test SysVolCheck
       Starting test: KccEvent
          ......................... INMU-ADC passed test KccEvent
       Starting test: KnowsOfRoleHolders
          ......................... INMU-ADC passed test KnowsOfRoleHolders
       Starting test: MachineAccount
          ......................... INMU-ADC passed test MachineAccount
       Starting test: NCSecDesc
          ......................... INMU-ADC passed test NCSecDesc
       Starting test: NetLogons
          Unable to connect to the NETLOGON share! (\\INMU-ADC\netlogon)
          [INMU-ADC] An net use or LsaPolicy operation failed with error 67,
          The network name cannot be found..
          ......................... INMU-ADC failed test NetLogons
       Starting test: ObjectsReplicated
          ......................... INMU-ADC passed test ObjectsReplicated
       Starting test: Replications
          ......................... INMU-ADC passed test Replications
       Starting test: RidManager
          ......................... INMU-ADC passed test RidManager
       Starting test: Services
             w32time Service is stopped on [INMU-ADC]
          ......................... INMU-ADC failed test Services
       Starting test: SystemLog
          An error event occurred.  EventID: 0x000003F4
             Time Generated: 05/05/2017   13:52:18
             Event String:
             There was an error while attempting to read the local hosts file.
          ......................... INMU-ADC failed test SystemLog
       Starting test: VerifyReferences
          ......................... INMU-ADC passed test VerifyReferences


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

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

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

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

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

    Running enterprise tests on : MM001.SIPL.NET
       Starting test: LocatorCheck
          ......................... MM001.SIPL.NET passed test LocatorCheck
       Starting test: Intersite
          ......................... MM001.SIPL.NET passed test Intersite


    Thanks,

    Yogesh 


    Friday, May 5, 2017 9:09 AM
  • Please follow the steps on the below TechNet link, they should resolve the Advertising issues and possibly the others as well.

    https://social.technet.microsoft.com/Forums/windowsserver/en-US/52aef8f1-7910-4651-8c96-f1c4ba40c689/new-dc-never-shares-sysvol-or-ntds-and-gets-event-13565-and-then-13508-trouble-replicating?forum=winserverDS

    Judging by your errors, it looks like an access related issue, but it could also be network related. Have you reserved an IP for this server? Is this a new DC or one that was running previously?

    Friday, May 5, 2017 10:03 AM
  • Yes Static IP provided for this server & that is reserved.

    This additional domain controller & this is not new dc.

    Friday, May 5, 2017 10:08 AM
  • Hi Yogesh Ghatge,

    1. What is the machine with name "INMU-BOVRDC01.MM001.SIPL.NET"? Is it a DC in you domain? How many DCs in your domain totally?

    2. Is the problematic machine "INMU-ADC"?

    3. Please provide the ipconfig/all on the problematic machine. Check if the machine could ping 127.0.0.1 and ping the PDC. Also check the firewall settings, you may also turn off the firewall temporarily for test purpose.

    Best Regards,

    Anne


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, May 8, 2017 9:03 AM
    Moderator
  • Hi Anne De,

    1. Host name is INMU-ADC. Yes this is a dc but additional domain controller. 2 dc in our domain.

    2. Yes

    3.Pc is pinging & firewall already off.

    Thanks & Regards,

    Yogesh Ghatge

    Tuesday, May 9, 2017 4:20 AM
  • Hi Yogesh Ghatge,

    Have you got any progress with the issue? If still not, I would recommend you open a case with MS, so that you may get more professional help:

    https://support.microsoft.com/en-us/gp/support-options-for-business

    Best Regards,

    Anne


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, May 24, 2017 7:10 AM
    Moderator