Hi all, we are currently running BES 4.1.2 (SP2) in an Exchange 2003 environment and I FINALLY figured out how to successfully push an application to a device! (woot woot)

I pushed the RIM "Enterprise Messenger" (aka: LCS messenger, aka: Windows Messenger) and I configured it according to the RIM documentation but, when I attempt to connect to my MSN account, I get the following error message on the handheld device:

"please contact your system administrator to enable this service."

I AM the system administrator, and sadly, I cannot help myself.

Anyone know what this message refers to?

We do NOT have any local messaging service/environment setup, I was hoping (and the RIM documentation made it seem possible) to connect to my MSN account with this application.

BTW... I am NOT talking about BBMessenger, this is the messenger released with BES 4.1.

Thanks

The enterprise messenger works with your internal enterprise messenger servers aka Live Communications Server or Office Communications server (not the public Msn messenger/ windows live servers)

I have LCS 2005 with sp1 and I just upgraded and am getting the same messages...any ideas?

I am having this trouble as well. Any fixes on this. Any help is much appreciated

What are you guys logging in with?

Sign in name, username ?
Also is this a clean 4.1.2 install or an upgrade?
Did you select LCS / windows messenger or LCS/office communicator at install / upgrade time?

Hi

I've been having exactly the same problem with a testbed 4.1 server I've been playing with prior to upgrading our 2.2 box. I have BES Express 4.1.2 sitting on Domino 6.5.4FP3 with the Sametime connector installed.

Two of the three users I've set up work perfectly. The third gets this every time. The only thing particularly different about him is that he has an older device and software version (he has a 7730 with 4.0.2, the others have 8700 series, both with 4.1.0).

If anybody has any ideas, I'd happily hear them.

Ian

Can you verify if "BlackBerry MDS Connection Service and BlackBerry Collaboration Service Enabled" is set to TRUE for the user having the issues logging in?

-zip

iF YOU HAVE LCS 2005 AND Enterprise Messenger on devices...when upgrading you have to choose LCS/windows messenger when upgrading if you chose anything else it deletes th correct connector on BES

I can indeed verify that. :o)

Actually, I reckon it must be to do with the handheld software now. One of the two that are working okay was just in the office so I hijacked his BlackBerry and signed into Sametime as my problem user. Straight in!

I'd already upgraded the guy's handheld to the latest version so I'm on plan "B" now which is "Nuking" the handheld and rebuilding from scratch. Let's see what happens!

Ian

Okay...now we're talking.
Nuking the handheld, reloading the software and then reactivating the user on this occasion fixed the problem.

Still not entirely sure why it didn't work for me in the first place and I've not a clue whether the above process would work for Exchange users since what I know about Exchange can be written on the back of a postage stamp but I'm (relatively) happy now!

Which application is on the handheld they are both called Enterprise Messenger but will have different modules.
net_rim_bb_qm_oc & net_rim_bb_qm_lcs
Which option did you install BES 4.1.2 for LCS / windows messenger or LCS/office communicator

You will need the following.
BES 4.1.2 for LCS / windows messenger
LCS 2005 SP1
Enterprise Messenger (net_rim_bb_qm_lcs)

BES 4.1.2 for LCS / Office Communicator
LCS 2005 SP1 (You will require 1 security update)
Communicator Web Access (You will require 1 security update) with a second instance(AJAX enabled)
Enterprise Messenger (net_rim_bb_qm_OC)

Good Luck

I have been having little success getting LCS for the BBs to work. I got the software pushed to the device (net_rim_bb_qm_lcs) as I installed the Windows Messenger component during my last Service Pack upgrade (4.1 SP2). I am logging in with the following credentials:
Sign-in name :email address
username: domain\username
password: domain password

and I get "Server Error (316). Please contact your system administrator if the problem persists." If i do a different combination for sign-in name and username i just get a "You have selected an invalid address" message. Any thoughts or ideas? Nothing in the event viewer for the LCS or BES. Also, I am running LCS 2005SP1

Anyone got any idea I am having the same problem I try to login with Black Berry Enterprise Messenger and I get the same error "Please contact your System Administrator to enable this service."

LCS 2005 SP1 all the hotfixes
BES server
Black Berry 8703e
All policies allow the IM service.

Anyone have a clue what to check?

I had this strange problem when users activated their handheld through the Desktop Manager instead of going through a Wireless Enterprise Activation. When I tried to dig deeper it looked like I had the policies set to restrictive, so after manually setting them to allow all forms of IM, etc. the problem went away.

Can you tell me exactly where you set this in the policy?

Was it the IT Policy or somewhere under the group settings?

I haven't been able to work out how I "push" the app to the handheld. During the upgrade process from 3.6.6 to 4.1.2 I chose the LCS/OC option but that is as far as i can get...

Make sure you have MSMQ (Message Queuing) installed on the BES that you want to run LCS. Once it's installed, restart all the services and it should start. Check the Collaboration Service tab on the console and make sure the ports are all set up, etc.

LCS is working great for us. If we get some of the errors mentioned in this thread, it's usually because MSMQ is either not installed or not started.

I was using the default Policy on my blackberry, but used my BB before with some test policy's... (8700 model). I also received the error that my account was not configured and needed to contact the administrator to have it enabled.

This is what I did to get it working:
- Whipe data from blackberry.
- removed policy from my blackberry

See: general-blackberry-discussion/67224-remove-policy.html

- wireless activation.

run the program:
sign-in name: (email address)
user name: domain\username (must be backslash)
password: ***** (domain password)

Our LCS is running on TCP port 5060