Microsoft
Software
Hardware
Network
Question : BES Activation issue
I have an issue with a Blackberry user, actually the user is myself thank goodness, but I need to know how to correct this issue as its probably only a matter of time before this happens to someone with less patience.
My Blackberry lost BIS emails yesterday for a short time, so I re-provisioned it, still nothing, ran the diags, came up clean, so I decided to wipe it. I woke up this morning to all my BIS emails, no big deal there, I've seen that from time to time. Now, when I went to reactivate myself on our BES, I set the activation password, and I sometimes get "an error has occurred, contact your admin", sometimes I get an "encryption verified", then right away I get "contact your admin". I thought at first it was the Blackberry, so I tried my second unit, same issue. I deleted the BES account, recreated and reset activation password, same issue. I created an all new exchange account and linked it to a new BES account, it activated it just fine. So I moved (recreated) the original account on another BES, (BESX), and I get the same issue, "an error has occurred, contact admin".
So, this leads me to think theres some sort of corrupt data somewhere linked to the Exchange account, any thoughts? All accounts in my organization have BES send as permissions as well.
Answer : BES Activation issue
Greetings,
I wonder if the corrupted data is in your Exchange account's hidden BlackBerry folder. Did you delete your BES account with the clean mailbox info option?
-silly-
Random Solutions
local hosting
Oracle SQL: why this regular expression doesn't work?
Server 2008 will restart on its own with this error during DC promo to this server
Monitor programs
SQL Syntax Error
Using perl, I need to check if all the files in a certain directory start with a certain character string.
Looking for bicycle cadence indicator using colored LEDs to show speed
OutOfMemoryException when reading users from AD
Changing Background colors for a column based on contents of cell
adding sudo info to my lastlogin's report