This concerns one of our databases on our Exchange 2007 server.
I am having difficulties mounting a datbasase on our Exchange 2007 server.
This database has been successfully repaired by using eseutil /p as shows the following output:
"Operation completed successfully with 595 (JET_wrnDatabaseRepaired, Database corruption has been repaired) after 218.484 seconds".
After this repair I have tried to run an isinteg -fix but his returns the following error in the command prompt window:
"Isinteg cannot initiate verification process.
Please review the log file for more information".
The strange thing is that the Isinteg log file is not being created at all.
I tried mounting the database but this throws the following error back in the Exchange Management Console:
"Failed to mount database 'MBX1.
Exchange is unable to mount the database that you specified. Specified database: EX1\SG1\MBX1; Error code: MapiExceptionJetErrorNoCurrentRecord: Unable to mount database. (hr=0x80004005, ec=-1603)".
The eventlog shows the following events:
9518 and 9519
Description:Error 0xfffff9bd starting Storage Group "storage group path" on the Microsoft Exchange Information Store.
MDB failed to start.
Description:Error 0xfffff9bd starting database "SG1\MBX1" on the Microsoft Exchange Information Store.
I have troubleshooted this with the following KB article: http://support.microsoft.com/kb/932599
Even though the article refers to Exchange 2000 and 2003.
There are no well known SIDS specified as Exchange (organization) Administrators or (other Exchange Administrators for that matter) and the checkbox "Allow inheritable permissions from the parent to propagate to this object and all child objects" has been ticked.
Can somebody assist in answering the following questions:
- Why does Isinteg not create a log?
- Is the article mentioned applicable to Exchange 2007 also?
- What could be the reason for the database not mounting?
Express yourself instantly with MSN Messenger! MSN Messenger