Hi Guys,

Not sure what has happened here but 60 users all lost their pin and have had to get reactivated. All the users where on the same Exchange server but the rest (530 users) are ok?
{name} Device ID used to be 2512xxxx but is now blank
[40245] (02/02 19:45:51.320):{0x2324} {email address Device ID changed
[30000] (02/02 19:45:51.320):{0x2324} {email address} Sending data to Dispatcher, size=158, Tag=566031
[40000] (02/02 19:45:51.320):{0x2324} {email address} SendToDispatcher, Tag=566031
[40000] (02/02 19:45:51.320):{0x1540} [BIPP] Send data, Tag=566031
[40255] (02/02 19:45:51.320):{0x2324} {email address} *****Redirection is disabled due to incomplete configuration*****
No infrastrcuture changes occured during or before the event! An exchange isnt showing any problems or changes either!
We migrated the DB to a SQL cluster the day after with no issue though, but th issue in hand occured the day before.
Any ideas??

**moved over to BES Admin area**

Whenever I see or hear that only users one particular Exchange server were affected then it's something with that Exchange server. Essentially the BB info in the mialbox corrupted, that's were it gets the PIN from.

This is due to some corruption in the mialbox. Reactivation is the fix to update the mailbox again but it is strange that only users one 1 server were affected.

Not sure what the casue was but I would think it has to do with the Exchange server.

I had simular issue on one of my servers couple of months ago. After couple of days they released this useless srticle:
http://www.blackberry.com/btsc/searc...200%2093408567

Where they don't mention what causes it...

Having completed a review of the customer's logs it appears that they are affected by a previously reported issue which has been logged. This issue is currently under investigation. MR3 for SP4 has included a code to generate additional logging surrounding this issue as well as resolve one of the potential causes. While there is no guarantee that MR3 will resolve this issue permanently for the customer, it will provide sufficient logging should the issue recur.

Bascially its a bug! quite a nasty one also!