Hello All, I have an Exchange 2003 server with about 30 mailboxes. Every now and then, the Store.Exe crashes for no reason. There are no 3rd party NAV\Spyware software running on the machine. I had since run the debug utility on the server before the crash, but to be honest, the output doesn't make any sense to me. It doesn't pinpoint what is causing the Store.Exe to crash, intermittently. Be that as it may, I am asking anyone for any advice\assistance. Here is the following App event: Faulting application store.exe, version 6.5.7653.1, faulting module store.exe, version 6.5.7653.1, fault address 0x000c3c35. Faulting application store.exe, version 6.5.7653.1, faulting module msvcrt.dll, version 7.0.3790.3959, fault address 0x000370d2. I am at wits end here. Should I be using a more stable version of the store.exe? I am just not sure anymore. Any feedback would be greatly appreciated. Thanks! JC

You have no third party software on there at all? No AV, Antispam etc? Is the server fully patched? Including all post SP2 updates? Most common reason for Exchange problems are third party interference. What is the specification of the server? Simon.Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

Many thanks Mr. Simon. No third party software, No NAV, No TrendMicro, No Nothing. Exchange server has SP2, and fully patched as of 2 weeks ago. This is a stand alone server for email. I have just 30 mailboxes on it. OWA is working fine. Nothing fancy or complicated. Straight out of the box setup and install. Thanks again for your assistance thus far. Please let me know if you need further information from me. JC JC

On Mon, 6 Jun 2011 23:57:15 +0000, JC65 wrote: >No third party software, No NAV, No TrendMicro, No Nothing. Do you have a Blackberry Enterprise Server? >Exchange server has SP2, and fully patched as of 2 weeks ago. There are builds of store.exe beyond 6.5.7653.1. For example, http://support.microsoft.com/kb/957213 You can take up the issue of CDO versions installed on the BES (if you have one) with RIM. Getting an older version of CDO that's still in RIM's support matrix can be a bear. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Ahhh yes...I do have a BES v. 5.0.1. The version of the CDO.DLL on the BES is 6.5.7651.61. On my Exchange 2003 server the version of CDO.DLL is 6.5.7651.61. Yes I did notice that there are later versions of store.exe but my thoughts are which one is a stable version? I was persuing this site: http://www.mskbfiles.com/store.exe.php. But I am hesitate to go with the latest version for 2003. I will look at the link you provided, and see if it makes sense to apply the patch. It does make sense though at first blush. If you have any other suggestions, please let me know. Thanks a lot Mr. Rich!JC

Also Mr. Rich, If I were to run the hotfix in the link you sent me on the troubled Exchange server, do I need to run it on the BES server as well? Or just copy over the CDO.DLL and register the DLL manually and reboot the BES? Please advise at your earliest convenience. Thank you for your help! JCJC

On Wed, 8 Jun 2011 01:15:02 +0000, JC65 wrote: >If I were to run the hotfix in the link you sent me on the troubled Exchange server, do I need to run it on the BES server as well? No. But you should try to get the most recent CDO version that's supported for your version of BES and install that on the BES server. >Or just copy over the CDO.DLL and register the DLL manually and reboot the BES? Get the CDO installation from Microsoft. There's more to DO than just the one DLL. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Please take some times to install the hotfix as soon as possible. If the issue persists, please run ExBPA to scan the whole server and check whether there is any problem can be detected. Thanks. NovakPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Thanks Rich. Here is a link that RIM sent me to run on the BES server: http://btsc.webapps.blackberry.com/btsc/search.do?cmd=displayKC&docType=kc&externalId=KB15779 Now along with your link to upgrade the STORE.EXE, I wasn't sure which to upgrade first. RIM did tell me that the MAPI32.DLL version on the BES needs to be newer than the MAPI32.DLL on the Exchange 2003 server. You have been a great help Rich, would you be able to preview the link RIM sent me, and let me know your thoughts. I was all set to install your suggestion, but when RIM came back to me with the link above, I was hesitate to move forward. Any help you can give me Rich, that would be totally awesome! Many, many thanks! JC65JC

CDO 1.2.1 is only available with Exchange 2007 and above. You cannot install it on Exchange 2003. Hence, it’s still recommended to install the hotfix which is mentioned by Rich. Thanks. NovakPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

