We haven't yet done full regression testing for the Office 2013 suite, so we're at risk of breaking other legacy applications if we the upgrade PCs now to Office 2013. How can this be submitted to the Office team? I believe this is a bug in the Lync installer and six patches described above.Īfter we delete the "2.b" registry key, the application works fine. The best thing to do is to ask the meeting presenter to send you a copy of the presentation or to use the Sharing feature to show the presentation. If the meeting organizer has scheduled the meeting using Lync 2010 Server, the PowerPoint presentation won’t be visible. However about 16 or so other Office 2013 patches that get applied to these Office 2010 with Lync 2013 PCs do not add the "2.b" registry key e.g. The PowerPoint presentation isn’t visible. KB3039779 : MS15-044: Description of the security update for Lync 2013 (Skype for Business):. I discovered the following the patches also add the "2.b" key on PCs with Lync 2013 and Office 2010 installed: "PrimaryInteropAssemblyName"=", Version=14.0.0.0, Culture=neutral, PowerPoint 14.0 Object Files (x86)\\Microsoft seems that the Lync 2013 installer is erroneously adding the "2.b" key assuming that PowerPoint 2013 is installed. We found that the following registry key: We've have discovered that when running Office 2010 (32-bit) with Lync 2013 (32-bit) that VBA code will give the error:
0 Comments
Leave a Reply. |