We upgraded to BES 5.0 and have one user with a bold who has had issues ever since. We are on Notes 7.0.4

At first, every time the user filed a message in one of his folders, five minutes later it would show back up in his inbox. Then a couple of days later he would start getting Java null exception errors and the blackberry would quit receiving emails even though the BES would say running and there were no pending packets.

I have run a fixup and compact on the user's mail file, I have also deleted and recreated him on the BES, as well as, deleted the state database.

Worked great for about 2 days then stopped, so I thought let's try a new BB. I had is old 8800 which I reactivated and worked for about 4 days then he started getting java null exceptions again and his emails quit working.

I have made sure he has no 3rd party apps on his bb, thinking this caused the java errors.

I am at a total loss, anyone have any ideas?

We have now had this happen on two other devices, both different devices and different carriers.....

What's the Domino server's version that host these affected mail files? 7.0.4 as well? What mail templates are they based on? Standard? DWA?

This is a known issue with 5.0 if your user has over 255 folders. This little bug has been a huge time killer for me over the past few weeks. The solution is to delete the user from your 5.0 environment and create them on a 4.1 BES.

IMHO, java null exception errors are normally related to device software corruption problems. It may just be coincidental. I'm aware of the 255 folders limitation in BES5, but that shouldn't caused the java exception.

Same with us... since upgrading tot BES5.0 there are problems with 2 devices and symptoms described above. These 2 users have over 255 folders in use... However, BB Helpdesk told me that it is not neccessarely the cause.

It started with duplicating 'ghost' folders, filed messages jumping back into inbox,... ending with no messages receiving anymore on BB device, however, inbox counter is goining up and up and up.

Finally, a remove/insert battery ends in "Uncaught exception: java.lang.IllegalArgumentException" directly after entering the PIN code.
From then on the device becomes extremely slow, does not receive messages anymore, cannot send mail and cannot connect to "desktop manager".

Already bought 2 new devices for the users which in the end didn't solve the problem.
- Replacing first device ended in 'problem solved' (hence the 2nd new device) but after 2 weeks it reappeared on the first. In an attempt to get rid of one ghost folder which still was left, i wiped the device, removed the user from BES and deleted the user's database from 'stat' folder. After the weekend the problems started all over again....
- On the second the activation of the new device didn't help at all