On Sun, 12 Jun 2011 23:24:28 +0000, JC65 wrote: >Here is a link that RIM sent me to run on the BES server: > >http://btsc.webapps.blackberry.com/btsc/search.do?cmd=displayKC&docType=kc&externalId=KB15779 > >Now along with your link to upgrade the STORE.EXE, I wasn't sure which to upgrade first. RIM did tell me that the MAPI32.DLL version on the BES needs to be newer than the MAPI32.DLL on the Exchange 2003 server. Do the Exchange server hotfix first. >You have been a great help Rich, would you be able to preview the link RIM sent me, and let me know your thoughts. Do *not* install CDO 1.21 on your Exchange 2003 server. DO install the hotfix I pointed out on your Exchange server. DO make sure the build of CDO 1.21 installed on the BES is in the RIM compatibility matrix and is acceptable to RIM. >I was all set to install your suggestion, but when RIM came back to me with the link above, I was hesitate to move forward. Be careful with the information you get from RIM. They'll tell you to get CDO 1.21 from MS, but what they DON'T tell you is that the version you'll get may not be supported on the version of BES you're running: http://us.blackberry.com/support/software/server_express_exchange_may_11_11.pdf This is the version you should install: MAPI/CDO 6.5.8131.0 or MAPI/CDO 6.5.8153.0 If you put a more recent version than MAPI/CDO 6.5.8165.0 on BES 5.0.1 then RIM probably won't want to talk to you if you have a problem. >Any help you can give me Rich, that would be totally awesome! When you call MS to get the older version of CDO 1.21 be sure to tell the support person to look on the machine named "boneyard" for it. :-) --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Thanks Mr. Rich. This is great stuff. I went back to RIM and mentioned what you wrote above. I haven't heard back from them, which I am sure you are not surprised. I will move forward with your suggestion this weekend. I will do a backup of the troubled exchange server before I run the updates. Make copied of necessary files accordingly. I will let you know how this all went. Thanks again! You're the only one that shed real light on the issue. Many thanks! JCJC

Mr. Rich, Just wanted to give you an update. 1. I reset the Virtual Directories of the Front End Server 2. I reset the Virtual Directories of the Back End Server (where OWA was running fine) 3. I enabled FE on the FE server 3. I exported the SSL cert from the BE server and imported the SSL on the FE server 4. When I load OWA internally, I can access a mailbox on the second BE server (Brand new install) 5. When I try to access a mailbox on the BE server where OWA used to live, I get "The page cannot be displayed. Please use https://. - Which I am. 6. Also I am getting Metabase errors on the BE server. The proverbial "Metabase Update failed replication 5 times with error 80070003 (The system cannot find the path specified.). " 7. I read another article where you had mentioned there should be a metebase.bin file in the C:\windows\system32\inetserv sub-dir. There isn't any metabase.bin file anywhere on the server. I checked a backup file from NTBACKUP and I cannot find it there either. 8. I reset the VDs again for OWA, per the MS document, but still a no go. Right now things are okay, but using OWA to get to the main BE server where all the mailboxes reside is not working. Any magic you can send my way to resolve this? Thanks for your help! JCJC

On Sun, 19 Jun 2011 01:02:36 +0000, JC65 wrote: >Mr. Rich, Just wanted to give you an update. >1. I reset the Virtual Directories of the Front End Server >2. I reset the Virtual Directories of the Back End Server (where OWA was running fine) >3. I enabled FE on the FE server >3. I exported the SSL cert from the BE server and imported the SSL on the FE server Why in the world would you be doing that instead of installing the hotfix???? It's like changing the air in the tires because the engine in your car won't start. >4. When I load OWA internally, I can access a mailbox on the second BE server (Brand new install) >5. When I try to access a mailbox on the BE server where OWA used to live, I get "The page cannot be displayed. Please use https://. - Which I am. >6. Also I am getting Metabase errors on the BE server. The proverbial "Metabase Update failed replication 5 times with error 80070003 (The system cannot find the path specified.). " >7. I read another article where you had mentioned there should be a metebase.bin file in the C:\windows\system32\inetserv sub-dir. There isn't any metabase.bin file anywhere on the server. I checked a backup file from NTBACKUP and I cannot find it there either. There should only be a metabase.xml file in the system32\inetserv directory. If it was the file tht couldn't be found the error would have been "2" and not "3". It says the path (i.e. directory) can't be found. But, since the source is 8007 I suspect the problem is within the metabase itself and not the directory containing it. Give this a try: http://www.online-it-support.co.uk/?p=740 >8. I reset the VDs again for OWA, per the MS document, but still a no go. Right now things are okay, but using OWA to get to the main BE server where all the mailboxes reside is not working. Any magic you can send my way to resolve this? Thanks for your help! JC >JC --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Thanks Mr. Rich. To be clear, I did indeed run the patch you sent me after performing two backups. The only issue that occurred was the server ExIFS I believe was in a flapping state after the patch was installed. All the Exchange services mounted properly but the IS database would not mount. I restarted the server, and the IS database was able to mount properly with no errors. When I was installing an FE server, which was another to do of mine yesterday, I reset the virtual directories on the Exchange server I ran the patch on thinking that OWA should be reset since it was acting as the OWA server before. But I realized, that was an unnecessary "to do". Thus far, no store.exe crashes with the hotfix installed. So thank you very much. I will give it about another week or so, when the users start using email more heavily. When I was perusing the Internet yesterday in regards to the Metabase error I am receiving, I noticed some other articles having similar issues and you actually gave them some advice as to how to resolve their issue, which led me to ask you about my metabase issue. Maybe I should start a new thread and use your suggestion you stated above, so I can mark the answer correct from your advice. I did read the article in the link above but was hesitate to perform those steps, but I think I have no choice. I am using Metabase Explorer from the IIS Resource Kit. The article calls to use Metaedit. Can I use Metabase Explorer instead? Thanks for everything Rich. You are the only one that actually gave me sound advice. Greatly appreciate your help! JC JC

