Freigeben über

SQL Server 2016 SP1: Known issues

  • Artikel

The SQL Product team has identified the following known issues which the customers may encounter after installing SQL Server 2016 SP1. The following post will help the customers  plan and prepare their environment for the following known issues while installing SQL Server 2016 SP1.

SQL Server Reporting Services (SSRS)

If Reporting Services is set to use a secure (https/SSL) connection, a warning about security content may be displayed or Print function may not work after installing SQL Server 2016 SP1. Please install the fix KB 3207512 (Build 13.0.4199.0) which contains the fix for the issue.

SQL Server Integration Services (SSIS) After installing SQL Server 2016 SP1, the DCOM permissions for launching and accessing Integration Services service may get reset to default permissions. This issue is unconfirmed yet but if you have customized DCOM permissions, you might have to reapply the customization. The issue is under investigation but users if hit it, they can use the workaround described in KB 2000474.

We confirm that SSIS is not impacted by the abovementioned issue in SQL Server 2016 SP1.

SQL Master Data Services (MDS)

After installing SQL Server 2016 SP1, when you try to add or edit a business rule, it fails with error below. This issue is introduced by Security Update MS16-136 fix in GDR which is also included in SQL Server 2016 SP1 and SQL Server 2016 CU3. The issue and error below is applicable only to SQL Server 2016 branches patched with Security Update, CU3 or SP1 and doesn't apply to lower versions of SQL Server.

"This business rule contains corrupted rule item(s), as corresponding SQL Script has been changed"
"The sequence must be greater than zero"

The fix for this issue is included in the following updates:

ODBC Driver 13.1

With the default installation of SQL Server 2016, ODBC Driver 13.0 is installed on the server which is used by SQL Agent and SSMS (installed on server) to connect to the SQL Server instance. If you have installed ODBC Driver 13.1 on your server for any reason, SQL Server 2016 SP1 installation overrides the ODBC Driver 13.1 installation and the fixes introduced in 13.1 like KB 3185365 may be lost. In this case post installation of SQL Server 2016 SP1, it is recommended to uninstall the ODBC Driver installed by SQL Server 2016 SP1 and install ODBC Driver 13.1.

To check for ODBC Driver installed on the server, you can go to Control Panel of the server –> Programs and Features –> Search for ODBC. The version number of ODBC Driver 13.1 is 13.1.811.168 as shown below

 

image

Uninstalling SQL Server 2016 SP1 (Not recommended)

If for any reason you choose to uninstall SQL Server 2016 SP1, the uninstallation of SQL Server 2016 SP1 is not blocked and you will be able to uninstall SQL Server 2016 SP1 like any other service pack. However, if you are running Standard, Web, Express edition of SQL Server and leveraging some of the new features which are unlocked only starting SQL Server 2016 SP1, you might see some unforeseen errors or databases might even be left in suspect state after uninstallation of SQL Server 2016 SP1. Even worse would be if the system databases are using new features for example, partitioned table in master database, it can lead to SQL Server instance unable to start after uninstalling SQL Server 2016 SP1 . Hence it is recommended to validate all the new features are disabled or dropped before you choose to uninstall SQL Server 2016 SP1 on editions other than Enterprise Edition. It is not possible to drop memory_optimized_data filegroup . Hence if you have setup memory_optimized_data filegroup on your database with SP1, you should not uninstall SQL Server 2016 SP1 in that case else the database will get in suspect mode with following error message logged in Errorlog

2016-11-24 04:45:39.74 spid15s     Error: 41381, Severity: 21, State: 1.
2016-11-24 04:45:39.74 spid15s     The database cannot be started in this edition of SQL Server because it contains a MEMORY_OPTIMIZED_DATA filegroup. See Books Online for more details on feature support in different SQL Server editions.

If you are running Enterprise edition of SQL Server 2016 SP1, none of this applies and you can uninstall SP1 without any issues or additional checks.

Please read our Tiger blog post for more details and scripts to detect and validate if new features are in use before you plan uninstall SP1 on Standard, Web, Express edition of SQL Server 2016.

Parikshit Savjani
Senior Program Manager (@talktosavjani)

