<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Exchange 2007 HUB Transport service will not start</title><link>http://blogs.technet.com/sfodel/archive/2008/07/10/exchange-2007-hub-transport-service-will-not-start.aspx</link><description>We are seeing lots of this issue today after customers install security updates. You may also see these events in your applicatiopn log: Event ID : 7009 Type : Error Message : Timeout (30000 milliseconds) waiting for the Microsoft Exchange Transport service</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Exchange 2007 HUB Transport service will not start</title><link>http://blogs.technet.com/sfodel/archive/2008/07/10/exchange-2007-hub-transport-service-will-not-start.aspx#3087823</link><pubDate>Sat, 12 Jul 2008 15:11:55 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3087823</guid><dc:creator>Woodzter</dc:creator><description>&lt;p&gt;I've had a nightmare time with this problem the last two days. I have googled the issue to find hardly any info. I came across the post and followed the instruction of give the LOCAL SYSTEM account the log on as right.&lt;/p&gt;
&lt;p&gt;I will be keeping tabs on this post to see what other users come up with and to also see what the Transport service accoutn should be eventually set to.&lt;/p&gt;
</description></item><item><title>re: Exchange 2007 HUB Transport service will not start</title><link>http://blogs.technet.com/sfodel/archive/2008/07/10/exchange-2007-hub-transport-service-will-not-start.aspx#3090752</link><pubDate>Fri, 18 Jul 2008 16:00:40 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3090752</guid><dc:creator>stukes501</dc:creator><description>&lt;p&gt;For me at least, this was a managed code issue (Discussed in the team blog linked above). &amp;nbsp;My exchange servers do not have internet access (as I imagine is the case for thousands of installs). &amp;nbsp;Quickest fix is to set up your hosts file to point at localhost for the crl servers. &amp;nbsp;(set crl.microsoft.com, crl1 – crl5.microsoft.com to 127.0.0.1 in your HOSTS file).&lt;/p&gt;
</description></item><item><title>re: Exchange 2007 HUB Transport service will not start</title><link>http://blogs.technet.com/sfodel/archive/2008/07/10/exchange-2007-hub-transport-service-will-not-start.aspx#3269075</link><pubDate>Wed, 29 Jul 2009 17:00:20 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3269075</guid><dc:creator>yusufahmad</dc:creator><description>&lt;p&gt;Any suggestions on the following error:&lt;/p&gt;
&lt;p&gt;Event ID: 4999&lt;/p&gt;
&lt;p&gt;Watson report about to be sent to dw20.exe for process id: 3992, with parameters: E12, c-RTL-AMD64, 08.01.0375.002, edgetransport, M.E.Transport, M.E.T.C.RoutingTables.CalculateE12ServerRoutes, System.ArgumentException, cb00, 08.01.0375.002&lt;/p&gt;
</description></item></channel></rss>