Blackberry Connection Specific Error
Well, I just encountered yet another issue with my blackberry that lost me several hours and data related to synching between my Blackberry and my PC. Over the past week, I kept getting a "Connection Specific Error" when synching with the Blackberry Desktop Manager (which means that my calendar entries were not being synched between outlook and my device). I looked at the log, which just gave me an "Internal Error #4238" message just before cancelling the transaction at the bottom of the log (not very useful)
So, I went to google to find out what the problem might be and how to work around it. Although much of what was out there was close to being right (there seems to be data in one of the calendars that is causing it to crash), much of the focus was on how to delete calendar items in outlook. Unfortunately, my issue happened to be with one of the calendar entries on my device (and not on my PC). I finally figured that out by trial and error (but I could have seen in the progress of the synch that the crash was occuring when reading the device calendar and not the outlook calendar).
So, I ended up deleting all of my future entries in outlook after printing them out to manually enter later (which didn't fix the issue and ended up adding a lot of work).
So, how did you fix it
Well, I ended up having to figure out how to delete everything from my device calendar (which is fine, because I can just re-synch it from outlook). To do this, you will need to go to Desktop Manger on your PC (yes, you have to use your PC to clear your device's calendar!). From there, you double click on Backup and Restore (yes, not where you would expect it to be). Click on the advanced button to see the list of databases on the device. Scroll down to Calenar (in the right hand list) and select it. The clear button will ungray and you can clear the database by clicking on that. You can then re-synch if the problem is the same as mine.
Arrgh
The folks at RIM could have saved me a lot of time by any of the following:
- Putting more information in the log about what stage of the synch it was on (device), and even what calendar entry that was causing the error.
- Providing an option to turn on detailed logging from desktop manager
- Making it easier to clear the database on the device (such as providing the option inside the calendar)
- Providing better information on the web (most of the links in posts related to my issue had been removed from the RIM support site
Labels: Blackberry, problems

8 Comments:
Thank you Larry - I was getting very frustrated with the same error you were getting and blackberry support was no help. You saved me from a lot of further aggravation!
Rob
Thank You!, Thank You!, Thank You!!!
Frank
You are a true lifesaver. You saved me tons and tons of aggravation. I could kiss you, but NO. That is not for me. A thank you should suffice. Prospero.
I'm on the phone with Verizon/RIM now and after wasting an hour with them, your post fixed the problem in less than 5 minutes. THANKS!
Thank you Thank you Thank you... I have been having this problem for about 2 week. The wierd thing is that i only get the error when syching via Bluetooth. Glad to see i did not have to re enter all 175 calendar entries.
Thanks Again
TJ
Dude...you are awesome! Tried everything from everywhere including 30 minutes on phone with Verizon and no help at all. I too missed the fact that the file error was on the blackberry end not outlook which I was spending all my time deleting calendar files in outlook. Your fix worked perfectly! People should know you need to have your blackberry connected to the pc when you go into desktop manager to do backup and restore or it won't show the databases. Maybe I'm dumb but I thought I'd throw it out there.
As with the other comments, I didn't know what to do and the online help was not adequate. Your solution worked for me, although it was Tasks that was the issue.
Thanks for the help.
Tyler
How can we figure out what is casusing the problem? I deleted my calendar entries and am still getting the same error message.
Post a Comment
<< Home