Thank you for visiting the BlackBerry Support Community Forums.
BlackBerry will be closing the BlackBerry Support Community Forums Device Forums on April 1st (Developers, see below)
BlackBerry remains committed to providing excellent customer support to our customers. We are delighted to direct you to the CrackBerry Forums, a well-established and thorough support channel, for continued BlackBerry support. Please visit http://forums.crackberry.com or http://crackberry.com/ask. You can also continue to visit BlackBerry Support or the BlackBerry Knowledge Base for official support options available for your BlackBerry Smartphone.
"When we launched CrackBerry.com 10 years ago, we set out to make it a fun and useful destination where BlackBerry Smartphone owners could share their excitement and learn to unleash the full potential of their BlackBerry. A decade later, the CrackBerry community is as active and passionate as ever and I know our knowledgeable members and volunteers will be excited to welcome and assist more BlackBerry owners with their questions."
- Kevin Michaluk, Founder, CrackBerry.com
Developers, for more information about the BlackBerry Developer Community please review Join the Conversation on the BlackBerry Developer Community Forums found on Inside BlackBerry.
03-05-2013 12:48 PM
03-07-2013 05:19 PM
Hi and Welcome to the Community!
Here is a KB that discusses that error:
Hopefully it contains something useful! There also are multiple existing threads on this site that discuss that exact error...your review of those might prove useful, and a search of this site, using the error message, error code, or symptom, should reveal all applicable existing threads to you.
Good luck and let us know!
03-09-2013 01:54 PM
Well, if you are indeed affected by the specific cause discussed in the KB, you would talk to your BES admins as they control the IT Policy that BES places onto your device.
If you are not presently on BES, then you need to look into if your BB was ever part of BES...for if it was, then it's possible that the IT Policy was not properly cleansed from the device, resulting in this impact now. You can check via:
If there is an IT Policy and you are 100% certain your are not presently part of BES, then you need to conduct a ResetToFactory WIPE in order to remove the IT Policy:
Be sure that you first conduct a good backup so that you can restore later...but do not do that wholesale. Rather, backup/restore only those databases you require, avoiding any that have anything to do with IT Policy...if you don't you will simply put the IT Policy back onto your BB, and be right back where you started.
You can find complete backup instructions via the link in my auto-sig on this post.
Good luck and let us know!