tag:blogger.com,1999:blog-77595049390279377992024-03-13T02:57:31.233-07:00Exchange Server RecoveryJohnson Jackhttp://www.blogger.com/profile/08711830363959109765noreply@blogger.comBlogger6125tag:blogger.com,1999:blog-7759504939027937799.post-39804450350495586632014-09-03T04:20:00.002-07:002014-09-05T04:00:55.056-07:00User Mailbox Recovery in Exchange 2003<div dir="ltr" style="text-align: left;" trbidi="on">
There are many methods for the recovery of a deleted Exchange 2003mailbox. They are:
<br />
<blockquote>
1. <b>Recover using the Exchange System Manager</b> </blockquote>
<blockquote>
<div style="text-align: left;">
<img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgxO8L_RAoEID9CvVGE1cpzEM-Le4ySuW161O8s943YTYe_2fmGQu0QmuECbWPZioBDWhSDNG143lSWPiNrxAUzW32RbtshktdxbZNm4mKNzG2GSB2jmgb-nxmY0pE_BR8rrFmazB95okA/s320/Exchange+System+Manager.jpg" /></div>
</blockquote>
<a name='more'></a><br />
<blockquote>
2.<b> Recover using the Recovery Storage Group Feature</b> </blockquote>
<blockquote>
<img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj8BWYIfMDwVkTiA43WcPCyV8ewmZAxWPVa9KCqpk7M5AKXgFg8SUbUJqhSFqJA_HLN1GHKQA3VOXvc2eIIWTXK0bk14iKNZlopvln0PlQE3naMwEq-etNKlOLKYYueoyOj40lkATdG91o/s320/Storage+Group+Feature.gif" /></blockquote>
<br />
<blockquote>
3. <b>Recovery from Backup Recovery Server</b> </blockquote>
<blockquote>
<img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhphHRHOVVsZZl7GFGVeZuLSywz8hklmouGorpG6dq9uDvQkMv221-fm1WxgN1m5DxYgSmEoF7YsGBKgfITN1v3HjyLt52HcZcBghuF8uH8QYxULg7Ox-CF3uPO158HpOwIDBaBAxXAjTQ/s320/ackup+Recovery+Server.png" /></blockquote>
<b>How to Restore a Deleted Exchange 2003 Mailbox Using Exchange System Manager</b><br />
<br />
It is easy to restore a user mailbox in Exchange 2003 after its deletion, if the deletion retention settings are configured properly in the Exchange prior to the deletion of the mailbox. Here we will show you how to configure the deletion retention settings, and how to restore Exchange 2003 mailbox. For this, one needs to make use of the Exchange System Manger.<br />
<br />
<b>Exchange System Manager</b><br />
<br />
Exchange System Manager is a specialized MMC console that facilitates better management of the Exchange Organization. It helps Exchange administrators in managing public folders, servers, routing, and policies very effectively.<br />
<br />
To open the Exchange System Manager:<br />
<ul style="text-align: left;">
<li>Click Start> Programs>Microsoft Exchange>System Manager </li>
</ul>
<ul style="text-align: left;">
</ul>
<ul style="text-align: left;">
</ul>
<blockquote class="tr_bq">
<img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhjI-JDOhFoSWWIFsi8mqUfyoxovb1-PAwDdhhr2ubFqmN7dr2b738WXfG0nbBnEF2l9g5_-Rs2XqTHNmmiCpDOWvb8ewiHqlGucUfCPA3Q1BWyz1eROyjTIj7YMpM1E1618exayyDmSjs/s320/untitled.JPG" /></blockquote>
<b>Verify/Configure Mailbox Deletion Retention Settings in Exchange 2003</b><br />
<br />
You can recover the deleted user mailbox using the Exchange System Manager, only if you have configured the deleted item retention settings prior to the deletion. This is how you can configure it:<br />
<blockquote>
1. Start the Exchange System Manager.</blockquote>
<blockquote>
2. Expand Administrative Groups, and then expand < administrative group> </blockquote>
Note: If you do not see the Administrative Groups displayed, Right-click < organization>, click Properties, click the Display administrative groups checkbox, click OK, click OK, and restart the Exchange System Manager.<br />
<blockquote>
3. Expand Servers, expand < server>, and expand <storage group=""><storage group=""></storage></storage></blockquote>
<blockquote>
4. Right-click the Mailbox Store</blockquote>
<blockquote>
5. Click Properties, and then click the Limits tab.</blockquote>
<blockquote>
6. Enter the number in Keep deleted mailboxes for (days) box (the deleted mailboxes will be kept for this number of days); click OK.</blockquote>
<b>Restore Deleted Exchange 2003 Mailbox</b><br />
<br />
The deleted user mailbox will remain in the server for the number of days specified in the deletion retention settings. Before the expiry of the retention days, you can recover the mailbox very easily by following the steps given below:<br />
<blockquote class="tr_bq">
1. Repeat the steps as above till the step 4.</blockquote>
<blockquote class="tr_bq">
2. Right-click Mailboxes and click Run Cleanup Agent.</blockquote>
<blockquote class="tr_bq">
3. Right-click the mailbox that is to be recovered, and click Reconnect.</blockquote>
<blockquote class="tr_bq">
4. Select the user account (when the list of Microsoft Active Directory directory service accounts appears) to which the mailbox is be connected; click OK.</blockquote>
<blockquote class="tr_bq">
5. Finally, quit Exchange System Manager.</blockquote>
<b>Professional Tools for the Recovery of Deleted Mailboxes
</b><br />
<br />
Kernel for Exchange Server is a professional third-party tool for the recovery of deleted Exchange Server mailboxes. Apart from the deleted mailboxes, it recovers all other inaccessible mailboxes from the corrupt or damaged Exchange database. Another advantage is that, it works with all versions of Exchange Server.<br />
To download trial version of this tool follow this link: <a href="http://www.exchangerecoverytools.org/" rel="nofollow">http://www.exchangerecoverytools.org/</a></div>
Johnson Jackhttp://www.blogger.com/profile/08711830363959109765noreply@blogger.com0tag:blogger.com,1999:blog-7759504939027937799.post-73478384524686712552014-05-02T03:40:00.000-07:002014-06-06T05:30:44.358-07:00Know why you don’t have to worry about EDB File Error 550 anymore<div dir="ltr" style="text-align: left;" trbidi="on">
Without giving a second thought, each one of use would accept the fact that emails nowadays is the most indispensible part of any organization. Today, working in any office environment, be it usual communication, or even reporting to managers. All these are done through emails. In fact, these days MS Outlook and MS Exchange server are the most used email clients and Exchange Server that are widely used by many professionals. <br />
<br />
The important aspect that one got to know is that while working on an exchange server, every time an email is sent through MS Outlook, a copy of that email is saved on Exchange Server in EDB (Exchange Server database) files. In fact, this EDB file very well stores vital information like to, CC, from, Bcc etc. and contacts, calendar, journal, and notes. But have you ever imagined what would you do if the MS Exchange Server database gets corrupted? Definitely, you may never ever like to think about any such situation because MS Exchange Server database corruption could easily lead to inaccessibility of mailbox, loss of the entire database. <br />
<a name='more'></a><br />
Working on MS Exchange Server, chances are always high that you may face any of the problems, mentioned like: <br />
<br />
<ul style="text-align: left;">
<li>You started the Exchange Server services and you encountered “Error -550” error message.</li>
</ul>
<ul style="text-align: left;">
<li>Exchange Server database gets marked as suspect and dirty shutdown.</li>
</ul>
<ul style="text-align: left;">
<li>Database doesn’t get recognized even after deletion of log files, which are “not committed."</li>
</ul>
Now, error code 550, generally takes place because of the inconsistency in backup. It results in failure of successful restore. Now, whenever error -550 takes place, as a user you may be not able to connect the Exchange mailbox to a specific domain. The situation appears where the destination server fails completely to receive the emails posted by source server. <br />
<br />
<b>How to Coup up With the Concern - Exchange Server Error 550?</b><br />
<br />
Before starting workout for resolving Exchange Error 550, it is crucial to check out certain things. Initially open ESM (Exchange System Manager) then, move on to the virtual server (SMTP) that is utilized by you for sending mails <br />
<br />
<ol>
<li>Find Out Properties -> "'Access'-> 'Relay'"</li>
<br />
<li>Find out whether the setting "Allow computers which successfully authenticate to relay" is enabled or not</li>
<br />
<li>Find out the exchange error from error log, which may assist you in finding the cause of error.</li>
</ol>
<br />
Now, you can very well try Eseutil Commands to remove the problems due to error 550. If this command doesn’t help you to sort out the error then, you may further try Eseutil /d. But, the problem turns trickier when both of these commands get failed. The known limitation of these commands is accessing 4KB data only to check out the problematic concern. Consequently, the right option you can opt is taking help of a third party exchange server recovery tool that can resolve the edb file error. In other words, you must take help of a proficient Kernel for Exchange Server Recovery. Designed to run safe scanning procedures, the software helps user to repair corrupted database and takes just few minutes to extract valuable data. In fact, the software has got an excellent ability to restore the lost, and deleted emails from MS Exchange Server database files. The good highlight of the software is its two different recovery modes primarily – Standard Scan and Advanced Scan that makes the entire EDB file recovery lot easier. Besides this, the tool even facilitates with usage of disk space that allow use of disk space while scanning and recovering EDB items. Moreover, the tool is very much compatible with MS Exchange Server 5.0, 5.5, 2000, 2003, 2007, 2010 and 2013.<br />
To Download Kernel for Exchange Server Recovery tool visit:- <a href="http://www.recoveryfiles.org/exchange-server-recovery.html" rel="nofollow">http://www.recoveryfiles.org/exchange-server-recovery.html</a>
</div>
Johnson Jackhttp://www.blogger.com/profile/08711830363959109765noreply@blogger.com1tag:blogger.com,1999:blog-7759504939027937799.post-38258998085896809092014-01-20T01:51:00.000-08:002014-06-06T05:31:39.632-07:00Best ways to eliminate bad page link error of MS Exchange Server<div dir="ltr" style="text-align: left;" trbidi="on">
MS Exchange Server is a server based application for storage and retrieval of email records. Mailbox information of all users connected with a MS Exchange network is saved in Exchange database folders and groups. Exchange database corruption adversely affects email services in business organizations that use MS Exchange Server. Logical EDB file errors are among the prominent Exchange Server corruption. Exchange Server error 327 is a common case of EDB logical corruption which appears in the Windows application log like this:<br />
<br />
<b>Source: </b>ESE<br />
<b>Category:</b> database corruption<br />
<b>Event ID:</b> 447<br />
<b>Computer:</b> Server name<br />
<b>Description: </b>A bad page link (error-327) has been detected in a B-tree (ObjectId: 70950, PgnoRoot: 157120) of database C:\Program files\Exchsrvr\MDBDATA\priv1.EDB (157120 => 129107, 129109)<br />
<br />
<b>Chief reasons: </b>Exchange error code 327 is reported during online defragmentation of MS Exchange Server. It indicates corruption at database page level of an Exchange mailbox store or jet database engine crash. It may happen due to several reasons such as corruption of the Windows logical or physical drive, virus infection, hardware problem and others.<br />
<a name='more'></a><br />
<b>Workaround: </b><br />
<br />
You can use Exchange Server offline defragmentation tool i.e., Eseutil/d to remove bad database pages of a mailbox store:<br />
<br />
<i>C:\Program files\Exchsrvr\Bin\ Eseutil/d “C:\ProgramFiles\Exchsrvr\MDBDATA\Priv1.EDB”</i><br />
<br />
After offline defragmentation, you should also repair priv1.EDB folder or mailbox store using following command:<br />
<br />
<i>C:\Program files\Exchsrvr\Bin\ Eseutil/r “C:\ProgramFiles\Exchsrvr\MDBDATA\Priv1.EDB”</i><br />
<br />
If Exchange database page error is not fixed with Eseutil/r command, you should use Exchange Server hard recovery option:<br />
<br />
<i>C:\Program files\Exchsrvr\Bin\ Eseutil/p “C:\ProgramFiles\Exchsrvr\MDBDATA\Priv1.EDB”</i><br />
<br />
Exchange Server hard recovery option or Eseutil/p is a destructive process and it will recover Exchange mailbox store or public store by omitting all invalid database pages. After successful execution of Eseutil commands, you must also perform integrity check of the corrupt Exchange Server using following command:<br />
<br />
<i>C:\Program files\Exchsrvr\Bin\ Isinteg –s (Servername) –fix-test alltests</i><br />
<br />
Run Isinteg command several times till MS Exchange Server does not report zero error. However, Eseutil and Isinteg commands will work only in case database bad page link error is limited to database level of MS Exchange Server only. <br />
<br />
Another troubleshooting option is move the corrupt Priv1.EDB to a new Exchange Server using move mailbox command of the Exchange management console or Exchange management Shell. Then recreate a new mailbox store on the source Server and copy the original mailbox information from the destination Exchange Server.<br />
<br />
Alternatively, you can use Exmerge.exe or Exchange mailbox merge program for moving Exchange mailbox data of a source server to mailboxes of a destination Exchange Server. But Exmerge program is available only with selected MS Exchange Server versions i.e., MS Exchange Server 5.0, 5.5 and 2000. Use of Exchange mailbox merge program also require deep knowledge of Exchange management tools.<br />
<br />
If Exchange error 327 is reported due to hardware failure or drive corruption, it is better to use a third party Exchange Server recovery tool. Kernel for Exchange Server recovery smartly recovers inaccessible priv1.EDB and pub1.EDB folders of MS Exchange Server. It recovers entire mailbox information of Exchange users such as emails, sent items, inbox, deleted items, drafts and notes. MS Exchange Server recovery software saves recovered Exchange mailbox information in PST files. It also saves information of successfully recovered mailboxes in a HTML file. MS Exchange recovery tool supports all MS Exchange Server and MS Outlook versions.
<br />
Free trial version download here: <a href="http://www.kerneldatarecovery.com/download-edb-email-recovery-software.html" rel="nofollow">http://www.kerneldatarecovery.com/download-edb-email-recovery-software.html</a>
</div>
Johnson Jackhttp://www.blogger.com/profile/08711830363959109765noreply@blogger.com1tag:blogger.com,1999:blog-7759504939027937799.post-15896450611141404632013-07-24T04:04:00.004-07:002013-09-13T03:08:02.263-07:00Is there any option to eliminate Exchange errors 0x8004011C and 0x80040115 manually?<div dir="ltr" style="text-align: left;" trbidi="on">
<div class="separator" style="clear: both; text-align: center;">
</div>
<div style="margin-left: 1em; margin-right: 1em; text-align: center;">
<img border="0" height="481" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgRbvIqyObaGmbRnHNf2PcwBvcpd1sebEZ-UrgQaHvhViDh8aj_E8fiNVEeQv2y4H1lT1g7W_YynwRXQzwsr3VwwjbecRgLPbSju9ygUC9wUmhfstf7xfCd9fLjWSFxWh7wuqpq6TnaZlE/s640/1513.024.bmp" width="640" /></div>
<br />
<div align="JUSTIFY">
Exchange Server 2013 is designed to provide smooth email services in business organizations. Besides, uninterrupted email services, Exchange Server 2013 also provide following benefits to users:</div>
<br />
<ul>
<li><span id="goog_723528044"></span><span id="goog_723528045"></span>1. New powershell cmdlets for easy management of Exchange mailboxes </li>
<li>2. Web based Exchange Administration Center in place of Exchange Management Console for IT administrators</li>
<li>3. Merger of public folders into mailbox databases for quick recovery of inaccessible Exchange mailboxes </li>
<li>4. Inbuilt anti-malware protection to prevent mailbox corruption and data theft events </li>
<li>5. New Outlook Web App (OWA) layouts that can be used even in small devices like tablets, ipads and mobiles <span id="goog_723528033"></span><span id="goog_723528034"></span></li>
</ul>
<div align="JUSTIFY">
<br />
<a name='more'></a><br /><br />
In spite of advanced security and data privacy features, mailbox databases of an Exchange Server 2013 organization may crash or get damaged due to several factors. These factors are virus attacks, unexpected shutdown of the Exchange Server, fault in the LAN cable and many more.</div>
<div align="JUSTIFY">
<br /></div>
Exchange Server 2013 database generate many typical error codes and 0x8004011C and 0x80040115 are some of them. These errors are also known as bugs in the Exchange Server 2013 and very often makes situation too complex.<br />
<br />
<div align="JUSTIFY">
<br /></div>
<div align="JUSTIFY">
These sorts of errors usually occur if Exchange Server 2013 runs Outlook 2013, Outlook 2010 or Outlook 2007 client. These errors will be flashed on your computer screen after you press “Send/Receive” button in your Exchange mailbox. This is a completely new event as you’ll see Outlook client connected with the Exchange Server, updating and also receiving emails in the mailbox folders.</div>
<div align="JUSTIFY">
Using Powershell set-autodiscovery and set-OutlookAnywhere cmdlets, you can easily eliminate these bugs in Exchange Server 2013:</div>
<br />
<ul>
<li> <b><span style="color: white;"><span style="background-color: #666666;">Set-AutodiscoverVirtualDirectory -Identity 'autodiscover(default Web Site)' -WindowsAuthentication $true -BasicAuthentication $true </span></span></b></li>
<br />
<li> <b><span style="color: white;"><span style="background-color: #999999;">Set-OutlookAnywhere -Identity:YourExchange2013CASServerrpc (Default Web Site) -IISAuthenticationMethods Basic,NTLM</span></span></b></li>
</ul>
<div align="JUSTIFY">
<br />
After having defined new authentication method to Auto discover and Outlook anywhere, restart your Exchange 2013 mailbox and press “Send/Receive” button again.</div>
<div align="JUSTIFY">
<br /></div>
<div align="JUSTIFY">
You’ll not get error codes 0x8004011C and 0x80040115. However, Powershell scripts can fix “send/receive” errors of only single Exchange mailbox at a time.</div>
<div align="JUSTIFY">
<br /></div>
<div align="JUSTIFY">
If Powershell scripts fail to resolve the issue, delete old OST file from your computer drive, create new Outlook profile and synchronize with Exchange Server. Now, you should restart Outlook to open your mailbox on the Live Server. This will probably solve “Send/receive” error of your Exchange mailbox. If none of inbuilt options are able to fix unknown error codes of MS Outlook or Exchange Server 2013, then it is better to use a third party software to fix the issue.</div>
<br />
<div style="text-align: center;">
<iframe allowfullscreen="" frameborder="0" height="315" src="//www.youtube.com/embed/Heuu9uDDPr4" width="560"></iframe><br /></div>
<div align="JUSTIFY">
<br />
Kernel for Exchange Server recovery is best remedy to cure or deal with Exchange mailbox corruption. It effectively fix all mailbox corruption errors. This Exchange Database repair software rebuild both public and mailbox stores of the MS Exchange organization. It retrieves mailbox information even from a large Exchange database and save it in PST file. This Exchange Database repair tool can restore mailbox database created by any Exchange version. It also creates a recovery report in HTML format that turns beneficial in acquiring information about successful recovery of mailbox I<span class="short_text" id="result_box" lang="en"><span class="hps">f you need</span> <span class="hps alt-edited">learn more</span><span class="">, please</span> <span class="hps">click here: <a href="http://www.edbtopstconverter.softwaredatarecovery.net/" rel="nofollow">http://www.edbtopstconverter.softwaredatarecovery.net/</a></span></span> </div>
</div>
Johnson Jackhttp://www.blogger.com/profile/08711830363959109765noreply@blogger.com3tag:blogger.com,1999:blog-7759504939027937799.post-4307213352430143252013-03-11T04:36:00.000-07:002014-02-16T23:36:24.923-08:00How to Export and Import mailboxes to outlook PST files?<div dir="ltr" style="text-align: left;" trbidi="on">
<div dir="ltr" style="text-align: left;" trbidi="on">
<div align="JUSTIFY" style="margin-bottom: 0in;">
Disaster on the Exchange
server creates a panic situation and interrupts entire communication
process in the organization. Exchange Server disaster can happen due
to several reasons such as:</div>
<div align="JUSTIFY" style="margin-bottom: 0in;">
<br /></div>
<ul>
<li> <b><span style="font-size: small;"><span style="font-family: Verdana, sans-serif;"><i>a).</i></span></span><span style="font-size: small;"><span style="font-family: Verdana, sans-serif;"><i> </i></span></span></b>Virus, spyware and ad-ware intrusion</li>
<li><b><i>b).</i></b> Corrupt hard disk or portable device</li>
<li><i><b>c)</b>. </i>Permanently deleted user accounts</li>
<li><b><i>d).</i> </b>Crash of MS Windows or MS Outlook</li>
<li><i><b>f).</b> </i>Other hardware malfunctions<a name='more'></a></li>
</ul>
<div align="JUSTIFY" style="margin-bottom: 0in;">
<br />
User accounts on Exchange
Server are stored in EDB file format. To deal with Exchange disaster
situation, network administrator needs to convert user accounts or
mailboxes into MS Outlook.
</div>
<div align="JUSTIFY" style="margin-bottom: 0in;">
<br /></div>
<div align="JUSTIFY" style="margin-bottom: 0in;">
<b>Exchange mailbox
recovery through MS Outlook</b></div>
<div align="JUSTIFY" style="margin-bottom: 0in;">
<br /></div>
<div align="JUSTIFY" style="margin-bottom: 0in;">
Exchange Server
corruption or disaster is unhealthy situation in the organization. It
prevents user from accessing their mailbox data on the Server. Many
times, converting Exchange mailbox into Outlook PST file helps the
administrator in eliminating Exchange Server disasters. Microsoft has
added Import and Export wizard in MS Outlook that enables exchange
administrator to convert Exchange mailboxes into PST file format.
Following conditions must be fulfilled for Exchange mailbox recovery
with MS Outlook:</div>
<ul>
<li><b><i>a).</i> </b>You must be network administrator of the Exchange Server and have access of all outlook profiles</li>
<li><b><i>b).</i></b> MS Outlook 2003 or higher version must be installed on the master computer of the network</li>
<li><b><i>c).</i></b> Exchange Server 2007 or higher version should be installed on the master computer </li>
<li><b><i>d).</i></b> You must create blank PST file using Accounts Setting of the outlook profile </li>
</ul>
<div align="JUSTIFY" style="margin-bottom: 0in;">
<br />
If Outlook 2010 is
installed in main computer, then you can recover Exchange mailboxes
with Outlook’s import and export wizard in the following steps:</div>
<div align="JUSTIFY" style="margin-bottom: 0in;">
<br /></div>
<ol>
<li><div align="JUSTIFY" style="margin-bottom: 0in;">
1. Open the specific
Outlook profile of a domain</div>
<div align="JUSTIFY" style="margin-bottom: 0in;">
<br /></div>
<img border="0" height="320" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhObZ8Zl8HfWnqaNzJudsDwX2OMJgjNAoVFXl1Him99m7Z2o6YuJP68OLZ7GMFur_NBpjoQpXNBZsr7P2lepZ_HKY8YZ0M5z4_lJd0PCv8LDvajjbt42AM8zM8lBGYJ2mqSsIGiVBMia34/s320/importexport.jpg" width="320" /></li>
<li><div align="JUSTIFY" style="margin-bottom: 0in;">
2. In the file menu of
the mailbox windows, hit <b>Open >Import</b> to open Import and
Export Wizard</div>
<div align="JUSTIFY" style="margin-bottom: 0in;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgG4Oc5FDr8JeG3X0QdElOuFAyzMrNJGAKvjGG-30TQxPVEbWzAHP60JhyuXuZ_IZPpVgEJsIDz6a822PP57pK0IS4V5Dl-BL5WhZqjVOgLJkmdm7Vi2r5StZUKxeqxVruDu_Ie0IBnddo/s1600/ExportAndImportWizard2.jpg" style="margin-left: 1em; margin-right: 1em;"></a><br /></div>
</li>
<li><div align="JUSTIFY" style="margin-bottom: 0in;">
3. Choose “<b>Export
to a file</b>” option from the available list and press “Next”<br />
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhLSNa5gu7L5M13N2CgVfpjb0oNXg4iKT-8dCsF32R8SCLBD5caZLpbcGHdBLVpbvEexuc8dIQGEyNORmZQxlGzsD0P5RxJXiof_Z0WcGVpFYSEqik7Kphb28JLvR3K-yvlLxVxWnIdvMc/s1600/ExportToAFile.jpg" style="margin-left: 1em; margin-right: 1em;"></a><br />
<img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgG4Oc5FDr8JeG3X0QdElOuFAyzMrNJGAKvjGG-30TQxPVEbWzAHP60JhyuXuZ_IZPpVgEJsIDz6a822PP57pK0IS4V5Dl-BL5WhZqjVOgLJkmdm7Vi2r5StZUKxeqxVruDu_Ie0IBnddo/s1600/ExportAndImportWizard2.jpg" /></div>
</li>
<li><div align="JUSTIFY" style="margin-bottom: 0in;">
4. Select “<b>Personal
Folder File (.PST)</b>” option and press “<b>Next</b>”</div>
<div align="JUSTIFY" style="margin-bottom: 0in;">
<img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhLSNa5gu7L5M13N2CgVfpjb0oNXg4iKT-8dCsF32R8SCLBD5caZLpbcGHdBLVpbvEexuc8dIQGEyNORmZQxlGzsD0P5RxJXiof_Z0WcGVpFYSEqik7Kphb28JLvR3K-yvlLxVxWnIdvMc/s1600/ExportToAFile.jpg" /></div>
</li>
<li><div align="JUSTIFY" style="margin-bottom: 0in;">
5. Choose some or all
folders of the Exchange mailbox for export
</div>
</li>
<li><div align="JUSTIFY" style="margin-bottom: 0in;">
6. Check the “<b>Include
sub folders</b>” check box and press “Next”<br />
<img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhE1zHgUNH_jYGlE5B3cBdKand8HGm2Y7ZNKQIuZWS6ExLT1klfDo1RJl4t5yypXWc4_tY_tKpwT0zeXLd3nKKCP_OP509aikMQV9AK2opT_SjGoZZWkSSTUF_9Ye8-zM3PTSqnqJ6HJC0/s1600/ExportOutlookDataFile.jpg" /></div>
</li>
<li><div align="JUSTIFY" style="margin-bottom: 0in;">
7. Specify the
destination folder to save exported mailbox in the blank PST file
<br />
<br /></div>
</li>
<li><div class="separator" style="clear: both; text-align: center;">
</div>
<div align="JUSTIFY" style="margin-bottom: 0in;">
8. Select “<b>Do not
export duplicate items</b>” option and press “<b>Finish</b>”<br />
<img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhwJaJlKlznIIJaVcBm4SIlWmph2sb4FxeUl_rRwUbL8ucelnjV3Wi285CywlHgVM4PZ4af90ppsaR6H0ITmOAerAzjy3z-6vU5u6obMaQ6vL7yBdu87PV-9USB_nvIkroD7Nk9T7NkVtY/s1600/ExportOutlookFile.jpg" /></div>
</li>
</ol>
<div align="JUSTIFY" style="margin-bottom: 0in; text-indent: 0.04in;">
</div>
<div align="JUSTIFY" style="margin-bottom: 0in;">
Folders and sub- folders
of the user mailbox selected for migration are exported to blank PST
file by the Import and Export migration wizard of MS Outlook.
</div>
<div align="JUSTIFY" style="margin-bottom: 0in; text-indent: 0.04in;">
<br /></div>
<div align="JUSTIFY" style="margin-bottom: 0in;">
<b>Limitations of
Outlook’s Import and Export wizard </b>
</div>
<div align="JUSTIFY" style="margin-bottom: 0in;">
<br /></div>
<div align="JUSTIFY" style="margin-bottom: 0in;">
Import and Export Wizard
of MS Outlook helps the network administrator in troubleshooting many
Exchange corruption issues. However, it has several limitations as
mentioned below:</div>
<div align="JUSTIFY" style="margin-bottom: 0in;">
<br /></div>
<ul style="text-align: left;">
<li><div align="JUSTIFY" style="margin-bottom: 0in;">
It cannot recover
Exchange mailbox or user profile, that are permanently removed from
the Exchange Server</div>
</li>
<li><div align="JUSTIFY" style="margin-bottom: 0in;">
It fails to extract
mailbox data, if Exchange Server crashes or frequently disconnects
from internet</div>
</li>
<li>It takes very long
time for large scale Exchange mailbox recovery</li>
</ul>
<div align="JUSTIFY" style="margin-bottom: 0in;">
<br /></div>
<div align="JUSTIFY" style="margin-bottom: 0in;">
Due to above-mentioned
limitations of MS Outlook, it is better that you use third party
Exchange mailbox recovery software.
</div>
<div align="JUSTIFY" style="margin-bottom: 0in;">
<br /></div>
<div align="JUSTIFY" style="margin-bottom: 0in;">
<b>Kernel for Exchange
server recovery </b>
</div>
<div align="JUSTIFY" style="margin-bottom: 0in;">
<br /></div>
<div align="JUSTIFY" style="margin-bottom: 0in;">
Kernel for Exchange
Server recovery is a proficient tool to deal with major EDB or
Exchange Server corruption. It is capable of recovering user
mailboxes from the severely damaged or crashed Exchange Server. This
Exchange mailbox recovery utility is very much competent in
recovering mailboxes from both public and private Exchange databases.
Finally, it save the recovered user accounts in Outlook PST file
format. Moreover, Exchange mailbox recovery utility also helps in
recovering and restoring inaccessible Exchange mailboxes or databases
into new EDB file.<b><i> </i></b>For more information, Visit <a href="http://www.edbtopstconverter.softwaredatarecovery.net/" rel="nofollow">http://www.edbtopstconverter.softwaredatarecovery.net/</a></div>
</div>
</div>
Johnson Jackhttp://www.blogger.com/profile/08711830363959109765noreply@blogger.com2tag:blogger.com,1999:blog-7759504939027937799.post-7556881023877439272013-03-11T02:24:00.000-07:002014-05-28T02:56:11.837-07:00How to recover corrupt PRIV, PRIV1, Pub, and Pub1 edb and stm database<div dir="ltr" style="text-align: left;" trbidi="on">
<div align="JUSTIFY" style="line-height: 150%; margin-bottom: 0in;">
<div class="separator" style="clear: both; text-align: center;">
</div>
<div class="separator" style="clear: both; text-align: center;">
<img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhbT6KJSZer2YJNUvPtAsOGIhjc40y_yCdIp1pEwcRC1n96knC14-jBVfx_-lP36zLcTNGyaSwOP3ZWrRNUAUWgs-FJWvwO5pjET6_yL19GxUJTV5Xh9It5U5o3zpbsEqt8Eg_I_eesKZ0/s1600/servers.gif" /></div>
<span style="font-family: Verdana, sans-serif;"><span style="font-size: small;">Most
of us are very much aware of the fact that Exchange Database files
are nothing more than the exact replica of user’s mailbox on MS
Outlook. Moreover, this MS Exchange Server works in proper
cooperation with MS Outlook in exchange of emails. And, each and
every single email that is received or sent at the user’s end is
primarily saved at server. Now, exchange server primarily store these
emails as Exchange Database files that prove very helpful when you
require dealing with accidental deletion of user mailbox.</span></span><br />
<a name='more'></a> </div>
<div align="JUSTIFY" style="line-height: 150%; margin-bottom: 0in;">
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi7AeX7qSf0vNf63WxT4HukukUHo2qFAOuClE4oKDTI7ur4PhvxAqnVZM-PDIZ1_1JToYZj1i98j6HLM6tYp444ekK8MA0Z4AbMb1W7FQ5NhytZV4zYV0dEm6oxPetvUFFAf2n1Uaq4hsI/s1600/image0041116861982484.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><br /></a></div>
<span style="font-family: Verdana, sans-serif;"><span style="font-size: small;">It
is really very important that you manage your exchange server
properly. As an IT administrator you need to maintain a proper check
upon your Information Store and at the same time validate its
consistency. Now, every single storage group in an Exchange server
normally includes one or more Mailbox and Public Folder stores.
During installation, by default just one storage group gets created.
With Exchange Server 2000 and 2003, every Mailbox store comprises a
database set consisting of two files: 'Priv1.edb' and 'Priv1.stm'.</span></span></div>
<div align="JUSTIFY" style="line-height: 150%; margin-bottom: 0in;">
<img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi7AeX7qSf0vNf63WxT4HukukUHo2qFAOuClE4oKDTI7ur4PhvxAqnVZM-PDIZ1_1JToYZj1i98j6HLM6tYp444ekK8MA0Z4AbMb1W7FQ5NhytZV4zYV0dEm6oxPetvUFFAf2n1Uaq4hsI/s1600/image0041116861982484.jpg" /></div>
<div align="JUSTIFY" style="line-height: 150%; margin-bottom: 0in;">
<span style="font-family: Verdana, sans-serif;"><span style="font-size: small;"><br />The
'Priv1.edb' file is more like a rich-text database that primarily
includes email messages, headers and text attachments corresponding
to the messages. Moreover, this file also has streaming file
'Priv.stm' that majorly stores multi-media data like video, audio,
images and other internet content files that is formatted as MIME
data. The real issue with 'Priv.edb' file is its size keeps on
increasing, which ultimately makes it susceptible of getting corrupt.
In addition, Hard disk corruption and header corruption are other key
causes accountable for corrupting the 'Priv1.edb' file. However, you
don’t have to worry as there is a manual method to recover the
corrupt Priv1.edb file. </span></span></div>
<div align="JUSTIFY" style="line-height: 150%; margin-bottom: 0in;">
<span style="font-family: Verdana, sans-serif;"><span style="font-size: small;"> </span></span>
</div>
<div align="JUSTIFY" style="line-height: 150%; margin-bottom: 0in;">
<span style="font-family: Verdana, sans-serif;"><span style="font-size: small;"><b>Manual
Method</b></span></span></div>
<ol>
<li><div align="JUSTIFY" style="line-height: 150%; margin-bottom: 0in;">
<span style="font-family: Verdana, sans-serif;"><span style="font-size: small;">1. First
of all start the information store service and make a note of all
the errors. </span></span>
</div>
</li>
<li><div align="JUSTIFY" style="line-height: 150%; margin-bottom: 0in;">
<span style="font-family: Verdana, sans-serif;"><span style="font-size: small;">2. Stop
the information store service and then run the following commands
from the 'Bin' folder: </span></span><br />
<span style="font-family: Verdana, sans-serif;"><span style="font-size: small;"><i><br /></i></span></span><span style="background-color: #999999;"><b><span style="font-family: Verdana, sans-serif;"><span style="font-size: small;"><i>"c:\exchsrvr\bin>eseutil /mh
..\mdbdata\priv1.edb"</i></span></span></b></span><br />
<span style="font-family: Verdana, sans-serif;"><span style="font-size: small;"><i> </i></span></span><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh5tpDyRaY4xVnuvGhLXtQIRMHbNguG260MU6CyL8Pwq8ps_wAQN0z4rmhnZI6kq2qJNFML52_Gk61ZINsJYdDUoZkpUIlOOeQoq1OIR1zR0lya2RyDcZYJ1Ad6Fd3KvO48VqOR3_j7Phw/s1600/1.jpg" width="575px" /></div>
</li>
<li><div align="JUSTIFY" style="line-height: 150%; margin-bottom: 0in;">
<span style="font-family: Verdana, sans-serif;"><span style="font-size: small;">3. Now,
you got to verify the 'State' line in the output. Just ensure that
all the files are consistent. In case, you find any of the files
inconsistent, conduct soft recovery. And, to perform such recovery,
you just got to switch to the folder where the database and log
files are located. After this, just ensure you run the following at
the command prompt: </span></span>
</div>
</li>
</ol>
<div style="line-height: 150%; margin-bottom: 0in; margin-left: 0.5in; text-align: left;">
<span style="font-family: Verdana, sans-serif;"><span style="font-size: small;"><span style="background-color: #999999;"><b><i>'C:\Program
Files\exchsrvr\MDBDATA>"C:\Program
Files\exchsrvr\BIN\eseutil" /r E00'</i></b></span></span></span><br />
<div class="separator" style="clear: both; text-align: center;">
<img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi1P4k8NBc7c0JmOWkazLH4phrqzCfnYFUi0rL2KtVgCyvClbYS2vYWDiaXnmGM-K6CUGz3VLUx_XkMEXlVH0VK3KUrzKPIPuhE3kPuqZwEdsnrwLublmSCbM_thmCpl3rjEowz4G-CBj0/s1600/4.jpg" width="575px" /></div>
</div>
<ol start="4">
<li><div align="JUSTIFY" style="line-height: 150%; margin-bottom: 0in;">
<span style="font-family: Verdana, sans-serif;"><span style="font-size: small;">4. Once
again, it is important that you ensure the consistency of both the
public information store and the private information store. </span></span>
</div>
</li>
<li><div align="JUSTIFY" style="line-height: 150%; margin-bottom: 0in;">
<span style="font-family: Verdana, sans-serif;"><span style="font-size: small;">5. If
they are consistent, then skip the next step. </span></span>
</div>
</li>
</ol>
<div align="JUSTIFY" style="line-height: 150%; margin-bottom: 0in;">
<span style="font-family: Verdana, sans-serif;"><span style="font-size: small;">If
you found the databases to be inconsistent, then it is important for
you to do a hard repair. To do this, run the following commands:</span></span></div>
<div align="JUSTIFY" style="line-height: 150%; margin-bottom: 0in;">
<span style="background-color: #999999;"><b><span style="font-family: Verdana, sans-serif;"><span style="font-size: small;"><i>'C:\Program
Files\exchsrvr\MDBDATA>"C:\Program
Files\exchsrvr\BIN\eseutil" /p priv1.edb'</i></span></span></b></span><br />
<br />
<img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEibaem4a2vncjHYiOpjRodEBBiuWNrdw00975jUgRRvMgqg9dnUGqTrfarHAJ63v8S-Akjri5hlCCHUiFVlIHRXVv4v16AU3ibHh3LOm90Yip1tWuJhkFrqtc0Y6cfHOUgwTcP7J8mveAM/s1600/13.jpg" /></div>
<span style="background-color: #999999;"><b>
</b></span>
<br />
<div align="JUSTIFY" style="line-height: 150%; margin-bottom: 0in;">
<br />
<span style="font-family: Verdana, sans-serif;"><span style="font-size: small;"><span style="background-color: #999999;"><b><i>'C:\Program
Files\exchsrvr\MDBDATA>"C:\Program
Files\exchsrvr\BIN\eseutil" /p pub1.edb'</i></b></span> </span></span>
</div>
<ol start="6">
<li><div align="JUSTIFY" style="line-height: 150%; margin-bottom: 0in;">
<span style="font-family: Verdana, sans-serif;"><span style="font-size: small;">6. Now,
it is important that you remove the log files from the 'Mdbdata'
folder. </span></span>
</div>
</li>
<li><div align="JUSTIFY" style="line-height: 150%; margin-bottom: 0in;">
<span style="font-family: Verdana, sans-serif;"><span style="font-size: small;">7. Delete
the '.chk' file and the 'Temp.edb' file. </span></span>
</div>
</li>
<li><div align="JUSTIFY" style="line-height: 150%; margin-bottom: 0in;">
<span style="font-family: Verdana, sans-serif;"><span style="font-size: small;">8. Now,
mount the databases and then, dismount them instantaneously. </span></span>
</div>
</li>
<li><div align="JUSTIFY" style="line-height: 150%; margin-bottom: 0in;">
<span style="font-family: Verdana, sans-serif;"><span style="font-size: small;">9.<span style="font-size: small;"> </span>Finally,
you got to stop the information store service and then defragment
the public and private store databases as follows:</span></span></div>
</li>
</ol>
<div align="JUSTIFY" style="line-height: 150%; margin-bottom: 0in; margin-left: 0.5in;">
<span style="font-family: Verdana, sans-serif;"><span style="font-size: small;"><b>For
Priv.edb:</b><br /><i>C:\Program Files\exchsrvr\BIN>eseutil
/d</i></span></span><br />
<span style="font-family: Verdana, sans-serif;"><span style="font-size: small;"><i>C:\Program Files\exchsrvr\MDBDATA\priv1.edb </i></span></span><br />
<span style="font-family: Verdana, sans-serif;"><span style="font-size: small;"></span></span><br />
<br />
<span style="font-family: Verdana, sans-serif;"><span style="font-size: small;"><span style="font-family: Verdana, sans-serif;"><span style="font-size: small;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhV6dKmVnnzKC6Snu4OxvUM1GSslYov7qV3IqijlyErds0SlatmHJLEKJNDV5qTh2tAfdzhneaJkLFaX_kFh7LvFFEswdryXhx8WKBicXHu392w5zLd54OawBPCZw01dvYHdHxC7QI0h7g/s1600/14.jpg" /></span></span><b> </b></span></span><br />
<span style="font-family: Verdana, sans-serif;"><span style="font-size: small;"><b>For
Pub.edb:</b><br /><i>C:\Program Files\exchsrvr\BIN>eseutil
/d</i><br /><i>C:\Program Files\exchsrvr\MDBDATA\pub1.edb</i> </span></span>
</div>
<ol start="10">
<li><div align="JUSTIFY" style="line-height: 150%; margin-bottom: 0in;">
<span style="font-family: Verdana, sans-serif;"><span style="font-size: small;">10. Run
the 'Isinteg.exe' utility just to ensure that each database is
consistent.</span></span></div>
</li>
</ol>
<div style="line-height: 150%; margin-bottom: 0in; margin-left: 0.5in; text-align: left;">
<span style="font-family: Verdana, sans-serif;"><span style="font-size: small;"><span style="background-color: #999999;"><b><i>'C:\Program
Files\exchsrvr\BIN>isinteg -s (servername) -fix -test alltests'</i></b></span></span></span><br />
<span style="font-family: Verdana, sans-serif;"><span style="font-size: small;"><span style="background-color: #999999;"><b><i><br /></i></b></span></span></span>
<br /><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhZNiSXmEqW_IjWrPm3W8McZdYao7_g3qZfTdZJ_tMjH3p4exd1-BgWGRn5HQi-5kCn3TaFgwZ6neuFhpkxpfOIvpiNDk81BFCHGRsWXT_RbKxBN1l4twYVS4qQHvfkt48rCYgYdj9UpsQ/s1600/15.jpg" /></div>
<ol start="11">
<li><div align="JUSTIFY" style="line-height: 150%; margin-bottom: 0in;">
<span style="font-family: Verdana, sans-serif;"><span style="font-size: small;"><span style="font-size: small;">11. </span>Restart
the information store service.</span></span></div>
</li>
</ol>
<div align="JUSTIFY" style="line-height: 150%; margin-bottom: 0in;">
<span style="font-family: Verdana, sans-serif;"><span style="font-size: small;">However,
after performing the manual method if you are not able to mount the
database and access your precious emails, then you don’t have to
worry. By taking help of a proficient third party exchange database
recovery tool like Kernel for Exchange Server Recovery you can fix
the issue very effectively. The application is very appropriate in
repairing corrupt Exchange server database files, i.e. 'Priv1.edb'
and 'Pub1.edb', and can help you retrieve the valuable user mailbox
data. The competent tool can effectively restore emails, contacts,
appointments, and other mailbox items. The software recreates the
entire EDB database which can be mounted easily. To operate the tool,
you don’t have to be an IT expert. Its graphical user interface
makes it a very user-friendly tool. At the same time the product is
very much compatible with MS Exchange Server 5.0, 5.5, 2000, 2003,
2007 and 2010.<a href="http://www.edbtopstconverter.softwaredatarecovery.net/" rel="nofollow">www.edbtopstconverter.softwaredatarecovery.net</a></span></span>
</div>
</div>
Johnson Jackhttp://www.blogger.com/profile/08711830363959109765noreply@blogger.com1