Blackberry Issues

Overview

I have setup the blackberry messaging agent to email me for critical or warning error messages.
This list errors that I have managed to get to the bottom of.

Unread Marks

Unread marks between Domino and Blackberry is a big issue. The BlackBerry Messaging Agent gives you the following message.
BlackBerry Messaging Agent (Server) (Application Event Log on Server) Date Time (EFFF2924) OTAFM (User (User Name): unable to set unread table, notification was rejected (You are not authorized to perform that operation 0x0246)

Our system with 1,500 Blackberry users generated about 10,000 of these messages a day.
Upon investigation I contacted the RIM help desk and was told that the domino server should be hard coded in the state database.
When I investigated I found this was not the case. What I also found is that it was a BesAdmin command that was making it wrong
Because Blackberry Enterprise Server does not have any automatic fail over solution then we have set our system up so that the three bes servers all share a singe sql database. This way should there be a problem you can move people between server and still keep things running
When you first create someone on the BES server it creates a state database for them with the domino server hard coded in the ACL
But later if you use the BesAdmin move command it will move the user from one BES server to another one but will not update the ACL.
Thus the ACL will remain wrong and the unread marks will fail and generate the above error message.

PNAB stops working with 4.1.6MR2 upgrade

We use PNAB's personal address books.
People sync the details between their desktop and a server. The BES then picks up from the server and passes it to the Blackberry. This was working fine with no problems. Until that is we upgraded from 4.1.3MR1 to 4.1.6MR2. All of a sudden we got these errors. When you looked at the address book details on the BES Manager the pnab details had been replaced with the person's mail file details.

Also on the domino server you would see this error.
Address book config, using iNotes database (mail file details).
Then the error.
Location cannot be changed for roaming/iNotes user while registry key PrepopulatePIMForiNotesUsers is set or absent.

You would go back to the persons entry in the BES Manager and where you had entered the pnab server and pnab name.nsf all this data was gone and it was replaced with the mail file details of the user. The default had changed to assume that the user is an iNotes user and their personal address book is stored in their mail file and this was not the case with our company.

This next image is after the pnab has been changed to the mail file.

What we found was a registry key setting that would put the system back to the way it used to work.
The Registry key location is:-
\HKEY_LOCAL_MACHINE\SOFTWARE\Research In Motion\BlackBerry Enterprise Server\Agents
You had to create PrepopulatePIMForINotesUsers as a REG_DWORD and set its value to 0.
This would then revert the way the BES worked back to the old way.

Blackberry Manager does not work with Lotus Notes. (no server drop down list)

Release BES 4.1.6 MR3 SP2 on domino.
Problem:-
In some companies when Admins run the Blackberry Administrator on their PC they do not see the drop down list of servers that enables them to select the user to be added to the BES. This picture shows how it should work with the server and a list of names. (blanked out here)
Reason:-
In many large companies people can logon to any PC with their id and get their desktop. The C drive is loaded with their notesdata directory under their id. The notes launch icon has this text. "C:\Program Files\Lotus\Notes\notes.exe" "=C:\Documents and Settings\Persons ID\Notesdata\notes.ini" This way the persons personal notes.ini is used when Lotus Notes is started. The blackberry admin manager does not support this solution. The admin manager uses the registry keys to find the Lotus Notes dll's and notes.ini HKEY_LOCAL_MACHINE\SOFTWARE\Lotus\Notes and HKEY_LOCAL_MACHINE\SOFTWARE\Lotus\Notes\#.0 In many companies these locations do not contain this data so the blackberry admin manager will never find the notes.ini
Solution:-
As a short term solution you can put a copy (copy not move) of your notes.ini into c:\Program Files\Lotus\Notes Then when you start the blackberry admin manager it will find the notes.ini and give you the drop down list of server and users from your NAB so you can add users to the BES. Not ideal but should get you working.

When USA AT&T users Roaming in the UK always switches back to Automatic network selection.

Release BES 4.1.6 MR4 on domino.
Blackberry AT&T users in the USA often travel to the UK. When they get to the UK they go to Manage Connections,Select Manual and select the best provider that works. (i.e. O2 UK) They then set "Select Automatic Mode when manually selected network is not available" to No. This stops the user from switching to problem providers when a signal is lost. (In a lift or underground etc etc. Only on the bold this No option is lost and the bold switches back to Automatic network selection without the user doing anything. It just changes to automatic on its own. Can happen any time. Thus the user ends up on a provider that does not work and misses emails.
The default level from AT&T is 4.6.0.167 on a platform 4.0.0.157. You can check for upgrades and select a platform of 4.0.0.217 but this does not fix the problem. I have also done a manual upgrade of the bold to vodafone code 4.6.0.266 on a platform 4.0.0.223 and still the same problem. We have other devices such as the storm that don't have the problem.

With Calendar Delegation on Domino changes between 4.1.3 and 4.1.6

Executives on a 4.1.3 server use the domino option "Type of meeting notices to be shown in your inbox = none". All thier calendar requests are sent to the assistant. This all worked fine until the executives moved to a 4.1.6 server then the meeting invites started to appear in the blackberry inbox.
The solution was resolved with the following registry key.
HKLM\Software\Research in Motion\BlackBerry Enterprise Server\Agents
FwdInvitesNotFromInbox = 0