I have a user that came to me saying he can't send or receive email suddenly on his 8330, Alltel.

Short of removing him from BES and wiping the handheld, and re-adding him, what can I do? I hate doing it this way.

I've tried:

1. Re-registering on the host routing table (as alltel has suggested in the past). Did not work.
2. resending the IT Policy, which did not work.

What do others do?

if you try to send a message from the handheld what happens? if you get a red x, open the message, scroll up and post what it says next to status.

also what kind of signal does he have?

Did IT policy get to the device and be applied?

Yes, the BES says the policy was successfully applied.

Yes, it displays the red X when I try to send an email to myself. I wasn't aware that it shows anything in the email when it gets a red X. I'll go find out what it says.

stay tuned, and Thanks!!

My guess is the user connected the device to their computer with Desktop Manager incorrectly installed. This will mess up the encryption key required for email. Most likely you can just reactivate the device and it should be good to go.

When I open a sent email with the Red X it states "Desktop Email program unable to save message"...

i'm going to search for those terms now...

well i am trying the re-activation and the special email that shows up in the inbox, is staying in the inbox, not 'disappearing' like they normally do.

sounds like either a permissions issue with the besadmin account and their mailbox or their mailbox changed and the bes is unable to pick it up (such as if in exchange, they stayed on the same exchange server but moved from one storage group to another). in this case the server needs to rebooted.

I ended up calling RIM. We discovered that the mapi32.dll and cdo.dll files are not the same between the exchange server and bes server. so i will install the patches they gave me to make them the same. This is probably what caused the problem on this blackberry and one other I found.

but to get them working he had me change a static agent or something. will do a downtime next week to get those patches done!!

the cdo and mapi were probably causing other issues, but changing the user to a static agent forced the server to do a full rescan of their mailbox. to permanently fix this all you have to do is reboot the server.

He advised that once the two devices were talking again to the server, and could send/receive, i reset them back to non-static, and then restart the BB connector service and director service, or rebooting the server...but restarting the services was easier.