EdgeSync Service Terminates Unexpectedly and unable to restart
I am currently trying to deploy Exchange 2010 Enterprise, at this point I am attempting to activate EdgeSync between my edge server inside my dmz and my hub transport server located inside the network. I issue the command successfully via EMS to produce a Edge Subscript XML File from the Edge Transport Server. Which I then successfully import via EMC (although I have tried EMS as a possible solution) on the HT server. Immediately after the import my edgesync service on the HT server begins to terminate and restart. The service continues this terminate restart non stop, and it is important to point out that the service never starts succesfully. In addition I cannot forceably stop the service and restart it manually as it fails to start. Synchronization never occurs from the moment EMC [or EMS] reports that the subscription file was successfully imported. Once I delete the edge Subscription (where there is no longer any subscriptions) this process stops and the EdgeSync runs continously without any issue. I have two Edge Transport Servers and two HT servers in my environment (it is important to note that the HT role is co-located with the CAS role which is clustered in a CAS array), my edge servers each contain only the edge role. I have noted that this has to be an environment issue as it occurs on both servers. The event logs receive are provided below. If anyone could offer a solution or help out I would greatly appreciate this. System Log: The Microsoft Exchange EdgeSync Service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 5000 milliseconds. Restart the service. Application Log: Watson report about to be sent for process id: 4624, with parameters: E12, c-RTL-AMD64, 14.00.0702.000, M.Exchange.EdgeSyncSvc, M.E.Data.Directory, M.E.D.D.ADValueConvertor.GetValueFromDirectoryAttributeValues, System.ArgumentException, de7b, 14.00.0702.000. ErrorReportingEnabled: False
July 29th, 2011 5:26pm

Hi, Can you post the entire event from Application and System Log. What is the service pack level you are running. Cause Could Be: Because the edge of the network card is specified on the external DNS SERVER, DNS SERVER internal HUB SERVER can not resolve the FQDN. Gulab | MCITP: Exchange 2010-2007 | Skype: Gulab.Mallah | Blog: www.ExchangeRanger.Blogspot.com
Free Windows Admin Tool Kit Click here and download it now
July 30th, 2011 12:42am

Thanks for the response. We utilize an internal DNS name which differs from our external (which the edge server uses as it's suffix) however I have created a primary zone on the internal DNS servers which matches the external dns zone (split horizon) and have placed the edge servers fqdn in the internal zone as A records. I can look up the servers address via nslookup internally, succesfully. In addition I have modified the host file for both edge servers to connect to the hub servers via smtp.
July 30th, 2011 4:51pm

Do you have any AV installed on your HUB servers? Disable it ot even better uninstall it to make sure it doesnt interfere. You must also make sure it has proper exclusions. http://technet.microsoft.com/en-us/library/bb332342.aspx lasse at humandata dot se, http://anewmessagehasarrived.blogspot.com
Free Windows Admin Tool Kit Click here and download it now
July 30th, 2011 5:32pm

I haven't installed the Anti-Virus client as of yet on any of these servers
July 30th, 2011 5:33pm

Can Edge servers resolv HUB servrs correct in DNS ? Can HUb communicate with Edge to port 50636 and 25? have you run EXBPA both on HUB and on Edge, does it give any clues?lasse at humandata dot se, http://anewmessagehasarrived.blogspot.com
Free Windows Admin Tool Kit Click here and download it now
July 30th, 2011 5:58pm

What if you try to run: Test-EdgeSynchronization What result do you get? http://technet.microsoft.com/en-us/library/aa996925.aspx Jonas Andersson | Microsoft Community Contributor Award 2011 | MCITP: EMA 2007/2010 | Blog: http://www.testlabs.se/blog | Follow me on twitter: jonand82
August 1st, 2011 8:04am

I receive Inconclusive for SyncStatus.
Free Windows Admin Tool Kit Click here and download it now
August 1st, 2011 10:31am

The Edge Servers can resolve the Hub servers via their host files. The hub servers can communicate with the edge servers via ports 50636 and 25
August 1st, 2011 10:43am

Hi CrashOver2000, Please install latest service pack and rollup for Exchange 2010 first if you didn't do. Please create a new certificate for Edge servers and delete the old one then try to subscribe Edgesync again. New-ExchangeCertificate http://technet.microsoft.com/en-us/library/aa998327.aspx Frank Wang
Free Windows Admin Tool Kit Click here and download it now
August 1st, 2011 11:44pm

Hi CrashOver2000, Any updates?
August 3rd, 2011 10:01pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics