02-07-2011 12:08 PM
Hi All, I have had extensive contact with RIM support and they tried to help me solve the problem and did a good job. I am able to sync everything and the only issue is Wifi sync and they were able to reproduce the problem and this will be fixed in an upcoming release.
So my advice is to open an official ticket and support will get back to you and look into your specific case.
02-08-2011 12:26 PM
I've been running circles round the BB support site, but only seem to come across BB Server support. How do I open a ticket to get my Desktop software issues solved?
02-10-2011 07:23 PM
i have the same issue. although, my came on suddenly. one day bb desktop manager was recognizing my device (and mounting them on my OS) the next day it didn't.
my mac: imac running the lastest snow leopard build
my phone: storm (gasp..yes, it's the first one) running OS 5 something or other.
02-11-2011 04:28 AM
As a stop-gap I now use MissingSync to at least get my calendar en contacts in sync. Although it works, it is far from ideal and very unstable. It crashes once every three or four syncs. But when it works, it gets my calendar en contacts across, so I am moderately happy with it.
Still, I would think a company like RIM with a long trackrecord in business phones, would at least make sure their software is up to scratch before putting it on the market. Rather surprising that it isn't...
02-11-2011 12:05 PM
also, as a stop gap, without having to use missing sync, i restart my computer. yes, in the how-to-get-any-windows-program-to-work fashion . the program seem to work the first time after restarting the system. dont' know why, but ti seems to want to behave. i also stopped syncing any media. that seemed to help as well....hmmm...maybe it's the media sync that's problematic.
03-14-2011 12:28 PM
Update: If your MacPro freezes when connecting your Storm (or other Blackberry) via USB do a search for the following driver: com.rim.RimBlackBerryUSB.plist and remove it. Once I removed this driver the freezing issue was resolved.
This problem was found and addressed by an Apple tech at the Genius Bar - no help came from RIM on this issue!