Welcome to Port3101.org : Your BES Connection Mark forums read | View Forum Leaders
Port3101.org : Your BES Connection



Reply
LinkBack Thread Tools Display Modes
Anyone using LCS2005 and BES Collaboration?
 
  #1 (permalink)  
Old 01-22-2010, 02:59 PM
BES Administrator
 
Join Date: Jan 2009
Location: Atlanta
Posts: 41
Default Anyone using LCS2005 and BES Collaboration?

I am having a heck of a time getting IM access to work correctly via my 5.0 servers so I'm looking for any help from someone who has it working. We are using 5.0.1 with LCS 2005 SP1 for IM, with a Communicator Web Access 2005 server AJAX setup as described in KB13530.
I have 2 different test devices with the correct Enterprise Messenger version according to the IM compatibility matrix, but when I try to log in, I get 'Feature Not Supported'.
If anyone has any input, I would appreciate it. This is the last stumbling block keeping me from fully deploying 5.x.

EDIT: Found the problem--in IIS, I had incorrectly set the AJAX site virtual directory wildcard application maps for not only ajax.dll but also cwaauth.dll and apparently the BES connector didn't like that. Once I removed the cwaauth.dll from the wildcard application map list, it worked. I was misunderstanding the KB section referring to ISAPI filters for both ajax and cwaauth.

Last edited by jdizzle; 01-29-2010 at 11:28 AM. Reason: Problem fixed
Reply With Quote
Sponsored Links
  #2 (permalink)  
Old 01-22-2010, 08:28 PM
RadHaz75's Avatar
BES Expert
 
Join Date: May 2009
Location: Philadelphia, PA
Posts: 98
Default

did you follow the instructions in the CWA documentation about setting up the AJAX support? it requires creating another iis site which in turn must use a different port since the cwa site itself uses 443. so your ajax setup will be using a different port like 444.

i just went through this. i set up the second ajax site and followed the instructions in the cwa doc and it worked like a charm
__________________
Two months ago, I saw a provocative movie on cable TV. It was called The Net, with that girl from the bus.
Reply With Quote
  #3 (permalink)  
Old 01-25-2010, 03:40 PM
BES Administrator
 
Join Date: Jan 2009
Location: Atlanta
Posts: 41
Default

I did follow the doc KB13530, but it didn't occur to me that using port 443 for the AJAX site conflicts with the default CWA site. So I blew away the old AJAX site from CWA and IIS and did it again from scratch just to make sure I hadn't missed anything, and to put in a different port number. Now when I attempt to sign in, it sits at 'Connecting' for about 5 minutes, then errors out to 'Cannot connect to server'. So its still not working, but I may be making progress since I at least have the port #s right now.
FWIW, if I put in a bad password, it errors out after a few seconds and tells me the password wasn't accepted so I know its at least authenticating somewhere.
Reply With Quote
Reply

Bookmarks

Thread Tools
Display Modes

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

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



All times are GMT -4. The time now is 03:13 PM.
Powered by vBulletin® Version 3.8.4
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
SEO by vBSEO 3.3.2