Home > Event Id > Event Id 2138 Exchange

Event Id 2138 Exchange

Can anyone shed any light on this for me and would it be best I give MS support a call. Restart the Microsoft Exchange Active Directory Topology service. The cache or hash table ran out of memory. ReplyDeleteClint BoessenOctober 2, 2012 at 6:28 PMHi Nikolia,Windows Vista upwards has changes to the network stack. Check This Out

The New Topology couldn't be generated. Ping using both the DNS name and the IP address. I'm still understanding and learning how about Exchange 2010 works and how it can be administrater properly. Post Navigation ← Previous Post Next Post → Search for: Posts So what's the most annoying thing Dec 21, 2016 So what happens when SHA1 falls out of Dec 21, 2016 http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Exchange&ProdVer=8.0&EvtID=2138&EvtSrc=MSExchange+ADAccess

An asynchronous LDAP call failed. Provisioning layer initialization failed: 'Failed to reconnect to Active Directory server DC01.abc.com. Collect: MSExchange ADAccess Domain Controllers: LDAP long running operations/Min. Exchange Active Directory Provider received a request to connection to domain controller but that domain controller is not available.

  1. Couldn't discover the Active Directory topology in a timely manner.
  2. The mail server is getting the same errors as you've posted.X2010 is running on a HP G5 Dual Xeon with 16GB memoey and over 1TB raid5 storage.
  3. The top advice via google appears to be to raise the logging level or use ADSIEdit, however neither options appear to be helping me.

The Active Directory provider maintains a pool of connections to the available domain controllers. In the absence of other events, this event shouldn't impact mail flow. Keeping an eye on these servers is a tedious, time-consuming process. LDAP notify call failed.

What are the benefits of an oral exam? The domain controller isn't available. This is the 3rd time it has happened over about 5 weeks, all on different days of the week. find more I have found the Configuration one and can see the dead servers thanks. –Phil Hannent Oct 13 '10 at 8:57 add a comment| Your Answer draft saved draft discarded Sign

Enter the product name, event source, and event ID. Do one or more of the following: Review the Application log for MSExchangeADAccess Event ID 2150. read more... New computers are added to the network with the understanding that they will be taken care of by the admins.

For More Information If you are not already doing so, consider running the Exchange tools, which have been created to help you analyze and troubleshoot your Exchange environment. http://www.eventid.net/display-eventid-2138-source-MSExchange%20ADAccess-eventno-9259-phase-1.htm The object was removed from the result set. The Exchange Active Directory Provider couldn't read an attribute from the root DSE of the Active Directory server. Newer Post Older Post Home Subscribe to: Post Comments (Atom) Clint Boessen [MVP] [email protected] Clint Boessen's Blog Clint Boessen Perth, Western Australia, Australia Microsoft Infrastructure Engineer MVP, MCSE, MCSA, MCTS, MCP

Will check the nic drivers.   Just read through the whole thread about the sorta same issue.   http://community.spiceworks.com/topic/134941-exchange-2010-ad-topology-failures-all-domain-controllers-unavailable?page=4

The hot fix only applies to 2003 though from what I can his comment is here A request to establish a connection between the Exchange Active Directory Provider and a domain controller failed. Topology discovery failed, error 0x80040952 (LDAP_LOCAL_ERROR (Client-side internal error or bad LDAP message)). An SRV record may be configured incorrectly in DNS.

Matt.ReplyDeleteAnonymousMay 22, 2015 at 7:52 AMHi all , just want to share that after i patched below hotfixes for win2008r2 sp1 ... I'm not a big fan of tweaking my TCP stack frequently. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. http://supportcanonprinter.com/event-id/event-id-8331-exchange.html This could result from internal Epoxy (ExIPC) failures or the system may be running out of memory.

Drives are at risk of running out of free space. To learn more about these tools, see Managing Tools in the Toolbox.   Show: Inherited Protected Print Export (0) Print Export (0) Share IN THIS ARTICLE Is this page helpful? Restart the Active Directory Topology service.

Run the Dcdiag command line tool to test domain controller health.

The warnings are all about servers that are offline (SERVER01 in this instance). 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. Exchange Active Directory Provider will attempt to reconnect with this domain controller when it is reachable. more hot questions question feed about us tour help blog chat data legal privacy policy work here advertising info mobile contact us feedback Technology Life / Arts Culture / Recreation Science

LDAP Search Timeouts - sustained for 5 minutes - Yellow(>10) LDAP Search Time - sustained for 5 minutes - Red(>100msec) The Exchange Active Directory Provider couldn't bind to Active Directory. Reenabling ipv6 (even unconfigured) then a quick reboot, cleared it right up for me. Compiling multiple LaTeX files Why do CDs and DVDs fill up from the centre outwards? http://supportcanonprinter.com/event-id/event-id-8197-exchange.html 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.

Posted by #[[email protected]]# at 7:44 PM Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest Labels: Exchange 2010, Setup, Windows Server 2008 R2 3 comments: Windows AuditingMar 30, 2012, 12:24:00 AMHello all,Exchange From the Support Center, you can also search the Microsoft Product Support Knowledge Base and contact Microsoft Product Support Services. Make sure the server is available, and that you have used the correct credentials.' Failed to reconnect to Active Directory server DC01.abc.com. The configuration domain controller specified in a call to SetConfigDCName is unreachable.

The Exchange Active Directory Provider couldn't find an available domain controller in the domain. LDAP Search Time - sustained for 5 minutes - Yellow(>50msec) Site monitor failed to update the msExchServerSite attribute in AD. If the product or version you are looking for is not listed, you can use this search box to search TechNet, the Microsoft Knowledge Base, and TechNet Blogs for more information. This was after trying every other fix you've probably already found in your searches. 0 Anaheim OP SamuelWib Nov 27, 2011 at 5:19 UTC ipv6 is enabled on

Did the page load quickly? The content you requested has been removed. Use Dcdiag to check domain controller and DNS health. Make sure that the local site has enough global catalog servers for Exchange.