Shulou(Shulou.com)06/03 Report--

Recently, I worked on a project to upgrade from lync server 2010 to 2013. During the coexistence, users in the lync server 2013 pool were unable to download address books. This problem plagued me for several days, but it was finally solved. To get back to the point, I would like to share with you the process of dealing with this problem. I hope it will be helpful to you.

Problem description:

When a user in the lync server 2013 pool logs in to the lync client, he / she is prompted that the address book cannot be synchronized with the following error:

The following error is reported on the lync server 2013 front-end server, event ID:21046

I used the POWERSHELL command: test-csaddressbookservice test reported 404 error

By looking at the IIS log, it is also a 404 error:

Process:

In view of the above error report, the preliminary judgment is related to the permissions of the shared folder, but after a detailed check of the shared folder, all the permissions are there, and I added the full control permissions of everyone, or reported an error. There is no way to delete and regenerate all the files under ABFiles. The process is as follows:

Delete the 00000000-0000-0000-0000-000000000000 folder under the ABFiles folder

On the lync server 2013 front-end server, open powershell and execute the command: Update-CsUserDatabase command to regenerate the address book file, and then wait about 5 minutes to execute the command: Update-CsAddressBook-Verbose. After the command execution is completed, open the event viewer and find that the 21046 event is coming out again. Headache ah

There is really no choice but to find Google. I really found an article that mentioned such a problem. Share it with you. See below:

Https://ucsteps.com/2015/12/07/skype-for-business-file-share-dfs/

Because for this shared folder, I did DFS to synchronize this shared folder to another server one-way. In terms of permissions, the permissions of the file sharing server sharing directory and the everyone permissions mentioned in the post are there, and I have complete control over this setting.

It's just that the permission of everyone in the permissions of another namespace server is to read

Is it for this reason that a dead horse should act as a doctor and check the change of authority?

After ticking, test again:

Succeed

Check the event log and find the long-awaited: 21056 event, see below:

Succeed

Log in to the lync client and search for the user:

The fuzzy search was successful and there was no error in the address book in the lower right corner. Ok

Summary: if you DFS a file share on lync server 2013 (or skype for business server 2015), you must add: change and read permissions to the share permissions on 2 named hosts

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.