Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Exchange 2003 IS keeps crashing 3

Status
Not open for further replies.

AltronicSD

IS-IT--Management
Oct 28, 2008
8
NL
Exchange server 2003 SP2 keeps on giving the following error:
Faulting application store.exe, version 6.5.7654.12, faulting module exoledb.dll, version 6.5.7638.1, fault address 0x000e0e9e.

Server is fully up-to-date both OS and Exchange.

We ran eseutil checksum checks / defrag etc. on both pub and priv db's, log files show no problems either.

No mail in badmail directories or any of the queues.

The only fix i have found for this problem is a post SP1 fix, which doesn't apply to this server as it is an SP2 server.

Can anyone offer a solution or a pointer as to where to look further? Nothing indicates a problem w this server, or it's db's except the crashing app.

 
Agree - might be worth installing Windows SP2 first then Exchange SP2 then Windowsupdate it.
 
HI,

Also how big is your store, and do you have plenty of space left on the drive where the databases are stored.

 
Thanx for the info guys, I did consider re-applying SP's to both OS and Exchange, but affirmation is always good ;-)

The size of the db is less than 10 Gb, with more than 180 Gb free space on the drive, so that is no issue.

I will re-apply the SP's and post follow-up information.

Kind regards,
Erik
 
You think you have a plan.
You post a good summary and ask for comments.
You follow the advice.
You give stars.

We like you :)
 
I feel a sudden rush of overwhelming emotions....somebody likes me!!! :p
 
Trust me on this Zelandakh...the feeling is mutual *lol*
 
I have re-applied SP2 to both OS and Exchange and to be on the safe side, ran an eseutil / isinteg afterwards, no indications of problems so far.

We're going to monitor the server from the moment users login tomorrowomorning until they log out.

Will keep you guys posted. For now, I am gonna pop down on the couch and keep my fin gers crossed ;-)
 
Make sure you are watching event log / Solarwinds / SNMP and be careful typing with your fingers crossed.
 
No joy I am afraid, this morning we've seen another round of store.exe crashing.

Same events as before are being logged.

Could this be a crooked client install?
 
Very unlikely. I'd look at the server rather than client.

What's the eventid being thrown and the source?
 
Dear Zelandakh,

It looks like we've found the source. We've compared versions of the exoledb.dll between several servers and the one experiencing this problem and found that the troubled server had an older version.

We replaced that one with the one from a server that has no issues like this, re-registered the DLL and so far so good, server's been up and running for a cpl hours now without the issue reoccurring.....

Version of exoledb.dll in use now is: 6.5.7654.12
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top