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
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.
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
I have experience the same issue with Office 2010 and Skype for Business 2016. Have you seen this ? and if so is there a hotfix that can resolve this issue?
hi Lian i am facing similar issue with Skype for business and unable to resolve it . Please share me on email sheeraz18(at)yahoo(dot)com if someone find the resolution..
If it is organization hierarchy issue, wouldn't it b e like, all users facing this issue?But here in my case,only one particular site users are facing issue.Any insight?