[Sohail]

I have noticed the scenario, in which If I move bb user from one exchange storage group to another storage group on the same exchange server. It stops working. If I take the same user to another BES server and add him there , it works fine. Bring it back to original BES server still hangs on activation. However if I reboot the BES server, the user is able to do activation and it works fine.
I have contacted RIM support, they are saying that its normal .. which I don't trust .... how can be a serious issue like this normal?
Anyone else experienced this or happen to know the resoloution, without rebooting or restarting services

thanks,
Sohail-

[dev]

My approach when moving users from one BES to another or simply between storage groups is run the handheldcleanup tool. If we take the extreme case of shuttling a user between BES servers as you're doing...obvioiusly at some point it will hang because it does take some time for the original services books to be flushed out. Every action or task you do has a wireless component...which will take a while, it's not instantaneous as if in a wired setting.
Rebooting the server causes it to authenticate again with the SRP host at RIM, therefore releasing all previous active threads.
My question is why are you moving users between storage groups? Is this a technical or architectural requirement related to performance testing?

[Sohail]

Well, we have mailbox size policy implemented per storage group. once the user is approved for higher limit , we move mailbox to SG with higher limit.
I do not move the user across the BES server. I am just moving the mailbox on exchange from one storage group to another and it stops working.
Unfortunately the hadheldcleanup tool does not work either. As per RIM and one of their KB-04474, its by design.
I do not want to reboot the server, everytime, I move a mailbox across Storage groups

[dev]

Have you tried "Reloading" the user in the BM console?

[Sohail]

Yes, pretty much tried everything. Handheldcleanup utility, dbclean utility, remove/re-add, wipe-out handheld, even bought a new handheld .. nothing worked so far. Unless you restart services or reboot the box ..