Skype for Business In-Place Upgrade failed with "Unsupported version of SQL Server detected"

-
I came across a problem a customer reported while he tried to upgrade an Lync 2013 Standard Server to Skype for Business Server.
 

The error is:

Before this server can be upgraded, the following must be resolved:
An unsupported version of SQL Server was detected. The local RTCLOCAL instance should be Microsoft SQL Server 2012 Express Edition SP1 or later. More information on downloading....
The local LYNCLOCAL instance should be Microsoft SQL Server 2012 Express Edition SP1 or later....
 
 
 
First let me remind, that you have to follow this upgrade steps: 
  • Install CU5+ latest hotfix to Lync 2013 topology
  • PowerShell RTM version (6.2.9200.0) or later
  • Have at least SQL server 2012 SP1 installed
    SP1 (    download), SP2 (download)
  • Operating System Hotfixes:
Out of the Box, Lync Server 2013 installed the SQL 2012 Express Edition RTM.
 

SOLUTION:

Now if you only install SP1, make sure you updated both instances RTCLOCAL and LYNCLOCAL.

Next, please ensure your CU Update is installed correctly.
You MUST patch you database. Read the instruction very carefully (LINK):

Install-CsDatabase -ConfiguredDatabases -SqlServerFqdn <SE.FQDN> -Verbose
 
If you simply for got, which is very very very often the case, you run into issue and it is very hard to support this. Mostly we MVP also forget checking all Lync Server if you have patch the Server since beginning correctly.
 
 

Author:

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