Fix: Lync Address book cannot load phone numbers from Active Directory

Check if Invalid_AD_Phone_Numbers.txt contains errors

You can find this file in your Lync Share:


If Address book cannot add some contacts you may see the following error :

Unmatched number: User: ‘’  AD Attribute: ‘telephoneNumber’  Number: ‘6567’

To fix this error, we need to create a normalization rule for numbers 6xxx, these rules are stored in a text file called Company_Phone_Number_Normalization_Rules.txt which is stored in the 1-WebServices-1\ABFiles\

NOTE: You should create Company_Phone_Number_Normalization_Rules.txt manually

Lync uses this file to convert phone numbers into E.164 format. In my example, ‘#’ = comments;  ^(6\d{3})$ and $1 = normalization rule for 6xxx phone numbers . So, add your normalization rules and save file.

Sample of Company_Phone_Number_Normalization_Rules.txt:lync_contacts_2

To verify your rules you must use abserver.exe utility

Set-Location 'C:\Program Files\Microsoft Lync Server 2013\Server\Core'
.\ABServer.exe -testphonenorm "3456"


After successful verification you should update your address book:

Update-CsAddressBook -Force

Instant message sent from Lync Web App displays wrong symbols in Lync 2013


Cyrillic characters are not readable in Lync 2013 rich client when send from Lync Web application client. Plus the following characters from languages:

  • Ukrainian
  • Macedonian (Macedonia, FYROM)
  • Bulgarian
  • Serbian (Cyrillic)
  • Belarusian (Belarus)
  • Greek
  • Japanese
  • Arabic
  • Hebrew
  • Farsi
  • Kazakh

lync cyrillic error

Microsoft’s Support answer:

Thank you very much for your patience throughout the work on your support request.
I am archiving the case at this time. The issue is planned to be fixed in the next Cumulative Update for Lync 2013, planned for October 2013.

If there will be any obstacles implementing the fix or change in the schedule for the Cumulative Update, we will let you know.

Here is a summary of the key points of the case for your records:


1) The problem can be reproduced issue in lab.

2) The issue is seen when the receiving Lync 2013 client machine has set the language for Non-Unicode Programs in Control panel to “Russian”

3) Workaround: Set the language for Non-Unicode language to English (a language captured in codepage Windows 1250/1252 )

4) While working on the repro we encountered a conversation from Unicode (used by LWA) to the Cyrillic codepage 1252. Likely the aim would be to keep the encoding at Unicode to be consistent among the products.

5) Lync 2010 WebApp used a different encoding mechanism for the body test (application\octetstream) instead of multipart\text now in LWA 2013.

6) We have requested a hotfix with the Lync Product Team to address the failing display of Cyrillic characters when using a combination of Lync 2013 Web App and Lync 2013 rich client. There was support from the Mircosoft Russian account team, because a large customer community is affected by this.

7) The Product Team acknowledged this request and plans to deliver a fix for it in the next cumulative update, planned for October 2013.


To resolve this issue, install the following update:

2825630 Description of the Lync 2013 update: September 20, 2013