Welcome!

Welcome to the official BlackBerry Support Community Forums.

This is your resource to discuss support topics with your peers, and learn from each other.

inside custom component

BlackBerry® OS Smartphones

Reply
New Contributor
Posts: 2
Registered: ‎01-26-2011
My Device: 8830
My Carrier: Sprint

Re: Desktop Manager 6.0 Crashes -- using .NET 2 instead of 3.5

My update or fresh install of 6.0.1.18 crashes too - see http://supportforums.blackberry.com/t5/BlackBerry-Desktop-Software/Desktop-Software-crashes/m-p/7577...

 

Cleaned it all out including registry and reinstalled 5.0.1 - 'cause I couldn't find a 6.0.0 release - yet.

 

 

New Contributor
Posts: 3
Registered: ‎02-15-2011
My Device: Not Specified

Re: Desktop Manager 6.0 Crashes -- using .NET 2 instead of 3.5

I download version 6.0.1.18 and installed totally brand new (no update) in a computer without any BB software and works fine... perhaps is a problem between registers due update.

 

I dont have any ideas about what to do... i've tried every one of the solutions and none of 'em worked.

 

 

New Contributor
Posts: 3
Registered: ‎02-15-2011
My Device: Not Specified

Re: Desktop Manager 6.0 Crashes -- using .NET 2 instead of 3.5

mmmm i dont think it has to be with xp, because i've use it in a computer with XP. However i cant make it work in my personal computer, which is supposed to be totally secured, updated and optimized :s LOL
Contributor
Posts: 21
Registered: ‎09-20-2010
My Device: Curve 8330
My Carrier: Sprint

Re: Desktop Manager 6.0 Crashes -- using .NET 2 instead of 3.5

I switched to an EVO SHIFT.
New Contributor
Posts: 2
Registered: ‎12-17-2009
My Device: Pearl 8130
My Carrier: Verizon

Re: Desktop Manager 6.0 Crashes -- using .NET 2 instead of 3.5

I was able to get DM6 to work following the following steps:

 

To resolve this issue, follow these steps:

  1. Exit all WPF-based applications that are running on the computer.
  2. Stop the Windows Presentation Foundation Font Cache 3.0.0.0 service. To stop the Windows Presentation Foundation Font Cache 3.0.0.0 service, use one of the following methods.

    Method 1: Use Microsoft Management Console
    1. Click Start, click Run, type Services.msc, and then click OK.
    2. Right-click Windows Presentation Foundation Font Cache 3.0.0.0, and then click Stop.
    Method 2: Use the command prompt
    1. Click Start, click Run, type cmd, and then click OK.
    2. At the command prompt, type net stop "Windows Presentation Foundation Font Cache 3.0.0.0", and then press ENTER.
  3. Delete the old Fontcache3.0.0.0.dat file.

    Note By default, the Fontcache3.0.0.0.dat file is located in the %windir%\ServiceProfiles\LocalService\AppData\Local folder in Windows Vista. By default, the Fontcache3.0.0.0.dat file is located in the %systemdrive%\Documents and Settings\LocalService\Local Settings\Application Data folder in Windows XP and in earlier versions of Windows.

quoted from http://support.microsoft.com/kb/937135

New Member
Posts: 1
Registered: ‎08-04-2011
My Device: Blackberry Bold 9700
My Carrier: abc

Re: Desktop Manager 6.0 Crashes -- using .NET 2 instead of 3.5

I solved the problem by turning off my media card support.

 

Turn off mass storage mode support

  1. In the device options, click Media Card.
  2. Set the Mass Storage Mode Support field to Off.
  3. Press the Menu key.
  4. Click Save.

After that, reconnect your blackberry with the Desktop Management, and work perfectly. 

 

OS: Microsoft Windows 7

DM: Version 6.1.0.35

.NET version 4

New Contributor
Posts: 4
Registered: ‎11-08-2010
My Device: Z 10
My Carrier: T-Mobile

Re: Desktop Manager 6.0 Crashes -- using .NET 2 instead of 3.5

Can you be a bit more helpful to some of the rest of us.  I am getting the same issues.

Highlighted
New Member
Posts: 1
Registered: ‎04-24-2012
My Device: Pearl
My Carrier: AT&T

Re: Desktop Manager 6.0 Crashes -- using .NET 2 instead of 3.5

This problem is occurring for restricted users. If you open Blackberry Desktop using "run as administrator", then the problem is resolved. Based on the errors thrown in the application event viewer, it would appear that restricted users do not have the necessary rights to launch applications that use .Net framework 2.0.

 

The application event viewer shows three performance counters was not loaded for System.ServiceModel 3.0 before the Event Type clr20r3, P1null reference exceptions were logged for:

 

1) rim.transcoder.exe

2) rim.desktop.autoupdate.exe

3) rim.desktophelper.exe