Windows Forum

Ask something
Discussion Locked

exchange info store not starting

0 helpful
6 replies

by rg11 1 view

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have exchange 5.5. We run Veritas backup every night. Out of the blue, after the backup is done the exchange info store and event service wont start up. I have to start them manually.
The event log has ID 145, source ESE97. MsexchangeIS(485) database engine could not access the file c:\exchesrvr\mdbdata\priv.edb.
Then event 1120, source msexchangeIS, Error Non-database file or corrupted database initializing the exchange server info store database.
Then Event 132, source ESE97, MSExchangeIS(347) unable to read header of database C:\exchsrvr\mdbdata\priv.edb error 1032 database may have been moved.Recovery will continue with database in new location.
Then event 1120, error 0xfffffbf8 initializing the ms exchange server info store database.
I checked the permissions on the exchsrvr folder and ran the diagnostic on the database and it was fine. Any thoughts.

6 replies

by rg11

Yes we have enough room, and we have also ran the eseutil/P. About a year ago we added a drive then about 5 months ago we moved the data base to this new drive and all this started about 1 month ago...

by derek

Were any settings changed in Veritas - is it scanning the edb files?
From the error, your system seems to be looking in C:\exchsrvr\mdbdata\ for priv.edb. Yet you said that you had moved the files to new Drive? As per previous poster, check the location of the databases.

by steveharman11

The Error "Non-database file or corrupted database initializing the exchange server info store database." that is being experienced enumerates the possob;ity iof the corruption took place in the Microsoft exchange databse file due to which such issue is getting encountred so frequently . The inability of the system to read or recognize the database header is also one of the symptoms of the dtaabase file corruption thus it means that the EDB file of the Microsoft exchange server database file is entirely got corrupted. However you are still able to have the data that are compiled in the exchange database file are able to get retrieved using [url="http://www.edbrepair.org"]EDB repair[/url] software that is built with high end recovery mechanism and lets ti recover the data back with quick scanning processing.

http://www.edbrepair.org

This discussion is closed to new replies.