I am getting this warning and errors from both nodes in the cluster about every 15 minutes: Event Type:WarningEvent Source:MSExchange ADAccessEvent Category:General Event ID:2601Date:11/29/2007Time:9:14:56 AMUser:N/AComputer:MAIL-01Description:Process MSEXCHANGEADTOPOLOGY (PID=1324). When initializing a remote procedure call (RPC) to the Microsoft Exchange Active Directory Topology service, Exchange could not retrieve the SID for account <WKGUID=DC1301662F547445B9C490A52961F8FC,CN=Microsoft Exchange,CN=Services,CN=Configuration,...> - Error code=8007077f. The Microsoft Exchange Active Directory Topology service will continue starting with limited permissions. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Event Type:ErrorEvent Source:MSExchange ADAccessEvent Category:General Event ID:2604Date:11/29/2007Time:9:14:56 AMUser:N/AComputer:MAIL-01Description:Process MSEXCHANGEADTOPOLOGY (PID=1324). When updating security for a remote procedure call (RPC) access for the Microsoft Exchange Active Directory Topology service, Exchange could not retrieve the security descriptor for Exchange server object PASDEX - Error code=8007077f. The Microsoft Exchange Active Directory Topology service will continue starting with limited permissions. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Event Type:ErrorEvent Source:MSExchange ADAccessEvent Category:General Event ID:2501Date:11/29/2007Time:9:14:56 AMUser:N/AComputer:MAIL-01Description:Process MSEXCHANGEADTOPOLOGY (PID=1324). The site monitor API was unable to verify the site name for this Exchange computer - Call=DsctxGetContext Error code=8007077f. Make sure that Exchange server is correctly registered on the DNS server. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Thanks, Steve

Although the messages do appear in both cluster node's event logs, verify that the COMPUTER field is in fact the same node on each log entry. If that computer is the Passive node, then it is just an erroneous message which the application of SP1 recently resolved in the environment I witnessed this behavior.

Hi, I am experiencing the exact same list of event log entries as the original poster, every 15 minutes too. However, this is on a single server, the only server on the network running Exchange. Exchange 2007 SP1 was clean installed on a new Windows Server 2003 x64 R2 SP2machine in a network with an existing Exchange 2003 SP2 server. I went through the transition documentation step-by-step and ultimately uninstalled Exchange 2003 from the old server and removed that server from the domain. We are experiencing very slow access to Public Folders from our Vista SP1, Outlook 2007 SP1 clients and I'm guessing that solving thisADAccess problem is the first step. We are also finding that the Information Store service doesn't start at system boot, the service manager reports error 0 as the reason. This is occuring even though changes have been made to the Exchange services' DependsOnService registry value as recommended by some KB articles. The Exchange server seems to have good network connectivity to the domain controllers. The server does use DHCP for obtaining an IP address and DNS settings but there is a reservation on the DHCP server to ensure the same address is issued every time. Any suggestions would be appreciated. Thanks,

I setup a test environment and started getting these errors when I created two sites under the sites and services for my server (they are on two different subnets). the errors when away after moving all the servers back under a single site. not sure if that is causing the errors but if you are going to try it, please post your results here.

Make sure you have KB948496 applied. This usually cures the issue. The Post-SP1 rollup implements some network scaleability features that cause some really strange connectivity errors, not just the Events 2601, 2604, 2501. KB948496 disables the chimney and a few other things in the HKLM\System\CurrentControlSet\Services\TCPIP\Parameters key (RSS & TCPA).Try it - Mikey likes it!!! :-)

Make sure you have KB948496 applied. This usually cures the issue. The Post-SP1 rollup implements some network scaleability features that cause some really strange connectivity errors, not just the Events 2601, 2604, 2501. KB948496 disables the chimney and a few other things in the HKLM\System\CurrentControlSet\Services\TCPIP\Parameters key (RSS & TCPA).Try it - Mikey likes it!!! :-)

I also am getting this exactbehaviour. like a previous poster it is on a clean install, will be installing the post SP1 rollups over this comming weekend hopefully that will resolve the issue however if somone sees anything in the meantime any assistance would be apreciated. Regards, John

I had a similar issue.I disolved my NIC teaming and problem immediately went away.I am currently looking at a new driver for my NIC and will re-try teaming to see if the problem re-occurs.

