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

Problem:

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:

Analysis

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.

UPDATE!!

To resolve this issue, install the following update:

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

Lync 2013 error : BackCompatSchema.ldf failed. The exit code is “8224”

During deploying Lync 2013 pilot pool for side-by-side migration from Lync 2010, I faced with strange problem on Step 1 (AD Preparation) in Wizard.schema error

I have had installed Lync 2010 in my infrastructure, so I have a “half-prepared” schema for Lync 2013 Server. To update your current schema Lync uses four ldf scripts , which you can find in your Lync installation disk (<drive letter>:\support\schema).

  • ExternalSchema.ldf is is used for interoperability with Microsoft Exchange Server
  • ServerSchema.ldf is the primary Lync Server 2013 schema file
  • BackCompatSchema.ldf is used for interoperability with any components from prior releases
  • VersionSchema.ldf is used for version information of the prepared schema

Wizard runs them in the following order :

  1. ExternalSchema.ldf
  2. ServerSchema.ldf
  3. BackCompatSchema.ldf
  4. VersionSchema.ldf

To resolve my problem I decided to run scripts manually on my DC
*don’t forget to change DC=  and type FQDN of your DC

ldifde.exe -i -v -k -j "C:\Users\rlevchenko\AppData\Local\Temp" -f "D:\Support\Schema\ExternalSchema.ldf" -c DC=X "DC=demo,DC=local" -s ad.demo.local
ldifde.exe -i -v -k -j "C:\Users\rlevchenko\AppData\Local\Temp" -f "D:\Support\Schema\ServerSchema.ldf" -c DC=X "DC=demo,DC=local" -s ad.demo.local
ldifde.exe -i -v -k -j "C:\Users\rlevchenko\AppData\Local\Temp" -f "D:\Support\Schema\BackCompatSchema.ldf" -c DC=X "DC=demo,DC=local" -s ad.demo.local
ldifde.exe -i -v -k -j "C:\Users\rlevchenko\AppData\Local\Temp" -f "D:\Support\Schema\VersionSchema.ldf" -c DC=X "DC=demo,DC=local" -s ad.demo.local