Search results for query: *

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

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?

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

Trust me on this Zelandakh...the feeling is mutual *lol*

I feel a sudden rush of overwhelming emotions....somebody likes me!!! :P

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

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

We have a setup where 1 main server backs up a fileserver, an exchange server and a terminal server. All run on W2K3 Server w all necessary updates / SP's. Backup runs fine when Exchange DB level is selected. Whenever we select to modify the backupjob and simply select the Brick Level box...