BES 4.0 - Not All Email Being Received
 

I have upgraded a handheld to OS 4.0 and am not receiving all email to the handheld now. The handheld/profile currently has no filters setup and is marked to deliver messages to the handheld. These are emails that are not being permanently deleted by and Outlook rule - and they show up in the Outlook inbox.

Below is the Event Log for emails not being delivered (I have the log files as well, but they are somewhat confusing, to say the least).

At one point, there were 41 unread emails in the Outlook Inbox - and only 16 total on the handheld. I'm going to update to HF1 for BES 4.0, but I'm not sure if the server is the issue (or either its just pure coincidence that it started after upgrading to OS 4.0).

Anyone else experience the same or similar issues?

Did you reactivate the handheld?

I've noticed within the Beta program that when we update the HH software, we have to reactivate the device with BES. I usually use this procedure:

1) Backup data
2) Upgrade device
3) Restore data
4) Reactivate device

1, 2 and 3 are separate because I always backup the data first instead of doing the backup+restore. Just in case something happens during the process no devices lose their data.

We have to reactivate each device after upgrading though or they won't receive email.

I upgraded the device. It synched up just fine. However, it was not showing up statistics for it on the server. So I removed the user from the BES, and did an enterprise activation (I wanted to see this in action). The activation was completed a little bit later on and its registering on the BES.

It is receiving email, but a good percentage is not being delivered. Each time it fails, the Dispatcher service gets the error above.

Sorry I can't help more, looks like GW BES works much differently than exchange or notes. We don't really get syslog messages, but about 10 different bes logs.

This same message is listed in the dispatcher BES log (in logs folder). The system log is the normal Windows Application Log (in Event Viewer).

:)

I'll document as I go along. I'm just reinstalling the 4.0 OS and removing/readding the user to the BES - completely starting over from scratch as far as the handheld and the user are concerned.

1) javaloader -usb wipe
2) open Desktop Manager then Application Loader; reinstall OS 4.0 and components
3) remove user from BES 4.0; remove information from user's mailbox (Yes/No when removing from BES)
4) complete OS4.0 installation
5) add user back; clear statistics from BES (Yes/No when adding to BES)
6) generate and email activation password to user
7) complete wireless Enterprise Activation for user

Still working from here.

Same issue, except this time, I was receiving this error from Blackberr Messaging Agent.

The odd thing about this error was that I continued to receive it even after I removed the user from the BES. It literally showed up about 300 times in a few minutes.

Anyhow, I have moved the user back to OS3.8. No more errors on the BES and all emails are being received. This is odd behaviour, I would think.

I have just patched BES4.0 to HF1 while downgrading the OS to 3.8. I didn't see any 'fixed issues' that would coincide with my issue. Anyhow, I guess I'll wait until the provider officially releases an OS4.0 that is greater than .185 to try again.

Could it be a space issue? Or possibly the sql database is full? Tried checking permissions? I'm just pulling things off the top of my head now.

SQL has no limitations for the BESMgmt database. Permissions are set per RIM's instructions.

When TMO releases their finalized flavoring of OS4.0 and I start testing it again, and if this is still an issue, I'll give RIM a call for help. I was just wondering if others had the issue as well.

:)

I'll keep all posted. I should have their OS4.0 early next week, I think (our rep is supposed to be getting this to me).

I loaded the new HK CSL software (albeit, the same version of OS4.0) and email redirection is working fine now - 100% of all emails are being received.

The only thing I did different was not engage the Enterprise Activation from the handset. I left it connected via USB, at which point it started the Activation process and completed by the time I got back to my desk (I left for a while).

Very odd.