 




<?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: Troubleshoot Task Microsoft Exchange Server reported error</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/itanswers/troubleshoot-task-microsoft-exchange-server-reported-error/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/itanswers/troubleshoot-task-microsoft-exchange-server-reported-error/</link>
	<description></description>
	<lastBuildDate>Sat, 18 May 2013 17:13:23 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: stevesz</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/troubleshoot-task-microsoft-exchange-server-reported-error/#comment-58158</link>
		<dc:creator>stevesz</dc:creator>
		<pubDate>Thu, 27 Nov 2008 15:53:15 +0000</pubDate>
		<guid isPermaLink="false">#comment-58158</guid>
		<description><![CDATA[Check the event logs on the workstations, and, if you do not know what they mean, or how to fix what is reported, try www.eventid.net for an answer.

Can you reach the Exchange server via OWA?

Can you ping the server by name and IP address?

Check the Exchange server. Ensure all Exchange services that should be running are running.

Check your store size. Has it exceeded its limit--store will not mount if it has.If you have not edited the registry to allow a store larger than 16GB, now would be a good time. It can be increased to 75GB.

Have you run oout of disk space on the drive hosting the store, hosting the logs. If the logs go back forever, or even a few days, you need to do a full backup of Exchange with an Exchange aware backup program so the logs can be written tothe store and deleted. Then ensure that this is done every day.

Check the event logs on the server. Follow up and resolve any errors found. Again, use www.eventid.net to assist.

If you have no idea what any of these steps involve, call someone to come in to resolve your problem for you.You have now been without e-mail for 4 days. Most places where I work would find 4 hours to be unacceptable. Wow, I just looked back at your post, and it is dated February 11, 2008. Sure hope your problem has been resolved.]]></description>
		<content:encoded><![CDATA[<p>Check the event logs on the workstations, and, if you do not know what they mean, or how to fix what is reported, try <a href="http://www.eventid.net" rel="nofollow">http://www.eventid.net</a> for an answer.</p>
<p>Can you reach the Exchange server via OWA?</p>
<p>Can you ping the server by name and IP address?</p>
<p>Check the Exchange server. Ensure all Exchange services that should be running are running.</p>
<p>Check your store size. Has it exceeded its limit&#8211;store will not mount if it has.If you have not edited the registry to allow a store larger than 16GB, now would be a good time. It can be increased to 75GB.</p>
<p>Have you run oout of disk space on the drive hosting the store, hosting the logs. If the logs go back forever, or even a few days, you need to do a full backup of Exchange with an Exchange aware backup program so the logs can be written tothe store and deleted. Then ensure that this is done every day.</p>
<p>Check the event logs on the server. Follow up and resolve any errors found. Again, use <a href="http://www.eventid.net" rel="nofollow">http://www.eventid.net</a> to assist.</p>
<p>If you have no idea what any of these steps involve, call someone to come in to resolve your problem for you.You have now been without e-mail for 4 days. Most places where I work would find 4 hours to be unacceptable. Wow, I just looked back at your post, and it is dated February 11, 2008. Sure hope your problem has been resolved.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pressler2904</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/troubleshoot-task-microsoft-exchange-server-reported-error/#comment-58147</link>
		<dc:creator>pressler2904</dc:creator>
		<pubDate>Wed, 26 Nov 2008 17:11:10 +0000</pubDate>
		<guid isPermaLink="false">#comment-58147</guid>
		<description><![CDATA[If all 30 workstations stopped working (Outlook, that is) 3 days ago, Technichic is right on the money by looking at what changed.  IF ALL 30 systems stopped connecting at the same time, I would start looking at the Exchange end or possibly the router/switch (unlikely), unless you pushed out the MS patches for November late, in which case look at them as well...

I&#039;d check Exchange Server application logs first.]]></description>
		<content:encoded><![CDATA[<p>If all 30 workstations stopped working (Outlook, that is) 3 days ago, Technichic is right on the money by looking at what changed.  IF ALL 30 systems stopped connecting at the same time, I would start looking at the Exchange end or possibly the router/switch (unlikely), unless you pushed out the MS patches for November late, in which case look at them as well&#8230;</p>
<p>I&#8217;d check Exchange Server application logs first.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using memcached
Database Caching 6/9 queries in 0.013 seconds using memcached
Object Caching 282/285 objects using memcached

Served from: itknowledgeexchange.techtarget.com @ 2013-05-18 18:25:14 -->