Download file kb2938053

Step number 5 most likely broke Exchange Toolbox and created this error when opening Exchange Management Shell for us:. Please test it yourself and let me know whether the problem was somehow only related to our environment.

And if not, please update your installation instructions and close this bug report. From: Stefan Profanter [ mailto: notifications github. I updated the install instructions according your suggestions. Skip to content. Star New issue. Jump to bottom. Exchange Toolbox snap fails to start after installing yestarday latest 3. Labels bug enhancement gui. Copy link. Here are the steps:. Follow the link: KB - Third-party transport agents cannot be loaded correctly in Exchange Server IMF Tune v8.

Latest Releases V8. The tests were run against the latest IMF Tune build to date, build 6. Fixing the Installation Apply the KB fix. We raised a fault with Microsoft and they were really helpful in fixing the issue - it hasn't crashed for around 5 days now. This is what we done all of this was carried out in live production during the day, and there was very little effect on the running of our business :. Microsoft also discussed best practices for receive connectors on Exchange Check your Organization Transport Settings; check the limits aren't set to unlimited - this can cause transport issues, e.

Having said all of the above, it is quite possible that the mail queue could have become corrupted from all the stopping and starting of the transport service. But the new queue database creation seems to have stabilised our transport service. Receive Connectors. Did you Monitor the queue all the times. Is it something like mails stuck in the queue and get flushed away when you restart the transport service? We are now having issues with Proxy Probe emails generating every 5 minutes going into our Quarantined items, but I'm going to start another post.

We also get the same error even after running the fix, along with occasionally high version buckets which disabled many of the transport services currently once a week. Restarting the transport service "frees up" everything again.

Only started getting this with Exchange SP1. I too am getting the same events constantly logged on exchange sp1 on r2. Z Description: A forced configuration update for Microsoft. RemoteDomainTable has successfully completed. TransportSettingsConfiguration has successfully completed. FrontendTransportServer has successfully completed. AcceptedDomainTable has successfully completed. XAuthoritativeDomainTable has successfully completed. ReceiveConnectorConfiguration has successfully completed.

MailboxTransportServer has successfully completed. We are still getting issues where our transport service needs to be restarted to let the queues go down again - so must be issue with SP1. Every 3 minutes we get a row of entries with event ID They consist of 4 blocks where each block has the same source.

The details show the same names except for the "Microsoft. No problem with the transport service so far, but Exchange should not be filling up the logs with this. ReceiveConnectorConfiguration Microsoft. TransportServerConfiguration Microsoft. AcceptedDomainTable Microsoft. XAuthoritativeDomainTable Microsoft. TransportSettingsConfiguration Microsoft. RemoteDomainTable Microsoft. MailboxTransportServer Microsoft. FrontendTransportServer Microsoft.

Another problem it causes for us is emails getting stuck in outboxes, until you attempt to send them again. This is happening for a few users All Outlook I am guessing this is due to the Transport service changing its state just at the time they are trying to send the email out. CU5 is incoming soon but I really wonder whether this will rectify the problem. I may try raising a support ticket but have a feeling it may be like going to the dentist A batch of multiple events every few minutes.

And then after a day or so, email just stops flowing until I restart the Transport Service. Trying to restart the Transport Service with Administrative Tools Services times out and fails, so I have to find it in the Task Manager and manually kill it and start it up again.

Apparently the Transport Service decides it only wants to talk to itself. Only one Exchange Server and no third party add-ons.

With all the latest patches from Windows Update installed. I just installed that Code2 fix from KB This does not fix the problem. To avoid these steps, make sure that you apply the "Fix it" solution to any server that is running Exchange Server SP1 immediately after the installation. Then, you can install any third-party agents. Need more help? Expand your skills. Get new features first. Was this information helpful?

Yes No. Thank you! Any more feedback?