06-22-2010 05:04 PM
But what if I'm not using a BES account?
There's pretty much no diagnosing those -- they are the equivalent of the random errors in Windows for which tracing the root cause is fruitless. Basically, these are the last out in the programming code -- some event occurred for which there is no handler in the code. The fix is a code update that handles the event...but, again, knowing what the event is is pretty much impossible. So, there are a few things to try:
Sometimes, the code simply becomes corrupt and needs to be refreshed -- just like a reboot:
There might be an updated code set from the carrier -- check them via this portal:
The toughest possible cause is a badly behaving app. To find it, one must remove apps one at a time, waiting a while in between (I usually recommend a week), until the problem ceases...thereby discovering the offending app.
Good luck and let us know!