none
Unable to Login on Active Cluster Node/Password Error

    Întrebare

  • Hi,

    I have Exchange 2007 Sp2 and MBX is in CCR. Yesterday i was unable to login on my Active node, wen i was using child domain admin credentials it was giving me password error and when i used Root domain for login it gives me Trust Relationship error. Passive node was fine and i was able to login on that. So when i login with local admin account on active node i came to know that it is not contacting AD and i was unable to open AD console although the ping was fine. I tried to restart AD toplogy service but it failed in Exchange Search INdex service. AFter that my Exhcange SA service was not restarting. There were many events related to this:

    Event ID 1119
    Cluster network name resource 'Cluster Name' failed to register DNS name 'mailstore.abc.com' over adapter 'Local Area Connection' for the following reason:

    'DNS bad key.
    '

    Event ID 1196
    Cluster network name resource 'Cluster Name' failed registration of one or more associated DNS name(s) for the following reason:
    DNS bad key.
    .
    Ensure that the network adapters associated with dependent IP address resources are configured with at least one accessible DNS server.

    The Node was Mailstore02 i..e passive node which was the source. Although the DNS records were available and DNS was up.

    When this event stop, i receive following events

    Event ID 1009

    The Microsoft Exchange Mail Submission Service is currently unable to contact any Hub Transport servers in the local Active Directory site. The servers may be too busy to accept new connections at this time.

    Event ID 8365

    Could not read the Security Descriptor from the Exchange Server object with guid=455503BCD4FB9442B1EFE3867DFE6DA0. As a result the Proxy Address Calculation RPC interface will not be available on the local Exchange Server.  

    Event ID 9035

    Service MSExchangeMailSubmission.  Unable to process anything for over 30 minutes.  Diagnostic info: Governor: Governor for DatabaseManagerEvent, Last run time: 4/12/2012 3:30:48 PM, Next retry interval: 00:05:00.  Current exception: Microsoft.Exchange.Assistants.TransientServerException
       at Microsoft.Exchange.Assistants.Util.CatchMeIfYouCan(CatchMe function)
       at Microsoft.Exchange.Assistants.Base.CatchMeIfYouCan(CatchMe function)
       at Microsoft.Exchange.Assistants.EventDispatcherPrivate.DangerousProcessItem(EmergencyKit kit, InterestingEvent interestingEvent)

    Event ID 1530
    Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards.  

     DETAIL -
     1 user registry handles leaked from \Registry\User\S-1-5-21-2776101096-4073983867-524009191-500:
    Process 1060 (\Device\HarddiskVolume1\Windows\System32\svchost.exe) has opened key \REGISTRY\USER\S-1-5-21-2776101096-4073983867-524009191-500\Printers\DevModePerUser

    Event ID 106
    Performance counter updating error. Counter name is Successful Submissions, category name is MSExchangeMailSubmission. Optional code: 2.

    After these event mails were not flowing inside/outside my organzation. Email sending was completely halted both locally and externally.

    Later i found

    Event ID 9144
    NSPI Proxy failed to connect to Global Catalog DC01.hec.gov.pk over transport Rpc/HTTP.  This server is down or unreachable. Clients will not be directed to this GC until it is available again.

    Then i move the cluster node to passive node and ultimately i had to restart my active node to solve these problems. After restart i was able to login on DC as well as services were started.

    I am unable to identify what the problem was which causes mailflow to stop.


    Hasan

    13 aprilie 2012 04:24

