Good day all,

We are running a BES 4.0 SP3 server with about 80 users. About a week ago, our server ran out of disk space and the culprit was the BES Alert log located in C:\Program Files\Research In Motion\BlackBerry Enterprise Server\Logs\<date>\<servername>_ALRT_01_<date>_000 1.txt. These daily files were growing to the tune of about 5 - 7 GB each with the following message:

[30000] (06/12 08:39:14):{0x67C} Queuing alarm: BlackBerry Messaging Agent <Servername> Agent 1 (Application Event Log on <Servername>): 06/05/2006 19:42:26 (AFFF4F4D) -> {<a particular user>} Unable to save configuration settings or statistics

This message is basically filling up the logfile. I checked and found that although BES had an entry in the manager for this person, there was no corresponding AD account. Ok, makes sense why it is having trouble updating it. I confirmed the person was no longer with us and promptly deleted the BES entry for this particualr user. However, the errors in the log are still happening.

Where do I have to go to tell BES now that this person is gone and do not try talking to their blackberry?? Thanks for any insight.

Mike.

have you try to disabled/kill the handheld by using blackberry manager?

The Alert file growing large is a known issue to RIM with SP3.
http://www.blackberry.com/knowledgec...nodeid=1145499

The message "Unable to save configuration settings or statistics" is a normal MAPI error code.
http://www.blackberry.com/knowledgec...?nodeid=736867

I have seen the following fix that error if you have virus scannening enabled on the Exchange server:
http://www.blackberry.com/knowledgec...l?nodeid=25340

Contact RIm for the DBClean utility, it will remove all BES settings hidden in hte ex users mailbox

Remove the user, BES will stop rescanning his mailbox.
Unable to save configuration and statistics is displayed after the BES trys reloading the using 3 times which is every 10 minutes and then gives up.
If for a normal active user, you see this message and then followed up ReloadPagerStats Failed (), this means that the BES lost connection with the mailbox and only way to reconnect is by rebooting the Blackberry Enterprise Server

Thanks for all the responses guy.

Andidarmali: Hard to do a kill/disable on a device that's not in the manager as I stated in my message the BB had already been deleted.

Ashworth: Yup saw the bug report in SP4 but we have been running the same config for over a year and I find it hard to believe that "suddenly" we expose the bug. I am considering patching but not until i talk to our provider and RIM. I have restarted BES but it made no difference which was not unexpected.
We do have A/V running on Exchange but it has been running on it since day one over 3 years ago, not likely to be the culprit now.

BBConnect: Again, not going to work too well with the user already being deleted out of AD and having no mailbox.

Obviously somewhere in the system it believes this user still exists yet they do not show up in BES or AD after having been deleted. I will see what our vendor says and try opening a call with RIM (After we renew our support ).

Something tells me I'll be patching...

I'll update when I know more, thanks again.

Mike.

I'm just saying this is an issue and they know about it with SP3: SDR72047