Embarassing as this is, it was a database error. We've reached the named properties limit on the specific database this guy was running, which was evidently preventing BES from doing its thing. Moved the mailbox and all is now fine.
Problem solved, but I'd like to thank everyone for their suggestions :) From: [email protected] [mailto:[email protected]] On Behalf Of Sobey, Richard A Sent: 27 November 2009 16:22 To: A list for BES Admin's to discuss issues, etc. Subject: [Bes-admins] BES 5.0 - activation fails for one user; BES 4.1 is fine? All, Can anyone suggest why one of my users' Blackberry fails to work with BES 5.0, but is fine on BES 4.1? It's a complete mystery to me. I've migrated him, along with over a hundred others, with the Enterprise Transporter tool. However, since migrating him his Blackberry functionality has ceased to work. This is a list of things I've tried: 1) Wiping handheld and reactivating. Activation email just sits in the Inbox and not collected by BES 5.0. 2) Upgrading firmware to latest, wiping and reactiving. Same thing. 3) Removing user from BES and reading. Same thing. 4) Failing over to a different BES and rebooting both. Same thing. 5) Resending service books. 6) Run IEMSTest.exe to verify permissions - all fine. 7) Ringing technical support ("Is your BES server running?" AAAARGH!) So I'm rather at a loss. Like I said, reactivating this use on BES 4.1 is quick and painless, so mailbox access from the BES service account is fine. Suggestions on a postcard please! Thanks Richard
_______________________________________________ Bes-Admins mailing list [email protected] http://www.dataoutages.com/mailman/listinfo/bes-admins http://www.dataoutages.com http://www.dataoutagenews.com RSS Feed: http://feeds.feedburner.com/Bes-admins ---------------------------------
