Posted on Tuesday, November 17, 2009 at 9:45 PM
Microsoft Exchange Server is a widely used and reliable method of creating a messaging collaborative environment. But in some cases, the Exchange Server Database (EDB) file may get damaged and you come across critical data loss situations. To handle the corruption situations, Exchange Server provides an inbuilt utility- Eseutil /p. It handles majority of EDB corruption situations and let you easily perform Exchange Server Recovery
in quick way.
The Eseutil /p is repair method for Microsoft Exchange Server. This procedure corrects most of the EDB corruption like issues and thus allows you to access your data. This utility works on ESE (Extensive Storage Engine) and the page level, not on the application level. Repair process goes through database and examines damaged pages and critical structures of database. After you perform application level repair, using Isinteg tool is required...
Posted on Thursday, November 12, 2009 at 11:25 PM
A compressed NTFS partition can cause several problems, if is made to store Information Store databases. Some of them are high CPU usage, delays when enumerating large NTFS directories and performance issues with many files. It can even corrupt the Information Store and prevent it from starting when it reaches to about 4 GB in size. Also, Exchange Server 2000 SP3 and Exchange Server 2003 do not support compressed Information Store. So, if you upgrade to any of these versions and store Information Store databases are stored on compressed NTFS partition, odds are that they might fail to mount. However, if the database are corrupted due to compression, you will need to restore them from backup or apply soft recovery commands. At times, when it doesn't work, you need a powerful Exchange Server Recovery
solution to repair the corrupted databases...
Posted on Wednesday, November 11, 2009 at 11:22 PM
Outlook Scanpst.exe is a utility to allow recovering folders and other items from a corrupted PST file. The Inbox Repair Tool (Scanpst.exe) examines the file directory structure and individual item headers and tries to repair what it can. But there can be instances when the tool might fail to work. This usually occurs when the corruption is severe or if the file size is more than 2 GB. If this occurs, you need an appropriate backup that could restore the lost data or a powerful third-party Outlook Inbox Repair utility that could apply suitable repair algorithms.
For example, consider a situation when you try to start Microsoft Outlook 2000. You can fail to start and receive the below error message:
“The file <drive>:\<path><file name>.pst could not be found.”
Where <drive> is the drive letter of your primary drive, <path> denotes the full path to .pst file and <file name> is the name of your Outlook PST file. Since Outlook cannot find the file it requires, it shows 'Create/Open Personal Folders File' dialog box to create a new file...
Posted on Tuesday, November 10, 2009 at 11:52 PM
In Exchange Server 5.5 and all of the earlier versions of Microsoft Exchange Server, it is necessary to run Isinteg -patch command line utility after restoring the Exchange Server Database (EDB file) from offline backup. This is not required in Exchange Server 2003 and 2000. For this operation to be completed successfully, the EDB file must be set to enable overwriting by the restore procedure. But in some cases, the Isinteg -patch operation can not complete successfully and you come across some error message. In these circumstances, the EDB file becomes inaccessible and you come across data loss situations. In order to retrieve data and EDB file objects, Exchange Server Recovery
In a practical scenario, when you run the Isinteg -patch utility on Microsoft Exchange Server that is running on Microsoft Cluster Server, the process may fail halfway and you might come across the below given error message:...
Posted on Monday, November 09, 2009 at 11:09 PM
Exchange Server storage groups and databases are the most vital component of recovery when the server crashes. You might observe typical symptoms with a corrupted Exchange database. For instance, you may fail to backup it. When it occurs, the corresponding event indicating the failure is logged in application event log, which helps you to deduce the cause. However, a corrupted Exchange database should be restored from backup. In case of unavailability of backup, you need an effective EDB Recovery
product to repair and restore it.
For example, you might encounter the below event logging into application log of Exchange Server after failing in attempts of backing up the Information Store:
Event Type: Error
Event ID: 217
Posted on Friday, November 06, 2009 at 11:19 PM
A corrupted PST file is often attempted to repair using Inbox Repair Tool((scanpst.exe). The tool is included in all the installation options of Microsoft Office Outlook. But if it fails to fix the corruption, you are suggested to look for powerful commercial applications to repair the file.
For example, consider a situation when you send an email in Microsoft Outlook. You notice that the mail is not moved to Sent Items folder, as expected, but instead gets stuck in Outbox folder. This might happen with each email that you send.
Some typical reasons causing this issue are:
1.You open and close the email message when it is still in Outbox folder. Outlook attempts to deliver the message after establishing a proper connection with mail server. If you open and close before it actually has been sent, you change its status.
2.You are running Outlook in offline mode
3.You have installed an outdated or incompatibile add-in...
Posted on Friday, November 06, 2009 at 10:53 PM
Exchange Server database files are the most important recovery elements, required to be rebuilt after information store crash. If you can successfully restore them from the last backup and all required transaction log files are available, you should replay them to get the database to the state that existed before the crash occurred. In case of any issues, eseutil repair utility can help, but can cause data loss. For safe database repair, use of Exchange Server Recovery
software is recommended. These tools can diagnose and repair all database contents using advanced procedures.
For instance, you might observe that Exchange Server storage group stops unexpectedly. If this leaves few database files unavailable for the server, you encounter the below error marked in the Application event log:...
Posted on Thursday, November 05, 2009 at 12:24 AM
Sometimes while working on Microsoft Outlook, you might encounter Invalid Page Fault errors that prevent you from accessing your important emails, notes, contacts, calendar entries and all other personal data. This behavior of Microsoft Outlook results into serious data loss situations by corrupting the PST (Personal Storage Table) file(s). You need to opt for PST Recovery
solutions to repair and restore all your personal information.
When you start Outlook, you might come across any of the below mentioned error messages:
1. Outlook caused an Invalid Page Fault in Module OLE32.DLL.
2. The instruction at referenced memory at . The memory could not be written.
3. An Application Error has occurred in Outlook.exe.
4. Stack Overflow.
5. Could not start processing services.
6. Invalid Stack Fault in OLE32.DLL
The last error message might occur when you try to open Microsoft Outlook with journaling enabled...
Posted on Tuesday, November 03, 2009 at 9:33 PM
Circular logging is a Exchange Server feature that implements recycling of logs. Microsoft Exchange Server writes the data to be committed to the database in transaction logs before actually writing it. If circular logging is enabled and four logs have been filled, it assumes that the first log as committed and thus, recycles the logs in order to save disk space. But it comes with a major flaw that prevents disaster recovery. If the database is corrupted while the feature is enabled, Exchange can only restore as far as the last backup is available. In case a suitable backup is unavailable, you are suggested to opt for Exchange Repair
solutions that are powerful and safe too at repairing a corrupted Exchange database.
For example, you observe an unexpected shutdown with an Exchange database. After this, when you try to start it, an 'JET_errFileNotFound' error is displayed with a numerical value, such as 4294965485, -1811 or 0xfffff8ed. When you view the application event log, it shows events 1120 and 5000...
Posted on Tuesday, November 03, 2009 at 5:26 AM
Transaction log files is the disaster recovery method used by Exchange Server to bring its databases to a consistent state post crash. The current transaction log data for a database is stored in E##.log file, which is further renamed to E#######.log when reaches to 5MB in size. The '##' is basically the storage group identifier. Thus, for first storage group, the file is E00.log. The file may go missing or get corrupt It generally occurs because of antivirus scanning and can render the databases unmountable as a consequence. At this point, you should remove all the transaction log files from the root folder and try to mount the database. If the problem continues, Exchange database corruption might be the reason. So, you need to use Exchange Recovery
solutions to repair and restore the files.
For instance, when you try to mount a mailbox or public store of Exchange Server 2000 or 2003, the operation might fail. When you view the application event log, you may come across events 9518 and 455...
Posted on Wednesday, October 28, 2009 at 11:14 PM
An Exchange public store or mailbox store of a storage group can be mounted using Exchange Management Console or Exchange Management Shell. This makes the databases ready for use. For any reason, if the process fails, it leads to data inaccessibility. Database mount failure primarily suggests that one or more storage group components are faulty. However, if one or more databases are corrupted, you should use eseutil utility to repair it. Alternatively, you can apply the last good backup or use a powerful EDB Repair
utility to repair the corrupted database.
For instance, suppose you try to mount public or mailbox store in Exchange Server. The operation fails and the application event log reports the below information message:
Event ID: 465
Information Store (2184) Corruption was detected during soft recovery in logfile C:\Programme\Exchsrvr\mdbdata\E00000E8.log. The failing checksum record is located at position 6531:471. Data not matching the log-file fill pattern first appeared in sector 6600. This logfile has been damaged and is unusable...