Hi,

My organization are having some issues with phone numbers replicating from AD to Lync 2013.  Up to 2 weeks ago this worked fine no issues, all of a sudden it just stopped.  The AD field we use is telephoneNumber.  There is nothing obvious in the logs etc.  It looks like normalisation is disabled/set to false.  When trying to verify the topology there are errors see below.  Is it possible that someone changed the share permissions on the LyncAddressShare folder, could this be causing the issue.  There was one other thing.  I changed my title on AD and after deleting my sip folder locally this replicated no issue.  Any suggestions would be very helpful

Warning: Unable to access share permissions for "\\XXXXXXXXXXXXXX\LyncAddressShare". This is expected if you are not an administrator on the file server, or if this is a Distributed File System (DFS) share. If the share permissions have already been configured, this warning can be ignored. If it is a new share, refer to the documentation for details on manually configuring share permissions.

Have you seen the share permissions on the folder? Do you see any changes?

Please check groups RTCHSuniversalServices, RTCComponentUniversalServices, RTCUniversalServerAdmins and RTCUniversalConfigReplicator have Change and Read permission to access Lync Server file share.

Run the command Test-CsAddressBookService to test the ability of a user to access the server that hosts the Address Book Download Web service.

For the information about the command Test-CsAddressBookService, see

http://technet.microsoft.com/en-us/library/gg398661.aspx

Hi Lisa,

I have added the suggested permissions and tried to republish the topology with the same errors.  The SQL backend is on a different domain than the Lync front end servers.  I presume the RTC groups that need share access are those of the domain where the front end servers are?  Also if I change other fields in AD eg Title that replicates fine.  If just seems to be the phone number not going over.

Normal it is not supported to use a SQL databse from another doimain.

The Domain is fully trusted?

Could you check the file Location for the addressbook Service. All files are created?

\\fileserver\webservice\ABFiles

Here is a good lin from Jeff Schertz

http://blog.schertz.name/2013/03/breaking-down-lync-file-share/

The fileshare is a windows SMB file share?

There is a two way trust with the domains, both trusts have been validated etc.

There are plenty of LSABS in there alright

Yes its a SMB file share.

Ok, maybe some of the files are corrupt. You can delete the files and run update-csaddressbook to create the files new.

You can force the Client to download the addressbook imediately, if you delete the galcontacts.db and.idx

http://terenceluk.blogspot.de/2013/02/forcing-lync-2013-client-to-download.html

Troubleshooting addressbook:

http://blogs.technet.com/b/nexthop/archive/2012/06/21/lyncmd-troubleshooting-the-lync-2010-address-book.aspx

Thanks for the help so far on this.  There are 2 event logs that occur just after an sync

The front end no longer owns the task and is therefore shutting down.

Cause: SQL Connectivity issues.

Resolution:

Verify that the RTCService account has access to the database and that the machine running the Lync Server Front-End service has connectivity to the back-end server.

*********************

Unable to create output file.

Path: '\\XXXXXXX\LyncAddressShare\1-WebServices-1\ABFiles\00000000-0000-0000-0000-000000000000\00000000-0000-0000-0000-000000000000\F-128e.dabs'
Exception: The process cannot access the file '\\XXXXXXX\LyncAddressShare\1-WebServices-1\ABFiles\00000000-0000-0000-0000-000000000000\00000000-0000-0000-0000-000000000000\F-128e.dabs.tmp' because it is being used by another process.
Cause: Either the path is inaccessible or the Address Book Server does not have the correct permissions to create the file.
Resolution:
Examine the details in the associated event log entry to determine the reason and the possible cause.

Seems like permission issues somewhere?

I would recomend to use the OCSLogger and start a trace on the addressbook releated parts, to find the issue or to check teh permissions with the other LS shares.

Try to add the user account you use to deploy Lync Server to the local administrator of the Back End Server.

Hi,

Just found something there that you guys may have seen before.  Our estate is XP (yeah I know) SP3 with Lync 2010 client.  We also have a hosted desktop off W2k8 servers with Lync Client 2013.  The phone number appears in the 2013 client but not on the 2010 client.......Anyone seen this before?