An Active Directory Error 0x51 Occurred When Trying
Contents |
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Asked by: an active directory error 0x51 occurred when trying to check the suitability of server ldap Active Directory Error 0x51 occurred when trying to check the an active directory error 0x51 occurred when trying to check the suitability of server exchange suitability of server '
Active Directory Error 0x51 Ldap Server Unavailable
the command 'Get-OwaVirtualDirectory'. Previous Versions of Exchange > Exchange Server 2010 Question 1 Sign in to vote This issue is driving us nuts - there
Active Directory Response The Ldap Server Is Unavailable Exchange 2013
are no issues with Domain Controllers or AD in this environment. The server it is citing in the error has been retired - it was gracefully dcpromo'ed down and removed from the environment. DNS has no record of it, nor is it located anywhere else. We are not able to log into error active directory response the ldap server is unavailable Outlook Web App either with authentication failed errors - and I can't help but expect these 2 issues are related? I tried hard coding the Configuration Domain Controller at the org level, as well as using the -staticdomaincontrollers and -staticglobalcatalogservers with the "Set-ExchangeServer" powershell command - no luck.... System settings of the exchange 2010 servers show they are pointing to the correct DCs - but I still get this error accompanied with long delays in rendering windows in EMC. Extremely frustrating..... I have an issue logged with MS now, but they aren't looking at them until Nov 9. Has anyone seen this issue at all? More info on the OWA config - using Form based auth, and I'm not able to perform a simple test-owaconnectivity -mailboxcredential (get-credential\username) -allowuntrustedcertificate -allowinsecurelogon - please help Thursday, November 05, 2009 4:05 PM Reply | Quote All replies 0 Sign in to vote Hi,Did you try usi
Error 0x51 Microsoft Exchange administrators get hung up some times when they encounter sudden Exchange Errors. Recently we ran into a
Kb2019500
similar problem that drove us nuts. We had just recently demoted kb 2019500 one of our old domain controllers. For a few days everything worked fine. But, just recently our exchange ldap server is unavailable 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 https://social.technet.microsoft.com/Forums/en-US/5302379e-9c43-49e5-9a20-b935bbe2b875/active-directory-error-0x51-occurred-when-trying-to-check-the-suitability-of-server-servername?forum=exchange2010 problem go away. What actually happens is that the 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 http://email-converter-tools.blogspot.com/2013/02/a-permanent-resolve-for-microsoft.html Keywords: Classic User: N/A Computer: COMPUTER NAME Description: Error: Microsoft.Exchange.Data.Directory.SuitabilityDirectoryException: An Active Directory error 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 Phoeni
Case and Cooling Fetish CPU & Motherboard Technologia Mobile Computing Outpost Networking Matrix Other Hardware Agora Classifieds Ars DIY Forum (Name TBD!) Operating Systems & Software Battlefront Microsoft OS & http://arstechnica.com/civis/viewtopic.php?t=39342 Software Colloquium Linux Kung Fu Windows Technical Mojo Distributed Computing Arcana Macintoshian Achaia Programmer's Symposium The Server Room Ars Lykaion Gaming, Extra Strength Caplets The Lounge The Soap Box http://www.adaxes.com/forum/error-on-mailbox-creation-t1857.html The Boardroom The Observatory Ars Help & Feedback Ars Subscription Member Areas Image Galleries Exchange 2010 MMC still trying to use decommissioned DC 6 posts nathaniel Ars Praefectus Registered: Feb 10, 2002Posts: 3913 active directory Posted: Tue Mar 16, 2010 8:23 am I've decommissioned our Small Business Server over the weekend and forgot to check the Exchange 2010 MMC for any references to our SBS server in the preferences of the snap in itself (Exchange 2010 settings are not using sbs2008). Now a day later the snap in fails sighting it can't find the SBS. If I run Get-OrganizationalUnit and Get-DomainController in EMS I get my only two new DCs active directory error not the SBS server. My DNS and ADSI Edit have no references to the SBS server yet the snap in keeps trying to use it. How do I change it or what is the EMS command for Setting the Organization Configuration's Configuration Domain Controller and Domain? scorp508 Ars Legatus Legionis Tribus: Boston, MA Registered: Apr 24, 2006Posts: 10150 Posted: Tue Mar 16, 2010 8:43 am If you right-click the org and hit properties there should be a window that allows you to either statically choose a GC or select on dynamically. nathaniel Ars Praefectus Registered: Feb 10, 2002Posts: 3913 Posted: Tue Mar 16, 2010 9:24 am quote:Originally posted by scorp508:If you right-click the org and hit properties there should be a window that allows you to either statically choose a GC or select on dynamically. If I try that I can't even select the domain because it keeps failing with Get-Domain error. Once I got the domain to show up but then trying to select the GC failed saying it can't get any info from Get-OrganizationConfiguration. Manually running both Get-Domain and Get-OrganizationConfiguration shows lots of info without any SBS server entries or it's IP... nathaniel Ars Praefectus Registered: Feb 10, 2002Posts: 3913 Posted: Tue Mar 16, 2010 10:15 am here is the event when I try and change the domain controller: -