<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Microsoft Exchange Recovery Tool &#187; Error -1069 = Jet_errVersionStoreOutOfMemoryError -327</title>
	<atom:link href="http://www.ms-exchange-server-recovery.com/blog/tag/error-1069-jet_errversionstoreoutofmemoryerror-327/feed" rel="self" type="application/rss+xml" />
	<link>http://www.ms-exchange-server-recovery.com/blog</link>
	<description>Exchange Server Recovery Software to recover corrupted edb files</description>
	<lastBuildDate>Mon, 18 Apr 2011 07:45:11 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Exchange Database Online Defragmentation Terminates Unexpectedly with Event 705</title>
		<link>http://www.ms-exchange-server-recovery.com/blog/exchange-database-online-defragmentation-terminates-unexpectedly-with-event-705</link>
		<comments>http://www.ms-exchange-server-recovery.com/blog/exchange-database-online-defragmentation-terminates-unexpectedly-with-event-705#comments</comments>
		<pubDate>Fri, 18 Dec 2009 06:40:57 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[software]]></category>
		<category><![CDATA[Err -1018]]></category>
		<category><![CDATA[Err -1018= Jet_errReadVerifyFailure]]></category>
		<category><![CDATA[Error -1069]]></category>
		<category><![CDATA[Error -1069 = Jet_errVersionStoreOutOfMemoryError -327]]></category>
		<category><![CDATA[Error -327 = Jet_errBadPageLink]]></category>
		<category><![CDATA[Error -338]]></category>
		<category><![CDATA[Error -338 = Jet_errBadParentPageLink]]></category>
		<category><![CDATA[exchange 2003 recovery]]></category>
		<category><![CDATA[exchange recovery]]></category>
		<category><![CDATA[exchange recovery software]]></category>
		<category><![CDATA[exchange recovery tool]]></category>
		<category><![CDATA[exchange server recovery]]></category>
		<category><![CDATA[Jet_errVersionStoreOutOfMemory]]></category>
		<category><![CDATA[microsoft exchange recovery]]></category>

		<guid isPermaLink="false">http://www.ms-exchange-server-recovery.com/blog/exchange-database-online-defragmentation-terminates-unexpectedly-with-event-705/</guid>
		<description><![CDATA[An Exchange Server database can get corrupt for several reasons, which include database page checksum errors, B-Tree damage, table corruption and more. At this point, you should consider restoring from the latest backup or repairing the database by running Exchange utilities. At the last resort, you can use an Exchange Server Recovery solution.
For instance, suppose [...]]]></description>
			<content:encoded><![CDATA[<p>An Exchange Server database can get corrupt for several reasons, which include database page checksum errors, B-Tree damage, table corruption and more. At this point, you should consider restoring from the latest backup or repairing the database by running Exchange utilities. At the last resort, you can use an <strong><a href="http://www.ms-exchange-server-recovery.com">Exchange Server Recovery</a> </strong>solution.</p>
<p>For instance, suppose the Exchange Server starts Online Defragmentation on the database, but the process stops with an error as below:</p>
<p>“<em>Online defragmentation of a database ended prematurely after encountering an unexpected error &lt;err_no&gt;. The next time online defragmentation is started on this database, it will resume from the point of interruption.”</em></p>
<p>The error is logged with <strong>event 705</strong> in application event log.</p>
<p><strong>Cause</strong></p>
<p>There can be several causes that generate event 705 and the exact root can be determined by the <em>err_no </em>displaying in the error code:</p>
<ol>
<li><em><strong>Err 	-1018= Jet_errReadVerifyFailure </strong>implies 	checksum errors on database page. This also indicates database 	corruption at ESE level. The general causes are file system issues, 	hardware problems or controller issues.</em></li>
<li><em><strong>Error 	-1069 = Jet_errVersionStoreOutOfMemory </strong>indicates 	out of memory issues in Exchange store.</em></li>
<li><em><strong>Error 	-327 = Jet_errBadPageLink </strong>and 	<strong>Error -338 = Jet_errBadParentPageLink </strong>imply 	bad page link in B-Tree of database. The errors indicate database 	corruption at Jet level. </em></li>
</ol>
<p><strong>Solution </strong></p>
<p>In case of <strong>Jet_errVersionStoreOutOfMemory </strong>error, you need to contact the product support services.  For the other two errors, you should try these steps:</p>
<ol>
<li>Y<em>ou 	should check the application event log for hardware, controllers and 	file system related concerns and take the corresponding action. </em></li>
<li><em>If 	the database exists in running state, you can use ExMerge to extract 	the database as .pst files and later, export them in a new database 	after deleting the corrupted one. Alternatively, you can move the 	mailboxes to another store. </em></li>
<li><em>If 	the database is not running, you should immediately restore it from 	an online backup (if available). When there is no backup, you need 	to repair the corrupted database by running eseutil /p and isinteg 	-fix commands to repair it. If none of the measures work, you are 	suggested to use a third-party <strong>Exchange Recovery </strong>tool. 	An <strong>Exchange Server Recovery </strong>software 	retrieves data from a corrupted Exchange database by running 	suitable repair algorithms. </em></li>
</ol>
<p><strong>Stellar Phoenix Mailbox Exchange Recovery </strong>is an advanced and safe tool that performs systematic database repair of damaged Exchange databases created with Exchange Server 5.5, 2000 and 2003. The tool can recover all email messages,  journals, notes, tasks and other objects. It is a comprehensive <strong>Exchange Recovery </strong>tool that extracts all user mailboxes by converting them into individual Outlook usable .pst files.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.ms-exchange-server-recovery.com/blog/exchange-database-online-defragmentation-terminates-unexpectedly-with-event-705/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

