I am still having problems with this. I will follow up tomorrow with the results from your suggestions.
Main Topics
Browse All TopicsAfter installing Office Communicator 2007 users are not able to access the corporate address book. Everything else seems to work as expected. I have attached the error messages they recieve upon logon. The first box asking for credintials pops up everytime the user logs into the machine, even if you type in the correct credentials.
Any help in solving this will be greatly appreciated.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
I forgot to say how you can check if the SSL certificate on the OCS is the problem.
- Open the Office Communications Server 2007 management console
- Expand to the server that is running the web components
- Select the FQDN of the server (server.domain.com)
- On the right you see available tasks --> validation. Expand
- Select Web Components Server and complete the wizard. If it fails with errors on connectivity, you probably see that iis default web site needs a valid certificate even if you do NOT require SSL on the ABS component. In that case submit a request to an internal or external CA and install the certificate on the default web site (using the button 'server certificate...' on the directory security tab
I had the same problem and solved it with the help of the validation wizard.
If you have other errors, you can always post them here
Error is:
Received a failure HTTP response.: InternalServerError
Suggested Resolution: Check whether the Web Server or Office
Communications Server component is running and also listening on
the specified url. If server is behind a load balancer, please make
sure the loopback connection is allowed from load balancer FQDN.
Suggested Resolution: Check the Web Proxy setting in this
machine and ensure that it is correctly configured
Do you use a proxy server?
Do you have sharepoint installed on the same server?
Check all the services regarding OCS2007 and IIS and see if they are started.
Check the permissions on the IIS server on the default website.
Did you have a certificate on the ABS component? start --> run --> inetmgr --> expand default website --> do you see the ABS component? Properties of default website --> directory security tab --> can you view the certificate?
Check the user on the applicationspools in IIS -> Apllicationpools -> LSGroupExpAppPool -> Properties -> Identity -> the User should be RTCComponentService
UCdeviceUpdater -> Properties -> Identity -> the User should be RTCComponentService
Also check the permissions on the ABS component in IIS. Anonymous access should be disabled, but you can enable integrated windows auth. and basic authentication.
Test the URL in the browser on a client: https://computername.domai
The user under the Identity tab is RTCService. Should I change it to RTCComponentService?
If I go to https://computername.domai
The website declined to show this webpage
The title of the webpage is HTTP 403 Forbidden.
Thanks for all the help and quick responses!!!!
You're welcome!
First of all, we narrowed the problem down to the security settings (Forbidden)
Yes, change to RTCComponentservice. It should look like domainname\RTCComponentSer
Test the URL again, test also without SSL (http://computername.domai
If that doesn't work, allow anonymous access
Currently we're having similar issues here.
-Office Communicator works just fine, it's just the synchronization with the corporate address book is the issue.
-I've tried all the suggestions from above and still no go.
-Certificates are working fine, RTCComponentService is being used but we still can't get to the <server>/Abs website either through SSL or not, even with anonymous access.
Let's start from the beginning:
- Can you ping the webserver from the clients?
- IIS services are all up and running?
- Do you see the ABS website in IIS on the OCS server?
If you can't access the abs website through https://server.domain.com/
Might want to try this link to see if it helps you at all
http://communicationsserve
I personally went through and verified some of those permission settings with the RTC usergroups to the directories local on the server where OCS is running and it didn't help. Still have the warning message.
Should note that any user in our organization can right now download to an address file manually through Internet Explorer so the permissions seem to be setup ok on that end, but the actual application itself still has the error from the initial poster.
Hi Edmond,
Did you turn on directory browsing in IIS?
The users can access the ABS website from IE? They see three directories listed: Ext, Files and Int
If they can see this directories and directory browsing is enabled, the OCS client should access the address book files. For testing, you have to restart the ocs client, also in the system bar on the right.
If this and above does not help you, could you provide more info on your situation and in brief the steps you took?
Thrain, Thanks for your responses:
To clarify what we're running into: If I turn on directory browsing in IIS any user in our organization can browse the files/directories if they connect to https://<servername>/abs. I'm not having any issue with that which is what is so bizarre. The certificate for SSL and permissions for accessing those directories are working fine as they can browse to those directories just fine through a web browser.
Even with that part working fine, every user of communicator still receieves the original error described (cannot synchronize address book information). Based on everything I've seen, what we've done should have resolved the issue. I'll type up some more information about our situation tonight as well.
Should the ABS Folder be a share? Also, I just noticed that I am receiving the following error message on the server:
Event Type: Warning
Event Source: ASP.NET 2.0.50727.0
Event Category: Web Event
Event ID: 1310
Date: 3/27/2008
Time: 8:26:40 AM
User: N/A
Computer: COMPUTERNAME
Description:
Event code: 3008
Event message: A configuration error has occurred.
Event time: 3/27/2008 8:26:40 AM
Event time (UTC): 3/27/2008 12:26:40 PM
Event ID: bd5da63f2f434168817a1a28d1
Event sequence: 1
Event occurrence: 1
Event detail code: 0
Application information:
Application domain: /LM/W3SVC/1/Root/Abs/Int/H
Trust level: Full
Application Virtual Path: /Abs/Int/Handler
Application Path: D:\Program Files\Microsoft Office Communications Server 2007\Web Components\Address Book Files\Int\Handler\
Machine name: COMPUTERNAME
Process information:
Process ID: 6520
Process name: w3wp.exe
Account name: domainname\RTCComponentSer
Exception information:
Exception type: ConfigurationErrorsExcepti
Exception message: An error occurred loading a configuration file: Access to the path 'C:\inetpub\wwwroot\web.co
Request information:
Request URL: https://computername.domai
Request path: /Abs/Int/Handler/D-08d5-0a
User host address: 192.168.84.31
User:
Is authenticated: False
Authentication Type:
Thread account name: domainname\RTCComponentSer
Thread information:
Thread ID: 6
Thread account name: domainname\RTCComponentSer
Is impersonating: False
Stack trace: at System.Web.HttpRuntime.Hos
Edmond and pghzooit,
Check the name of the file share location for the address book: http://www.ocspedia.com/AB
which version of ocs 2007 do you have? standard or enterprise?
pghzooit, ABS folder is not a share if located on the same server as IIS. I see that you installed OCS under D:\Program Files\Microsoft Office Communications Server 2007\Web Components\Address Book Files. On this directory make sure the NTFS rights are List folder contents,read, read & execute.
In IIS, properties of ABS the local path has to be the same path if iis is on the same server (D:\Program Files\Microsoft Office Communications Server 2007\Web Components\Address Book Files). Application pool on the same screen is lsgroupexpapppool.
You have also a problem with the User domainname\RTCComponentSer
Make sure aonymous access is enabled on the abs website and folders below in iis. According to a post it has to be enabled. It is enabled in my testing environment: http://forums.microsoft.co
i do not quite get following error:
Exception information:
Exception type: ConfigurationErrorsExcepti
Exception message: An error occurred loading a configuration file: Access to the path 'C:\inetpub\wwwroot\web.co
My guess is the handler directory is configured wrong in iis. Should look like D:\Program Files\Microsoft Office Communications Server 2007\Web Components\Address Book Files\Int\Handler or ext\handler. There is a web.config file there. Check all your directories in iis.
When testing in ocs try rebooting clent computer first.
I've been watching this thread because I am having the same exact problem. Though probably unrelated, I didn't start having the problem until I installed and activated Communicator Web Access. Even after uninstalling, I still had all the same problems you had.
The good news is that I finally fixed it after finding this site:
http://blogs.technet.com/j
What actually fixed it was running the following command on the LCS server:
Setspn -A HTTP/{servername} {domainname}\RTCComponentS
As soon as I ran that on the server, I restarted communicator and it didn't prompt me for credentials. Hope this helps you too.
Check the ports you are using for each website if you also have CWA installed on that server. I.e. click Properties on the Default Web Site (or the site for OCS) and verify the SSL port is set to 443. I then went and changed my CWA site to use port 8443.
I had changed these around when I installed CWA so I could more easily access that site without having to remember to put the additional port qualification when navigating to it.
Not sure if there's a way to swap these by changing a setting within OCS or the MOC client to tell it that the OCS website is located on a different port so you can keep CWA on the standard 443.
Trying to lab this product by using as few servers/virtual machines as possible is much harder than it should.
Business Accounts
Answer for Membership
by: ThrainSonOfTimorPosted on 2008-03-13 at 09:27:32ID: 21117904
I don't know if you still need help with this one, but maybe you could try the microsoft solution to your problem: om/kb/9382 86
com/kb/939 530/en-us)
http://support.microsoft.c
Or if that doesn't solve your problem, you have to check if you have an SSL certificate installed for the address book website in IIS. It seems that it is obliged to have one (http://support.microsoft.