[dannymac77]

This has been happening alot randomly, customer will report unable to receive their BES email on the blackberry, but can send BES email fine, personal accounts can send/rec no problem. On the bb manager, it shows that it is delivering the messages to the handheld, no errors, no packets pending.

We have troubleshot by pushing service books, deleting service books, reseating the battery, wiping the handheld and performing another enterprise activation, all with the same effect. The only way that I have seen that makes this work, is to delete all the desktop service books,remove from the bes, re-add and perform another EA.

I even pulled another berry from another carrier, ea'd on this out of the box device and it still had the same issue, email would send, but no email would come in, put according to the BES all is working just peachy.

I could live with the fact if I had to remove from the BES, readd, etc except that it only temporarily fixes, usually within a month, they customer is calling back in again, reporting same issue. Anybody have any idea? We are a state agency and waiting for budget approval to renew our T-sub

[knottyrope]

Running BRK yet?
Might help figure out what is causeing it.
Is the device running out of memory?

BRK here.
https://www.blackberry.com/Downloads...C1D6CE93DC54B8

[bulletooth]

I've started seeing this as well and found it to be a folder redirection issue where the inbox is randomly becoming deselected.

Check your folder redirection settings and make sure inbox is selected.

4.1.6 MR7 has this as a resolved issue in the tech notes.....

*SDR 353296
In BlackBerry Enterprise Server version 4.1 SP6 or later, in certain circumstances, when a user synchronized folders over the wireless network to a BlackBerry device, the BlackBerry device might have sent an information packet to the BlackBerry Enterprise Server that the BlackBerry Enterprise Server processed incorrectly. This might have turned off folder redirection for some of the userxxx8217;s folders.
In BlackBerry Enterprise Server version 4.1 SP6 MR7, this issue is resolved.