UCMAPI 3.0-based Lync Server 2010 components crash when a client that can send invalid culture information joins a conference

Symptoms
Assume that a client that can send invalid culture information joins a conference. For example, a Damaka XAVY client joins the conference. In this situation, the Microsoft Unified Communications Managed API 3.0 (UCMAPI 3.0)-based Microsoft Lync Server 2010 components, such as the Conferencing Announcement Service and the Conferencing Auto Application, crash. Additionally, the following event is logged in the Application log.

Event ID: 33126
Task Category: (1301)
Level: Error
Keywords: Classic
User: N/A
Computer: <Computer Name>
Description:
An unhandled exception was encountered in Conferencing Announcement Service.
Exception: System.ArgumentException: Culture name 'en_US' is not supported.
Parameter name: name


Cause
This issue occurs because the client sends the invalid culture string "en_US." Then, the UCMAPI 3.0-based Lync Server 2010 components do not handle the invalid culture information correctly.

Resolution
To resolve the issue, install the following cumulative update:
2793341 Description of the cumulative update for Lync Server 2010, Unified Communications Managed API 3.0 Runtime: March 2013
More information
For more information about the RegionInfo Constructor (String), go to the following Microsoft website:

For more information about Damaka, go to the following website:

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.
Properties

Article ID: 2772396 - Last Review: 03/14/2013 16:29:00 - Revision: 6.0

Microsoft Unified Communications Managed API v3.0 Core Runtime

  • kbqfe kbfix kbsurveynew kbexpertiseinter KB2772396
Feedback