[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1406
  • Last Modified:

Exchange Transport service stops randomly HELP

Hi A few months ago we installed a new exchange 2010 server with our exchange 2007 server and they have been coexisting for the past few months with out an issue. Now the past 2 weeks at random times the exchange transport service on the 2010 server just stops and nothing we can do besides a total reboot to get the service to start again. In the error logs it says that it cant contact any of the domain controllers! I can still get online and ping the domain controllers so its not network related i don't think. I have tried a different nic, different switch port. I also made a new store data base in cause there was just too many users in the main store we have.

Out current configure on exchange 2010
980 users
4 database stores
96gb of ram
24 logical procs x64bit
5 tb of available disk space for exchange

I get this error befor it starts to get bad. Event id 2102
Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=1924). All Domain Controller Servers in use are not responding:
Filesvr1.uhca1.local
Filesvr.uhca1.local


any ideas on what else i can check?
0
nshutters
Asked:
nshutters
  • 14
  • 11
1 Solution
 
JBaltaCommented:
Check whether the Exchange Enterprise Servers security group have "Manage auditing and security logs"  permissions on the domain controller.

http://www.eventid.net/display.asp?eventid=2102&eventno=1362&source=MSExchangeDSAccess&phase=1
0
 
AmitIT ArchitectCommented:
Run EXBPA, whenever you have this issue. It might show up the results. Secondly, check below article.

http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Exchange&ProdVer=8.0&EvtID=2102&EvtSrc=MSExchange+ADAccess&LCID=1033
0
 
nshuttersAuthor Commented:
ok so i read the links posted and when the issue happened again i tried to run the EXBPA and it cant contact any domain controllers even if you specify them! finally had to reboot the server and all is back to normal for now. The server does not loose network connectivie when this happens. Just seems like RPC calls are just not working, you would think that it would be on the mail server as a reboot fixes it and the domain controllers dont get a reboot to fix the issue. Any other ideas or other areas i could look into?
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
AmitIT ArchitectCommented:
Can you check the system logs and do you see any error related to Remote Registy service?

Recently, i have seen same issue, after restart remote registry service, everything was back to normal.
0
 
nshuttersAuthor Commented:
i checked didnt see any remote registry service entries just alot of msactive directory access events saying they can contact the domain controllers. i checked back to the last time we had an issue and still nothing on the remote registry.
0
 
AmitIT ArchitectCommented:
After how long, do you see this issue?
0
 
nshuttersAuthor Commented:
id have to saw every few days it happens. It happened friday afternoon and so far hasn't happened yet but i have a feeling that tomorrow morning it will do it again as its been a few trouble free days. at first ill see errors with the ad access then the transport service just stops and it wont restart.
0
 
AmitIT ArchitectCommented:
Can you check below article
http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Exchange&ProdVer=8.0&EvtID=2102&EvtSrc=MSExchange+ADAccess&LCID=1033

And verify it, when you see this issue again. If possible restart the remote registry service before rebooting the server
0
 
nshuttersAuthor Commented:
Ok did a dcdiag on both dc's. The first dc i tested no errors at all. the second one i got 4 errors and they all had the same result.

FrsEvent
DfrsEvent
KccEvent
Systemlog

all returned "The RPC server is unavailable" but if i test the other domain controler from the other i get no errors at all.
0
 
AmitIT ArchitectCommented:
Type "Set l" without quotes at the cmd prompt and see, to what DC is it authenticating
0
 
nshuttersAuthor Commented:
let me clarify this! i ran dcdiag from the mail server and got those errors, then if i do them on a domain controller to another domain controller i get no errors.
0
 
nshuttersAuthor Commented:
so "dcdiag /s:filesvr1 Set I"

tells me invalid synatx
0
 
AmitIT ArchitectCommented:
You need to run just set l

c:\set l

this will tell you againt which DC you are currently logged on
0
 
nshuttersAuthor Commented:
ok gotcha!

its set to our dc filesvr which i get no errors from when i do the dcdiag
the other dc filesvr1 gets errors which i stated above.
0
 
AmitIT ArchitectCommented:
goto the dc and run

repadmin /replsum

and see if any replication errors are generating.
0
 
nshuttersAuthor Commented:
ok got no failures on both source and destination and 5 total tries and 0 failures.
0
 
nshuttersAuthor Commented:
any thing else to check?
0
 
AmitIT ArchitectCommented:
0
 
nshuttersAuthor Commented:
Well it happened again this morning around 3:30am. i started getting error id 2070

Then 2014
Process MAD.EXE (PID=7004). Topology discovery failed due to LDAP_SERVER_DOWN error. This event can occur if one or more domain controllers in local or all domains become unreachable because of network problems. Use the Ping or PathPing command line tools to test network connectivity to local domain controllers. Run the Dcdiag command line tool to test domain controller health.

Then 2121
Process MAD.EXE (PID=7004). Exchange Active Directory Provider is unable to connect to any domain controller in domain uhca1.local although DNS was successfully queried for the service location (SRV) resource record used to locate a domain controller for that domain.
 The query was for the SRV record for _ldap._tcp.dc._msdcs.uhca1.local
 The following domain controllers were identified by the query:
filesvr.uhca1.local
filesvr1.uhca1.local

 Common causes of this error include:
 - Host (A) records that map the name of the domain controller to its IP addresses are missing or contain incorrect addresses.
 - Domain controllers registered in DNS are not connected to the network or are not running.
 For information about correcting this problem, Type in the command line:
hh tcpip.chm::/sag_DNS_tro_dcLocator_messageHa.htm        

and then all mail stopped working again till reboot. I restarted the remote registry but that didnt change anything i was going to stop and restart the rpc service but it wouldn't let me. The domain controllers had no errors during this time.
0
 
AmitIT ArchitectCommented:
Do you have any NIC teaming, with multiple subnets?
0
 
nshuttersAuthor Commented:
the server has two nics but one is disabled. we do have multiple subnets but all servers are on the same subnet 10.10.0.x
0
 
AmitIT ArchitectCommented:
Can you check this KB
http://support.microsoft.com/kb/895858

and check if any event 2080 is showing in the logs.
0
 
AmitIT ArchitectCommented:
0
 
nshuttersAuthor Commented:
sorry for the delay. i have tons of 2080 errors all when this happens. i have checked dns settings all are good and i can ping dns when this issue happens. We went for 6 days with out an issue then the past 2 days every morning the system has to be rebooted.
0
 
nshuttersAuthor Commented:
The only way we have gotten around this is to setup a sechudal to reboot every 12 hours. its a pain but keeps the mail flowing.
0
 
nshuttersAuthor Commented:
nobody knows the answer
0

Featured Post

Prepare for your VMware VCP6-DCV exam.

Josh Coen and Jason Langer have prepared the latest edition of VCP study guide. Both authors have been working in the IT field for more than a decade, and both hold VMware certifications. This 163-page guide covers all 10 of the exam blueprint sections.

  • 14
  • 11
Tackle projects and never again get stuck behind a technical roadblock.
Join Now