Creating backup of Exchange Server database is a very common practice for database administrators. It helps them in restoring the database if any kind of data loss, corruption or other errors occur. But sometimes, after restoring your database from backup, you may find it difficult to access data from it.
One such scenario occurs when you try to start directory server in Exchange Server after restoring from backup. When you try to do this, you may encounter the following error message:
“Error 1067. The process terminated unexpectedly.”
Along with this error message, the following event entries might appear in the Application Even Log:
Event ID: 124
Source: ESE97
Description: MSExchangeDS ((1432 ) ) Unable to read the log header.
Error -530.
Event ID: 1196
Source: MSExchangeDS
Description: Couldn’t recover the restored Microsoft Exchange Server
database (EDB). Cannot continue. Error c8000212.
After this error message, you can not access anything from your Exchange Server database and may fall in need of Exchange Server recovery.
Reason of this issue
This problem generally occurs when Edb.log file, which is created while performing restoration from backup, interfaces with recovery process. It occurs on recovery server.
Due to this problem, the recovery process could not be completed successfully and you might face this behavior of Exchange Server. It cause complete inaccessibility of Exchange Server database.
Work around
To fix this problem, manually delete the existing data from the Dsadata folder before starting restore operation from the backup. It will delete Edb.log file.
Though, it could fix the issue, but it is not a safe method. Deleting Edb.log file might introduce severe errors in the Exchange Server database and may corrupt it.
EDB corruption is the worst scenario for a database user and it might put him/her in need of exchange server repair. Exchange Server repair can easily be carried out using Exchange Server recovery software.
Stellar Phoenix Mailbox Exchange Recovery software is the best ever made Exchange Server repair software to work around all the corruption issues. Using this Exchange Server recovery software, you can perform easy, quick and absolute Exchange Server repair. Phoenix Exchange Server Repair is applicable to all the Exchange Server file versions.
Exchange Server Database Corruption Due to “Error 1067”
Error -1216 in Exchange Server and EDB Recovery
“Error -1216 (JET_errAttachedDatabaseMismatch)”
It is the most common Jet error in Microsoft Exchange Server. Error -1216 shows that the Exchange Server has determined that the files in Exchange Server database’s running set are lost or they have been reinstated with the different file versions.
Error -1216 could also be symbolized hexadecimally as ‘0xfffffb40’. When the error takes place, the Exchange Server aborts the soft recovery of EDB file before doing some changes to database, which may prevent re-integration of missing database files with data set.
When this error takes place, you should attempt to restore the missing database files. When these files are not available, you could use Eseutil for overriding the error and go on with software EDB recovery.
Error -1216 is caused when the comparison of header information in database and the log files shows that the removal or replacement of some critical files has been done. This error message may cause data loss, if the administrator run the soft recovery.
Grounds of the trouble
This problem occurs due to the inconsistency of the database, which might occur due to unexpected shut down of the Exchange Server or the Storage Group service has been stopped improperly. You may find the following entries in the Application Event Log, when the Exchange Server was stopped abnormally:
“Event Type: Error
Event Source: ESE98
Event Category: Logging/Recovery
Event ID: 0
Date: 4/24/2001
Time: 6:20:18 PM
User: N/A
Computer: EXCHANGE1
Description: Information Store (4312) Database recovery failed with error -1216 because it encountered references to a database, ‘D:\exchsrvr\mdbdata\PRIV2.edb’, which is no longer present. The database was not brought to a consistent state before it was removed (or possibly moved or renamed). The database engine will not permit recovery to complete for this instance until the missing database is re-instated. If the database is truly no longer available and no longer required, please contact PSS for further instructions regarding the steps required in order to allow recovery to proceed without this database.
Nevertheless the cause of this issue, the database inconsistency will ultimately cause EDB corruption and finally the data loss. In such circumstances, you need to perform Exchange Server recovery to recover your lost data. It is feasible using good EDB repair software such as Stellar Phoenix Mailbox Exchange Recovery.
Phoenix Exchange Server repair is extremely powerful EDB recovery product to handle EDB corruption scenarios. It can perform Exchange Server recovery for all of the EDB repair objects including emails, notes, contacts and so forth. Phoenix Exchange Server repair is applicable to all file versions of Microsoft Exchange Server including Exchange 5.5, 2000, and 2003.
EDB Corruption When Defragmentation Fails
Microsoft Exchange Server runs a defragmentation process to rearrange the mailbox store and public folders and stored data more competently, eradicating unused storage space.
You could use Eseutil utility for defragmenting the Exchange Server database. It examines the basic structure of the database and rearrange them. It is required for better performance of the database.
Sometimes when you defragment the database, the process fails half-way though. After the process gets halted, you get a temporary file of Priv1.edb. When you rename this file, it gets disappeared. In such situations, the Mailbox store gets corrupted and you can not mount it. In this case, when you use the Eseutil /MS (to dump the space usage), the operation gets terminated with the following error message:
“Error -2211 (JET_errSLVHeaderCorrupted, SLV file header contains invalid
information)”
After getting this corruption error message, when you use Eseutil /P to repair the database, you will get the further error message stating:
“Checking database integrity. Operation terminated with error -1206 (JET_errDatabaseCorrupted, Non database file or corrupted db) after 1.912 seconds.”
This behavior results into the inaccessible Exchange Server database. You can not retrieve even a single bit of data from the database and you may fall in the grave situations of data loss.
Cause
As stated in the above error message, this problem takes place due to damaged Exchange Server database. The database corruption could be the possible result of unexpected system shutdown, virus attack, oversized EDB file and so forth.
It does not matter what the reason of data loss is. The only thing which matter is how to retrieve your precious data? The answer of this question is Exchange Server recovery.
Exchange recovery is the process of repairing the damaged database with the help of EDB recovery software and restore it. EDB recovery software are easy to use tools, which help you in all cases of EDB corruption and can recover all of the EDB objects.
Stellar Phoenix Mailbox Exchange Recovery is the most advanced Exchange Server repair software. It supports EDB repair from Exchange Server 5.5, 2000, and 2003. It systematically scans the entire database and ultimately gives you fruitful results of Exchange Server recovery.
Error While Moving Exchange Server Mailboxes
MS Exchange Server is a server application which retains users’ data in the form of mailboxes, which all are stored in Mailbox Folder. Mailbox Folder is comprised of two main files: Priv1.edb and Priv1.stm. Priv1.edb is the database file which contains all the e-mail messages, message headers and attachments, whereas, Priv1.stm is a streaming file and contains all the multi-media data. Corruption of EDB creates needs of EDB Repair.
Using Move Mailbox Wizard, MS Exchange Server allows moving mailboxes within any versions of MS Exchange, MS Exchange Server 5.5, 2000 and 2003, under a condition that they should be within same Exchange organization. But, when the user tries to move mailboxes from Exchange Server 5.5 to Exchange Server 2000, the process may fail with the following error message:
Error: Moving messages
CN=TestUser,CN=Users,
DC=Machine,DC=Company,DC=Com:
The MAPI call failed.
MAPI or an unspecified service provider.
ID no: 80004005-0000-00000000
Viewing Application log of Exchange Server 2000 shows that the application is failing to move some of the mailboxes. The problem is associated with few of the mailboxes which contain corrupt messages, stripped or disassociated attachment. In case of corrupt messages in mailboxes, EDB gets corrupt and needs exchange server recovery. When we click the messages of mailboxes, which contain the disassociated or stripped attachments, some error messages are encountered which states that attachment can’t be opened or access is denied.
* In order to resolve this issue, we need to permanently delete the message using SHIFT+DELETE or simply deleting the message and emptying the Deleted Items folder.
* If corruption is high, we need to repair EDB as a whole using Eseutil utility or EDB Repair software. Eseutil deletes the corrupt pages from corrupt database; however, this is safe to use EDB Recovery software which apply safe, yet powerful scanning algorithms to extract lost information from corrupt database.
Stellar Phoenix Mailbox Exchange Recovery is a powerful EDB Repair application which is compatible with Exchange Server 5.5, 2000 and 2003. This EDB Recovery software has interactive interface and restores recovered mailboxes in PST format, usable with MS Outlook. The application can recover all the database objects.
What is the meaning of 1216 error in Exchange Server and how to recover?
In Microsoft Exchange 1216 error is the most common error. This error shows that the Exchange server has determined that the files in Exchange Server database’s running set are lost or they have been reinstated with the different file versions.
Sometimes this error 1216 shows in hexadecimal like “0xfffffb40”. When the error generates, Exchange Server aborts the soft recovery of EDB file before doing changes to database.
This error may be occurring due to problem in the database or comparison of header information and the log files shows that the removal or replacement of some critical files has been done.
This error will damage your edb file and finally the loss your important data. But you don’t have to worry because you can recover your edb file through software such as Stellar Phoenix Mailbox Exchange Recovery.
Through Exchange Recovery software, you can recover your corrupted or damaged edb files of Microsoft Exchange Server. This software is extremely powerful product to handle edb corruption scenarios. This will repair all your emails, contacts, notes, and it will also recover RTF and HTML messages. This software will restore mailboxes in PST format. Exchange Recovery is very easy to use and also user friendly. One of the best thing in this software is that its support exchange server 5.5, 2000 and 2003 and its compatible with Windows 2000, XP and 2003.
EDB Corruption and Access Problems in Exchange Server
Sometimes when you retrieve your data from exchange server, the process mail fail and at the same point you are getting an error message as given below:
“Access denied to database Mailbox Store (SERVER2K3).
WARNING: “\\SERVER2K3\Microsoft Information Store\First Storage Group\Mailbox Store (SERVER2K3)” is a corrupt file.
This file cannot verify.
Database or database element is corrupt”
In this case, its mean you lost your important data. The error message may occur due to one of the following reason:
1. You don’t have required permissions to access the database
2. Some of important Exchange Server files such as user permissions file go missing
3. Exchange Server database is corrupt and data can not be accessed from it
If you want to fix this problem, then you have only three options:
1. You have appropriate permission from the administrator and then try again.
2. You can repair your Exchange Server.
3. Repair Exchange Server database using Eseutil.exe tool
EDB corruption is one of the most critical situations and should be repaired. Eseutil.exe is an inbuilt Exchange Server utility that can verify and then repair the .edb files. But if you want to fix the errors or edb corruption then you have to go for EDB Recovery
Exchange Recovery Software recovers corrupted or damaged edb files of Microsoft Exchange Server. Stellar Phoenix Mailbox Exchange Server can recover all your emails, notes, contacts, journal, calendar entries and many other things from the corrupted edb files.
One of the best things in this software is that it supports Exchange Server5.5, 2000, and 2003. EDB recovery software is very user friendly and easy to use. Phoenix EDB Recovery software is compatible with Windows XP, 2003 and 2000.
EDB Corruption After Upgrading to Exchange Server 2000 SP3 or Later
Microsoft Exchange Server is the most important application to create a collaborative messaging environment. It stores all of the critical user information in Exchange Server Public Information Store. The Exchange Server database contains a separate mailbox for every user and an exact copy of the mailbox is stored on the user hard drive in the form of OST file. In some cases, the Exchange Server database may get damaged due to virus attack or other similar reasons and you need to opt for Exchange Recovery to sort out this scenario.
Sometimes, when you attempt to mount the Exchange Server database (EDB file), you might come across any of the following events in the Application Event Log of Exchange Server:
Event Type: Error
Event Source: ESE
Event Category: General
Event ID: 505
Description: Information Store (2028) An attempt to open the compressed file “drive:\Exchsrvr\MDBDATA\priv1.edb” for read / write access failed because it could not be converted to a normal file. The open file operation will fail with error -4005 (0xfffff05b). To prevent this error in the future you can manually decompress the file and change the compression state of the containing folder to uncompressed. Writing to this file when it is compressed is not supported.
Or
Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Event ID: 9519
Description: Error 0xfffff05b starting database “First Storage Group\Mailbox Store (EXCHANGE)” on the Microsoft Exchange Information Store. Failed to attach to Jet DB.
This issue generally occurs when you upgrade to Exchange Server 2000 Service Pack 3 or later and the Information Store database is compressed using NTFS (New Technology File System) file system compression. Under some situations, NTFS compression may damage the Exchange Server database like when the EDB file exceeds 4 GB size. In such cases, Exchange Repair is required to work around the issue.
Exchange Server 2000 Service Pack 3 and later do not allow NTFS compressed information store to mount. The files are managed by Extensible Storage Engine (ESE) that needs sector independence for log-based recovery that is not allowed in compression.
This entire behavior of Exchange Server corrupts the EDB file and you are required to repair and restore is using Exchange Recovery software to access your critical data. These software can recover all of the Exchange Server database objects.
Stellar Phoenix Mailbox Exchange Recovery is the most advanced Exchange Repair software that works in most of EDB corruption cases. It works well with Exchange Server 2003, 2000 and 5.5. This software is compatible with Microsoft Windows 2003, XP and 2000
Exchange Database Doesn’t Mount After Installing SP3 or Later to Exchange 2000
Exchange Server public information store database contains all the user mailboxes, apart from the information which is required in Exchange Server environment and thus is considered most important. However, Information Store also comprises one another database called Public information store database, which manages data in public folders. Exchange database corruption requires Exchange Server Software.
In some of the cases, user may fail to mount the information store database and encounter an event in the application log of Event Viewer:
Event Type: Error
Event Source: ESE
Event Category: General
Event ID: 505
Description: Information Store (2028) An attempt to open the compressed file “drive:\Exchsrvr\MDBDATA\priv1.edb” for read / write access failed because it could not be converted to a normal file. The open file operation will fail with error -4005 (0xfffff05b). To prevent this error in the future you can manually decompress the file and change the compression state of the containing folder to uncompressed. Writing to this file when it is compressed is not supported.
Or
Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Event ID: 9519
Description: Error 0xfffff05b starting database “First Storage Group\Mailbox Store (EXCHANGE)” on the Microsoft Exchange Information Store. Failed to attach to Jet DB.
This problem is specifically encountered when user upgrades to Exchange Server SP3 or later. If the information store database has been compressed using NTFS file system compression.
Note: NTFS compression can corrupt Exchange database under critical situations like when the information store reaches to about 4 GB in size, in which Exchange Server Recovery is required.
Exchange Server SP3 and later versions, including Exchange Server 2003 don’t allow NTFS compressed information store to mount. These files are managed by ESE (Extensible Storage Engine) which require sector independence for log-based recovery process, which is not allowed in compressed files. Thus database corruption may result, specifically in database files, larger than 128 MB, which require Exchange Server Repair. Files, smaller than 128 MB, are automatically decompressed in Exchange Server SP3 and later.
In order to resolve the issue, we need to decompress the folders of Information store databases and logs after dismounting the database. Then, we need to carry out offline defragmentation using eseutil /d command and mount the database again. If the database comes out to be corrupt, we need to apply Exchange Server Repair or else perform the online backup of the database.
Exchange Server Recovery can be performed using Eseutil utility, but the corrupt pages will be deleted. So using commercial Exchange Server Repair software can be used which apply powerful, yet safe, scanning algorithms to repair the corrupt database.
Stellar Phoenix Mailbox Exchange Recovery is an excellent Exchange Sever Recovery software which is compatible with Exchange Server 5.5, 2000 and 2003. This Exchange Server Repair software has interactive interface and recover mailxes in PST format, usable with MS Outlook.
EDB Recovery after Corruption to the Database Elements
Microsoft Exchange Server is an important part of a collaborative and messaging environment. Due to the importance of Exchange Server database and stored data, you should regularly back it up. But in some situations, when you attempt to backup EDB (Exchange Server Database) file, the process gets terminated halfway due to corruption to EDB file. In such cases, you need to first perform Exchange Server Recovery to sort out the issue to gain access of your mission critical data.
Sometimes when you attempt to create backup of Microsoft Exchange Server database, which is damaged and inaccessible, you might come across the below given error message:
“Database or database element is corrupt”
Furthermore, with this error message, you might also get a statement, which states that this file can not be verified. Due to corruption, the Exchange Server can not recognize the database and thus can not access it. At this point, you need to identify the cause of data loss and carry out Exchange Server Repair by sorting it out.
Root of the issue
As stated in the above error message, this situation occurs due to corruption to the EDB file. The corruption could be the possible result to virus infection, accidental system shutdown, application errors, operating system malfunction and other similar reasons.
Resolution
In order to fix this issue, you should go for Eseutil/p utility. This is an inbuilt tool in Microsoft Exchange Server that is used to repair damaged EDB file. This tool scans the damaged database and can repair in a number of cases.
Although, this utility is helpful in resolving this error message, but it also has a downside. It deletes all of the database elements that are not recognized by this tool. This behavior of Eseutil tool cause critical data loss situations and make your data permanently inaccessible. To safely retrieve your critical data, go for advanced and powerful Exchange Server Recovery software.
These software are particularly designed to safely, smoothly and thoroughly scan entire database and retrieve all of the inaccessible database objects. These software use efficient and powerful scanning algorithms to achieve perfect Exchange Server Repair. With interactive and simple graphical user interface, such applications are easy to use and do not require sound and prior technical skills.
Stellar Phoenix Mailbox Exchange Recovery is the most advanced and effective software that can handle all EDB corruption scenarios. It can repair and restore damaged EDB file of Exchange Server 2003, 2000 and 5.5. This software is compatible with Windows 2003, XP and 2000.
