asked on

ISINTEG cannot initiate verification process

We have an exchange 2003 SP1 server running on Virtual Machine software. Unfortunately the Virtual Machine crashed. After restarting the Exchnage server the exchange server mailbox store and public store won't mount.

I have run eseutil /P and eseutil /D without any problem. Both finished without an error. After entering the isinteg -s servername - fix -test -alltests it tells me "ISINTEG cannot initiate verification process"

Checking the logfile tells me the following :

1) Event Type:      Error
Event Source:      ESE
Event Category:      Logging/Recovery
Event ID:      494
Date:            11/22/2005
Time:            1:19:15 AM
User:            N/A
Computer:      EXCHANGE2003
Description:
Information Store (3548) First Storage Group: Database recovery failed with error -1216 because it encountered references to a database, 'D:\Program Files\Exchsrvr\MDBDATA\priv1newloc.edb', which is no longer present. The database was not brought to a Clean Shutdown 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.

F.Y.I : Strange enough the database file is in the exact location as the filepath mentioned above be it a lille smaller since it has been succesfully defragged.

2) Event Type:      Error
Event Source:      ESE
Event Category:      Logging/Recovery
Event ID:      454
Date:            11/22/2005
Time:            1:19:15 AM
User:            N/A
Computer:      EXCHANGE2003
Description:
Information Store (3548) First Storage Group: Database recovery/restore failed with unexpected error -1216.

F.Y.I : This error is logged directly after the error mentioned under point 1)

3) Event Type:      Error
Event Source:      MSExchangeIS
Event Category:      General
Event ID:      9518
Date:            11/22/2005
Time:            1:19:15 AM
User:            N/A
Computer:      EXCHANGE2003
Description:
Error 0xfffffb40 starting Storage Group /DC=nl/DC=beers/CN=Configuration/CN=Services/CN=Microsoft Exchange/CN=Scania Netherlands/CN=Administrative Groups/CN=First Administrative Group/CN=Servers/CN=EXCHANGE2003/CN=InformationStore/CN=First Storage Group on the Microsoft Exchange Information Store.
Storage Group - Initialization of Jet failed.

4) Event Type:      Error
Event Source:      MSExchangeSA
Event Category:      MAPI Session
Event ID:      9175
Date:            11/22/2005
Time:            1:19:30 AM
User:            N/A
Computer:      EXCHANGE2003
Description:
The MAPI call 'OpenMsgStore' failed with the following error:
The Microsoft Exchange Server computer is not available. Either there are network problems or the Microsoft Exchange Server computer is down for maintenance.
The MAPI provider failed.
Microsoft Exchange Server Information Store
ID no: 8004011d-0526-00000000

5).Event Type:      Error
Event Source:      MSExchangeSA
Event Category:      MAPI Session
Event ID:      9175
Date:            11/22/2005
Time:            1:20:26 AM
User:            N/A
Computer:      EXCHANGE2003
Description:
The MAPI call 'OpenMsgStore' failed with the following error:
The Microsoft Exchange Server computer is not available. Either there are network problems or the Microsoft Exchange Server computer is down for maintenance.
The MAPI provider failed.
Microsoft Exchange Server Information Store
ID no: 8004011d-0526-00000000

-----------
Any help would be much apprecited since I have no clue on how to proceed from here.

ASKER CERTIFIED SOLUTION

stafi

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

SOLUTION

Exchange_Admin

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

ns8matrix

ASKER

I managed to solve it by throwing away all transaction logs relating to the repaired database. Then I defragged the Virual Machine and then mounted the database and everything worked just fine.

granthb

Change the solution to the author comment. That saved my butt!!!!!!!

eMicros

Thanks a lot. I repaired my private and public databases using eseutil /p as both were corrupt. defragged them both with eseutil /d. all reported that everything was ok but could not mount them and running isinteg came back with the error reported by the original poster of this thread. And he's right, moving the logfiles out of the store folder allowed isinteg to complete and the exchange stores to mount. Good work fella ...

Exchange_Admin

The reason is that when you run a defrag on a database, the past logfiles are no good. The log files have a database ID written into them when they are generated. When you run a defrag of a database, a new database ID is created. Hope this helps.

rushnowinc

I ditto exactly what eMicros says. Of all the noise out there on Exchange corrupted databases and using ESEUTIL and ISINEG, this post helped me the most and I am back up. Thanks!

sgt_best

Thanks so much. Deleting the ALL of the log files from the MDBDATA folder allowed me to mount the databases. I'm up!