BlackBerry Mobile Fusion

[Gareth]

Completely removing both components, cleaning folders, registry etc.

Re-installed as I did before.

Used only the Device Service BAS as an MDM

Service failed to start.

Moved this file as I did before.

Manually started the service.

It started.

Now will see if I can add other BAS Services from BES servers.

[Gareth]

Oh yea, I also changed the Device Service port to 8443 and left Fusion Service port at 443.

[sirmyk]

I am getting this error, but do not use Blackberry Device Service at all. I only need Blackberry Mobile Fusion Studio and UDS.

[sirmyk]

I was able to finally get this working by installing the piece of **bleep** known as Blackberry Device Service, uninstalling it, searching for the msvcr71.dll file, copying it to the C:\Windows\SysWOW64 folder, restarting the service, and then it started working.

All I can say is that RIM/Blackberry is a joke.

[Gareth]

I have had a rim incident open for this.

1. They claim they can't replicate the problem.

2. They have made no acknowledgment of a problem. Although acknowledged the work around.

[adrenaline_x]

THis worked for my WIN2K3 R2 SP 2 (32bit) install with BESX 5.0.3 running with exchange 2003.

The service would not start until i copied the dll to the c:\windows\system32 folder   Syswow64 is the same location on a 64 bit install

In reply to:

Copy the msvcr71.dll file from C:\Program Files (x86)\Research In Motion\BlackBerry Device Service\BAS\external\bin\msvcr71.dll to C:\Windows\SysWOW64\ and then start the service manually