[hindgrinder]

This maybe the completely wrong are to post this.....

I have the Office Communicator Web access 2007 installed and fully functional.
I'm trying to figure out all the steps needed to integrate enterprise messaging with my BES. This ajax.dll file thats needed for OCWA, where do i get it from. I cant find it on the 2007 OCS disk. As stated earlier my ocs is fully functional via the web.

Any ideas?

Thanks

[RayGee]

check C:\Program Files\Microsoft Office Communicator Web Access\ajax

In IIS Manager:

1) Right-click Web Service Extensions folder and choose 'Add a new Web service extension...'
a. Fill in the Extension name field with "Ajax"
b. Add the 'ajax.dll' from C:\Program Files\Microsoft Office Communicator Web Access\ajax
c. Place a check in the Set extension status to Allowed box
d. Click OK
2) Right-click the CWA virtual Web server and choose Properties
a. Go to the ISAPI Filters tab
b. Add the 'ajax.dll' file from C:\Program Files\Microsoft Office Communicator Web Access\ajax
c. Click OK
3) Right-click the CWA application from within the CWA virtual Server and choose Properties
a. Go to the Virtual Directory tab
b. Click the 'Configuration...' button
c. Under Wildcard application maps (order of implementation): click 'Insert...'
d. Insert the 'ajax.dll' file from C:\Program Files\Microsoft Office Communicator Web Access\ajax
e. Click OK and OK
f. Restart the CWA virtual Web server


Regards-------

[hindgrinder]

I have done a physical search for the ajax.dll file and it doesn't exist on the server.

[penguin3107]

Originally Posted by hindgrinder

I have done a physical search for the ajax.dll file and it doesn't exist on the server.

I believe all of the "ajax stuff" was for LCS 2005 integration.
We're on OCS 2007 and it's integrating fine with BES 4.1.6 ... and I never did any of the above steps related to ajax.

[hindgrinder]

Thats good to know. I havent installed 4.1.6 yet, just waiting for the go ahead fom our Server Manager.


Thanks

[slickvision]

penguin,

I just downloaded the handheld client for LCS 2007. I have BES 4.1.6 installed on the server and we are using Exchange 2007 with LCS 2k7.

I have never setup this before -- LCS is working fine on workstations, but for the life of me, i have no idea why or what steps to take to get it to work on our BB? Can you (or anyone else) assist with the steps? ..or point me to the right article (though i tried that already)

[CYUL]

Originally Posted by RayGee

check C:\Program Files\Microsoft Office Communicator Web Access\ajax

In IIS Manager:

1) Right-click Web Service Extensions folder and choose 'Add a new Web service extension...'
a. Fill in the Extension name field with "Ajax"
b. Add the 'ajax.dll' from C:\Program Files\Microsoft Office Communicator Web Access\ajax
c. Place a check in the Set extension status to Allowed box
d. Click OK
2) Right-click the CWA virtual Web server and choose Properties
a. Go to the ISAPI Filters tab
b. Add the 'ajax.dll' file from C:\Program Files\Microsoft Office Communicator Web Access\ajax
c. Click OK
3) Right-click the CWA application from within the CWA virtual Server and choose Properties
a. Go to the Virtual Directory tab
b. Click the 'Configuration...' button
c. Under Wildcard application maps (order of implementation): click 'Insert...'
d. Insert the 'ajax.dll' file from C:\Program Files\Microsoft Office Communicator Web Access\ajax
e. Click OK and OK
f. Restart the CWA virtual Web server


Regards-------

This is not working, we've tried several times and several ways.


Paul

[CYUL]

Originally Posted by hindgrinder

This maybe the completely wrong are to post this.....

I have the Office Communicator Web access 2007 installed and fully functional.
I'm trying to figure out all the steps needed to integrate enterprise messaging with my BES. This ajax.dll file thats needed for OCWA, where do i get it from. I cant find it on the 2007 OCS disk. As stated earlier my ocs is fully functional via the web.

Any ideas?

Thanks

You do not need this file. No longer used in this version as per RIM.

Paul

[Devious]

Does anyone else notice that if you keep your OCS logged in its a real battery killer?

Without the client running, I can go 2 1/2 days without a charge, with it running, i can hardly hit 8 hours!

[penguin3107]

Wirelessly posted (Breaking Ball)

Originally Posted by Devious

Does anyone else notice that if you keep your OCS logged in its a real battery killer?

Without the client running, I can go 2 1/2 days without a charge, with it running, i can hardly hit 8 hours!

What device and OS?
(I can't see your profile on WAP)

I don't have that issue.
8310 with 4.5.0.69

[Keyscan]

Be sure to have Windows Authentication enabled on your OCS server. BES requires it I believe, and if you only have Forms Based enabled, you will not be able to login via the handheld.

[Devious]

Sorry, my profile is probably out of date as is -- I tend to like to upgrade frequently. I found it on the 8300 Curve (GSM) and now on the Bold. Surprisingly I had it fully charged this morning and its down to 20% at 6pm. On the weekend I close the IM and it doesn't have the same issue. Granted, I have 250 people on my roster.. i wonder if this is part of the effect (and why others may not be experiencing the same issue)

Originally Posted by penguin3107

Wirelessly posted (Breaking Ball)



What device and OS?
(I can't see your profile on WAP)

I don't have that issue.
8310 with 4.5.0.69