Sharing this from issues encountered before.

(1) message reference not found

OTAFM: message reference is not found, notification was discarded (RID=-1048194027) (Entry not found in index 0x0404).

A message on the BlackBerry device contains a reference ID that does not exist in the BlackBerry device user's state database. This can be caused by state database pruning, corruption, or the BlackBerry device being configured to keep messages forever.


(2) folder reference not found

[10548] (06/02 10:01:55.241):{0x1ED4} {User Name/ORG} OTAFM: folder reference is not found; RID=-3 (Entry not found in index 0x0404)
[40246] (06/02 10:01:55.241):{0x1ED4} {User Name/ORG} OTAFM (MessageInFolder): unable to get folder table (RID=-3)
[30300] (06/02 10:01:55.241):{0x1ED4} {User Name/ORG} Incoming NID=19CAEE was not found in any of the 1 redirected folders

In a BlackBerry Environment where we have fail over (stand by) BlackBerry Enterprise Server, the conflict replica documents in the State Database may be created if there is wrong Notes replication setting of the for the State Database. Rim supports just One-Way PULL replica from the Primary BES to the contingency server.

Also, a possible scenario where the conflict replica documents are created is a BES fail over. It is a good habit checking in the target BES that there are not conflict documents in the State and Profile Lotus Notes database.


(3) Unable to find original message

Unable to find original message<noteid> for user<user_name>/<organization> (Entry not found in index 0x0404)

Cause 1

The BlackBerry Enterprise Server is configured in a cluster with a secondary BlackBerry Enterprise Server instance. Cluster replication does not keep the state database current when CPU usage is spiking. Thus, the document referencing the Message Identifier (MSGID) and the Universal Note ID (UNID) of the original message cannot be found in the user’s BlackBerry state database.
If a BlackBerry device user forwards, replies to, requests more (all), or opens an attachment with the original message while CPU usage is high, load balancing engages. This request then fails over to the BlackBerry device user’s state database on the clustered BlackBerry Enterprise Server. If a cluster replication is not current, and requests are made too quickly, the MSGID and UNID of the original document does not exist in the replica of the state database on the clustered server.
Resolution

BlackBerry Enterprise Server clustering may tax system resources. Re-evaluate system requirements, including system hardware, the volume of traffic, the number of BlackBerry device users, and the BlackBerry services that are enabled for BlackBerry device users.
Search the IBM Lotus Domino Support web site for information on clustering.
Cause 2

This error occurs if a BlackBerry device user tries to forward, reply to, request more (all), or open an attachment where the message reference has been pruned (removed).
Resolution

The recommended time to retain a message in the state database is 365 days.
Cause 3

The index of the document referencing the MSGID and UNID of the original message cannot be found in the user's state database. You might find the document referencing the MSGID and UNID, but a corrupt view index prevents the IBM Lotus Notes® application programming interface (API) from retrieving the document using the index number.
Resolution

To fix a corrupt index, open the corrupt view and perform one of the following:

• Press SHIFT + F9 and then refresh the view indexes by pressing CTRL + SHIFT + F9
• Run the Updall maintenance task using the -R switch on all the BlackBerry Enterprise Server databases.

See the IBM Lotus Domino Administrator Help files or KB02207 for more information on running maintenance tasks.