I seem to have a bit of a plague going through my devices right now. Many users have been complaining about wireless reconciliation not working properly. On inspecting the devices I see that there is no wireless reconciliation option under Email Reconciliation.

Resending the service book seems to correct the issue, wireless reconciliation can then be set to on, and then everything works alright.

However, I've seen perhaps half of the 40 or so devices I have come up with this issue over the last few days. Is this something I've inadvertently set on the server? IT Policy? Or is there something else at play here?

As a side note, when I resend the service book and reset the wireless reconciliation, a users local Outlook will get messages that have previously been read marked as Unread (as on the blackberry.) This is even though the device is set to have 'mailbox win' on conflicts.

Any help would be appreciated. Resending the service book is an easy enough fix, I am a bit concerned as to the root of the problem.

Try to upgrade the device OS. You can set this using the software configuration option on the BES. Each time users will cradle their device with the desktop and open Blackberry Desktop Manager, their devices will be upgraded.

Essentially all of my devices are running the latest device OS versions. *unless one has been released in the last 4 weeks*

This is a relatively new setup and the devices are all new and I loaded them with the latest before deploying.

Any other ideas?

This is interesting. I have also been having the exact same problem the last few days. What carrier are these devices with. I wonder if a carrier has sent out new service books which broke the BES service books.

All of our devices are on tmobile.

Well, shoots that theory. The users I know having this problem are Cingular and Verizon customers. I may just upgrade my BES to see if it helps.

Yeah, we're running 4.1 but not SP1. Going to do an SP1 upgrade this weekend, but its still weird. fine for 2 months, and then a slew of them this weekend.

I'm still running BES 4.0 SP4. Since you are having the same thing and it happened at the same time, it makes me wonder if something happed at RIMs NOC or something. It would be interesting to see if anyone eles is running into this.

I would be interested to know what the root cause is as well.

Yeah,
i'm having exactly the same problem - we are 4.0 SP4 and T-Mobile as carrier.
I would like to know what's goin' on because it's really annoying to answer people that i don't know the cause ...

I'm seeing the same problems with Cingular for users spread over different servers. What the heck is going on?

BTW, activations don't appear to be working very well either.. Half the time it hangs on "Waiting for servcies". Anybody else see that too?