Hello!
Windows 7
Lync 2013 client
When sharing my dekstop with Lync2013, I'm getting a message that it has stopped working and it will signed me out.
Any hints/tips how to fix this?
Technology Tips and News
Hello!
Windows 7
Lync 2013 client
When sharing my dekstop with Lync2013, I'm getting a message that it has stopped working and it will signed me out.
Any hints/tips how to fix this?
Try to Logging clean boot to perform a Lync sharing desktop.
For your reference: http://support.microsoft.com/kb/929135
Check if other users in your company have the same problem.
If they have the same problem, then the problem is related with Lync Server.
If only you have this problem, try to sign in on another computer to check if the problem persists.
Please check if you have the same problem with Lync 2010.
Check if you can find any error in event log when the client stops working.
I am having the same issue, and it is only occurring on one of our 150+ machines on Lync 2013
Log Name: ApplicationI am having the same issue, and it is only occurring on one of our 150+ machines on Lync 2013
Log Name: ApplicationI am having the same issue, and it is only occurring on one of our 150+ machines on Lync 2013
Log Name: ApplicationWe are having this problem with Lync 2013, only on new Carbon X1 machines. Attempted a clean boot per the instructions provided above, and it is still failing.
The exception code (0x00000879) and faulting module (KERNELBASE.dll) match your issue, Eric.
One thing that has worked as a workaround is to disable desktop composition:
http://msdn.microsoft.com/en-us/library/windows/desktop/aa969540(v=vs.85).aspx
http://www.sevenforums.com/tutorials/22803-desktop-composition-disable-program.html
You can also disable desktop composition from the shortcut for Lync itself, but when you launch Lync, windows says 'The color scheme has been changed to Windows 7 Basic' - so it seems that, ultimately, desktop composition is disabled as long as Lync is running (which is virtually 24x7 for most people). So that isn't a great workaround anyway.
So, normally Lync does this right when you go to share your screen - it flips to windows 7 basic, which apparently is required for desktop sharing to work - but for some reason it's failing to switch to that mode and crashing.
I suspect it's a driver thing, but I'm still not sure what is causing it. I'm still digging.
We have fixed it, but I'm still not entirely sure what the cause is.
We built a new image, which is essentially:
- Windows 7 x64 Enterprise, with .NET 4.5.1 and IE9, patched as of May 1st, 2014.
Any of our new Lenovo machines that are imaged with the new image do not have the problem. Same drivers as the old image, everything else is exactly the same, but something with the updated image fixes the problem. Maybe it has to do with security patch updates / ordering / etc. Hard to say.
We have fixed it, but I'm still not entirely sure what the cause is.
We built a new image, which is essentially:
- Windows 7 x64 Enterprise, with .NET 4.5.1 and IE9, patched as of May 1st, 2014.
Any of our new Lenovo machines that are imaged with the new image do not have the problem. Same drivers as the old image, everything else is exactly the same, but something with the updated image fixes the problem. Maybe it has to do with security patch updates / ordering / etc. Hard to say.
We have fixed it, but I'm still not entirely sure what the cause is.
We built a new image, which is essentially:
- Windows 7 x64 Enterprise, with .NET 4.5.1 and IE9, patched as of May 1st, 2014.
Any of our new Lenovo machines that are imaged with the new image do not have the problem. Same drivers as the old image, everything else is exactly the same, but something with the updated image fixes the problem. Maybe it has to do with security patch updates / ordering / etc. Hard to say.
This was the solution that works for now.
"Disable desktop composition from the shortcut for Lync itself"
From Office 2013 installation folder Lync.exe properties.
Cheers!
Ismail
Seeing the same problem on Lenovo Thinkpad T540p.
After installing the following update seems to solved the problem.
http://support.microsoft.com/kb/2670838yes its worked for me also...
Thanks.