Active Directory Error 0x51
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 active directory error 0x51 occurred exchange to check the suitability of server '
Exchange 2013 Active Directory Error 0x51
The LDAP server is unavailable'. It was running the command 'Get-OwaVirtualDirectory'. Previous Versions of Exchange > Exchange
Exchange 2010 Active Directory Fehler 0x51
Server 2010 Question 1 Sign in to vote This issue is driving us nuts - there are no issues with Domain Controllers or AD in this environment. The server
An Active Directory Domain Could Not Be Contacted
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 Outlook Web App either with authentication failed errors - and I can't help but expect these 2 issues are an active directory domain controller cannot be contacted 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 using Get-OwaVirtualDirectory with -DomainController
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 us nuts. We had just recently demoted one of active directory error 0x51 occurred when trying to check server our old domain controllers. For a few days everything worked fine. But, just recently our active directory error 0x8000ffff Exchange Server 2010 started throwing up error 0x51 while pointing to the demoted domain controller. The whole database would be locked an active directory error 0x51 exchange 2007 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. 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 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 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 http://email-converter-tools.blogspot.com/2013/02/a-permanent-resolve-for-microsoft.html 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 be downloaded from the website and shows a clear preview of the Exchange Mailbox items even in the demo version. You can chose to select which items you need to recover. We downloaded the free trial version and checked the preview. It had all the data we wanted to recover. We activated the software a
Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time https://www.experts-exchange.com/questions/27726429/Exchange-2010-Active-Directory-error-0x51-LDAP.html Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > Exchange 2010 - 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,285 Views Last active directory Modified: 2014-04-14 Hi all. We've got two domain controllers. The second is a new one. First DC ist Windows 2008 Standard, 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 active directory error 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 Active Directory 7 Exchange 4 Message Active 7 days ago Expert Comment by:Kini Pradeep2012-05-22 couple of things first. once you install the windows 2008 r2 DC, it is advisable to move the FSMO roles from 2008 to R2. Is the 2008 R2 DC also a Global catalog server ? In the Exchange console do you see the DC (2008 r2) Listed ? 0 Message Author Comment by:Opusretis2012-05-22 The new one is a global Catalog server. I did not move the FSMO roles to the new one yet. Yes t