03-29-2012 04:53 AM - edited 03-29-2012 04:55 AM
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.
Now will see if I can add other BAS Services from BES servers.
04-06-2012 07:43 PM
04-07-2012 02:31 AM
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.
04-13-2012 03:27 PM - edited 04-13-2012 03:29 PM
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