none
Lync 2013: An error occured during the screen presentation

    Question

  • Hi All,

    I have installed onto a number of new PC's Office 2013 which includes an update to Lync 2013.

    My problem is that every time someone tries to share there screen with the new PC's the following message is displayed:

       "An error occurred during the screen presentation"

    Note: On other (much older) previously configured machine, logging in with the same accounts the desktop can be shared.

    For Info: It is possible to share the whiteboard and transfer files, just not share desktop or specific monitors?

    All suggestions and solution gratefully received!!

    Thanks for help

    John

    Thursday, March 21, 2013 9:07 AM

Answers

  • I don't know if I have the full story but I think there is something missing from the KB2760556 patch.  It assumes that the previous update is there already, but if you try to install both at the same time things go wrong.

    I removed all three of the 2013 lync patches.  programs and features -> view installed updates.

    remove all lync patches under the office 2013 section.

    reboot.

    screen sharing should be back.

    apply the lync patches one at a time.  KB2760512 first, and then KB2760556

    screen sharing is still working for us after that.  I opened a case but it it has not been picked up yet.

    Sunday, March 24, 2013 3:09 AM

All replies

  • I have the same problem with Office 2013 Pro Plus 32bit. On a previous computer with standalone Lync 2013 Client, no problems. Sharing content from my desktop works, but viewing content shared by others fails with the message in the topic.
    Thursday, March 21, 2013 4:47 PM
  • I'm experiencing the same problem.  The interesting thing is that this does not happen when I share my screen with others, only when someone else is sharing with me.

    Anyone with any ideas why this happens would be much appreciated.

    • Edited by Ptolemy02 Friday, March 22, 2013 4:15 PM
    Friday, March 22, 2013 4:13 PM
  • The same here, I think I'm getting this issue after a patch. It was fine before.  Anyone knows what's causing it?  This is the only result that comes up with the exact search string: "An error occurred during the screen presentation" in Bing.  I assume it's a new issue.
    • Edited by myws Friday, March 22, 2013 4:16 PM
    Friday, March 22, 2013 4:14 PM
  • Just started happening to me too after installing windows updates last night so I agree it must be an issue with a recent patch.
    Friday, March 22, 2013 4:34 PM
  • I don't know if I have the full story but I think there is something missing from the KB2760556 patch.  It assumes that the previous update is there already, but if you try to install both at the same time things go wrong.

    I removed all three of the 2013 lync patches.  programs and features -> view installed updates.

    remove all lync patches under the office 2013 section.

    reboot.

    screen sharing should be back.

    apply the lync patches one at a time.  KB2760512 first, and then KB2760556

    screen sharing is still working for us after that.  I opened a case but it it has not been picked up yet.

    Sunday, March 24, 2013 3:09 AM
  • Thanks, this worked for me.
    Monday, March 25, 2013 8:12 AM
  • i am having the same problem, removing kb2760556 fixed the desktop sharing problem

    Michal K

    • Proposed as answer by teekenees Wednesday, March 27, 2013 2:59 PM
    Monday, March 25, 2013 4:58 PM
  • Worked for me too.  thanks.
    Tuesday, March 26, 2013 1:50 PM
  • Hi

    Same problem, removing KB2760512 and KB2760556 as suggested
    did not help.

    Any word from MS on your case?

    Regards

    Robban




    Wednesday, March 27, 2013 2:52 PM
  • Worked for me too. Thx a lot.
    Thursday, March 28, 2013 9:16 AM
  • Thanks for posting. This fixed the issue for me as well.
    Wednesday, April 03, 2013 7:15 AM
  • We're seeing this issue too with Lync 2013 32bit with Lync 2010 server, on windows 8 64bit.

    We tried the patch removal/adding, but we are still seeing issues.  the odd thing is the behavior isn't consistent between users.  for example, we can share with one user and see their screen when they share.  another user, we can't do either.  another user, we can only do 1.


    Ben Pahl

    Wednesday, April 03, 2013 7:50 PM
  • I too had this issue with a customer. Some users were able to share app/desktop and some users not. Turned out that removing KB2760512 and KB2760556 did the trick.

    For internal users:

    From Windows 7, Lync 2013 user with all updates app/desktop sharing worked.

    From Windows 8, Lync 2013 user with all updates app/desktop sharing does not work.

    Uninstalled updates on both clients so i'm not sure if it's a Windows 7 or Windows 8 issue or something else.

    -edit-

    Ok, i installed the KB2760556 on the windows 8 machine and app/desktop sharing still works. After installing the update on the Windows 7 machine the app/desktop sharing was broken again.

    • Edited by P. Slijkerman Thursday, April 04, 2013 12:06 PM added info
    Thursday, April 04, 2013 10:55 AM
  • Any new updates? I have tried to remove the 2 patches but that did not seem to help for my user.
    Thursday, April 04, 2013 8:11 PM
  • Hi there,

    I do see that problem, too. Some clients are not able to accept Application Sharing sessions, they can share their desktop/application with others, though. Lync Monitoring shows unexpected errors like:

    From user agent: UCCAPI/15.0.4481.1000 OC/15.0.4481.1000 (Microsoft Lync)  
      Diagnostic header: 52165; reason="Appsharing Session disconnected due to a connection failure in the RDP stack";

    SIP/SDP signaling seems to be fine, so I looked into the client logs (Lync-AppSharingMediaProvider-0.AppSharingMediaProviderlog) and it goes like this:

    04/04/2013|07:22:54.295 B5C:E18 INFO  :: CAppsharingMediaProvider::StartLogging: tracing enabled
    04/04/2013|09:27:16.609 B5C:880 INFO  :: CRDPRTPTransportStream::StateChange - Received an Adapter State Change Event - State = 0x1, Direction = 0x3, Reason = 0x1
    04/04/2013|09:27:16.609 B5C:E18 INFO  :: CRDPRTPTransportStream::TraceInfoMessage RDPSessionQoeAggregator[11A71568]: SetTraceCallback with callback pointer. Current refCount: 4.
    04/04/2013|09:27:16.609 B5C:E18 INFO  :: CRDPRTPTransportStream::TraceInfoMessage RDPSessionQoeAggregator[11A71568]: Current # of active RDPSessionQoeAggregator instances: 1.
    04/04/2013|09:27:16.609 B5C:E18 ERROR :: CRDPRTPTransportStream::ConnectRDPtoDataChannelForViewer: HRESULT API failed: 80070057 = hr. failed to Enable Zoom
    04/04/2013|09:27:16.609 B5C:E18 TRACE :: CRDPRTPTransportStream::TraceVerboseMessage RDPSessionQoeAggregator[11A71568]. Release() returning 3.
    04/04/2013|09:27:16.609 B5C:E18 ERROR :: CRDPRTPTransportStream::ConnectRDPtoDataChannel: HRESULT API failed: 80070057 = hr. ConnectRDPtoDataChannelForViewer failed
    04/04/2013|09:27:21.615 B5C:E18 INFO  :: CRDPRTPTransportStream::Terminate - MediaManager terminates appsharing media provider session
    04/04/2013|09:27:21.702 B5C:E18 WARN  :: CAppsharingMediaProviderSession::AddAppSharingNode - no tns:InboundStream stream node
    04/04/2013|09:27:21.702 B5C:E18 TRACE :: CAppsharingMediaProviderSession::AddAppSharingMetricsToReport: Condition failed with 80004003: 'spAppShareNode != 0'. Invalid spAppSharingNode pointer
    04/04/2013|09:27:21.702 B5C:E18 WARN  :: CAppsharingMediaProviderSession::GetQoEData - AddAppSharingMetricsToReport failed hr = 80004003
    04/04/2013|09:27:21.717 B5C:E18 TRACE :: CRDPRTPTransportStream::TraceVerboseMessage RDPSessionQoeAggregator[11A71568]. Release() returning 2.
    04/04/2013|09:27:21.717 B5C:E18 INFO  :: CRDPRTPTransportStream::Close - RDP session closed
    04/04/2013|09:27:21.717 B5C:E18 TRACE :: CRDPRTPTransportStream::TraceVerboseMessage RDPSessionQoeAggregator[11A71568]. Release() returning 1.
    04/04/2013|09:27:21.748 B5C:E18 TRACE :: CRDPRTPTransportStream::TraceVerboseMessage RDPSessionQoeAggregator[11A71568]. Release() returning 0.
    04/04/2013|09:27:21.748 B5C:E18 INFO  :: CRDPRTPTransportStream::TraceInfoMessage RDPSessionQoeAggregator[11A71568] Disposing instance.

    Anyone else seeing those errors?

    I haven't a had a chance to try uninstalling and re-installing the updates, yet. I'll look into that tomorrow and post an update here.

    Cheers!
    Tom

    Thursday, April 04, 2013 8:54 PM
  • I discovered that this can occur if one user has the "Microsoft Lync 2013" version of Lync installed (what I think of as the standalone version) and the other has the "Microsoft Office 2013 Professional Plus" version of Lync installed (i.e., as a component of Office 2013).  We chose to uninstall the standalone version from machines and replace it with a customized install of Lync using the OCT to specify all the settings and registry keys and such.  So far so good.

    That being said, I also had to stop WSUS from pushing out KB2760556, as that also caused the same problem for some folks.  I'm hoping this gets fixed in the next round of patches next week.

    Hope that helps,

    Shawn 

     
    Friday, April 05, 2013 2:12 AM
  • Removing both KB2760512 and KB2760556 and then re-installing them one at a time did the trick.

    Cheers!
    Tom

    Friday, April 05, 2013 7:06 AM
  • This solution worked for me, thanks!
    Friday, April 05, 2013 10:12 AM
  • Removing KB2760512 and KB2760556 worked for me also, thank you!
    Friday, April 05, 2013 10:56 AM
  • I also had some users who could not share or be shared to at all, and some who could only receive or send sharing.  

    The only fix that worked 100% for me was a full re-install of Office Professional Plus 2013 32bit.  We only have a couple users using 64 bit, haven't tested with them.  Uninstalling the updates was hit or miss

    We are running Lync Server 2010 at the moment, should be on 2013 shortly, I will test again after the upgrade and post if that fixes it.


    • Proposed as answer by Alex Marit Monday, April 08, 2013 4:38 PM
    • Edited by Alex Marit Monday, April 08, 2013 7:03 PM
    Monday, April 08, 2013 2:13 PM
  • I also had some users who could not share or be shared to at all, and some who could only receive or send sharing.  

    The only fix that worked 100% for me was a full re-install of Office Professional Plus 2013 32bit.  We only have a couple users using 64 bit, haven't tested with them.  Uninstalling the updates was hit or miss

    We are running Lync Server 2010 at the moment, should be on 2013 shortly, I will test again after the upgrade and post if that fixes it.


    We have seen this on the Lync 2013 client.  We are using Office 2010.  Will microsoft release a patch, for this broken patch?
    Tuesday, April 09, 2013 6:16 PM
  • This removing kb2760556 worked for me too
    Wednesday, April 10, 2013 5:26 PM
  • We have run into this as well.

    CU1 installed on the server.

    All lync patches installed - we show three:

    KB2760512
    KB2760556
    KB2760556

    Yes, the 2760556 shows it is installed twice.  All of the machines i've spot checked show this.  I've tried uninstalling all of the patches and testing -same problem.  I've tried letting the patches reinstall - same problem.  I've found no work around.

    I've moved the users back to our 2010 pool - same problem.  I then moved them back to the 2013 pool and tested with Lync 2010 client - no problem - it works fine.  The problem definitely seems like a software bug or interop problem.

    Guessing a call to Microsoft is needed.  I'm hoping this is a bug that has already been identified.

    Anyone else have any other ideas?


    Skippy


    • Edited by Skipdog77 Wednesday, April 10, 2013 8:55 PM wording
    Wednesday, April 10, 2013 8:53 PM
  • If using Lync 2013, make sure the clients are all at the same version level. In February 2013 a patch was released for Lync (the client) and if some clients are on different versions than the others, desktop sharing can be finicky.

    Brian Ricks, MCSE, MVP BriComp Computers, LLC http://blogs.bricomp.com/blogs/uc/default.aspx

    Thursday, April 11, 2013 1:20 PM
  • Brian,

    So you are talking about the following two patches in Feb:

    KB2760512 -- LyncLoc

    KB2767852 -- MSores

    My clients has LyncLoc - but MSores won't install or says it doesn't apply.

    We've tried removing 2760512 with no change in behavior.  I will try removing it again and manually installing it.

    Skip



    Skippy


    • Edited by Skipdog77 Thursday, April 11, 2013 1:28 PM grammar
    Thursday, April 11, 2013 1:28 PM
  • Removing the updates and installing them manually did indeed help.. However we need a more substantial solution to this.  How do we roll this product out? We can't go around and install these patches manually.  Has anyone engaged Microsoft yet concerning this issue?


    EDIT: On a few machines when I reinstall the patch KB2760556 which appears twice on all of my machines the problem comes back immediately.  If I uninstall this patch and retry the sharing session it works without rebooting.

    • Edited by Skipdog77 Thursday, April 11, 2013 9:53 PM more info
    Thursday, April 11, 2013 7:45 PM
  • We have the same problem aswell. Can Microsoft propose another fix for this than manually having to uninstall and reinstall these KBs?

    Kind Regards

    Marcus

    Sweden

    Friday, April 12, 2013 10:16 AM
  • We've now encountered machines that refuse to work even after manually installing KB2760556.  On some machines if we do the process just right, it continues to work fine, but we've found some that just refuse to work with this patch.  We've disabled the patch via WSUS for now since it doesn't seem to impact us (no VDI)

    I'm hoping the Microsoft Lync has seen and will deal with this!


    Skippy

    Friday, April 12, 2013 4:23 PM
  • Same issue for us.  Removing the KB2760556 patch fixed the issue.  We have removed the KB2760556 patch for WSUS so it does not install.  Hopefully MS sees this post and either removes KB2760556 from distribution or patches the patch.

    Jim

    Friday, April 12, 2013 10:58 PM
  • Same issue here, removing KB2760556 resolves it. Mixed results adding the patch back.
    Monday, April 15, 2013 10:10 PM
  • Just curious - KB2760556 requires 2 prerequisites to be installed.

    ---------------------------------------------------

    To apply this hotfix, you must have the following updates installed:
    Lyncloc
    Download the x86 package now.
          (http://www.microsoft.com/downloads/details.aspx?FamilyId=95804c44-9308-4dd0-a0dd-88087aca0812)    
    Download the x64 package now.
          (http://www.microsoft.com/downloads/details.aspx?FamilyId=e440d931-41c1-4206-a864-82f0e706ca81)    
    Msores
    Download the x86 package now.
          (http://www.microsoft.com/downloads/details.aspx?FamilyId=cef3ff2c-23bc-4b41-84f5-efd4a0e1b5f7)    
    Download the x64 package now.

          (http://www.microsoft.com/downloads/details.aspx?FamilyId=76c7a4af-8952-450c-99a5-16d06248f2aa)    

    ----------------------

    http://support.microsoft.com/kb/2760556

    Are they in reality also installed?

    Tuesday, April 16, 2013 12:16 PM
  • Lync screen sharing didn't work here either, removed patch KB2760556 and rebooted, now it works like a charm. We are declining the patch distribution for now, let's hope for a quick proper fix...
    Tuesday, April 16, 2013 12:47 PM
  • Andres P-

    Yes they were installed.  We've tried every variant with mixed success.  Something is obviously wrong with KB2760556 in that under certain situations it breaks functionality.  Hoping the Lync team addresses.



    Skippy

    Tuesday, April 16, 2013 1:03 PM
  • I have the same issue. I have Lync 2013 Basic 32bit edition after receiving an email from Office 365 advising that Lync ought to be updated. All my users have the old Lync 2010 (which is still the version being pushed from the install link on the office 365 portal).

    I have tried to uninstall KB2760556 and KB2760512 with a restart but unfortunately this does not restore functionality.

    It appears that the Lync 2010 and 2013 versions are unable to communicate with each other. This is just not good enough if you need to share desktops/applications with clients/staff. I can update all the staff to 2013, but obviously cannot enforce this on clients.

    I am tempted to re-install Lync2010 and if 2013 isn't fixed, I will be uninstalling it.

    I have to say I'm not happy with the whole Office 2013, Windows 8 and subscription licencing experience. I shall be sticking to W7 & O10 for the foreseeable future.

    Wednesday, April 17, 2013 10:12 AM
  • No word on it, yet.
    Wednesday, April 17, 2013 1:58 PM
  • Hi, any update on this?!

    I'm observing similar issues on my project. Would be very nice to have some sort of update.

    The solution in this thread is rather a workaround than an answer to the problem.

    Tuesday, April 23, 2013 12:25 PM
  • We are having the same issue. Uninstalling patches and re-installing doesn't make a difference.
    Thursday, April 25, 2013 8:33 PM
  • The 4/27 Lync update does not fix this.  All of our Windows 8 machines are now encountering the problem.  We have no way to mass-uninstall these updates for everyone affected. 
    • Edited by pesospesos Tuesday, April 30, 2013 2:06 PM
    Tuesday, April 30, 2013 1:33 PM
  • Skip - yup but because of my late reply it looks like you discovered this already. Unfortunately I have not heard of anything that addresses this other than making sure the patch is either completely and correctly installed or not at all. The interesting thing is while there is a definite issue seen in the forums, I have not seen it in all deployments (maybe less than 5%) and that would be my guess as to why it hasn't been globally resolved. That said, it is an issue for some and perhaps SIP traces and client logs would bring to light what is different in the installs where the problem exists.

    Brian Ricks, MCSE, MVP BriComp Computers, LLC http://blogs.bricomp.com/blogs/uc/default.aspx

    Tuesday, April 30, 2013 1:45 PM
  • We are seeing this on new Win 7x64 SP1 Office 2013 OSD deployment. It was installing update kb2760556 during the task sequence.

    Uninstalled kb2760556 after user experienced the issue and it is now working.

    Tuesday, April 30, 2013 7:41 PM
  • Hi all,

    I have opened a case with PSS as we urgently need this resolved and have too many machines to fix manually.

    MS has acknowledged and escalated the problem (supposedly) and the engineer I spoke with expects to have test results of an internal patch by Monday.

    Basically on newly built machines, all of the Lync patches download at once when the machines hits Microsoft Update, and the automated patch process messes something up timingwise when this happens.  Machines that were built in February or earlier do not exhibit the problem as they downloaded and installed the Feb update in Feb, March in March, etc -- only one patch at a time.  This explained why we see the issue on our newly reimaged offices and not our offices that were reimaged back in February - despite using the exact same Win8/Office2013 image that we created back in January.

    For those that need an urgent fix for a small number of machines, uninstalling both the *512 update and the *556 update, then rebooting and manually installing them one at a time has fixed every machine we've tried thus far.  Be sure to uninstall both instances of *556 as it usually shows up twice under updates.

    • Proposed as answer by Brer_Bunny Friday, May 24, 2013 9:41 AM
    Thursday, May 02, 2013 5:31 AM
  • Further to Pesospesos comment, I can confirm that I have gone back in and removed the *512 and both versions of the *556 update and tested Lync. It works now!

    I then manually installed the updates in sequence, and rebooted between each, and tested.... That works too!

    Thank you Pesospesos!

    To recap as per Pesospesos "Be sure to uninstall both instances of *556 as it usually shows up twice under updates."


    -Brer Bunny

    Thursday, May 02, 2013 9:22 AM
  • I see the same problem at our customer. Maybe you could keep us up to date with the progress of the call. If you send me call id i could advise the customer to jump on the ticket to have more pressure.
    Thursday, May 02, 2013 2:58 PM
  • I discovered that this can occur if one user has the "Microsoft Lync 2013" version of Lync installed (what I think of as the standalone version) and the other has the "Microsoft Office 2013 Professional Plus" version of Lync installed (i.e., as a component of Office 2013).  We chose to uninstall the standalone version from machines and replace it with a customized install of Lync using the OCT to specify all the settings and registry keys and such.  So far so good.

     

    Hi Shawn

    I am getting the same Screen Sharing error in my company. I'm testing Lync 2013 from Office 365 and have deployed the Lync Basic 2013 client to around 20 people, most of whom are seeing this error.

    I'm interested in what you are doing RE pushing out the 'full' Lync client included with Office 2013 Pro Plus. Is this allowed? Would you have to purchase a copy of ProPlus for all users in order to push the full Lync client out to them? It seems the full Lync client isn't available to buy on it's own...

    Many thanks
    Andy

    Friday, May 03, 2013 12:22 PM
  • We tried removing these patches via WSUS but the 512 patch gets stuck in a loop and doesn't uninstall properly. Now it keeps prompting the users to remove/reboot which is just adding more frustration to this issue.

    Friday, May 03, 2013 9:57 PM
  • can confirm only removing the patch KB2760556 solves the problem.
    Monday, May 06, 2013 1:46 PM
  • 2 Updates... So much time lost lately because of problem from updates.  I am glad this fixed my problem internally.  Now I can work on fixing my problem with external clients and the web app.
    • Edited by SubNet.Zero Wednesday, May 08, 2013 2:47 PM
    Wednesday, May 08, 2013 2:46 PM
  • Lisa, please unmark the earlier post as an answer.  It is not an answer - it is a workaround.  There is no answer yet  - not until Microsoft releases a patch to fix what they have broken.  Marking this thread as answered does nothing to keep the issue in the forefront and push for a true fix.  Unfortunately due to the timing of our rollout this issue has pretty much ruined our deployment and has everyone reverting back to GoToMeeting.  Users' faith/trust in Lync has been marred by this being their first experience with it, and I am less than impressed with the speed with which Microsoft has addressed the issue.  Maybe they should try actually patching a fresh install of Lync each time they release a new patch to ensure they don't cause this type of situation again.  This kind of bush league stuff should not be happening in 2013.
    Friday, May 10, 2013 7:30 AM
  • Perfect world: Best practices are to test every single update in your test environment before you deploy them to your production environment.

    Reality: Most people don't have the resources available to have a true test environment.  Their test environment is their production environment.

    Think of all the other workarounds you have implemented just to get something working.  The idea is to get whatever is broken working again and removing the two updates fixes the problem of desktop sharing.

    Friday, May 10, 2013 12:51 PM
  • I had the same results in our test pool - Uninstalling and re-installing fixed it so I can share with other people, but nobody can share with me and also nobody can share with each other...

    So - 7 our of 8 computers still are broken even after doing this workaround...  I opened a new thread last week to show that this workaround does not completely resolve the problem and could still use a fix

    Friday, May 10, 2013 2:45 PM
  • We have been experiencing this same issue.  Uninstalling KB2760556 nad 2760512 then reinstalling did not resolve.  However we did fid a procedure that works.

    1)  uninstall KB2760556 and REBOOT

    2)  uninstall KB2760512 and REBOOT

    3)  From an ELEVATED COMMAND PROMPT, apply 2760512 and REBOOT.

    4)  From an ELEVATED COMMAND PROMPT apply 2760556 and REBOOT

    The key for us seems to be the elevated command prompt.  This has fixed 2 out of 3 systems experiencing this issue (third user is not available to apply the patches to)

    Friday, May 10, 2013 4:29 PM
  • SubnetZero, the idea is to get a scalable fix that can be deployed to hundreds of machines.  If Microsoft plans to compete with GoToMeeting/WebEx/etc. they need to get their ish together.
    Friday, May 10, 2013 4:32 PM
  • I followed the instructions from above (remove updates, reboot in between, reinstall updates one at a time), however I noticed something about KB2760556, it's no longer available in the Microsoft Download Center! Also, the download link in its KB Article is broken.

    I did some searching in the Download Center and Microsoft has a new KB for Lync 2013 client, KB2768004.

    x86 - http://www.microsoft.com/en-us/download/details.aspx?id=39009

    x64 - http://www.microsoft.com/en-us/download/details.aspx?id=39009

    I applied KB2760512, restarted, then applied KB2768004 and restarted my system again.  Screensharing worked again!  I also ran Windows Updates on my machine afterwards and KB2760556 was no longer applicable so it appears that KB2768004 supersedes KB2760556.

    Hope this helps!  I haven't yet tested to see if KB2768004 will supersede both updates.  

    Tuesday, May 14, 2013 4:49 PM
  • PSS is telling me that 2768004 released today should fix the problem for those experiencing it.  We are putting together some tests with affected machines and will report what we find.
    Tuesday, May 14, 2013 8:43 PM
  • x86 was duplicated.  

    Correct x86 link:

    http://www.microsoft.com/en-us/download/details.aspx?id=39008


    Skippy

    Tuesday, May 14, 2013 8:49 PM
  • after installing 2768004, first test I did was connecting to a meeting from 2013 to 2010(host), it didn't connect on 2 pc's I tested this update on...

    removed 2768004 and can connect just fine.

    I don't have KB2760512 or KB2760556 installed, those 2 updates were creating problems with screen share.


    Michal K

    Tuesday, May 14, 2013 9:16 PM
  • The only machine I've worked on so far today, I uninstalled *512 and *556, then manually installed them, then let *004 install via windows update, and sharing worked after that.

    Scary to hear that *004 might be breaking things on its own - will have to test further.

    • Proposed as answer by kylebh10 Thursday, May 23, 2013 11:48 PM
    • Unproposed as answer by kylebh10 Thursday, May 23, 2013 11:48 PM
    Tuesday, May 14, 2013 9:18 PM
  • Microsoft have released an update which should now resolve this issue -

    http://support.microsoft.com/kb/2768004

    Wednesday, May 15, 2013 1:08 PM
  • How can I get this installed when apparently I have installed with click-to-run?  My Lync 2013 64-bit version is from MSO:

    Microsoft Lync 2013 (15.0.4420.1017) MSO (15.0.4420.1017) 64-bit

    the installer above did not identity "a product to which this applies"

    Thursday, May 16, 2013 3:57 PM
  • I've been working on this for a while with Microsoft. I heard from them today that it's an issue with NVIDIA and they should have a fixed release soon. I'll post back when I have an update.
    Thursday, May 23, 2013 11:51 PM
  • The *004 patch has fixed it for all of our Windows 8 x64 machines with Office 2013 x86 installed.

    Friday, May 24, 2013 12:21 AM
  • I know this is an old thread but it is the first one I found when searching for this problem.

    The problem for me was just that the 'Lync Server Application Sharing' service had stopped on the Lync server.  Given the message, this makes sense.  Started the service and everything was good.  I also changed the Recovery properties of the service so that 'Subsequent failure' was set to 'Restart the Service', perhaps that will stop the problem recurring.

    I have an error in the Lync Server log (EventID 32069) which says that 'The Mcu Factory returned failure for a request sent to it' but I have no idea what an 'Mcu factory' is or how to go about troubleshooting.  I am going to stick my fingers in ears and sing 'La, la, la' and hope it goes away.


    Paul Linton

    Wednesday, September 04, 2013 4:19 AM
  • LYNC 2013 desktop sharing shows blank screen:

    This problem was solved by removing the following registry entry:

    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\ActiveX Compatibility\{00000000-0000-0000-0000-000000000000} (if using LYNC 2013 32 bits on Windows 8 64 bits)

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{00000000-0000-0000-0000-000000000000} (if running LYNC 2013 64 bits or running LYNC 2013 32 bits on Windows 8 32 bits)

    Thursday, October 17, 2013 8:31 AM
  • @kylebh10:

    I have the same problem on a HP 8770w with NVIDIA K3000M.

    Any news from Microsoft?

    Thanks,

    Ioannis

    Tuesday, October 22, 2013 4:36 PM
  • @kylebh10:

    I have the same problem on a HP 8770w with NVIDIA K3000M.

    Any news from Microsoft?

    Thanks,

    Ioannis

    The solution we found (even after applying the latest client update!) was you need to delete a registry related to Active X.  Here:  http://mikefrobbins.com/2013/02/21/unable-to-view-a-shared-desktop-or-application-in-a-microsoft-lync-2013-meeting/

    Tuesday, October 22, 2013 5:44 PM
  • @net1994:

    Thanks for the feedback.

    My problem is NOT that it shows a blank screen. My problem is that when somebody else tries to shares his screen/desktop with me, connection fails on my side, with a message "an error occurred during the screen presentation". The opposite direction works fine (me sharing my desktop with somebody else).

    Anyway, I searched for the registry key but I don't have it.

    The problem appeared as soon as I changed my laptop to this brand new HP 8770w that has an NVIDIA card. The previous laptop had an Intel onboard graphics card. I am the only one using this type of laptop in my office at the moment. This is why I suspect that it could be a problem with NVIDIA (as kylebh10 mentioned above), although I have installed the latest drivers (Oct 2013).

    Any other ideas are welcome ...

    Thanks,

    Ioannis

    Tuesday, October 22, 2013 6:13 PM
  • OK issue resolved :)

    The problem was related to the registry settings under [HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client] which I exported from my previous laptop and imported earlier. The reason was that I wanted to maintain the list of the servers appearing when opening Remote Desktop Connection. Although this works fine (i.e. server list appears fine and you can select any server you want, while also the username used during the last login is also shown), Lync for some reason cannot cope, even though I couldn't find which subkey(s) exactly caused the problem; structure is very simple and practically consists only of the server names, and the usernames used last to login.

    Anyways, after a clean install of Windows, I did an export of the registry key above before importing the exported one from my previous laptop. After restoring this export, problem was resolved :)

    Thanks,

    Ioannis

    Tuesday, October 29, 2013 9:21 PM
  • Oh dear, the problem has come back again. I just get a blank screen when attempting to share desktop or other presentation.

    I've given up on using Lync for this and have decided to use Logmein's join.me website, as it is more reliable.

    Brerbunny


    -Brer Bunny

    Wednesday, December 18, 2013 10:24 AM
  • Yes, we too are having issues. Some users can work some users can't.  We have 7 users in house and 6 remote users. Some are Lync 2010 and some are Lync 2013.  Funny, Internally, I can share with only one user, doesn't matter what version of Lync they are using, I am able to share. But once I try sharing with more that one user internally, who ever I am trying to share with can not connect, their Lync freezes and the only way out of it is to End Task and restart Lync. 

    Now, for my external users. There are some that I can share with and they can share with me, but then there are some that I can not share with and they can not share with me, we get the following error message "We couldn't connect to the presentation because of network issues. Please try again later."

    With that said, these issues above exist when it's 2013 sharing with 2010,  2013 sharing with 2013, 2010 sharing with 2013 and 2010 sharing with 2010.

    Before anyone say's, get everyone on 2013, we have MAJOR issue getting people on 2013 that are still using Office 2010 at this time, we are not ready to spend time figuring out what exactly this issue is. 

    Wednesday, January 08, 2014 3:46 PM
  • We are having the same issues through the Office365 version. Even after opening a trouble ticket with Microsoft, pulling countless logs and turning on tracing for Lync the problem is unresolved. Microsoft blamed our ISP and the Consistency of Service (COS) even though the problem occurs with users on the same wired gigabit network.

    We too have moved to using Join.me after utilizing Lync 2010 for years. This is a great way for them to kill user adoption of a product.

    This was the tool they used to point the finger at our ISP and the 50MB internet connection we have.

    In a web browser, browse to the Office 365 Lync Online Transport Reliability IP Probe (TRIPP) tool URL that's closest to the user's physical location, and then click Start Test:

    Thursday, January 30, 2014 6:06 PM
  • I thought I'd give the TRIPP tool a go to see what it says about my location. Thanks for Moonblink for providing the links (these are also given on the Microsoft Support page You can't connect to Lync https://support.microsoft.com/kb/2409256)

    Java security blocks the tool from running! I thought I'd add an exception to allow it to run, although Java recommends you dont add http sites to the list, only https. I tried again, and Java blocked it again! It blocked it because the tool accesses script from other domains.

    I have the latest Java version.

    Comment withdrawn, see later post:(It seems that Microsoft have badly designed the tool, and in a manner that resembles malicious script. Obviously, it isn't, but it comes to something when even their test tool doesn't work properly!)


    -Brer Bunny


    • Edited by Brer_Bunny Friday, January 31, 2014 2:43 PM
    Friday, January 31, 2014 10:21 AM
  • this started to happen with the last java 7, update 51.. I get the same Blocked page on multiple sites, its not really MS tool error;

    open Configure Java > Security and make your changes there,


    Michal K


    • Edited by Michal K Friday, January 31, 2014 1:26 PM
    Friday, January 31, 2014 1:25 PM
  • I have. But it still wont work because the newest version of Java does not allow calls to multiple domains. Those changes were made intentionally to make Java more secure.

    I would have to go in and manually add each referred domain to the exception list. I could do this but tbh, I'd rather not. I personally haven't had issues with Java on other websites. 

    Perhaps the TRIPP tool ought to be updated to bring it in line with the more secure Java update. I do however take back my previous comment!


    -Brer Bunny

    Friday, January 31, 2014 2:42 PM