BlackBerry Forums Support Community               

Closed Thread
 
LinkBack Thread Tools
Old 06-19-2007, 01:52 PM   #1 (permalink)
New Member
 
Join Date: Apr 2007
Model: Pearl
Carrier: cingular
Posts: 11
Post Thanks: 0
Thanked 0 Times in 0 Posts
Question uncaught exception: net.rim.device.api.system.ObjectGroupReadOnlyExcep tion

Please Login to Remove!

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?!?!?
Offline  
Old 07-11-2007, 08:08 AM   #2 (permalink)
New Member
 
Join Date: Dec 2006
Model: Pearl
Carrier: O2
Posts: 2
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default any luck with this one?

i'm having the same problem. Have you managed to solve it?
thanks
Offline  
Old 07-11-2007, 08:31 AM   #3 (permalink)
New Member
 
Join Date: Apr 2007
Model: Pearl
Carrier: cingular
Posts: 11
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

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.
Offline  
Old 07-26-2007, 11:03 AM   #4 (permalink)
New Member
 
Join Date: Jul 2007
Model: Pearl
PIN: N/A
Carrier: AT and T
Posts: 1
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default 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.
Offline  
Old 07-26-2007, 11:20 AM   #5 (permalink)
BlackBerry God
 
aiharkness's Avatar
 
Join Date: Jul 2005
Location: Florida Panhandle
Model: Z10
OS: 10.2.1
Carrier: T-Mobile USA
Posts: 13,697
Post Thanks: 15
Thanked 498 Times in 485 Posts
Default

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.
__________________
- Ira
Offline  
Old 11-01-2007, 10:32 AM   #6 (permalink)
New Member
 
Join Date: Aug 2007
Model: 8100
PIN: N/A
Carrier: Rogers
Posts: 3
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

I had the exact same issue and removing the battery remedied it.
Offline  
Old 09-01-2008, 07:07 PM   #7 (permalink)
New Member
 
Join Date: Sep 2008
Location: Bay Area, CA
Model: 8100
PIN: N/A
Carrier: AT&T
Posts: 1
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

Ah! Pull the battery and put it back! Such a simple remedy for such a lengthy note of error. Relief!
Offline  
Old 12-10-2008, 12:08 AM   #8 (permalink)
New Member
 
Bob R's Avatar
 
Join Date: Oct 2007
Location: St Louis (Ballwin), MO
Model: 8100
PIN: N/A
Carrier: AT&T Cingular
Posts: 5
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

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.
Offline  
Old 04-18-2009, 01:39 AM   #9 (permalink)
New Member
 
Join Date: Nov 2007
Model: 8100
PIN: N/A
Carrier: T-Mobile
Posts: 2
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

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.
Offline  
Old 04-28-2009, 04:54 AM   #10 (permalink)
New Member
 
Join Date: Apr 2009
Model: 8900
PIN: N/A
Carrier: vodafone
Posts: 2
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

Quote:
Originally Posted by grfxguy View Post
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
Offline  
Old 05-12-2009, 10:57 AM   #11 (permalink)
New Member
 
hasten3's Avatar
 
Join Date: Jan 2006
Model: 8900
Carrier: ATT
Posts: 1
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

Quote:
Originally Posted by grfxguy View Post
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.
Offline  
Old 05-13-2009, 07:09 AM   #12 (permalink)
New Member
 
Join Date: Apr 2009
Model: 8900
PIN: N/A
Carrier: vodafone
Posts: 2
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

Quote:
Originally Posted by clicknomore View Post
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
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
Offline  
Old 06-01-2009, 04:43 PM   #13 (permalink)
New Member
 
Join Date: Mar 2009
Model: 8900
PIN: N/A
Carrier: T-Mobile
Posts: 3
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

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
Offline  
Old 06-01-2009, 05:00 PM   #14 (permalink)
Knows Where the Search Button Is
 
Join Date: Nov 2005
Model: 8700
Carrier: Cingular
Posts: 47
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

I am having this error and did the same download of Facebook contacts app
Offline  
Old 06-01-2009, 05:01 PM   #15 (permalink)
Knows Where the Search Button Is
 
Join Date: Nov 2005
Model: 8700
Carrier: Cingular
Posts: 47
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

The thing is that it says to hit "ok" to clear the message but it does not go away!!!!
Offline  
Old 06-09-2009, 10:36 PM   #16 (permalink)
New Member
 
Join Date: Jun 2009
Model: 8900
PIN: N/A
Carrier: AT&T
Posts: 2
Post Thanks: 0
Thanked 0 Times in 0 Posts
Wink 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
Offline  
Old 06-09-2009, 10:57 PM   #17 (permalink)
New Member
 
Join Date: Jun 2009
Model: 8900
PIN: N/A
Carrier: AT&T
Posts: 2
Post Thanks: 0
Thanked 0 Times in 0 Posts
Wink Resolved

Quote:
Originally Posted by hasten3 View Post
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
Offline  
Old 06-19-2009, 01:33 AM   #18 (permalink)
New Member
 
Join Date: Jun 2009
Model: 8350i
PIN: N/A
Carrier: nextel
Posts: 1
Post Thanks: 0
Thanked 0 Times in 0 Posts
Thumbs up Nice men,you fix my phone.

Quote:
Originally Posted by grfxguy View Post
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.
Offline  
Old 06-25-2009, 08:37 PM   #19 (permalink)
New Member
 
Join Date: Jun 2009
Model: 8900
PIN: N/A
Carrier: T-Mobile
Posts: 2
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default 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!
Offline  
Old 06-29-2009, 10:45 AM   #20 (permalink)
Knows Where the Search Button Is
 
xion's Avatar
 
Join Date: Aug 2008
Location: USA
Model: 9630
OS: 4.7.1.40
PIN: 30bc04e7
Carrier: Sprint-Nextel
Posts: 24
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

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.
Offline  
Closed Thread


Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On





Copyright 2004-2014 BlackBerryForums.com.
The names RIM and BlackBerry are registered Trademarks of BlackBerry Inc.