Exchange Active Directory Error 0x51
Contents |
360 games PC games active directory response the ldap server is unavailable exchange 2013 Windows games Windows phone games Entertainment All Entertainment error active directory response the ldap server is unavailable Movies & TV Music Business & Education Business Students & educators error 0x51 fail to connect to ldap Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security Internet
Kb2019500
Explorer Microsoft Edge Skype OneNote OneDrive Microsoft Health MSN Bing Microsoft Groove Microsoft Movies & TV Devices & Xbox All Microsoft devices Microsoft Surface All Windows PCs & tablets PC accessories Xbox & games Microsoft Lumia All the ldap server is unavailable exchange 2010 Windows phones Microsoft HoloLens For business Cloud Platform Microsoft Azure Microsoft Dynamics Windows for business Office for business Skype for business Surface for business Enterprise solutions Small business solutions Find a solutions provider Volume Licensing For developers & IT pros Develop Windows apps Microsoft Azure MSDN TechNet Visual Studio For students & educators Office for students OneNote in classroom Shop PCs & tablets perfect for students Microsoft in Education Support Sign in Cart Cart Javascript is disabled Please enable javascript and refresh the page Cookies are disabled Please enable cookies and refresh the page CV: {{ getCv() }} English (United States) Terms of use Privacy & cookies Trademarks © 2016 Microsoft
Error 0x51 Microsoft Exchange administrators get hung up some times when they encounter sudden Exchange Errors. Recently we ran into a similar problem that drove an active directory error 0x52 occurred when trying to check server us nuts. We had just recently demoted one of our old domain controllers.
Exchange 2010 Error 0x51
For a few days everything worked fine. But, just recently our Exchange Server 2010 started throwing up error 0x51 while pointing to the demoted domain controller. The whole database would be locked up and mostly a restart would make the problem go away. What actually happens is that the https://support.microsoft.com/en-us/kb/2986941 Exchange Management Console tries to connect to the non-existent DC which was a part of the network sometime back. This would throw up an error message similar to this: Log Name: Application Source: MSExchange Configuration Cmdlet - Remote Management Date: DATE Event ID: 4 Task Category: General Level: Error Keywords: Classic User: N/A Computer: COMPUTER NAME Description: Error: Microsoft.Exchange.Data.Directory.SuitabilityDirectoryException: An Active Directory error http://email-converter-tools.blogspot.com/2013/02/a-permanent-resolve-for-microsoft.html 0x51 occurred when trying to check the suitability of server ‘SERVER NAME'. Error: ‘Active directory response: The LDAP server is unavailable.' What we found online was that the aforestated error is a result of Exchange Management Console trying to connect to an old domain controller that is no longer available. To point to the new domain controller we had to follow these steps: • Open Exchange Management Console • Right click on Organization Configuration • Click Modify Configuration Domain Controller • Check Use Default Domain Controller This should have resolved the issue. However, we were able to execute the same steps successfully but the problem persisted. We tried another solution that was to delete the Exchange Management Console file from the following location: C:\users\\AppData\Roaming\Microsoft\MMC\Exchange Management Console Close and restart Exchange Management Console. But the issue still lingered on and there was no other way but to opt for a third party Exchange Server Recovery tool. Stellar Phoenix Mailbox Exchange Server Recovery is one such powerful solution that can resolve all kinds of Exchange Server Errors, JET Engine errors and Active Directory errors. The software can
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a https://www.experts-exchange.com/questions/27726429/Exchange-2010-Active-Directory-error-0x51-LDAP.html Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search Submit Close http://www.networksteve.com/exchange/topic.php/Exchange_2013_SP1_CU11_Install_Fails_-_Active_directory_response/?TopicId=62548&Posts=4 Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > Exchange 2010 - Active Directory active directory error 0x51 LDAP Want to Advertise Here? Solved Exchange 2010 - Active Directory error 0x51 LDAP Posted on 2012-05-21 Exchange Active Directory 1 Verified Solution 7 Comments 4,349 Views Last Modified: 2014-04-14 Hi all. We've got two domain controllers. The second is a new one. First DC ist Windows 2008 Standard, the ldap server second Windows 2008 R2 Enterprise. The Exchange Server is 2010 Standard Service Pack 2. We need the second DC for failover if the first goes down. We tried this szenario (shut down the first domaincontroller) but Exchange is not work on. We tried to Add the second DC as PreferredServer with the "Set-ADServerSettings" Command in the PowerShell. [PS] C:\>Set-ADServerSettings -PreferredServer dc2.local We get the following error message: An Active Directory error 0x51 occured when trying to check the suitability of server dc2.local 'Active Directory response: The LDAP server is unavailable. CategoryInfo: NotSpecified: (0:Int32) [Set-ADServerSettings], SuitabilityDirectoryException FullyQulifiedErrorid: 96AD2D25, Microsoft.Exchange.Management.ADServerSettings.SetADServerSettings 0 Question by:Opusretis Facebook Twitter LinkedIn Google Best Solution byOpusretis Yes we use the AD integrated DNS - both DC's are DNS Server and they are replicated. The Exchange is pointing in his networksettings primarly to dc1 and alternatively to dc2. Go to Solution 7 Comments LVL 13 Overall: Level 13 Ac
2013 SP1 CU11 install. I'm trying to Upgradefrom Exchange Server 2013 SP1 CU9. Searchinggoogle, this appears to have been an issue many versions back when talking to a DC that is not a GC. The domain controller listed in the error is in facta DC with the Infrastructure Master role so is not a GC. There is a GC in the site that is up and functional. I don't see any errors on the domain controller in question. The servers appears to be healthy. Has anyone come across this problem before? Error: The following error was generated when "$error.Clear(); initialize-ExchangeUniversalGroups -DomainController $RoleDomainController -ActiveDirectorySplitPermissions $RoleActiveDirectorySplitPermissions " was run: "Microsoft.Exchange.Data.Directory.SuitabilityDirectoryException: An Active Directory error 0x51 occurred when trying to check the suitability of server 'DC01.mydomain.com'. Error: 'Active directory response: The LDAP server is unavailable.' ---> System.DirectoryServices.Protocols.LdapException: The LDAP server is unavailable. at System.DirectoryServices.Protocols.LdapConnection.Connect() at System.DirectoryServices.Protocols.LdapConnection.BindHelper(NetworkCredential newCredential, Boolean needSetCredential) at Microsoft.Exchange.Data.Directory.PooledLdapConnection.BindWithLogging() at Microsoft.Exchange.Data.Directory.PooledLdapConnection.TryBindWithRetry(Int32 maxRetries, ADErrorRecord& errorRecord) --- End of inner exception stack trace --- at Microsoft.Exchange.Data.Directory.TopologyDiscovery.SuitabilityVerifier.CheckIsServerSuitable(String fqdn, Boolean isGlobalCatalog, NetworkCredential credentials, String& writableNC) at Microsoft.Exchange.Data.Directory.ConnectionPoolManager.GetConnection(ConnectionType connectionType, String partitionFqdn, ADObjectId domain, String serverName, Int32 port, NetworkCredential credential) at Microsoft.Exchange.Data.Directory.ConnectionPoolManager.GetConnection(ConnectionType connectionType, String partitionFqdn, NetworkCredential networkCredential, String serverName, Int32 port) at Microsoft.Exchange.Data.Directory.ADDataSession.GetConnection(String preferredServer, Boolean isWriteOperation, String optionalBaseDN, ADObjectId& rootId, ADScope scope) at Microsoft.Exchange.Data.Directory.ADDataSession.GetReadConnection(String preferredServer, String optionalBaseDN, ADObjectId& rootId, ADRawEntry scopeDeteriminingObject) at Microsoft.Exchange.Data.Directory.ADGenericReader.GetNextResultCollection(Type controlType, DirectoryControl& responseControl) at Microsoft.Exchange.Data.Directory.ADPagedReader