4.1 SP2 LCS jmsmq.dll error collaboration service
 

Hello,

I first installed SP2 using "LCS/Office Communicator" option, then realized I needed "LCS/Windows Messenger" in order for BES to use TCP/TLS to interact with LCS, so I installed SP2 again (over existing SP2).

Now my collaboration service seems to be hozed... It's status displays as blank in bb enterprise manager, handheld clients get error 302, and the following error is displayed in BBIM log :

<2006-09-20 10:02:46.901 EDT>:[7]:<BBIM_NS1020_BBIM_1>:<ERROR>:<LAYER = SCM, Can't load library: C:\Program Files\Research In Motion\BlackBerry Enterprise Server\BBIM\Servers\SERVERNAME/bin/Jmsmq.dll>

and event log:

Event Type: Error
Event Source: BlackBerry Collaboration Service
Event Category: None
Event ID: 15000
Date: 9/20/2006
Time: 11:33:46 AM
User: N/A
Computer: SERVERNAME
Description:
<2006-09-20 11:33:46.199 EDT>:[75]:<BBIM_NS1020_BBIM_1>:<ERROR>:<LAYER = SCM, Can't load library: C:\Program Files\Research In Motion\BlackBerry Enterprise Server\BBIM\Servers\SERVERNAME/bin/Jmsmq.dll>


there is no such DLL on the entire machine (MSMQ is installed though).

Any ideas/suggestions ? Thanks.

We had the same problem.
 

We installed the exact same way you did, realized our mistake and did a reinstall just as you did. The results were the same.

In our environment we run SQL server so I can ony attest to this fix working on SQL server based dataases and don't know what would happen if you are using msde.

We were able to solve this 2 ways. We have 2 servers and each method worked.

Method 1:
You will need the Original 4.1 Install files.
Run setup.exe form the version 4.1 files and from the menu choice select the option to just install the LCS service (you will see variations of what and how you want to install) Follow the prompts to complete the LCS services install.

You then must reinstall Service pack 2 selecting the Windows messenger option.

We also upgraded our Client versions of the LCS software before this update was done, so I am not sure f the older client would still connect to the newer instance.

This method was easy and painless but only worked on one of our 2 servers.


Method 2:
You will need install files for 4.1 install and service pack
Perform uninstall of BES
Reinstall BES 4.1 with your settings except when prompted to interact with the database give new database names for the 3 databases. You will need them only long enough to finish the upgrade. Complete the install.

Install SP2 with the Windws Messenger option selected. When the database screens come up enter you original database locations and names. The install will see the upgrade is done already and basiclly go past this part. Finish the install.

Your original settings, policies etc... should all be available and your LCS service should be back and running. This method took us 22 minutes from start finish.

Hope this helps.

Thanks!
 

Guzilla,

I used your method 2 (using 4.1 - which you meant to type instead of 4.0) and it worked like a charm... 20 min and things are up and running again :smile:

Thanks a mil !!!

good to hear
 

just noticed i typed 4.0, you are correct as I meant 4.1.

Glad I could help.