Toate mesajele

  • Hi
    Please check availability your Domain controller and DNS server.
    Run command below on Domain controller

    Dcdiag /v
    Netdiag

    Ensure possibility register DNS record "mailstore.abc.com" on your DNS server. For additional information see link below

    http://smtp25.blogspot.com/2008/10/cluster-network-name-resource-name_23.html


    13 aprilie 2012 05:53
  • Hi
    Please check availability your Domain controller and DNS server.
    Run command below on Domain controller

    Dcdiag /v
    Netdiag

    Ensure possibility register DNS record "mailstore.abc.com" on your DNS server. For additional information see link below

    http://smtp25.blogspot.com/2008/10/cluster-network-name-resource-name_23.html



    All DNS records were there and there was no changes.

    Hasan

    13 aprilie 2012 07:17
  • Hi
    Please check availability your Domain controller and DNS server.
    Run command below on Domain controller

    Dcdiag /v
    Netdiag

    Ensure possibility register DNS record "mailstore.abc.com" on your DNS server. For additional information see link below

    http://smtp25.blogspot.com/2008/10/cluster-network-name-resource-name_23.html



    All DNS records were there and there was no changes.

    Hasan

    Did you check that solutions ?

    "Go to DNS, find the record ( A & Pointer record) for the cluster name resource.

    Make a right click
    Go to properties
    In the security make sure the "Authenticated users" are included
    Make sure it has "Write: rights and Special permissions
    Click Advance, locate authenticated users, and click edit
    Make sure, Write all properties, Read permissions, All Validated Writes selected
    Click okay tree times to exit"

    Try to run on cluster node ipconfig /flushdns after that run ipconfig /registerdns

    What about result Dcdiag and Netdiag ?

    13 aprilie 2012 07:33
  • Since you have rebooted the box, you are not likely going to get to the root cause.  This is the classic situation - do you want relief or root cause?

    If you wanted root cause, then you would need to see why you could not get to AD, and why logon was failing.  One thing that will cause this is leaky NIC device drivers - but you would have needed to look at the non paged memory before rebooting, and then compare it to your baseline.  The PAL tool at code plex can also assist with this, or you go and get the values from SCOM and see how they tracked prior to being unable to logon. 

    Also, you do realize that SP2 for Exchange 2007 is no longer supported? 

    http://blogs.technet.com/b/rmilne/archive/2012/03/26/exchange-2007-service-pack-3-is-required.aspx 

    You must update to SP3 to receive full support from Microsoft.


    Cheers, Rhoderick NOTICE: My posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

    13 aprilie 2012 13:45
  • Since you have rebooted the box, you are not likely going to get to the root cause.  This is the classic situation - do you want relief or root cause?

    If you wanted root cause, then you would need to see why you could not get to AD, and why logon was failing.  One thing that will cause this is leaky NIC device drivers - but you would have needed to look at the non paged memory before rebooting, and then compare it to your baseline.  The PAL tool at code plex can also assist with this, or you go and get the values from SCOM and see how they tracked prior to being unable to logon. 

    Also, you do realize that SP2 for Exchange 2007 is no longer supported? 

    http://blogs.technet.com/b/rmilne/archive/2012/03/26/exchange-2007-service-pack-3-is-required.aspx 

    You must update to SP3 to receive full support from Microsoft.


    Cheers, Rhoderick NOTICE: My posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.


    Well that is production environemtn and i couldn't wait 2-3 days for forum support and get help. I had to do it something at that time, priority was to UP the service at that time so i had to do it in that situation.

    Hasan

    13 aprilie 2012 19:51
  • DCDIAG for ROOT DOMAIN where server is located is:

    C:\Windows\system32>dcdiag

    Directory Server Diagnosis

    Performing initial setup:
       Trying to find home server...
       Home Server = DC01
       * Identified AD Forest.
       Done gathering initial info.

    Doing initial required tests

       Testing server: Islamabad\DC01
          Starting test: Connectivity
             ......................... DC01 passed test Connectivity

    Doing primary tests

       Testing server: Islamabad\DC01
          Starting test: Advertising
             ......................... DC01 passed test Advertising
          Starting test: FrsEvent
             ......................... DC01 passed test FrsEvent
          Starting test: DFSREvent
             ......................... DC01 passed test DFSREvent
          Starting test: SysVolCheck
             ......................... DC01 passed test SysVolCheck
          Starting test: KccEvent
             ......................... DC01 passed test KccEvent
          Starting test: KnowsOfRoleHolders
             ......................... DC01 passed test KnowsOfRoleHolders
          Starting test: MachineAccount
             ......................... DC01 passed test MachineAccount
          Starting test: NCSecDesc
             ......................... DC01 passed test NCSecDesc
          Starting test: NetLogons
             ......................... DC01 passed test NetLogons
          Starting test: ObjectsReplicated
             ......................... DC01 passed test ObjectsReplicated
          Starting test: Replications
             REPLICATION-RECEIVED LATENCY WARNING
             DC01:  Current time is 2012-04-14 01:29:33.
                DC=ForestDnsZones,DC=abc,DC=com
                   Last replication received from KHIDC01 at
              2012-04-12 18:54:46
                   Last replication received from LHRDC02 at
              2012-04-12 18:54:59
                   Last replication received from LHRDC01 at
              2012-04-12 18:58:54
                   Last replication received from PSHDC01 at
              2012-04-12 18:45:59
                   Last replication received from PSHDC02 at
              2011-01-14 12:58:09
                   WARNING:  This latency is over the Tombstone Lifetime of 180
             days!
                CN=Schema,CN=Configuration,DC=abc,DC=com
                   Last replication received from KHIDC01 at
              2012-04-12 18:52:52
                   Last replication received from LHRDC02 at
              2012-04-12 18:54:59
                   Last replication received from LHRDC01 at
              2012-04-12 18:58:51
                   Last replication received from PSHDC01 at
              2012-04-12 18:45:59
                   Last replication received from PSHDC02 at
              2012-04-12 18:35:23
                CN=Configuration,DC=abc,DC=com
                   Last replication received from KHIDC01 at
              2012-04-12 18:52:51
                   Last replication received from LHRDC02 at
              2012-04-12 18:54:59
                   Last replication received from LHRDC01 at
              2012-04-12 18:58:50
                   Last replication received from PSHDC01 at
              2012-04-12 18:45:59
                   Last replication received from PSHDC02 at
              2011-01-14 12:58:09
                   WARNING:  This latency is over the Tombstone Lifetime of 180
             days!
                DC=KHI,DC=abc,DC=com
                   Last replication received from KHIDC01 at
              2012-04-12 19:01:15
                DC=LHR,DC=abc,DC=com
                   Last replication received from LHRDC02 at
              2012-04-12 18:54:59
                   Last replication received from LHRDC01 at
              2012-04-12 18:58:57
                DC=PSH,DC=abc,DC=com
                   Last replication received from PSHDC01 at
              2012-04-12 18:46:15
                   Last replication received from PSHDC02 at
              2011-01-14 12:58:10
                   WARNING:  This latency is over the Tombstone Lifetime of 180
             days!
             ......................... DC01 passed test Replications
          Starting test: RidManager
             ......................... DC01 passed test RidManager
          Starting test: Services
             ......................... DC01 passed test Services
          Starting test: SystemLog
             An Warning Event occurred.  EventID: 0x000003FC
                Time Generated: 04/14/2012   00:55:20
                Event String:
                Scope, 10.80.7.0, is 91 percent full with only 18 IP addresses remai
    ning.
             An Warning Event occurred.  EventID: 0x000003FC
                Time Generated: 04/14/2012   00:55:20
                Event String:
                Scope, 10.80.18.0, is 92 percent full with only 9 IP addresses remai
    ning.
             An Warning Event occurred.  EventID: 0x8000001D
                Time Generated: 04/14/2012   00:57:35
                Event String:
                The Key Distribution Center (KDC) cannot find a suitable certificate
     to use for smart card logons, or the KDC certificate could not be verified. Sma
    rt card logon may not function correctly if this problem is not resolved. To cor
    rect this problem, either verify the existing KDC certificate using certutil.exe
     or enroll for a new KDC certificate.
             An Error Event occurred.  EventID: 0x00000457
                Time Generated: 04/14/2012   01:29:16
                Event String:
                Driver Adobe PDF Converter required for printer Adobe PDF is unknown
    . Contact the administrator to install the driver before you log in again.
             An Error Event occurred.  EventID: 0x00000457
                Time Generated: 04/14/2012   01:29:23
                Event String:
                Driver HP Universal Printing PCL 6 required for printer HP Universal
     Printing PCL 6 is unknown. Contact the administrator to install the driver befo
    re you log in again.
             An Error Event occurred.  EventID: 0x00000457
                Time Generated: 04/14/2012   01:29:24
                Event String:
                Driver Microsoft Office Live Meeting 2007 Document Writer Driver req
    uired for printer Microsoft Office Live Meeting 2007 Document Writer is unknown.
     Contact the administrator to install the driver before you log in again.
             An Error Event occurred.  EventID: 0x00000457
                Time Generated: 04/14/2012   01:29:27
                Event String:
                Driver Send To Microsoft OneNote 2010 Driver required for printer Se
    nd To OneNote 2010 is unknown. Contact the administrator to install the driver b
    efore you log in again.
             ......................... DC01 failed test SystemLog
          Starting test: VerifyReferences
             ......................... DC01 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 : hec
          Starting test: CheckSDRefDom
             ......................... abc passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... abc passed test CrossRefValidation

       Running enterprise tests on : abc.com
          Starting test: LocatorCheck
             ......................... abc.com passed test LocatorCheck
          Starting test: Intersite
             ......................... abc.com passed test Intersite


    ----------------------------------------------------------------------------------------------------------------


    Hasan

    13 aprilie 2012 20:43
  • DCDIAG for sub domain is:


    Directory Server Diagnosis


    Performing initial setup:

       Trying to find home server...

       Home Server = ISBDC01

       * Identified AD Forest.
       Done gathering initial info.


    Doing initial required tests

       
       Testing server: Islamabad\ISBDC01

          Starting test: Connectivity

             ......................... ISBDC01 passed test Connectivity



    Doing primary tests

       
       Testing server: Islamabad\ISBDC01

          Starting test: Advertising

             ......................... ISBDC01 passed test Advertising

          Starting test: FrsEvent

             ......................... ISBDC01 passed test FrsEvent

          Starting test: DFSREvent

             ......................... ISBDC01 passed test DFSREvent

          Starting test: SysVolCheck

             ......................... ISBDC01 passed test SysVolCheck

          Starting test: KccEvent

             An Warning Event occurred.  EventID: 0x8000061E

                Time Generated: 04/14/2012   01:25:21

                Event String:

                All directory servers in the following site that can replicate the directory partition over this transport are currently unavailable.


             An Warning Event occurred.  EventID: 0x8000061E

                Time Generated: 04/14/2012   01:25:21

                Event String:

                All directory servers in the following site that can replicate the directory partition over this transport are currently unavailable.


             An Warning Event occurred.  EventID: 0x8000061E

                Time Generated: 04/14/2012   01:25:21

                Event String:

                All directory servers in the following site that can replicate the directory partition over this transport are currently unavailable.


             An Error Event occurred.  EventID: 0xC000051F

                Time Generated: 04/14/2012   01:25:21

                Event String:

                The Knowledge Consistency Checker (KCC) has detected problems with the following directory partition.


             An Warning Event occurred.  EventID: 0x80000749

                Time Generated: 04/14/2012   01:25:21

                Event String:

                The Knowledge Consistency Checker (KCC) was unable to form a complete spanning tree network topology. As a result, the following list of sites cannot be reached from the local site.


             An Warning Event occurred.  EventID: 0x8000061E

                Time Generated: 04/14/2012   01:25:21

                Event String:

                All directory servers in the following site that can replicate the directory partition over this transport are currently unavailable.


             An Warning Event occurred.  EventID: 0x8000061E

                Time Generated: 04/14/2012   01:25:21

                Event String:

                All directory servers in the following site that can replicate the directory partition over this transport are currently unavailable.


             An Error Event occurred.  EventID: 0xC000051F

                Time Generated: 04/14/2012   01:25:21

                Event String:

                The Knowledge Consistency Checker (KCC) has detected problems with the following directory partition.


             An Warning Event occurred.  EventID: 0x80000749

                Time Generated: 04/14/2012   01:25:21

                Event String:

                The Knowledge Consistency Checker (KCC) was unable to form a complete spanning tree network topology. As a result, the following list of sites cannot be reached from the local site.


             An Warning Event occurred.  EventID: 0x8000061E

                Time Generated: 04/14/2012   01:25:21

                Event String:

                All directory servers in the following site that can replicate the directory partition over this transport are currently unavailable.


             An Warning Event occurred.  EventID: 0x8000061E

                Time Generated: 04/14/2012   01:25:21

                Event String:

                All directory servers in the following site that can replicate the directory partition over this transport are currently unavailable.


             An Error Event occurred.  EventID: 0xC000051F

                Time Generated: 04/14/2012   01:25:21

                Event String:

                The Knowledge Consistency Checker (KCC) has detected problems with the following directory partition.


             An Warning Event occurred.  EventID: 0x80000749

                Time Generated: 04/14/2012   01:25:21

                Event String:

                The Knowledge Consistency Checker (KCC) was unable to form a complete spanning tree network topology. As a result, the following list of sites cannot be reached from the local site.


             An Warning Event occurred.  EventID: 0x8000061E

                Time Generated: 04/14/2012   01:25:21

                Event String:

                All directory servers in the following site that can replicate the directory partition over this transport are currently unavailable.


             An Warning Event occurred.  EventID: 0x8000061E

                Time Generated: 04/14/2012   01:25:21

                Event String:

                All directory servers in the following site that can replicate the directory partition over this transport are currently unavailable.


             An Warning Event occurred.  EventID: 0x8000061E

                Time Generated: 04/14/2012   01:25:21

                Event String:

                All directory servers in the following site that can replicate the directory partition over this transport are currently unavailable.


             An Error Event occurred.  EventID: 0xC000051F

                Time Generated: 04/14/2012   01:25:21

                Event String:

                The Knowledge Consistency Checker (KCC) has detected problems with the following directory partition.


             An Warning Event occurred.  EventID: 0x80000749

                Time Generated: 04/14/2012   01:25:21

                Event String:

                The Knowledge Consistency Checker (KCC) was unable to form a complete spanning tree network topology. As a result, the following list of sites cannot be reached from the local site.


             An Warning Event occurred.  EventID: 0x8000061E

                Time Generated: 04/14/2012   01:25:21

                Event String:

                All directory servers in the following site that can replicate the directory partition over this transport are currently unavailable.


             An Warning Event occurred.  EventID: 0x8000061E

                Time Generated: 04/14/2012   01:25:21

                Event String:

                All directory servers in the following site that can replicate the directory partition over this transport are currently unavailable.


             An Error Event occurred.  EventID: 0xC000051F

                Time Generated: 04/14/2012   01:25:21

                Event String:

                The Knowledge Consistency Checker (KCC) has detected problems with the following directory partition.


             An Warning Event occurred.  EventID: 0x80000749

                Time Generated: 04/14/2012   01:25:21

                Event String:

                The Knowledge Consistency Checker (KCC) was unable to form a complete spanning tree network topology. As a result, the following list of sites cannot be reached from the local site.


             An Warning Event occurred.  EventID: 0x8000061E

                Time Generated: 04/14/2012   01:25:21

                Event String:

                All directory servers in the following site that can replicate the directory partition over this transport are currently unavailable.


             An Warning Event occurred.  EventID: 0x8000061E

                Time Generated: 04/14/2012   01:25:21

                Event String:

                All directory servers in the following site that can replicate the directory partition over this transport are currently unavailable.


             An Error Event occurred.  EventID: 0xC000051F

                Time Generated: 04/14/2012   01:25:21

                Event String:

                The Knowledge Consistency Checker (KCC) has detected problems with the following directory partition.


             An Warning Event occurred.  EventID: 0x80000749

                Time Generated: 04/14/2012   01:25:21

                Event String:

                The Knowledge Consistency Checker (KCC) was unable to form a complete spanning tree network topology. As a result, the following list of sites cannot be reached from the local site.


             An Warning Event occurred.  EventID: 0x80000786

                Time Generated: 04/14/2012   01:25:42

                Event String:

                The attempt to establish a replication link to a read-only directory partition with the following parameters failed.


             ......................... ISBDC01 failed test KccEvent

          Starting test: KnowsOfRoleHolders

             ......................... ISBDC01 passed test KnowsOfRoleHolders

          Starting test: MachineAccount

             ......................... ISBDC01 passed test MachineAccount

          Starting test: NCSecDesc

             ......................... ISBDC01 passed test NCSecDesc

          Starting test: NetLogons

             ......................... ISBDC01 passed test NetLogons

          Starting test: ObjectsReplicated

             ......................... ISBDC01 passed test ObjectsReplicated

          Starting test: Replications

             [Replications Check,ISBDC01] A recent replication attempt failed:

                From PSHDC01 to ISBDC01

                Naming Context: DC=ForestDnsZones,DC=abc,DC=com

                The replication generated an error (1256):

                The remote system is not available. For information about network troubleshooting, see Windows Help.

                

                The failure occurred at 2012-04-14 00:50:48.

                The last success occurred at 2012-04-12 17:57:04.

                39 failures have occurred since the last success.

             [PSHDC01] DsBindWithSpnEx() failed with error 1722,

             The RPC server is unavailable..
             [Replications Check,ISBDC01] A recent replication attempt failed:

                From LHRDC01 to ISBDC01

                Naming Context: DC=ForestDnsZones,DC=abc,DC=com

                The replication generated an error (1256):

                The remote system is not available. For information about network troubleshooting, see Windows Help.

                

                The failure occurred at 2012-04-14 00:51:09.

                The last success occurred at 2012-04-12 17:57:08.

                41 failures have occurred since the last success.

             [LHRDC01] DsBindWithSpnEx() failed with error 1722,

             The RPC server is unavailable..
             [Replications Check,ISBDC01] A recent replication attempt failed:

                From PSHDC01 to ISBDC01

                Naming Context: CN=Schema,CN=Configuration,DC=abc,DC=com

                The replication generated an error (1722):

                The RPC server is unavailable.

                The failure occurred at 2012-04-14 00:51:52.

                The last success occurred at 2012-04-12 17:47:50.

                32 failures have occurred since the last success.

                The source remains down. Please check the machine.

             [Replications Check,ISBDC01] A recent replication attempt failed:

                From LHRDC01 to ISBDC01

                Naming Context: CN=Schema,CN=Configuration,DC=abc,DC=com

                The replication generated an error (1722):

                The RPC server is unavailable.

                The failure occurred at 2012-04-14 00:52:13.

                The last success occurred at 2012-04-12 17:47:50.

                32 failures have occurred since the last success.

                The source remains down. Please check the machine.

             [Replications Check,ISBDC01] A recent replication attempt failed:

                From PSHDC01 to ISBDC01

                Naming Context: CN=Configuration,DC=abc,DC=com

                The replication generated an error (1722):

                The RPC server is unavailable.

                The failure occurred at 2012-04-14 00:50:48.

                The last success occurred at 2012-04-12 17:47:49.

                33 failures have occurred since the last success.

                The source remains down. Please check the machine.

             [Replications Check,ISBDC01] A recent replication attempt failed:

                From LHRDC01 to ISBDC01

                Naming Context: CN=Configuration,DC=abc,DC=com

                The replication generated an error (1722):

                The RPC server is unavailable.

                The failure occurred at 2012-04-14 00:51:09.

                The last success occurred at 2012-04-12 17:47:49.

                33 failures have occurred since the last success.

                The source remains down. Please check the machine.

             [Replications Check,ISBDC01] A recent replication attempt failed:

                From PSHDC01 to ISBDC01

                Naming Context: DC=abc,DC=com

                The replication generated an error (1256):

                The remote system is not available. For information about network troubleshooting, see Windows Help.

                

                The failure occurred at 2012-04-14 00:50:48.

                The last success occurred at 2012-04-12 17:47:50.

                35 failures have occurred since the last success.

             [Replications Check,ISBDC01] A recent replication attempt failed:

                From LHRDC01 to ISBDC01

                Naming Context: DC=abc,DC=com

                The replication generated an error (1256):

                The remote system is not available. For information about network troubleshooting, see Windows Help.

                

                The failure occurred at 2012-04-14 00:51:09.

                The last success occurred at 2012-04-12 17:47:50.

                33 failures have occurred since the last success.

             [Replications Check,ISBDC01] A recent replication attempt failed:

                From PSHDC01 to ISBDC01

                Naming Context: DC=KHI,DC=abc,DC=com

                The replication generated an error (1256):

                The remote system is not available. For information about network troubleshooting, see Windows Help.

                

                The failure occurred at 2012-04-14 00:50:48.

                The last success occurred at 2012-04-12 17:47:50.

                32 failures have occurred since the last success.

             [Replications Check,ISBDC01] A recent replication attempt failed:

                From LHRDC01 to ISBDC01

                Naming Context: DC=KHI,DC=abc,DC=com

                The replication generated an error (1256):

                The remote system is not available. For information about network troubleshooting, see Windows Help.

                

                The failure occurred at 2012-04-14 00:51:09.

                The last success occurred at 2012-04-12 17:47:50.

                32 failures have occurred since the last success.

             [Replications Check,ISBDC01] A recent replication attempt failed:

                From PSHDC01 to ISBDC01

                Naming Context: DC=LHR,DC=abc,DC=com

                The replication generated an error (1256):

                The remote system is not available. For information about network troubleshooting, see Windows Help.

                

                The failure occurred at 2012-04-14 00:50:48.

                The last success occurred at 2012-04-12 17:47:51.

                32 failures have occurred since the last success.

             [Replications Check,ISBDC01] A recent replication attempt failed:

                From LHRDC01 to ISBDC01

                Naming Context: DC=LHR,DC=abc,DC=com

                The replication generated an error (1256):

                The remote system is not available. For information about network troubleshooting, see Windows Help.

                

                The failure occurred at 2012-04-14 00:51:09.

                The last success occurred at 2012-04-12 17:47:51.

                34 failures have occurred since the last success.

             [Replications Check,ISBDC01] A recent replication attempt failed:

                From PSHDC01 to ISBDC01

                Naming Context: DC=PSH,DC=abc,DC=com

                The replication generated an error (1256):

                The remote system is not available. For information about network troubleshooting, see Windows Help.

                

                The failure occurred at 2012-04-14 00:50:48.

                The last success occurred at 2012-04-12 17:58:01.

                39 failures have occurred since the last success.

             [Replications Check,ISBDC01] A recent replication attempt failed:

                From LHRDC01 to ISBDC01

                Naming Context: DC=PSH,DC=abc,DC=com

                The replication generated an error (1256):

                The remote system is not available. For information about network troubleshooting, see Windows Help.

                

                The failure occurred at 2012-04-14 00:51:09.

                The last success occurred at 2012-04-12 17:47:51.

                32 failures have occurred since the last success.

             ......................... ISBDC01 failed test Replications

          Starting test: RidManager

             ......................... ISBDC01 passed test RidManager

          Starting test: Services

             ......................... ISBDC01 passed test Services

          Starting test: SystemLog

             An Warning Event occurred.  EventID: 0x000016AF

                Time Generated: 04/14/2012   01:22:21

                Event String:

                During the past 4.19 hours there have been 11 connections to this Domain Controller from client machines whose IP addresses don't map to any of the existing sites in the enterprise. Those clients, therefore, have undefined sites and may connect to any Domain Controller including those that are in far distant locations from the clients. A client's site is determined by the mapping of its subnet to one of the existing sites. To move the above clients to one of the sites, please consider creating subnet object(s) covering the above IP addresses with mapping to one of the existing sites.  The names and IP addresses of the clients in question have been logged on this computer in the following log file '%SystemRoot%\debug\netlogon.log' and, potentially, in the log file '%SystemRoot%\debug\netlogon.bak' created if the former log becomes full. The log(s) may contain additional unrelated debugging information. To filter out the needed information, please search for lines which contain text 'NO_CLIENT_SITE:'. The first word after this string is the client name and the second word is the client IP address. The maximum size of the log(s) is controlled by the following registry DWORD value 'HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\LogFileMaxSize'; the default is 20000000 bytes.  The current maximum size is 20000000 bytes.  To set a different maximum size, create the above registry value and set the desired maximum size in bytes.

             An Error Event occurred.  EventID: 0xC00A0038

                Time Generated: 04/14/2012   01:32:24

                Event String:

                The Terminal Server security layer detected an error in the protocol stream and has disconnected the client.

             An Error Event occurred.  EventID: 0x00000457

                Time Generated: 04/14/2012   01:32:53

                Event String:

                Driver Adobe PDF Converter required for printer Adobe PDF is unknown. Contact the administrator to install the driver before you log in again.

             An Error Event occurred.  EventID: 0x00000457

                Time Generated: 04/14/2012   01:33:00

                Event String:

                Driver HP Universal Printing PCL 6 required for printer HP Universal Printing PCL 6 is unknown. Contact the administrator to install the driver before you log in again.

             An Error Event occurred.  EventID: 0x00000457

                Time Generated: 04/14/2012   01:33:00

                Event String:

                Driver Microsoft Office Live Meeting 2007 Document Writer Driver required for printer Microsoft Office Live Meeting 2007 Document Writer is unknown. Contact the administrator to install the driver before you log in again.

             An Error Event occurred.  EventID: 0x00000457

                Time Generated: 04/14/2012   01:33:02

                Event String:

                Driver Send To Microsoft OneNote 2010 Driver required for printer Send To OneNote 2010 is unknown. Contact the administrator to install the driver before you log in again.

             ......................... ISBDC01 failed test SystemLog

          Starting test: VerifyReferences

             ......................... ISBDC01 passed test VerifyReferences

       
       
       Running partition tests on : DomainDnsZones

          Starting test: CheckSDRefDom

             ......................... DomainDnsZones passed test CheckSDRefDom

          Starting test: CrossRefValidation

             ......................... DomainDnsZones passed test

             CrossRefValidation

       
       Running partition tests on : isb

          Starting test: CheckSDRefDom

             ......................... isb passed test CheckSDRefDom

          Starting test: CrossRefValidation

             ......................... isb passed test CrossRefValidation

       
       Running partition tests on : ForestDnsZones

          Starting test: CheckSDRefDom

             ......................... ForestDnsZones passed test CheckSDRefDom

          Starting test: CrossRefValidation

             ......................... ForestDnsZones 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 enterprise tests on : abc.com

          Starting test: LocatorCheck

             ......................... abc.com passed test LocatorCheck

          Starting test: Intersite

             ......................... abc.com passed test Intersite

    Hasan

    13 aprilie 2012 20:44
  • Hi,

    The issue has been solved after you restart the active node, is that ture?

    From the logs that you have posted here, I think we need to fix the DC related issue first. Exchange has a lot dependency on Active Directory services. You can post the issUe in Windows Server forum to get better help.

    http://social.technet.microsoft.com/Forums/en/winserverDS/threads


    Xiu Zhang

    TechNet Community Support


    16 aprilie 2012 07:11
  • Hi,

    The issue has been solved after you restart the active node, is that ture?

    From the logs that you have posted here, I think we need to fix the DC related issue first. Exchange has a lot dependency on Active Directory services. You can post the issUe in Windows Server forum to get better help.

    http://social.technet.microsoft.com/Forums/en/winserverDS/threads


    Xiu Zhang

    TechNet Community Support


    Yes Thats true, when i restart the active node the issue was solved...My Exchange servers are part of root domain i.e. they are member of DC01 domain and wen i run DCDIAG on DC01 i can't find any error you can see above...

    Errors are in ISBDC01 which is the sub domain of DC01...


    Hasan

    18 aprilie 2012 03:43
  • Hi,

    For errors from DCdiag on ISBDC01, I recommend you to post the issue in windows server forum to get better help.

    Also I'd like to share similar thread:

    Problem with Windows 2003 Directory Service

    http://social.technet.microsoft.com/Forums/en-US/winserverDS/thread/bfeffa0d-0665-4d23-83ed-15ed6fa7ac83/


    Xiu Zhang

    TechNet Community Support

    18 aprilie 2012 05:39
  • Since you have rebooted the box, you are not likely going to get to the root cause.  This is the classic situation - do you want relief or root cause?

    If you wanted root cause, then you would need to see why you could not get to AD, and why logon was failing.  One thing that will cause this is leaky NIC device drivers - but you would have needed to look at the non paged memory before rebooting, and then compare it to your baseline.  The PAL tool at code plex can also assist with this, or you go and get the values from SCOM and see how they tracked prior to being unable to logon. 

    Also, you do realize that SP2 for Exchange 2007 is no longer supported? 

    http://blogs.technet.com/b/rmilne/archive/2012/03/26/exchange-2007-service-pack-3-is-required.aspx 

    You must update to SP3 to receive full support from Microsoft.


    Cheers, Rhoderick NOTICE: My posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.


    Well that is production environemtn and i couldn't wait 2-3 days for forum support and get help. I had to do it something at that time, priority was to UP the service at that time so i had to do it in that situation.

    Hasan

    That is why there are a range of support options.  If you want immediate assistance, please call in to CTS and they can work with you. 

    That said, you really MUST get your active directory into a better state.  The fact that I see tombstone expired objects in the dcdiag output frightens the heck out of me.  I should not bee seeing that in the output. 

                   WARNING:  This latency is over the Tombstone Lifetime of 180
             days!

    If you cannot have AD up and running, then Exchange has zero chance of functioning, since all of its configuration is stored in AD.


    Cheers, Rhoderick NOTICE: My posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

    18 aprilie 2012 13:20