In Microsoft Exchange Server, each database, log or checkpoint file starts with a 4-KB header. The file header contains its configuration and identification data. Unlike log file headers, the database (*.edb) and checkpoint (*.chk) headers are constantly updated while normal operations. There is one more header called ’shadow header’ that is identical to primary header, lying next to it. This header safeguards the primary header while updates as modifications are first made to shadow header page prior to primary header. So, if a crash occurs before the updates could finish, the primary header still remains intact. But some factors can prevent the write operation to be performed to database files, resulting into an error described below. To resolve the issue, you may need to repair the unmountable database using eseutil repair utilities. However, you can also opt for safe and better alternative of using EDB Recovery software.
For example, you might receive the below error when mounting or using an Exchange Database:
“Unable to write a shadowed header for the file.”
The error is marked with event 439 in application event log.
Cause
The above error indicates access-denied condition. This is because the shadow page is the first header page that is updated. At this point, the database service stops in order to preserve database integrity. The Exchange database engine is denied to write data to its own EDB or CHK files due to one of the possible reasons:
-
The file is in use by another process. In this case, you usually get -1032 error.
-
The root folder permissions have been removed.
-
The file is read-only. It generally occurs with *.chk files.
-
The drive cannot be accessed because of disk or controller failure.
-
The root folder of files has been either deleted or renamed.
Solution
You need to apply one or more of the below steps:
-
Check the application and system log for disk capacity issues and resolve them
-
Restart the Exchange computers
-
Check for sufficient disks’ access
-
If database is running, move its mailboxes to another server using Move Mailbox command
-
If the database cannot mount, consider one of the methods:
- Restore from backup
- Run eseutil /p and isinteg -fix commands to repair the database. Use ExMerge to a new database
- Repair the database using EDB Recovery Software. These special tools can perform safe and quick EDB Recovery using advanced scanning algorithms.
Stellar Phoenix Mailbox Exchange Recovery is a reliable and efficient utility to repair a corrupted Exchange database created with Exchange Server 5.5, 2000 and 2003. The powerful EDB Recovery Tool can restore individual mailboxes in .pst files, without changing their contents. The software is known for best database repair results.
Website Development India, Outsourcing Website Development India, Offshore Website Development India – Dreamz Net Solutions is a Website Design Company, Website Development Company & Professional Web Designing Company in Mumbai providing customized Website Designing Services & Website Development
