hard shutdown leaves problems

[bbxrider]

sbs2003 exch 6.5
the server had power outtage and the apc didn't bring it down softly
had to reinstall iis, that seems to be ok, at least websites are coming up but exchange is not coming up, i've been down a lot of roads and not getting too far, hoping for some help or ideas to try

-the ms exch information store starts

-i cannot mount either the public store or mailbox store (mapi call 'openMsgStore' failed-the ms exch computer is not available.....id no:8004011d-0526-00000000) this msg comes up every minute in the application log, even when i pause the ms exch information store service. this exchange is on the local server

-best practices report has 1 critical, see below and i can't seem to find anything about addressing it other than it happens where upgrading from 2003 to 2007
Server PMCC-SERVER is a routing group master but a connection to port 691 cannot be established from the workstation where this tool is running.

- the trouble shooting assitant reports that both the public store and private store have a clean shutdown. i tried to also run eseutil, but keeps giving the callback error, i have the same jcb.dll in the bin and sys32, its version 6.5.7638.2, aarghhhhhhhhhh

- when i try to run isinteg, i get: 'Isinteg cannot initiate verification process. Please review the log file for more information' - but there is no log file, in the bin or mdbdata directories, aarghhhhhhh

-i did get a priv1+pub1.integ.raw files in the bin folder. they have dirty shutdown messages, and lots of dbtime is larger database dbtime messages, like thousands of those

i did not set up this sbs2003 and exchange so i very leary about a starting over

 

[bbxrider]

an update, i was able to run eseutil /mh on both priv1 and pub1 edb's (and not the callback error) and it reported clean shutdown and 0 errors in all categories for both db's.
so it appears i have good db's, and hope this narrows the scope of what the problem may be

 

[xmsre]

http://support.microsoft.com/kb/248122/en-us

 

[bbxrider]

thanks for the reply
ok it looks as if the log file check from that link passed ok as well. i ran the /ml check on the e00.log and the this is the summary of that:
Integrity check passed for log file: c:\program files\exchsrvr\mdbdata\e00.log

Operation completed successfully in 1.0 seconds.

so again hopefully this narrows the problem even more?

if nothing suitable comes up to fix the current problem, can i try a fresh install/setup of exchange and have my users restore their history from their full .pst file backups?

 

[58sniper]

a restore from tape would be better than trying anything with .pst files, IMNSHO.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.ucblogs.net/blogs/exchange/

 

[xmsre]

You have three components; the database, the logs, and the checkpoint.

database - ok
logs - ok


what about the checkpoint?

read "Roll Forward Restoration of an Offline Backup"

in

http://support.microsoft.com/kb/296788

So, if the db is ok, and all the logs are there undamaged and no gaps, you could remove the chk and replay them all. Obviously, backup everything first.