Hi, hope someone can offer some useful advice!...Since we upgraded from BES 4.0 to 4.1, we have to reboot the server at least once a week. The Domino server since the upgrade looks extremely busy (even though CPU is very low (7% on average!), NBES.exe is using 694Mb...The crashes all occur, when the domino server simply stops responding (usually the BES Task just stops responding...the NSD generated indicates nBES each time). We also seem have to lots of errors in Event Viewer from the Blackberry Messaging Agent and Blackberry Router, which I'm not sure relates to the problem. Examples include:
1. The description for Event ID ( 30375 ) in Source ( BlackBerry Messaging Agent UKSUP03 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: SRP: TID=1141492, returned DELIVERED, but no transaction has been found.."
2. [SERVICE_RELAY_SESSION:S787661:0078db58] Service transaction not found. SERVICESESSION_TAG=15910263
3. OTAFM: folder reference is not found (Entry not found in index 0x0404)
4. UpdateMessage: unable to find message by tag! (1187874)
5. Unable to open note (user 63CA) (Document has been deleted 0x0225)
6. The description for Event ID ( 40243 ) in Source ( BlackBerry Messaging Agent UKSUP03 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: OTAFM: message reference is not found, notification was discarded (RID=-875434195) (Entry not found in index 0x0404).
The BES Logs just don't show anything that's causing this!..

We also noticed 4.1 was not a very clean and stable build, 4.1 SP1 fixed it all. After the SP1 upgrade I have never seen these babies deliver mail so fast. Good Job RIM, and I don't spread that lightly.

Yes all of us on Domino will occasionally get the dreaded Access Violation NSD errors which hang Domino, usually due to the NBES process.

Some of them are known bugs in the RIM code, some are unknown bugs, but many of them can be eliminated or reduced by doing the following:

UPGRADE YOUR RAM TO 4GB. NOW. DO NOT PASS GO. DO NOT RUSH TO UPGRADE DOMINO OR BES VERSIONS. FIRST GET 4GB OF RAM AND SEE WHAT HAPPENS.

Domino grabs all the memory it can, so high memory usage in itself is not an issue. What you need is to give the server as much memory breathing room as possible so the processes don't step all over eachother's memory spaces (i.e. memory access violations C00000005 errors).

Just my experience, but I sleep better at night these days since running 2GB only servers.

ignore the event log and look at the besmgmt logs
Much more information

We are running 4.1 sp1 with domino 7.01 and love it - the bes has had one issue in the past 60 days - the collaboration service was using a little more resources than we liked so I restarted the service

[SERVICE_RELAY_SESSION:S787661:0078db58] Service transaction not found. SERVICESESSION_TAG=15910263

You will get this error and it is not really an error. It is just when there was a packet that was sent out to the network and was pending for a few days, that never hit the handheld and when the BES was rebooted it lost the tag that was in memory, when the BES makes the new connection to RIM you will see a bunch of this coming back from the internet to the BES and since the bes lost the information in the memory from the reboot it spits out this error.

The reason it is not an error because any message that did not get send will get re-queued during the rescan when the bes sees that message has not been delivery to the HH.