[mpalmer]

Anyone got any thoughts on this?

I have activated 4 BB's over the last couple of days, all 4 have been fine. I needed to reallocate one to a different user though. I deleted that user off the BES and then added in the new one.

I then re-ran the enterprise activation on the BB, it said 'new user, delete etc' which I allowed it to do. Now when I try to re-run it again though to allocate it to the user I get the following message

"The server is not responding, please contact your system admin"

Everything is fine with the server though, all the other BB's are working perfectly. I'm pretty new to this so would just like some ideas on where to start looking.

Oh, yes, I do have wireless turned on and i'm in a good signal strength area

Thanks

[Sagz]

Usually it means the carrier dropped Data Service from the BB. Did you make sure the BB still has data service on it?

[juwaack68]

Whenever I reallocate a device from one user to another I wipe the device...maybe that will work vs. allowing the activation to do the deletion?

[mpalmer]

ok so i've spoken to the provider, they can see the BB quite happily and its active for data.

I've wiped the BB, deleted the user account and recreated it. Still no beans though.

Anyone else got any ideas what I can check on the server? Thanks

[Nashkat]

Originally Posted by mpalmer

ok so i've spoken to the provider, they can see the BB quite happily and its active for data.

I've wiped the BB, deleted the user account and recreated it. Still no beans though.

Anyone else got any ideas what I can check on the server? Thanks

If completely wiping the device does not work then try and set the activation password yourself rather than letting the server set it, sometimes that can get screwed up.

[val7250]

did you remove the old account off the bes server, a pin to pin transfer works?

[mpalmer]

I took advantage of the bank holiday to reboot the server, as soon as that was done I could activate the BB. No idea what that was all about, thanks everyone for the replies though.

Matt

[syoulden]

If you experience the problem again, try stopping and restarting the Synchronization service and the Policy service on the server. This sometimes corrects the issue