Need help > Office 2013 MSI and Skype for Business 2016 Entry / Error, Repair

Valued Contributor

So, most of our users have an Office 2013 Standard MSI Installation. 

We recently started rolling out Skype for Business 2016 EntryRetail (because those users only have O365 E1 licenses) for those users as well, from the Click2Run Setup via ODT2016 (setup.exe), but we're getting the following error.

Mind you, this error is a Skype for Business 2016 Error, not an Outlook Error, even though the Window Title says so.

ced37ccd-546d-4de4-8b28-60cbb8745840.png

 

I'm NOT getting the same error for those users have have Office 2013 MSI + Skype for Business 2016 ProPlus (from Click2Run) for those users with Office 365 E3 Licenses.

 

For those unfamiliar with the used Product IDs:

O365 E3 <Product ID="O365ProPlusRetail">

O365 E1 <Product ID="SkypeforBusinessEntryRetail">

 

If found this thread http://answers.microsoft.com/en-us/office/forum/office_2013_release-outlook/installed-skype-for-busi...

though as usual answers.microsoft.com does not help with these kind of specific problems.

3 Replies

Ivan - I too have been perplexed by not being able to find any real solutions when this error occurs. One issue I know is the confusion over compatibility issues when various versions (e.g., 2013 / 2016 or MSI / C2R) are installed.

 

Just reading the article Office installed with Click-to-Run and Windows Installer on same computer isn't supported doesn't quite answer your question - but certainly hints at the problem. Hopefully someone from the Skype for Business or Office 365 team will see this thread and provide a better resolution than just to upgrade to the same versions (i.e., C2R + 2016) for Office & Skype for Business.

Hi Ivan,

 

Were you able to solve this issue?  We have basically the same problem, PCs with oem click-to-run Office 2013 and Skype for Business Office 365 Business Essentials work OK, but our laptops with Volume Lic Office 2013 msi install and Skype for Business frequently give the same errors as you are getting.

Not solved, only a workaround (which I'm not totally happy with).
Remove the C2R SfB Version, and install the MSI SfB Vesion.