Search This Blog

Jan 9, 2012

Cannot install Exchange servers / Error Message "Set-WERRegistryMarkers; Provisioning layer initialization failed: 'Failed to reconnect to Active Directory ...'"


Hello All,

This is my first blog topic about the Exchange 2010. I'm still understanding and learning how about Exchange 2010 works and how it can be administrater properly. These few days after new year I worked with some issues we got during the installation with the following Events  ID Error

 Log Name:      Application
Source:        MSExchangeSetup
Event ID:      1002
Task Category: Microsoft Exchange Setup
Level:         Error
Computer:      E2K10.abc.com
Description: Exchange Server component Management Tools failed.
Error: Error:
The following error was generated when "$error.Clear();
          Set-WERRegistryMarkers;
        " was run: "Provisioning layer initialization failed: 'Failed to reconnect to Active Directory server DC01.abc.com. Make sure the server is available, and that you have used the correct credentials.'".
Provisioning layer initialization failed: 'Failed to reconnect to Active Directory server DC01.abc.com. Make sure the server is available, and that you have used the correct credentials.'
Failed to reconnect to Active Directory server DC01.abc.com. Make sure the server is available, and that you have used the correct credentials.
Active Directory server DC01.abc.com is not available. Please retry at a later time.


Log Name:      Application
Source:        MSExchange ADAccess
Event ID:      2138
Task Category: Configuration
Level:         Error
Computer:      E2K10.abc.com
Description: Process ExSetup.exe (PID=1972). Exchange Active Directory Provider received a request to connection to domain controller DC01.abc.com but that domain controller is not available. Use the Ping or PathPing command-line tools to test network connectivity to local domain controllers. Run the Dcdiag command line tool to test domain controller health.



Solution1
============


  • Checking Logs and the info


[01/09/2012 18:16:17.0188] [1] [ERROR] The following error was generated when "$error.Clear();

          Set-WERRegistryMarkers;

        " was run: "Provisioning layer initialization failed: 'Failed to reconnect to Active Directory server DC01.abc.com. Make sure the server is available, and that you have used the correct credentials.'".

[01/09/2012 18:16:17.0188] [1] [ERROR] Provisioning layer initialization failed: 'Failed to reconnect to Active Directory server DC01.abc.com. Make sure the server is available, and that you have used the correct credentials.'

[01/09/2012 18:16:17.0188] [1] [ERROR] Failed to reconnect to Active Directory server DC01.abc.com. Make sure the server is available, and that you have used the correct credentials.

[01/09/2012 18:16:17.0188] [1] [ERROR] Active Directory server DC01.abc.com is not available. Please retry at a later time.

[01/09/2012 18:16:17.0204] [1] [ERROR-REFERENCE] Id=AllRolesCommonFirst_RunOnce___b30cefaa0d2a486086e9b6517e52add7

[01/09/2012 18:16:17.0204] [1] Setup is stopping now because of one or more critical errors.

[01/09/2012 18:16:17.0204] [1] Finished executing component tasks.


  • Uninstall the Microsoft Forefront Protection 2010 (FEP) or set the "Microsoft Antimalware Service" Service to disable.
  • After restarting the server the Exchange installation worked properly.



Solution2
============


  • After trying steps above started some troubleshooting

  • Disabled and uninstall FEP (It works on first server CAS installed, but now it’s not).
  • Disabled all Offload configuration on NIC Cards and also by netsh command(http://support.microsoft.com/kb/951037)
  • Restarted the DC DC01.abc.com
  • Changed the Bind Order and also changed the IP DNS Servers to others DC server  (GC enabled).
  • Ran ProcMon and nothing found
  • Checked all Microsoft .NET Framework version 2 and 4 services and it’s set as Manual for Version2 and Automatic (Delay) for version4.
  • Executed ‘NLtest /dsgetdc:nestle.com /force’ to find another DC to communicate with Exchange Server.
  • After all steps above we removed the Microsoft SCOM Agent 2007 R2 and restarted the server.
  • Exchange 2010 installation completed sucessfully.


02/10/2012 Update: Another way to try fix was if you are using the Exchange installation thru network shared folder try copy the installation under some disk like F:\ or C:\ and install from there. It will avoid network packets and probably there's a bad communication or network issue.

3 comments:

  1. Hello all,

    Exchange continues to make high-availability simple by creating DAGs, multiple servers cooperating to make a set of exchange mailboxes highly available through continuous replication and high-availability failover. Thanks for sharing it.....

    ReplyDelete
  2. Had the same problem...thanks for providing the steps to try!!! Running the NLtest command and fixing the binding order on the NICs fix the problem on my machine.

    ReplyDelete
  3. NLtest was the fix. Thanks for posting this!

    ReplyDelete