Exchange 2003 Information store crashing / possible BES interaction causing it to crash
Hello everyone,We have contacted RIM and they went through all the logs and they seem to be under the impression that everything is fine on their end. We are running Exchange 2003 Sp2 on Windows 2003 server R2 Sp2. Nothing has changed in over two months. In the past 24 hours our Information Store has been crashing and we need to restart the service to email to come back online. Once we re-establish connection to the Blackberry Enterprice Server after about 30 mintues it(store.exe) crashes again. If we turn off all BB services (which is a different server btw and running 4.1 Sp6 MR4) it seems to remain stable. It almost seems as if BES encounters a corrupt message/cal item and crashes but RIM support say they don't see any errors. Here is what seems to be the event that occurs everytime we crash with same values: The Microsoft Exchange Information Store encountered an unexpected exception 0xC0000005 at address 00428590 while processing a request for user besadmin.This is eventID 9659, Source: MSExchangeISThis same address above happens everytime how can we find out what it is?then -Faulting application store.exe, version 6.5.7654.12, stamp 492cd78a, faulting module store.exe, version 6.5.7654.12, stamp 492cd78a, debug? 0, fault address 0x00028590.This is eventID 1000, Source, MS Exchange Serverthen -Faulting application store.exe, version 6.5.7654.12, faulting module store.exe, version 6.5.7654.12, fault address 0x00028590.This is eventID 1000, source, Application Errorthen - this warningAn internal MTA error occurred. Too many entity control blocks (ECB) were processed in one thread. 10 ECBs were processed. [XAPI TRANSFER 12 138] (14) This is eventID 3129, source MSExchangeMTAWe checked mta stack and it checked out ok.After this we can to start the Information store service to restore access to exchange. has anyone seen this or know how to find this issue? Thanks in advance!-Troy
August 30th, 2009 9:20am

Please try to use Hotfix 957213, and copy the CDO.dll onto the BES server It almost seems as if BES encounters a corrupt message/cal item and crashes but RIM support say they don't see any errors Yes, corrupted items can cause such symptom without error info. Please mount blank store on the exchange 2003 and monitor for 30 minutes, see if the issue still occurs If the hotfix above doesnt fix the issue, then we need to take the dumps to locate the root cause. Unfortunately, it is beyond what we can do in the forum as the nature of forum support. I'd like to recommend you to contact Microsoft Customer Support Service (CSS) for assistance so that this problem can be resolved efficiently. Herere the phone lists [US, outside of US] How to use the Userdump.exe tool to create a dump file How to use ADPlus to troubleshoot "hangs" and "Crash"
Free Windows Admin Tool Kit Click here and download it now
August 31st, 2009 6:03am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics