<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Problem Starting the Exchange 2003 System Attendant</title>
	<atom:link href="http://www.beakersoft.co.uk/2007/06/18/problem-starting-the-exchange-2003-system-attendant/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.beakersoft.co.uk/2007/06/18/problem-starting-the-exchange-2003-system-attendant/</link>
	<description>My (mis)adventures in the IT industry</description>
	<lastBuildDate>Tue, 07 Feb 2012 22:18:59 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Ben</title>
		<link>http://www.beakersoft.co.uk/2007/06/18/problem-starting-the-exchange-2003-system-attendant/comment-page-1/#comment-75616</link>
		<dc:creator>Ben</dc:creator>
		<pubDate>Fri, 22 Jul 2011 02:03:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.beakersoft.co.uk/2007/06/18/problem-starting-the-exchange-2003-system-attendant/#comment-75616</guid>
		<description>Thankyou very much for posting this tip. After spending a couple of hours trying to troubleshoot an issue with Exchange services on an SBS 2003 server, this gave us the pointer we needed.

We ran mad.exe manually and discovered a corrupt .dll that was causing it to fail, though it was a different .dll than yours. And the problem had existed for some time (over a month) judging by the modified dates on the dll - the issue didn&#039;t rear it&#039;s ugly head until the server was rebooted.

Cheers for giving us the hint that saved our bacon :)</description>
		<content:encoded><![CDATA[<p>Thankyou very much for posting this tip. After spending a couple of hours trying to troubleshoot an issue with Exchange services on an SBS 2003 server, this gave us the pointer we needed.</p>
<p>We ran mad.exe manually and discovered a corrupt .dll that was causing it to fail, though it was a different .dll than yours. And the problem had existed for some time (over a month) judging by the modified dates on the dll &#8211; the issue didn&#8217;t rear it&#8217;s ugly head until the server was rebooted.</p>
<p>Cheers for giving us the hint that saved our bacon <img src='http://www.beakersoft.co.uk/wordpress/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>