Comments

  • Anonymous
    November 25, 2016
    Hi,I registered this bug with PBM, but it wasn't corrected yet.https://connect.microsoft.com/SQLServer/feedback/details/3031421/error-when-executing-custom-table-level-condition-with-executesql-in-pbmcheers,
    • Anonymous
      December 28, 2016
      Thank you for reaching out to us. The Connect item will be updated once we have a resolution or if there is an update to be posted. Depending on the priority and severity of the issues, development resources are assigned to Connect items. If this is of an urgent nature and requires immediate resolution, I would recommend opening a Microsoft support incident to request for a fix.
  • Anonymous
    November 28, 2016
    Master Data Services is also broken with SP1. Three bugs identified in the sp1. Cloud focus equals bad software quality?
    • Anonymous
      November 28, 2016
      Hello Sebastien, Can you please point me to those 3 identified bugs? Are you stating they were introduced with SP1? You can either contact CSS for help, or submit feedback to MDS product team by clicking the new feedback button in SQL16 MDS. The MDS product team will receive an email and works directly with customers to troubleshoot the issue.Thanks!
  • Anonymous
    December 09, 2016
    After installing SP1, the below error has re-appeared for us after disabling Named Pipes and Shared Memory protocols for a SQL 2016 instance:https://support.microsoft.com/en-us/kb/3185365Trying to update the ODBC Driver to v13.1 throws an error about the current version being newer. I had to uninstall the ODBC Driver 13 which came with the SQL Server installation first, Installed 13.1 and the issue now appears resolved.
  • Anonymous
    December 12, 2016
    By the end of the year my intention was to upgrade the MDS servers to SQL 2016 SP1 - does anyone know if there is a resolution as yet ?
    • Anonymous
      December 12, 2016
      Hi David, We should have a fix by end of this week or early next week. We are actively working on it.Thanks !!!
    • Anonymous
      December 16, 2016
      The fix for this issue is now available. I have updated the blog
  • Anonymous
    December 20, 2016
    Since installing Hotfix 3207512 to SQL Server 2016 SP1 I'm unable to send emails from the server, either SQL Server Agent job alerts or using sp_send_dbmail. It worked fine right up to the point of installing the hotfix. Despite following online guidance about troubleshooting it's never worked since. Anyone else noticed this?
  • Anonymous
    December 27, 2016
    i have find below error once applied SQL2K16 SP1 , where SSISDB in read only mode but where other server database 'SSISDB' is R/W could not found any issue , once enable trace flag T902 sql services are up . is issue with SQL2016- SP1 or SSISDB in read only mode issue .Error: 912, Severity: 21, State: 2.Error: 3417, Severity: 21, State: 3.
    • Anonymous
      January 03, 2017
      hi Kiron, this is by design behavior, T-SQL scripts need to be executed against SSISDB during upgrade.
  • Anonymous
    January 24, 2017
    We have built our SQL Server 2016 instance running on Azure VM (IAAS) using image in Azure portal. We just have ODBC 11 available in this server and not 13.0. Is there any reason why ODBC 11 by default?
    • Anonymous
      January 29, 2017
      Which image are you testing? . All SQL Server 2016 images have ODBC 13.0 installed by default.
      • Anonymous
        January 29, 2017
        Apologies, It was mistake from our end, validation was performed in old server which caused the confusion. We have 13.0 installed on the servers which has MS SQL 2016.
  • Anonymous
    February 01, 2017
    The comment has been removed
    • Anonymous
      February 01, 2017
      Hi Daniel, We haven't had any known issue with R services. You can open a support incident with CSS to help you troubleshoot the issue.
      • Anonymous
        February 03, 2017
        We had the same problem , the quick fix is to put the lauchpad service account in local administrators
        • Anonymous
          March 09, 2017
          Thanks, for now it works.
  • Anonymous
    March 08, 2017
    FYI. uninstalling SP1 going back to RTM resulted in SSRS unable to connect to the reporting database due to a schema mismatch. InvalidReportServerDatabaseException: The version of the report server database is either in a format that is not valid, or it cannot be read. The found version is '175'. The expected version is '173'.