[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 6369
  • Last Modified:

cannot synchronize with the corporate address book - error on internal clients

We have noticed clients have been receiving these error messages as below consistently this year..

"cannot synchronize with the corporate address book because the file could not be found"

we foudn a post on this here http://blankmanblog.spaces.live.com/blog/cns!D0A1CD5B821F0EF9!300.entry?sa=305748799 
Our shared abs folder contains many .dabs and .lsabs - with many of these having modified date of this morning..
Clients galcontacts.db gets modified daily but no new users are appearing in their address books.
In ..\Web Components\Address Book Files\Files our Int and Ext folders are both empty other than we.config files and a bin folder / files.
Do you think this could be our problem?

If not another thing that may be related - we upgraded our .NET version to 3.0 I think a couple of days before we began getting these errors appearing
0
northtecicts
Asked:
northtecicts
4 Solutions
 
HayesJupeCommented:
use abserver.exe /sync and /regenUR to force new address books to be created
check the application event log after doing this, it will lead you to the source of your error.
0
 
northtecictsAuthor Commented:
We ran those two commands and get no errors..
There was one warning about a few number failing to normalise (we're using Telephony) but I don't think this is related..
Any other suggestions?
0
 
HayesJupeCommented:
ok, so the ab is generating correctly (albeit a few normalisztion errors)
so if you goto your OCS server
get the patch to your address book files and enter it into IE
you shoudl be prompted for auth... and then get an error saying the directory contents casnt be listed.
if thats the case, your server side is looking ok.
So turn on full logging in options in your client...
0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 
northtecictsAuthor Commented:
We ran web component validation in OCS 2007 MMC console and got the following errors:-

The message "Failure [0xC3FC200D] One or more errors were detected" were reported on both following path:-

URL: https://OCSServer.np.ac.nz/GroupExpansion/Int/service.asmx
URL: https://OCSServer.np.ac.nz/Abs/Int/Handler/Company_Phone_Number_Normalization_Rules.txt

The detail errors came from IIS and they are the following:-

Received a failure HTTP response.: HTTP Response: 401 Unauthorized
Content-Length:1539
Content-Type:text/html
Server:Microsoft-IIS/6.0
WWW-Authenticate:Negotiate,NTLM
X-Powered-By:ASP.NET
Date:Fri, 13 Feb 2009 04:26:44 GMT


You are not authorized to view this page

You do not have permission to view this directory or page using the credentials that you supplied.
 
Please try the following:
·         Contact the Web site administrator if you believe you should be able to view this directory or page.
·         Click the Refresh button to try again with different credentials.
HTTP Error 401.1 - Unauthorized: Access is denied due to invalid credentials.
Internet Information Services (IIS)
 
 
Technical Information (for support personnel)
·         Go to Microsoft Product Support Services and perform a title search for the words HTTP and 401.
·         Open IIS Help, which is accessible in IIS Manager (inetmgr),
and search for topics titled Authentication, Access Control, and About Custom Error Messages.


Received a failure HTTP response.: Unauthorized
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
0
 
NerdAtLarge403Commented:
Neither of those web pages are designed for human viewing through a browser - they are web services which 'speak' to your MOC clients through TLS and you shouldn't expect them to deliver understandable content via browser.

I've just gone through a lot of trials and tribulations with my Address Book service and got a whole lot more familiar with it that I had ever wanted to.  You post is a couple weeks old now, if you're still running into trouble please let me know by posting something here.

If you run and address book server dump, do you see your 'new' users in the resulting text file?
( C:\Progra~1\Micros~2\Server\Core\abserver -dumpfile \\srv-van-sql\ABS\XXXXX.lsabs (where XXXXX is the name of the newest lsabs file in your abs share)?

Knowing that would narrow us down to whether your breakdown is occurring at the address book generation or publishing level.
0
 
northtecictsAuthor Commented:
Hi thanks for the follow up..
Yes we've resolved our problem now.
Turns out that when we installed .NET 3.0 it somehow unregistered two of the DLL's (.lsabs and .dabs) and also disabled the .NEt 2.0 web service extension.
After we restored these all's been well
0
 
dharnetCommented:
cannot synchronize with the corporate address book - error on internal clients on my pc where as it works for other PC clients. Please advise what need to be look on the client which is not pulling the address book files.
0
 
northtecictsAuthor Commented:
dharnet - if none of the above helps you (sounds like you have a different problem to ours) then I'd suggest you post a new question.. Good luck
0
 
DownTownMTBCommented:
northtecicts, Was the .NET work done on the clients or the Front End server?
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now