Visual C++ 2012 Runtime Version Error during installing Lync Server 2013 Debugging Tools

-
Lync Server 2013 Debugging Tool Visual C++ 2012 x64 Minimum Runtime Error

If you are trying to install the Lync 2013 Debugging Tools on Windows Server 2012 or Windows 8, where no Lync Server 2013 is installed, you might run into an wired issue.

After you installed all prerequisites:
.Net Framework, PowerShell 3.0 and the Visual C++ 2012 Runtime

The installation wizard will raise an error message:
Microsoft Lync Server 2013, Debugging Tools installation or uninstallation requires that Microsoft C++ 2012x64 Minimum Runtime -  11.0.50727 Package is already installed. Either use Setup.exe for installation or run vcredist_x64.exe included with the product to install the redistributable.

 

Probably you will check the installation and see that the Visual C++ 2012 Runtime is already installed:


If you try installing the Debugging Tools again, you will run into the same issue, even if you see the a version high than requested is installed. Searching the Internet for the mentioned version might not be successful.

There for you are reading the error message carefully, you will the that Microsoft requires the exact version, which is 11.0.50727 and this special version is only included with the Lync Server 2013 ISO Image (DVD).

What to do (Solution):

Insert or mount the ISO Image of Lync Server 2013 and ACCEPT the Installation of the correct (requested) Visual C++ version 11.0.50727.

Afterwards you check again if the installation was successful.

Now you restart the installation process for your Debugging Tools and if will succeed.

The Lync Server 2013 Debugging Tools can be download here.


Comments

Post a Comment

Popular posts from this blog

Cannot join external Lync Meeting: Lync Edge Server Single IP Address (Lync Edge Server Single IP Web Conferenceing Problem)

-
Image
Lync Edge Server FQDN and IP PORTS (Version 1.2, Update 26.11.2014) As we all know, we can configure Lync Edge Server in several way. 1) Single Edge Server with a SINGLE IP ADDRESS 2) Single Edge Server with MULTIPLE IP ADDRESSES (3x IPs) 3) Multiple Edge Server in a Pool, with MULTIPLE IP ADDRESSES (Zx 3 IPs) Regardless what we are going to configure, there are common / well-known TCP Port necessary making Lync work, which are: Access: Port: 443 and 5061 Conferencing: Port: 443 and (444) AV: Port: 443 (I have not listed other ports, e.g. STUN or the dynamic port range. This is not required for the topic discussed here) External FQDN with single IP address: What can we see here? If we are going to choose a single IP address, we would have TCP Port overlapping. Therefore the only way avoiding this is assigning other ports. Additionally we will also see and are reminded that Lync highly depends on DNS. If we have single IP, we must have use single, unique FQDN fo
Read more

MFA with Guest Access and different tenants settings

-
Image
There is an update regarding MFA Multi Factor Authentication. If you are guest with a different Tenant, the MFA Settings are now reflecting the settings of all tenants in a different way. Each MFA setting is reflected and you can setup your MFA device as per tenant and the admin settings allow. Login to your Profile in Office 365/ Azure AD: https://account.activedirectory.windowsazure.com/r/#/profile or https://myapps.microsoft.com Go to your PROFILE: Sign in to https://myapps.microsoft.com Select your account name in the top right, then select profile. Select Additional security verification. If might be happen, your admin hast configured MFA, so you wouldn't see this menu. Simply switch the tenant to the guest tenant where you need to configure MFA. Once you go back to your profile and you will find the MFA device and other settings a usual:
Read more

Skype for Business, Lync and Exchange Web Services (EWS) and different DNS Domains- Exchange crawling e.g. for presence

-
Image
Hi all, (This is an updated version 2.2: 09 .07.201 5 ) This blog entry is valid for Lync 2010, Lync 2013 and Skype for Business Server. Generally, I'll write a new blog article, since the conversion history over multiple device and other service have change with Skype for Business 2015 Server. Once this written, I post the link here. there is always confusion in how Lync is crawling Exchange Web Services (EWS). Generally it is necessary to understand how DNS must be implemented: Just remember, identify if you have DNS Split configuration, different internal and external DNS names and what are your SMTP and SIP Domains. Very often you find in Lync/ Exchange deployments an issue, where the Lync configuration show up with empty: EWS Internal URL EWS External URL and EWS Information = EWS not deployed Therefor Exchange Web Service are not connected deployed and several Lync Integration Features are not working, e.g. Presence Information based on your Outlook Calendar.
Read more