I've got an Exchange 2003 SP2 server running on Small Business 2003. This morning I had one of my disks in my RAID array go belly up and it seems to have thrown some things through a loop. After getting the system operational again I'm finding this error: "Faulting application store.exe, version 6.5.7654.12, faulting module store.exe, version 6.5.7654.12, fault address 0x000289ab." I've run eseutil /k on both my pub and private stores and they both check out without problems. I've applied a couple of hotfixes: 944254,933398 I cannot find anything via google on that fault address listed. I've also tried to restore 'store.exe' from a backup as of this past Sunday night to no avail.... I am running Trend Micro Worry Free Business Advanced 5.0 (with all their latest hotfixes). Even shutting down those services have not seemed to help.

Do you have a good Exchange aware backup of the info store?Any other errors in the event logs System or App?When the disk failed, were you able to gracefully stop the Info Store service? Can you remove the Trend product?Any other 3rd party apps installed or running?

Do you have a good Exchange aware backup of the info store? Any other errors in the event logs System or App? When the disk failed, were you able to gracefully stop the Info Store service? Can you remove the Trend product? Any other 3rd party apps installed or running? When the disk failed (right before I walked into the office) the machine was frozen. So it's likely it didn't stop gracefully. The errors are logged under 'Applications". As far as a backup goes, I'm using SBS2003's integrated "NTBackup", which is apparently exchange aware but I cannot restore the store because I cannot start the Information Store service. There are other errors, like ID 8197 "Error initializing session for virtual machine DHL2003. The error number is 0x8004011d. Make sure Microsoft Exchange Store is running. " I can remove the Trend product if needed. Though I think I'll need to do this at off hours (which puts me in a pickle to get our email back up).

Ok, Since this is a server down issue, I am hesitant to have you go through a lot of motions that may not produce anything valuable. I only mention the Trend piece because AV software is always a potential cause of this error, though I doubt it in this case given the crash. You may be looking at a reinstallation of Exchange in disasterrecovery mode and then restoration of the store from backup and log replay to get to the point of failure. Its pretty trivial with a stand-alone Exchange 2003 server, but SBS2003 is a different beast at times. I would suggest asking in a SBS2003 forum if you want togo withthe disasterrecovery route or callMicrosoft support since forums such as these arent always the best way to handle a situation like this.

Ok, Since this is a server down issue, I am hesitant to have you go through a lot of motions that may not produce anything valuable. I only mention the Trend piece because AV software is always a potential cause of this error, though I doubt it in this case given the crash. You may be looking at a reinstallation of Exchange in disasterrecovery mode and then restoration of the store from backup and log replay to get to the point of failure. Its pretty trivial with a stand-alone Exchange 2003 server, but SBS2003 is a different beast at times. I would suggest asking in a SBS2003 forum if you want togo withthe disasterrecovery route or callMicrosoft support since forums such as these arent always the best way to handle a situation like this. I was just about to try to do an exchange reinstallation but it won't let me with mailboxes on the system. I'm about to try a /disasterrecovery just on SP2. I guess we'll see. I have removed the Trend software from the system, however since the store isn't active it could not remove the store scanning agent it installs. *Edit: /disasterrecovery on SP2 didn't help.

To further add to this, I've since then 'reinstalled' Exchange 2003 w/ SP1 and then applied SP2 on top of it, however the same problem exists. The only thing I have not done since then is restarted the server (as people are using the SQL database).

Hi Ryan. You may have some storage corruption. But its hard to say from here. I would recommend calling Microsoft support since you have a server down.

I am awaiting a callback from MS as we speak.

Ok, please let us know how it goes!

Ok, please let us know how it goes! This rep is nice, but it's hard to understand him (as I thought it would be). He's patient and repeats himself though, so I'll give him the benefit of the doubt.

OK MS Support was a pretty big help. He had me reinstall Exchange SP2, but then we had to manually replace the store.exe with the SP2 version since it wasn't being overwritten by the installer. The rep said mad.exe and store.exe versions were 'too far apart'. This must have happened with an update I ran Wednesday night (and subsequently broke my Exchange server on restart Thursday morning). A Sharepoint 3.0 update also broke that... talk about bad luck. This got the store back up (and subsequently my email) however anyone accessing email via OWA crashes the store... so I gotta get back in touch with the rep at MS on Monday.

Thanks for the follow-up.One thing to note. I found that with Exchange 2003, you should always stop all the Exch services and ensure they are stopped before applying any update. ( You probably already know this!)Exchange 2007 is much better at this.