On Sun, 19 Jun 2011 15:01:26 +0000, JC65 wrote: >To be clear, I did indeed run the patch you sent me after performing two backups. The only issue that occurred was the server ExIFS I believe was in a flapping state after the patch was installed. All the Exchange services mounted properly but the IS database would not mount. I restarted the server, and the IS database was able to mount properly with no errors. That's a "good thing". :-) >When I was installing an FE server, which was another to do of mine yesterday, I reset the virtual directories on the Exchange server I ran the patch on thinking that OWA should be reset since it was acting as the OWA server before. But I realized, that was an unnecessary "to do". > >Thus far, no store.exe crashes with the hotfix installed. So thank you very much. I will give it about another week or so, when the users start using email more heavily. > >When I was perusing the Internet yesterday in regards to the Metabase error I am receiving, I noticed some other articles having similar issues and you actually gave them some advice as to how to resolve their issue, which led me to ask you about my metabase issue. Maybe I should start a new thread and use your suggestion you stated above, so I can mark the answer correct from your advice. A new thread would be appropriate since you're asking about two separate problems. >I did read the article in the link above but was hesitate to perform those steps, but I think I have no choice. I am using Metabase Explorer from the IIS Resource Kit. The article calls to use Metaedit. Can I use Metabase Explorer instead? Use the one that's approriate to the release of IIS you're running. MetaEdit is an old(er) tool that works, IIRC, on the metabase.bin file. The explorer should work on the metabase.xml file. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Thanks again Rich. I marked your previous reply and the answer for me. I also started a new thread. Thanks for your help!! You are the man!JC

Rich, Just a heads up, the store.exe crashed again a little while ago. See below for more info. The hotfix I ran did didn't stop the store.exe from crashing. Back to square one. Do you have any other ideas? Event Type: Error Event Source: Application Error Event Category: (100) Event ID: 1000 Date: 6/19/2011 Time: 8:51:52 PM User: N/A Computer: NYCEX00 Description: Faulting application store.exe, version 6.5.7654.8, faulting module store.exe, version 6.5.7654.8, fault address 0x00002b08. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 41 70 70 6c 69 63 61 74 Applicat 0008: 69 6f 6e 20 46 61 69 6c ion Fail 0010: 75 72 65 20 20 73 74 6f ure sto 0018: 72 65 2e 65 78 65 20 36 re.exe 6 0020: 2e 35 2e 37 36 35 34 2e .5.7654. 0028: 38 20 69 6e 20 73 74 6f 8 in sto 0030: 72 65 2e 65 78 65 20 36 re.exe 6 0038: 2e 35 2e 37 36 35 34 2e .5.7654. 0040: 38 20 61 74 20 6f 66 66 8 at off 0048: 73 65 74 20 30 30 30 30 set 0000 0050: 32 62 30 38 2b08 JC

On Mon, 20 Jun 2011 01:21:59 +0000, JC65 wrote: >Just a heads up, the store.exe crashed again a little while ago. See below for more info. The hotfix I ran did didn't stop the store.exe from crashing. In a way, it did. The address at which the exception occured is quite didtant (in terms of memory) for the address in your initial report. >Back to square one. Do you have any other ideas? For this problem, no. You'll have to engage MS for help on this one. They may have other instances of this in their problem reporting database. You do have to understand that the version of Exchange you're running is no longer in "mainstream support". It entered "extended support" over two years ago. http://support.microsoft.com/lifecycle/?LN=en-us&p1=1773&x=8&y=11 If there's no existing fix for your problem, and you're not paying for extended support, you may be out of luck. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP