Exchange 2003 - cannot mount information stores

Hi

Need some advice. Server crashed last night and upon restarting this morning, no email.
Event logs show that information store is not being mounted, ala :

"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 "

I can start the Microsoft Exchange Information Store service, but from the server management console, I cannot mount the stores as the option to mount is greyed out.  Had issues once befopre on this server a year ago and resolved by restoring exchange store from backup and running eseutil and isinteg.  But the the event log messages are different this time and the backup is 5 days old so I don't want to run the restore to find the issue is something different than a corrupt store.

This server is a single domain controller.

I'm fighting the clock here as I know these repair utilities can take all night to run, if it needs to be done then I want to run it immediately, but want to take onboard your opinions first.

Thanks
eMicros
eMicrosAsked:
Who is Participating?
 
Mehmet MuhannaConnect With a Mentor Senior System EngineerCommented:

The Event you write is allways shown in Evenlog when your database is NOT mounted,
you will need to search for more
Anyway
your Database seem to be Dead
http://www.computerperformance.co.uk/exchange2003/exchange2003_eseutil.htm 
This help is greate
After you Recover your Emails, make sure that you create a new mailbox Store and move all the Emails to it and remove the database and then restart your server
 
0
 
eMicrosAuthor Commented:
Just restarted server, now have the option to mount the stores, and mounting both throws up the error that the store is corrupt.  So here goes the restore ...
0
 
Mehmet MuhannaSenior System EngineerCommented:
HI
Run ESEUTIL /P for the database
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
eMicrosAuthor Commented:
I have copied the priv1.edb and priv1.stm to a separate folder and run the following command :

"eseutil /p priv1.edb /s priv1.stm /t temp.edb"

the log files are not in the same directory. should i run this command with the logfiles in place?  its about 10% through, if i do need to run with log files in place, can i stop and rerun it?

Was planning on next  running :

"isinteg in -fix -test alltests mode" command next.

I know last time i did it it repaired the database and rolled forward the changes in the log file but i cant remember my exact commands. any help appreciated.
0
 
eMicrosAuthor Commented:
Perhaps when the repair is completed, i can move the database files into the folder with the logfiles and run eseutil /r ?
0
 
eMicrosAuthor Commented:
I've fixed this now as follows :

1. eseutil /p priv1.edb (& later pub1.edb),
2. eseutil /r E00 /i (not sure this was necessary but output from previous command suggested it)
3. eseutil /d
4. delete all the log files in the store directory
5. isinteg -s servername -fix -test alltests - and choose the relevant production databases listed (re-run command for each required)
6. mount stores from server management console

It's all working and reports db is good and has no errors.  

Housammuhanna: you mentioned creating a new store and moving all emails into it.  how would you go about this?
0
 
Mehmet MuhannaSenior System EngineerCommented:
Right Click on the server object and select Create New StorageGroup
Set the pathes for it
and then in the new storage Group Right Click on it and select New Mailbox Store
Set the pathes for it
and now mount the database
Right Click on Mailboxsobject in the Old  Database and select Exchange Task , then Select Move Mailbox
Select the target the new database and start moving
 
0
 
eMicrosAuthor Commented:
ok, thanks.  Why is this necessary? Seems like an excercise in renaming the storeage group, unless it physically carries out some repair tasks?
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.