Mike LaForest
asked on
Exchange 2007 Transport Service Stops
Hello,
We recently demoted an old DC running Server 2003 to raise our Forest & Domain Functional Level to 2008 R2. We had added a 2008 R2 domain controller and tested running with that before demoting the old server without any issues with the domain or our Exchange 2007 server. But since demoting the 2003 server and raising the functional levels on the domain we've had issues with the Exchange 2007 machine (Server 2008 not R2) and the Transport service stopping. We now only have the one DC, the Server 2008 R2 machine.
The first error that happens:
Source: MSExchangeADAccess
EventID: 2102
Process MAD.EXE (PID=3972). All Domain Controller Servers in use are not responding: <ourdc>.<domain>.local
That error happens a few times before this error, where the transport service stops:
Source: MSExchangeTransport
EventID: 12009
Microsoft Exchange couldn't read the Receive connector configuration because the directory is unavailable. The service will be stopped.
All the microsoft articles say to make sure the exchange server can communicate with the DC. There should be nothing preventing them from communicating. The one Microsoft artilce says to make sure that the exchange server is in the policy to "Manage auditing and security logs", which it already is in there. Running DCDIAG it fails in 2 spots, NCSecDesc which from what I read there should be nothing to worry about. And the other spot DCDIAG fails is Services. One article I found said to start the RPC Locator service on the DC, but that didn't seem to resolve the error from DCDIAG. Any help on the issues would be greatly appreciated.
We recently demoted an old DC running Server 2003 to raise our Forest & Domain Functional Level to 2008 R2. We had added a 2008 R2 domain controller and tested running with that before demoting the old server without any issues with the domain or our Exchange 2007 server. But since demoting the 2003 server and raising the functional levels on the domain we've had issues with the Exchange 2007 machine (Server 2008 not R2) and the Transport service stopping. We now only have the one DC, the Server 2008 R2 machine.
The first error that happens:
Source: MSExchangeADAccess
EventID: 2102
Process MAD.EXE (PID=3972). All Domain Controller Servers in use are not responding: <ourdc>.<domain>.local
That error happens a few times before this error, where the transport service stops:
Source: MSExchangeTransport
EventID: 12009
Microsoft Exchange couldn't read the Receive connector configuration because the directory is unavailable. The service will be stopped.
All the microsoft articles say to make sure the exchange server can communicate with the DC. There should be nothing preventing them from communicating. The one Microsoft artilce says to make sure that the exchange server is in the policy to "Manage auditing and security logs", which it already is in there. Running DCDIAG it fails in 2 spots, NCSecDesc which from what I read there should be nothing to worry about. And the other spot DCDIAG fails is Services. One article I found said to start the RPC Locator service on the DC, but that didn't seem to resolve the error from DCDIAG. Any help on the issues would be greatly appreciated.
ASKER
We've rebooted the DC & Exchange since demoting the old DC & upgrading the functional levels. But, I got the SERVICES error from DCDIAG to clear up by enabling the w32time service to start automatically on our DC. The only other error that shows up in DCDIAG from the exchange server now is system log error, which only lists printer errors from terminal services & and the same NCSecDesc error. Also, there is no NETDiag on Server 2008, which is what the Exchange 2007 is installed on...
ASKER
http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Exchange&ProdVer=8.0&EvtID=2102&EvtSrc=MSExchange+ADAccess
Had already seen this article. As per the suggestions in the article...Ping and pathping both work without issues. Running DCDIAG only says the NCSecDesc & System log fails, which to my understanding neither of those will negatively affect it. Also, the last suggestion on this article, "Manage Auditing and Security Log" is already allowed by the Exchange servers, so it's not that.
http://messaging2day.blogspot.in/search/label/Exchange%20HUB
As for this article, we're not getting any EventID:5023 errors. I went through the steps anyway, I don't believe it applies in this situation.
DNS was running on our the recently demoted 2003 DC, although we had pointed DNS on all our servers to our new DC. But I went ahead and removed the DNS role from the old DC & since rebooted the new DC. The transport hasn't stopped yet today. It seems to do it at least once a day & the only way to seem to get the transport service back up and running in a timely manner is to reboot the server.
Had already seen this article. As per the suggestions in the article...Ping and pathping both work without issues. Running DCDIAG only says the NCSecDesc & System log fails, which to my understanding neither of those will negatively affect it. Also, the last suggestion on this article, "Manage Auditing and Security Log" is already allowed by the Exchange servers, so it's not that.
http://messaging2day.blogspot.in/search/label/Exchange%20HUB
As for this article, we're not getting any EventID:5023 errors. I went through the steps anyway, I don't believe it applies in this situation.
DNS was running on our the recently demoted 2003 DC, although we had pointed DNS on all our servers to our new DC. But I went ahead and removed the DNS role from the old DC & since rebooted the new DC. The transport hasn't stopped yet today. It seems to do it at least once a day & the only way to seem to get the transport service back up and running in a timely manner is to reboot the server.
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
This seemed to clear up after removing DNS from the old DC & rebooting the new DC.
then you can do DCDIAG and NETDiag