Thank you for visiting the BlackBerry Support Community Forums.
BlackBerry will be closing the BlackBerry Support Community Forums Device Forums on April 1st (Developers, see below)
BlackBerry remains committed to providing excellent customer support to our customers. We are delighted to direct you to the CrackBerry Forums, a well-established and thorough support channel, for continued BlackBerry support. Please visit http://forums.crackberry.com or http://crackberry.com/ask. You can also continue to visit BlackBerry Support or the BlackBerry Knowledge Base for official support options available for your BlackBerry Smartphone.
"When we launched CrackBerry.com 10 years ago, we set out to make it a fun and useful destination where BlackBerry Smartphone owners could share their excitement and learn to unleash the full potential of their BlackBerry. A decade later, the CrackBerry community is as active and passionate as ever and I know our knowledgeable members and volunteers will be excited to welcome and assist more BlackBerry owners with their questions."
- Kevin Michaluk, Founder, CrackBerry.com
Developers, for more information about the BlackBerry Developer Community please review Join the Conversation on the BlackBerry Developer Community Forums found on Inside BlackBerry.
10-06-2011 11:38 AM
I have a Curve 8330 and cannot get the Desktop Manager to connect with it. This was a frequent problem for a long time until the the latest DM upgrade. Suddenly, now the same thing is happening. DM just shows "connecting" but no connection takes place. I've uninstalled then downloaded and reinstalled v6, but no luck. Anyone have any suggestions?
10-06-2011 08:49 PM
Hi and Welcome to the Community!
Here is the list of troubleshooting articles...hopefully something will be useful:
KB28457 BlackBerry Desktop Software is unable to detect the BlackBerry Smartphone due to administrative permissions
KB28458 BlackBerry Desktop Software is unable to detect the BlackBerry Smartphone when user account control is enabled
KB28459 BlackBerry Desktop Software is unable to detect the BlackBerry Smartphone when a full version of Roxio® Media Manager is installed
KB28456 BlackBerry Desktop Software is unable to detect the BlackBerry Smartphone when USB selective suspend setting is enabled
KB28444 The BlackBerry smartphone is not detected by BlackBerry Desktop Software when connected by USB to a USB hub or a docking station
KB28443 BlackBerry Desktop Software cannot detect the BlackBerry smartphone when it is connected via USB
KB02640 Troubleshooting USB connections
KB15486 Top 10 BlackBerry smartphone and BlackBerry Desktop Manager troubleshooting tips
KB00125BlackBerry Desktop Software cannot detect the BlackBerry smartphone
KB11439 BlackBerry Desktop Software does not detect the BlackBerry smartphone when it is connected
KB00019 No PIN displayed in BlackBerry Desktop Redirector
KB10938 "USB charging current is insufficient" appears on the BlackBerry smartphone
KB01451 How to turn on advanced synchronization logging if a wired synchronization fails
KB19717 The BlackBerry smartphone is not detected as a USB Mass Storage Device when connected to a computer
KB16310 Media Transfer Protocol and the BlackBerry Storm smartphone
Also, check that you are using only root USB ports...no hubs (sometimes the front-side ports are hubs...use a rear USB port). And make sure to try disabling USB power management in your system configuration (Device Manager).
Also check on conflicting software...it has been reported that the software package NTI Shadow&Ninja can cause a conflict; removing them and reinstalling the BB desktop software allows it to install correctly.
Apologies in advance if this is redundant -- there's no way to be sure if you've already seen and tried these. Also apologies if any are not presently available...RIM takes them up and down at will as they revise things.
Hopefully something there is helpful!
10-10-2011 09:24 AM
Thanks! You've certainly given me plenty of options, so I'll start at the top aned work down from there. I'll Reply again once I've found one that fixes my problem.