I'm running Exchange Server 2013 on Windows Server 2012 R2, and I'm getting this error event every time I start the server: ID 1032, source MSExchangeDiagnostics, text "The EDS Job manager failed to start the following jobs: Job: 'TransportSyncHealthHubLog' is poisoned."  I have not noticed any problems with the Exchange Server's operation, but the text of this event sounds ominous.  I haven't been able to find anything helpful about it online, so I figured I'd throw it up here and see if anyone has any insight into it.  Thanks in advance if you do.

Hi DBVW ,

Thank you for your question.

Did you  post Event id details to ibsexc@microsoft.com for our troubleshooting. Because this error appear by various factors.

Whats CU of Exchange 2013? By my research, we could update Exchange 2013 to CU5 or higher to check if the issue persist.

In addition, we could changing the TransportSyncHubHealthLogEnabled and TransportSyncHubHealthLogFilePath attributes in the Set-TransportService cmdlet to check if issue persist by the following link:

http://technet.microsoft.com/en-us/library/jj215682(v=exchg.150).aspx

We could check the path of drive:\TransportRole\Logs\SyncHealth\Hub if it is available(include drive).

If there are any questions regarding this issue, please be free to let me know. 

Best Regard,

Jim

Hi DBVW ,

Thank you for your question.

Did you  post Event id details to ibsexc@microsoft.com for our troubleshooting. Because this error was occurred by various factors.

Whats CU of Exchange 2013? By my research, we could update Exchange 2013 to CU5 or higher to check if the issue persist.

In addition, we could change the TransportSyncHubHealthLogEnabled and TransportSyncHubHealthLogFilePath attributes in the Set-TransportService cmdlet to check if issue persist by the following link:

http://technet.microsoft.com/en-us/library/jj215682(v=exchg.150).aspx

We could check the path of drive:\TransportRole\Logs\SyncHealth\Hub if it is available(include drive).

If there are any questions regarding this issue, please be free to let me know. 

Best Regard,

Thanks for your reply, Jim.  I can't email the event details right now because the event only occurs on system start, and now the events from last week have been automatically deleted to make room for new events.  (Exchange 2013 seems to be very verbose.)  This installation of Exchange 2013 is at SP1, so it does not yet have CU5.  I'm reluctant to apply any updates right now since the server is performing well and I don't want anything to change that.  (I'm just going through the event logs to check for signs of trouble.)  I looked at the Set-TransportService link in your reply, but I couldn't see how to change those two attributes, or what I should change them to--would you provide more details please?  Finally, I think I found the path you asked about: C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\Logs\SyncHealth.  However, there is no Hub subdirectory in the SyncHealth directory.

Thanks again for your help.

Hi DBVW,

By my research, this error was occurred by mistake configuration on Exchange server. which include all configuration on Exchange server. if we did not find anything, we could ignore it temporarily. If there are not any issue or continuously occurred, you could post issue with this Event log to our forum, we will give a better solution for you.

If there are any questions regarding this issue, please be free to let me know. 

Best Regard,

Jim

Thanks Jim--I will add it to my "safe to ignore" list.