Ron Glaister wrote: Make sure you have KB948496 applied. This usually cures the issue. The Post-SP1 rollup implements some network scaleability features that cause some really strange connectivity errors, not just the Events 2601, 2604, 2501. KB948496 disables the chimney and a few other things in the HKLM\System\CurrentControlSet\Services\TCPIP\Parameters key (RSS & TCPA).Try it - Mikey likes it!!! :-) Update installed, and then disabling Receive Side Scaling worked for me. Thank you VERY much. I really didn't like unteaming as a "fix"

In my case this problem was caused by Exchange services starting up to fast (or network services starting up to slow). Solved it by: 1. ChangedExchange services to manual startup 2. Made a batch script with "net start" commands that would start allthe necessaryExchange Services (and a simple ping commandto delay the scripta bit) 3. Scheduled it via Scheduled Tasks to run at computer startup. The server also didn't always mount the databases (located on iSCSI which also had eventlog failures during startup) so my script also callsan additional Powershell script that mounts the databasesif they aren't already mounted. The scriptrepeats itself three times.

Steen, I have the same case as you with Databases on iSCSI and it is showing those 3 errors. Would you mind sharing your batch and powershell script with me? Thanks John sforcejr@yahoo.com

Hi John, Here you are: StartServices.bat StartServices.bat @echo off ping 10.11.12.13 net start "Microsoft Exchange Active Directory Topology Service"net start "Microsoft Exchange Anti-spam Update"net start "Microsoft Exchange EdgeSync"net start "Microsoft Exchange File Distribution"net start "Microsoft Exchange IMAP4"net start "Microsoft Exchange Information Store"net start "Microsoft Exchange Mail Submission"net start "Microsoft Exchange Mailbox Assistants"net start "Microsoft Exchange POP3"net start "Microsoft Exchange Replication Service"net start "Microsoft Exchange Search Indexer"net start "Microsoft Exchange Service Host"net start "Microsoft Exchange System Attendant"net start "Microsoft Exchange Transport"net start "Microsoft Exchange Transport Log Search"net start "Microsoft Search (Exchange)" ping 10.11.12.13 net start "Microsoft Exchange Active Directory Topology Service"net start "Microsoft Exchange Anti-spam Update"net start "Microsoft Exchange EdgeSync"net start "Microsoft Exchange File Distribution"net start "Microsoft Exchange IMAP4"net start "Microsoft Exchange Information Store"net start "Microsoft Exchange Mail Submission"net start "Microsoft Exchange Mailbox Assistants"net start "Microsoft Exchange POP3"net start "Microsoft Exchange Replication Service"net start "Microsoft Exchange Search Indexer"net start "Microsoft Exchange Service Host"net start "Microsoft Exchange System Attendant"net start "Microsoft Exchange Transport"net start "Microsoft Exchange Transport Log Search"net start "Microsoft Search (Exchange)" ping 10.11.12.13 net start "Microsoft Exchange Active Directory Topology Service"net start "Microsoft Exchange Anti-spam Update"net start "Microsoft Exchange EdgeSync"net start "Microsoft Exchange File Distribution"net start "Microsoft Exchange IMAP4"net start "Microsoft Exchange Information Store"net start "Microsoft Exchange Mail Submission"net start "Microsoft Exchange Mailbox Assistants"net start "Microsoft Exchange POP3"net start "Microsoft Exchange Replication Service"net start "Microsoft Exchange Search Indexer"net start "Microsoft Exchange Service Host"net start "Microsoft Exchange System Attendant"net start "Microsoft Exchange Transport"net start "Microsoft Exchange Transport Log Search"net start "Microsoft Search (Exchange)" Call MountStores.bat MountStores.bat MountStores.batC:\WINDOWS\system32\WindowsPowerShell\v1.0\PowerShell.exe -PSConsoleFile "C:\Program Files\Microsoft\Exchange Server\bin\exshell.psc1" -command ". 'C:\scripts\MountStores.ps1'" MountStores.ps1 MountStores.ps1 mount-database -Identity "MAIL1\MDB1" mount-database -Identity "MAIL1\Public Folders"

Steen, I am trying to understand why does the script repeat itself three time? do you mean retry to start the services 3 times? Thank you very much for sharing. I have been battling with the issue of the databases(in the iscsi not being mounted at startup). John

Hi John, Sorry it was a bit unclear - yes, it just tries to start the services three times with a simple delay(well -"ping"). Ping of a non-existing IP takes approx 4 seconds. You might use wait.exe (http://www.afreego.com/Categories/Utilities/Automation/006450.php) with a longer waitor add some more pings (ping -n parameter) and just start the services once. Use "Scheduled Tasks" in Control Paneland schedule StartServices.bat to run at computer startup. Steen

Hi guys,I believe this error is caused by a lack of communication with the DNS servers ensures that there is resolution "nslookup" Thank you for your attention.

I had a similar situation, and it would definitely involve DNS. Win 2008 DCs with IPv6 disabled, but the Exchange 2007 servers with the issue, also on Win 2008 had IPv6 enabled. Disabling IPv6 on the Exchange 2007 servers running on Win 2008, and restarting the MSExchange AD Topology service did the trick.

if you're running windows 2008 r2, the quick fix is set your MSExchangeADTopology to delayed start.JR

I changed out my Exchange 2003 server for a single 2010 server (on server 2008 R2), and began receiving those errors once I decommissioned the Exchange 2003 server. I disabled IPv6, and set the topology to delay start, and they still keep coming every 10 minutes or so. Running nslookup from the 2010 box resolves itself nicely. I've checked my NIC binding order, and the active NIC is at the top of the lists for binding. Other than those errors, all email flow seems to be working fine.

Hi, Has anyone found out why these errors occour? Have a single 2010 SP1 box [all roles] had a clean Application log, since a reboot last night I am getting these errors. Checked DNS - all ok, no issues connectivity or mail flow wise, ExBPA reports no show stoppers. Will try the Restart of the Microsoft Exchange Active Directory topology to correct. Fizzmo

We've done this here and it prevents this errors from occuring but some other strange behaviour comes up: The Services: Microsoft Exchange Service Host Microsoft Exchange Protected Service Host Microsoft Exchange RPC Client Access do not automatically start up. We can start them manually after reboot, but this is not the way it shoul work like. The system holds all the current fixes which are available and it is the same on all 4 nodes within this one HUB/CAS Unicast NLB-Array. Any ideas welcome! Best regards out of snowy Switzerland ... Stefan

Hi all just an update restarted the Microsoft Exchange Active Directory topology to correct.

I noticed that restarting the Active Directory topology service requires a restart of the following dependent services: Microsoft Exchange Transport Log Search Microsoft Exchange Transport Log Microsoft Exchange Service Host Microsoft Exchange Search Indexer Microsoft Exchange Replication Service Microsoft Exchange Mail Submission Microsoft Exchange Mailbox Assistants Microsoft Exchange File Distribution Microsoft Exchange EdgeSync Microsoft Exchange Anti-spam Update As I have a lot of users on this server: how will this impact them? I tested on a lab server & things seem OK, but I want to be 100% sure. (no users on the test server but me) Anyone tried this on a busy server, and what happened? Regards, Paul www.servercare.nl

I thought it would be driver issue for my NIC and I will try teaming to see if the problem still exist.Webmaster Forum | Webmaster Pride | Webmaster Forum

I thought it would be driver issue for my NIC and I will try teaming to see if the problem still exist. SEO Forum | SEO Company | Webmasters Forum

It seems to work fine for me too. +++++++++++++++++++++++++++ Exchange 2007 sp1

Disableing IPV6 solved the problem for me. 2k8 R2 exch 2k10. Additionally, I couldn't connect to the exchange server from clients. Once IPV6 was disabled, the MSEXCHANGEADTOPOLOGY and the clinet connectivity issues dissappeared. I'm going to set static IPV6 and test again but for the moment it is all working.

KB948496 REALLY SOLVES THIS ISSUES, INCLUDING THE UNSTARTED EXCHANGE SERVICE ISSUE AFTER REBOOT, SO THAT YOU HAVE TO START IT MANUALLY. OUR SYSTEM: WINDOWS SERVER 2003 R2 X64 with EXCHANGE 2007 SP3, ROLLUP 5