BlackBerry Forums Support Community

BlackBerry Forums Support Community (http://www.blackberryforums.com/)
-   RIM Software (http://www.blackberryforums.com/rim-software/)
-   -   uncaught exception: net.rim.device.api.system.ObjectGroupReadOnlyExcep tion (http://www.blackberryforums.com/rim-software/82153-uncaught-exception-net-rim-device-api-system-objectgroupreadonlyexcep-tion.html)

logikman 06-19-2007 01:52 PM

uncaught exception: net.rim.device.api.system.ObjectGroupReadOnlyExcep tion
 
I keep getting the following error when saving events to my Calendar:

Code:

uncaught exception: net.rim.device.api.system.ObjectGroupReadOnlyException
It takes two (2) attempts to successfully save the event. After the save I receive the error.

While the event is saved successfully the alarm never alerts me.

Anybody have an answer?!?!?

luzippu 07-11-2007 08:08 AM

any luck with this one?
 
i'm having the same problem. Have you managed to solve it?
thanks

logikman 07-11-2007 08:31 AM

Well I solved it but I have no idea how.

Out of frustration I just double and triple checked my settings and then just took my battery out and rebooted. It works fine now.

mjaypitt 07-26-2007 11:03 AM

uncaught exception: net.rim.device.api.system.ObjectGroupReadOnlyExcep tion
 
I couldn't solve this problem but after ensuring contacts, calendar etc were entered correctly, I did a search on my Pearl (Group Read Only Exception) and found one email that popped up. I deleted it, took the battery out to reboot and now it works fine. Maybe only the rebooting was necessary.

aiharkness 07-26-2007 11:20 AM

Wirelessly posted (8700g: BlackBerry8700/4.1.0 Profile/MIDP-2.0 Configuration/CLDC-1.1 VendorID/100)

Quote:

Originally Posted by mjaypitt
I couldn't solve this problem but after ensuring contacts, calendar etc were entered correctly, I did a search on my Pearl (Group Read Only Exception) and found one email that popped up. I deleted it, took the battery out to reboot and now it works fine. Maybe only the rebooting was necessary.

Indeed. To repeat what is often stated on the board, the battery pull fixes many things. Probably the number one action to try when things were working and next moment they weren't.

J-Do 11-01-2007 10:32 AM

I had the exact same issue and removing the battery remedied it.

firefly5354 09-01-2008 07:07 PM

Ah! Pull the battery and put it back! Such a simple remedy for such a lengthy note of error. Relief!

Bob R 12-10-2008 01:08 AM

Thank You, thank you, thank you ... i am finally back in business. i had become quite dependent on this feature and for just the removal and replacement of the battery.

grfxguy 04-18-2009 01:39 AM

I had this problem on a Curve 8900, and finally narrowed it down to when I had a missed or ignored call, and then went back and clicked on the phone log - that would trigger it.

After spending several hours with up to tier 2 support at T-Mobile, they finally switched me over to RIM support who provided this solution.

Because I had narrowed the problem down to a specific and repeatable sequence, the RIM support tech determined that my phone log database had gotten corrupted. Here are the steps he gave me to clear it:
  1. Start BB Desktop & connect phone
  2. Click backup & restore
  3. Click Advanced
  4. In the right window, scroll down to Phone call log & select
  5. Click the clear button
No more uncaught exception errors.

clicknomore 04-28-2009 04:54 AM

Quote:

Originally Posted by grfxguy (Post 1356843)
I had this problem on a Curve 8900, and finally narrowed it down to when I had a missed or ignored call, and then went back and clicked on the phone log - that would trigger it.

After spending several hours with up to tier 2 support at T-Mobile, they finally switched me over to RIM support who provided this solution.

Because I had narrowed the problem down to a specific and repeatable sequence, the RIM support tech determined that my phone log database had gotten corrupted. Here are the steps he gave me to clear it:
  1. Start BB Desktop & connect phone
  2. Click backup & restore
  3. Click Advanced
  4. In the right window, scroll down to Phone call log & select
  5. Click the clear button
No more uncaught exception errors.

I had the same problem on a vodafone branded 8900 and yes, your solution solved the problem. Thanks for taking the time to share this solution with us - you saved me some hours with the vodafone support I guess (y)

hasten3 05-12-2009 10:57 AM

Quote:

Originally Posted by grfxguy (Post 1356843)
I had this problem on a Curve 8900, and finally narrowed it down to when I had a missed or ignored call, and then went back and clicked on the phone log - that would trigger it.

After spending several hours with up to tier 2 support at T-Mobile, they finally switched me over to RIM support who provided this solution.

Because I had narrowed the problem down to a specific and repeatable sequence, the RIM support tech determined that my phone log database had gotten corrupted. Here are the steps he gave me to clear it:
  1. Start BB Desktop & connect phone
  2. Click backup & restore
  3. Click Advanced
  4. In the right window, scroll down to Phone call log & select
  5. Click the clear button
No more uncaught exception errors.

I noticed I started having that error AFTER I install the Facebook contacts application.

clicknomore 05-13-2009 07:09 AM

Quote:

Originally Posted by clicknomore (Post 1367177)
I had the same problem on a vodafone branded 8900 and yes, your solution solved the problem. Thanks for taking the time to share this solution with us - you saved me some hours with the vodafone support I guess (y)

I have to add that I got this problem again ... so it seems to help sort term but sooner or later it might appear again

kspero 06-01-2009 04:43 PM

What if the Phone Call Log is not accessible to clear - indicates device is configured for wireless synchronization, wireless backup and read-only. You cannot clear or restore.

So, how to clear this log with recurring errors?

Thanks... Keith

emsdavid 06-01-2009 05:00 PM

I am having this error and did the same download of Facebook contacts app

emsdavid 06-01-2009 05:01 PM

The thing is that it says to hit "ok" to clear the message but it does not go away!!!!

jealfonso 06-09-2009 10:36 PM

uncaught exception
 
I am having same trouble on a Javelin 8900 with 4.6 software

Can not go out of the message unless I remove the battery and reboot

jealfonso 06-09-2009 10:57 PM

Resolved
 
Quote:

Originally Posted by hasten3 (Post 1380876)
I noticed I started having that error AFTER I install the Facebook contacts application.

Yes, it worked, thanks a lot. In my case the call logs were corrupted

eltambo 06-19-2009 01:33 AM

Nice men,you fix my phone.
 
(y)
Quote:

Originally Posted by grfxguy (Post 1356843)
I had this problem on a Curve 8900, and finally narrowed it down to when I had a missed or ignored call, and then went back and clicked on the phone log - that would trigger it.

After spending several hours with up to tier 2 support at T-Mobile, they finally switched me over to RIM support who provided this solution.

Because I had narrowed the problem down to a specific and repeatable sequence, the RIM support tech determined that my phone log database had gotten corrupted. Here are the steps he gave me to clear it:
  1. Start BB Desktop & connect phone
  2. Click backup & restore
  3. Click Advanced
  4. In the right window, scroll down to Phone call log & select
  5. Click the clear button
No more uncaught exception errors.


AJMac25 06-25-2009 08:37 PM

8900 Curve with same problem
 
So, I too have this error and I can clear my call logs, but it just re-occurs later on. Any one have ideas as to why this occurs and the real fix?

Thanks!

xion 06-29-2009 10:45 AM

I have the same issue on 8350i running 4.6. it happens in simular situation. whenever i am doing something and hit the send button to go to call log. phone freezes and get this error. I have to do batt pull. I have attached to bb dt manger, but call log is geyed out and clear is not an option. I noticed issue after connecting to my companies BES. Any resolution out ther for this? My issue is I use the Direct Connect quite a bit and use the call log for current conversations, so Ill be in a walkie talkie call and get this error and my phone freezes. It takes about 4 min to reboot from a batt pull. By that time the conversation is over. Nextel people are used to conversations that last less than a min. so im loosing customers.


All times are GMT -5. The time now is 08:54 AM.

Powered by vBulletin® Version 3.6.12
Copyright ©2000 - 2018, Jelsoft Enterprises Ltd.