BlackBerry Forums Support Community               

Closed Thread
 
LinkBack Thread Tools
Old 10-30-2007, 03:44 PM   #1 (permalink)
New Member
 
Join Date: Oct 2007
Model: 8300
PIN: N/A
Carrier: Verizon
Posts: 2
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default BES 4.1.4.15 and OCS 2007

Please Login to Remove!

Greetings all:

I'll try to word this as helpfully as possible. Today I re-installed my BES server in order to choose the IM connector for LCS so we could use the Enterprise Messenger version 1.1.0.18 for LCS. The problem is we are using Office Communications Server 2007, rather than the 2005 SP1 that is reccommended. I pushed the Enterprise Messenger client using the BES to a single test phone, and the user attempted to sign in. While signing in, the process stops and an error appears stating "Please contact your administrator to enable this service."

Now there are several possiblities as to what could be the problem here, and I was hoping for some insight from the community here.

Option 1:
BES version 4.1.4.15 just "doesn't work" with OCS 2007. I've gone through the settings on the server that seem to relate to the IM connectivity. I've set the hostname and port of the OCS 2007 Web Access server in the Collaboration Service tab. The values I used here are verified correct, as from Internet Explorer you can log in through Web Access and use Communicator just fine. However, I have never received an option to choose between TCP and TLS for the communication protocol. The only options I have here are HTTP and HTTPS. For the time being, I have selected HTTPS, as that is what the Web Access server is using. I've verified that Collaboration Services and MDS Connection Services are enabled for the user testing the software. Going through the logs shows no messages about BB IM, either for success or failure. In fact, there is no BB IM service running at all, which could be a negative sign. It still "sees" the OCS server though if you check under the IM To BES Mapping option, which is strange.

Option 2:
When I pushed the Enterprise Messaging client out to the phone, I screwed up and left something restricted where it should have been allowed, causing the message about "contacting the Administrator to enable" comes from. In the software policy for the push, I set the External Network Connections and Internal Network Connections both to "Allowed", as well as checking it on the phone itself for being blocked. I can't see anything that would be actively preventing the application from making a connection, but I'm fairly new at this whole BES administration thing and could be overlooking something obvious.

I called RIM support and they basically told me that OCS 2007 is not supported as of yet, although I have read one post on this forum where someone had it working.

Can anyone point me in the right direction to get this configuration working?

Thanks for your help!
Offline  
Old 10-30-2007, 06:02 PM   #2 (permalink)
Thumbs Must Hurt
 
Join Date: Apr 2005
Location: South FL
Model: 8300
Carrier: AT&T
Posts: 63
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

It does not work with OCS 2007. But the work around we are doing right now is to run an LCS 2005 SP1 server with the web access components on it and point the BES server at that and you will be able to get in and everything works(meaning you can IM with the people on OCS 2007). But there is one caveat. The users that are going to use this can not be upgraded to enhanced presence. If they are then the only thing they can sign into is OCS 2007 and of course that does not work.

I spoke to RIM yesterday about this and the response I got was that they where going to have support for it in the next service pack. But now it has been pushed out until sometime next year. I really hope he was wrong.
Offline  
Old 10-30-2007, 08:04 PM   #3 (permalink)
Thumbs Must Hurt
 
TDOERR's Avatar
 
Join Date: Jan 2006
Location: Alabama
Model: 9000
Carrier: Cingular AT&T
Posts: 67
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default working ocs 2007 with bes

I have bes working with ocs 2007. I was orginally using lcs 2005 using tcp as connection type. And tried upgrade and had issues with database side of ocs. Did clean install of ocs with auto configuration. After running install I had to repoint bes to new pool name and it works. Not supported by rim. Sorry can't be of more help. We don't use web access stricklty client.
Offline  
Old 10-31-2007, 09:37 AM   #4 (permalink)
New Member
 
Join Date: Oct 2007
Model: 8800
PIN: N/A
Carrier: AT&T
Posts: 1
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default Version

Can you tell me what version of BES you have working with the LCS connector? I haven't loaded it yet, but would like to try and hopefully succeed as you.

I talked to bes also, and they told me it would be a few months before they supported ocs 2007.
Offline  
Old 11-01-2007, 07:53 AM   #5 (permalink)
Thumbs Must Hurt
 
TDOERR's Avatar
 
Join Date: Jan 2006
Location: Alabama
Model: 9000
Carrier: Cingular AT&T
Posts: 67
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default BlackBerry Enterprise Server Version: 4.1.4.12

BlackBerry Enterprise Server Version: 4.1.4.12
Offline  
Old 11-06-2007, 09:16 AM   #6 (permalink)
New Member
 
Join Date: Oct 2007
Model: 8300
PIN: N/A
Carrier: Verizon
Posts: 2
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

Just thought I'd post my progress to see if anyone has suggestions. I feel like I am close to getting it to work.

The first step is removing the LCS connector and installing the Windows Messenger connector. This step seems counter-intuitive, but for some reason the LCS connector doesn't actually work with the LCS server per se, it connects to the web client, which is not what we want. Once you have the right connector installed, you can now choose the TLS/TCP option, as well as the correct port (5061).

To get the Windows Messenger connector installed, you need the Microsoft Message Queuing service installed. You can add this through Add/Remove Windows Components, underneath the Application Server category. The service is called Message Queuing. Once you install MSMQ and the Windows Messenger connector, you can then see that it starts the Blackberry Instant Messaging service.

The server actually relays the IMs through the BES to the OCS server, so for the address of the OCS server, you'll want to use the internal or Front End server address.

On your BES install CD, there are 2 different IM clients inside the IM directory that work with LCS. One is called lcs.zip and the other is called oc.zip. For connecting using the TLS/Windows Messenger connector, you'll want to use the oc.zip client. This was a mistake I made because I used the one downloaded from Blackberry's site, which is for the LCS connector/web client front end. I wiped the test handheld and repushed the correct oc.zip client. After this, I tried to log in, but it just sat for a while and then gave an error message that said "Server Busy". This is error number 302.

I created a test user on the OCS 2007 server, because I wanted to see if enhanced presence caused a problem with the client designed for 2005. However, there is no way to disable enhanced presence on a user created on a 2007 server. I later stumbled across some steps using ADSIedit from the Windows 2000 Server resource CD to go into the user's Active Directory properties and remove enhanced presence. The value you are looking for is msRTCSIP-OptionFlags in the AD attributes. The default value is 0. 1 is for Public IM connectivity, and 256 is for enhanced presence. If you edit this value to be 0 (or 1 if you want public IM), the enhanced presence will be gone, and you should theoretically be able to use a 2005 client as if you were created on a 2005 server. Please note this is no way supported by Microsoft, and I can't be responsible if you hose anything up. In any case, I couldn't see a difference using this user to try to log in, I still have the same Error 302.

In any case, this at least says to me that it is talking to the server, just failing to log in. I think that possibly a LCS 2005 client cannot log into an OCS 2007 server, as I have tried the actual Communicator 2005 client and failed to log in as well. If anyone has some insight as to where to go from here, I would be grateful.

And thanks for all the suggestions so far!

Last edited by eramnes : 11-06-2007 at 09:47 AM.
Offline  
Closed Thread


Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On





Copyright 2004-2014 BlackBerryForums.com.
The names RIM and BlackBerry are registered Trademarks of BlackBerry Inc.