[dfradsham]

BTW - I am experiencing the same issue. New install on a new server. Here's my list of config items, perhaps we can find a common thread:

IBM 346 server, 4gb RAM, PAE enabled, DEP turned off
Windows Server 2003 SP1 with all the latest patches
Running BES for exchange 4.0 sp3 with patch 1
Exchange is 2003 sp1 cluster

As previous posts state, this error occurs while looking at the properties of users in BES Admin, and cites the RIMDeviceManager as the offending application.

I have since changed the recovery options for the RPC service to just restart the service so the bloody thing stops rebooting.

here are the applicable log entries created by the fault;

Application log entries:

Application error 1000

Faulting application mmc.exe, version 5.2.3790.1830, faulting module BESManMMC.dll, version 4.0.3.10, fault address 0x000874eb

dr. Watson 4097 error

The application, C:\WINDOWS\system32\mmc.exe, generated an application error The error occurred on 12/02/2005 @ 13:15:48.559 The exception generated was c0000005 at address 015C74EB (BESManMMC!DllUnregisterServer)

System log entry:
The Remote Procedure Call (RPC) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Reboot the machine.

[jibi]

Originally Posted by BBTechGuy

Have both of you checked for the presence of the following Reg Key on your 2003 SP1 boxes yet?

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Wind ows Server 2003\SP1\KB823980

Also please check if DEP is enabled at the hardware or software level.

KB823980 was dated July 2003. If anyone updated to SP1, then they received this. The registry post-SP1 reflects SP2 as the registry key.

Hardware DEP is not enabled. Software DEP is excluding mmc.exe and RIMDeviceManager.exe. Any others?

[BBTechGuy]

Originally Posted by jibi

KB823980 was dated July 2003. If anyone updated to SP1, then they received this. The registry post-SP1 reflects SP2 as the registry key.

Hardware DEP is not enabled. Software DEP is excluding mmc.exe and RIMDeviceManager.exe. Any others?

I have no further suggestions.

[dfradsham]

One thing that was pointed out to us, We have Service Pack 2 for Exchange applied to the system management tools installed on our system - can anyone with this problem confirm or deny this as a possible suspect?

Apparently it is not currently supported...

[B B King]

I have this C++ problem with either Exchange sp1 or sp2 applied on the BES, so we can rule that out.

[bbhell]

Still working with both Microsoft and RIM engineers on this issue. MS engineer was able to get the RPC reboots to stop by rem'ing out some registry entries. There are some entries that are put in the reg by the BES install. Strange thing is that there are identical entries on other BES that are not experiencing this issue. I won't put those keys on here until we know for sure what's going on. This is still a workaround and MS is still troubleshooting with RIM. Supposedly, another customer has this same issue replicated in a test environment and MS is doing a live debug. Will keep you posted on final resolution. Hopefully.

[dfradsham]

K - I didn't really think it was an SP2 issue either, but it was worth a shot.

Regarding the reboot issue, all I did was go into the properties of the RPC service in computer management and change the recovery options to restart the service instead of reboot the server. Still bombs the app and service though.

DF

[jibi]

bbhell, thanks. please keep us posted. atleast its nice to hear they don't think its Blaster anymore... heh.

[Inphektion]

I had so many issues with the handheld software manager I don't run it currently. I just use the manager. But one thing that resolved my issue with it was disabling the DB consistency service.

[B B King]

My DB consistency service came disabled from the installation. My rpc issue came after sp3 + hf1 update.

I installed hf2 yesterday and so far I haven't had the rebooting issue, although I was in Management console only for about 2 minutes or so today.

[jibi]

installed HF1 and HF2 yesterday. just had the C++ error today.

[B B King]

My BES sp3 HF2 crashed with C++ error today also.

[jibi]

*sigh* This just seems to be one of those issues where no one wants to take fault. Its getting old.

[wshepherd]

Any updates on this?

[BB_God]

Try Workaround 2 in this KB article

http://www.blackberry.com/knowledgec...2834&vernum=13

I do realize that it is for Desktop Manager but I think it is worth a shot.

[wshepherd]

Anything is worth a try.

I called RIM and they said I should contact Microsoft.

[brent613]

Setup:
Windows Server 2003 SP1
Blackberry 4.0
Exchange 2003 SP1

I was getting the same errors in my Event Log:
"Faulting application mmc.exe, version 5.2.3790.1830, faulting module BESManMMC.dll, version 4.0.3.10, fault address 0x000874eb"

I put version 6.5.6980.3 of CDO.DLL in my BIN dir on the BES. Exchange 2003 SP1 has a version of 6.5.7226.0

I saw this error go away after a restart.

[wshepherd]

Just wanted to post an update.

Workaround 2 in the KB article that BB_God supplied did the trick. The problem went away and I hope it never comes back.

Thanks BB_God

[jibi]

If anyone wants to give this a try...

http://www.blackberry.com/knowledgec...80222&vernum=0

[andyscott]

Finally! My nice new BES had been crashing with that. Just hope that solves it...