Hi all

We have a really strange problem here. We are using about 55 BlackBerry 8800 devices on BES 4.1.3 Server. The device has firmwares 4.2.1.101 (vodafone) or lower. On about 25 percent of the devices we had the application error 523 appearing on the device. After updating the firmware, the device is well for some days and then the same error again.

We have contacted RIM already about this serious problem, but they don't know what to do!!! It's unbelieveable over 25% of the devices are for the trash. The devices are from different shipments.

RIM just says we should replace it with new one within warranty, but about 25% is way too much...

Any help?

Thanks a lot!!!!

Wirelessly posted (Opera/8.01 (J2ME/MIDP; Opera Mini/3.1.7196/1704; en; U; ssr))

I have an 8800 on tmobile usa network and downloaded a theme on my device then tried to delete two applications on my device and received the same app error 523. I had to have someone reload os and the later on that day I received the same error. I deleted the theme and that resolved my issue.

Thanks for your reply. Unfortunately we won't allow any third party software to use on the blackberry. So I Think it should be something else.

The last couple of days there we 3 more dead 8800's..

We have a very restrictive IT Policy. Could it be related to the IT Policy? What about content protection. Has it something to do with that?

We have now 2 more dead 8800's.

Anyone?

JVM error 523 is stating that a critical java process has died and the device cannot continue to operate normally. You stated that you updated the firmware. Have you completely wiped a device and reinstalled the OS? I would try that if it hasn't been tried yet.

How do I wipe the BlackBerry using Jl Cmder? - BlackBerryFAQ

What to do next if Jl Cmder will not connect and wipe - BlackBerryFAQ

Yep...Error 523. After a full day of phone calls, TMOB is replacing it.

This is GOOD to hear. I doubt smartphones like HTC even if branded in partnership with TMobile would warrant the same.

I had the same problem using OS 4.2.1 rel 103, happened once and reloaded OS. It happened again, whiped the phone with JL_Cmder and upgraded to OS 4.2.1 rel 164 Vodaphone. Have not had that problem again (at least yet). Two weeks now with phone on 24/7 and no problem.