[Last updated on 27th February, 2014]

Hi there,

You can find a list of CU versions compiled from KB articles for cumulative update packages released for Lync client and Lync servers. Please note that the list only includes version information for Lync 2010 (desktop edition), Lync Server 2010, Lync 2013 (desktop edition) and Lync Server 2013 and it excludes interim updates, security updates, updates for non-desktop clients like WP8, iOS devices, Android, Lync phone edition)

Lync 2010

Lync Server 2010

Lync 2013

Lync Server 2013  

Hope this helps

Thanks,

Murat 

Hi there,

I was dealing with a Lync 2013 client crash problem a few months ago and I wanted to provide some details on this issue since you might hit the same problem in your deployments as well when certain conditions are met. The exact problem was that when a user clicks on the “Organization” tab of any given contact in Lync 2013 client, the Lync 2013 client immediately crashes. After some troubleshooting we came to the conclusion that there was a problem with the module which handles “Organization” tab in Lync 2013 client (and in various Office products like Outlook). In order for you to hit this issue, the following two conditions should be met:

- You have to be using Office 2010 + Lync 2013 client combination on the client

- Any user in your Active directory organization hierarchy should be assigned as a manager to himself/herself (this generally occurs when the top level manager object (which represents CEO user) is assigned as a manager to herself/himself)

You won’t hit this problem if you don’t meet the above condition. If you hit the issue because the above conditions are met in your deployment, you can install the following Office 2013 update on your Lync clients which fixes this problem:

http://support.microsoft.com/kb/2817352 Description of the Office 2013 hotfix package (Mso-x-none.msp): June 20, 2013

Issues that this hotfix package fixes

• Consider the following scenario:
• You have Office documents that are synchronized between the local disk and Microsoft SkyDrive or Microsoft SkyDrive Pro.
• You receive an error message when you upload a file in Office upload center.
• You delete the file on the local disk.
• You discard the changes you made for the file in Office upload center.

In this situation, you receive the following error message:

The action can't be completed because the file is open. Close the file and try again.

• You cannot save a document in Word 2013 or Excel 2013 as a web page (.html or .htm file type) to a local SkyDrive Pro folder.
• Consider the following scenario:
• There is a file conflict between a local folder for SkyDrive Pro and a SharePoint Server 2013 document library.
• You open the file in an Office application, and then you click Keep Server Version in the Resolve Conflict dialog box.
• You make some changes for the file in an Office Web App.
• You open the file in the Office application again.

In this situation, you cannot download the file changes from the server.

When you click the Organization tab of a contact in Lync 2013, Lync 2013 crashes.

Hope this helps

Thanks,

Murat

Hi again,

I dealt with a Lync server 2013 problem recently where the server was intermittently logging event ID 56417 in the Lync server event log:

- <System>

  <Provider Name="LS Data Collection" />

  <EventID Qualifiers="51423">56417</EventID>

  <Level>2</Level>

  <Task>2271</Task>

  <Keywords>0x80000000000000</Keywords>

  <TimeCreated SystemTime="2013-05-10T12:16:51.000000000Z" />

  <EventRecordID>18850</EventRecordID>

  <Channel>Lync Server</Channel>

  <Computer>FE1.contoso.local</Computer>

  <Security />

  </System>

- <EventData>

  <Data>QoE Adaptor</Data>

  <Data>System.IO.InvalidDataException: Invalid input. EndPoint is null. at Microsoft.Rtc.Server.UdcAdapters.QoE.PackReport.Pack(VQReportEventType report, LyncMessageDetails msgDetails, DBQoEReport dbReport) at Microsoft.Rtc.Server.UdcAdapters.QoE.QoEProcessor.ProcessMessageForStore(LyncMessageDetails msgDetails) at Microsoft.Rtc.Server.UdcAdapters.QoE.QoEProcessor.ProcessQueueItems(LyssQueueItem queueItem)</Data>

  </EventData>

  </Event>

Based on the error description, we expect the event to be logged when there’s a problem with an incoming QoE report sent by an UC endpoint. We collected a number of logs from the Lync server including SIPStack/S4 logs, event logs and a network trace. Such QoE reports are sent with a SIP SERVICE command to the FE server (and then from FE server to Monitoring server):

- You can filter them with VQReportEvent keyword while checking the SIPStack log with snooper:

There were some QoE reports sent around the time of the 56417 event with some non-English characters but I wasn’t able to establish a direct tie between this and the event being logged. But after with some further troubleshooting, we found out (with the help of one of my colleagues) that the error was logged especially when the Server language format was set to non US English format. After the language format was changed to US English, the issue was resolved:

Hope this helps

Thanks,

Murat