[mrchips]

Hi all,

Hopefully one of you kind folk maybe able to shed some light on a strange issue I am experiencing. If not then give me a starter for 10....

Anyway, our BB environment is BES 5.0.1 and Domino 8.5.2 FP1. We have 2 primary BES's with two standby BES's and approximately 950 BB handhelds.

What has started very recently is that a small selection of our users are experiencing that the BB's are not automatically reconciling. They have noticed that that have emails in their inboxes but those emails do not appear on the BB's. if they issue a "Reconcile Now" those emails will then appear. Once user waiting 4 hours before issuing a reconcile now. Once reconciled emails will flow as normal for a few hours then it stops.

Checking the MAGT logs I am seeing Coverage State - Out of coverage for those users. Now all the users that have so far complained have BB Curves 8310 running 4.5.0.163 (Platform 2.7.0.92) or 4.5.0.180 (Platform 2.7.0.105).

My original thought was it must be the network providors cell coverage, but the they are in the same location as me, some of them on the same BES as me and yet my device does not show the same symptoms. My BB is a 8900 running 5.0.0.681 (Platform 5.2.0.67).

I have logged a call with our network providor but have yet to get a response apart from it could be "clunking email" .

Any thoughts you may have would be greatly appreciated.

Carl.

[noname]

Symptons similar to known issue due to the use of the new API NSFGetDbChanges():-

Link 1: IBM - Information on synchronization issues with BES 5 and Domino 8
Link 2: KB18171-Email messages are received in batches by BlackBerry smartphone users on BlackBerry Enterprise Server 5.0 when BlackBerry Messaging Agent is delayed in picking up new items
Link 3: KB24375-Reconciliation of Read/Unread status for messages from IBM Lotus Notes to the BlackBerry smartphone takes longer than 1 hour on the BlackBerry Enterprise Server 5.0

Try setting reg key for agent PollByMailServer = 0.

[mrchips]

Thanks for the response.

The errors indicated in those articles are different to what I am seeing, and trying to apply some logic to it (yes that is dangerous), I would have thought that if it was the issue mentioned in those articles then I would expect all users to have the same problem, not as it appears so far, users of 8310's.

Carl.

[mrchips]

Just to try an bump this up a bit. Still no resolution but it does appear like the device is no longer on the RIM network as Pin to Pin messages don't get through either, unless a reconile is performed or the battery pulled.