An Active Directory Error 0x51 Exchange 2010
Contents |
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Asked by: Active Directory Error 0x51 occurred when trying to active directory error 0x51 occurred exchange check the suitability of server '
The Ldap Server Is Unavailable Exchange 2010
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 using Get-OwaVirtualDirectory with -DomainController
Error 0x51 Microsoft Exchange administrators get hung up some times when they encounter sudden Exchange
An Active Directory Error 0x52 Occurred When Trying To Check Server
Errors. Recently we ran into a similar problem that drove us nuts. We had just recently demoted one of our old domain controllers. 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 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 would be locked up and mostly a restart would make the 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 http://email-converter-tools.blogspot.com/2013/02/a-permanent-resolve-for-microsoft.html 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 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 loca
Case and Cooling Fetish CPU & Motherboard Technologia Mobile Computing Outpost Networking Matrix Other Hardware Agora Classifieds http://arstechnica.com/civis/viewtopic.php?t=39342 Ars DIY Forum (Name TBD!) Operating Systems & Software Battlefront Microsoft OS & 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 The Boardroom The Observatory active directory 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 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 active directory error 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 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 dynamical