Compartilhar via

SQL Server 2014 Service Pack 1 has released - Updated

  • Artigo

 Important Updates on 4/22:

Immediately following the removal, we started preparing a new SQL Server 2014 Service Pack 1. We have learned several things that we wanted to pass along as well as share what is happening currently:

 

  • In the 11 hours of availability, there were 270 downloads from the Download Center. No other distribution channels were affected.

  • The original release was version 12.0.4050.0, the new release will have a new KB and build number.

  • If you have already installed the original SP1 release (12.0.4050.0), you are welcome to use it. However, we do want to minimize the number of installs of 12.0.4050.0 for servicing reasons.

    • When SP1 is rereleased, we will recommend that 12.0.4050.0 be uninstalled prior to applying the new SP1 update. This includes any "Side by Side" instance scenarios.

  • We are targeting release in a few weeks and will share updates as we go.

 

Although the package was only briefly available on the Microsoft Download Center, we apologize for this mistake and the inconvenience you may have encountered as a result. We not only did a full root cause analysis, but have also taken additional measures to prevent this in the future. We remain fully committed to top quality SQL Server servicing deliverables going forward.

 

Thank You

SQL Server Engineering Team

Important Updates on 4/16:

Dear SQL Customers,

We have chosen to remove SQL Server 2014 Service Pack 1 (SP1) from the Microsoft Download Center due to a significant installation issue discovered shortly after release. We sincerely apologize for the inconvenience this has caused you.

We will fix the installation issue and release the Service Pack for production use in a few weeks. Although operationally equivalent, only the newly released SP1 will be serviced (security updates, cumulative updates, hotfixes). Therefore, it will be important that you replace the current version of SP1 (12.0.4050.0) with the upcoming one.

In the meantime, you can continue to test and use build 12.0.4050.0. If you are experiencing the issue below, please implement the steps described in the workaround section.

We will communicate further as we approach the release date and we appreciate your patience.  

Rong Wu

SQL Engineer Team

Issue summary:

Description

Any SQL Server instance with SSISDB catalog enabled runs into the following installation error during SQL Server 2014 SP1 upgrade.  The instance is then in an invalid and unusable state.

Error: 912, Severity: 21, State: 2.

Script level upgrade for database 'master' failed because upgrade step 'SSIS_hotfix_install.sql' encountered error 3602, state 251, severity 25. This is a serious error condition which might interfere with regular operation and the database will be taken offline. If the error happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion.

Error: 3417, Severity: 21, State: 3.

Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books Online. SQL Server shutdown has been initiated

Workaround

  1. In SQL Server Configuration Manager, click SQL Server Services.
  2. In the right pane, right-click SQL Server(InstanceName), and then click Properties.
  3. On the Startup Parameters tab, in the Specify a startup parameter box, type the parameter “-T902”, and then click Add.
  4. Click OK.
  5. Restart the Database Engine.
  6. Connect to SQL Server instance from SQL Server Management Studio and run the following script to resolve the errors causing script upgrade to fail. This will create a temp table.
     
    use master go   

CREATE SCHEMA [internal] AUTHORIZATION. dbo

CREATE TABLE [internal].[object_parameters]   

(      

    [project_id] [bigint] NOTNULL,

    [project_version_lsn] [bigint] NOT NULL

)

   

        7. Remove the -T902 trace flag from SQL Server Configuration manager

        8. Restart SQL Server Instance.  SQL server SP1 will be installed correctly.

        9. Remove the temp table by the following script

   
   

use master

go   

DROP TABLE [internal].[object_parameters]

   

 

 Notice: The SQL SSIS team has found an issue with SP1 installation if SSIS catalog is present in the SQL Server instance.They are currently investigating this issue including possible workarounds and fixes. We have temporarily put the package download on hold and will provide an update with a solution. SQL Server 2014 Service Pack 1 is now available

One year ago, we launched SQL Server 2014. Today, April 15, we are pleased to announce the release of SQL Server 2014 Service Pack 1 (SP1). The Service Pack will be available for download on the Microsoft Download Center.

SQL Server 2014 SP1 contains fixes provided in SQL Server 2014 CU 1 up to and including CU 5, as well as a rollup of fixes previously shipped in SQL Server 2012 SP2. For highlights of the release, please read the Knowledge Base Article for Microsoft SQL Server 2014 SP1.

As part of our continued commitment to software excellence for our customers, this upgrade is available to all customers with existing SQL Server 2014 deployments via the download links below. SQL Server 2014 with SP1 will be available in additional venues including the Volume Licensing Center and via Microsoft Update starting May 1, 2015.

Microsoft® SQL Server® 2014 SP1

Microsoft® SQL Server® 2014 SP1 Express

Microsoft® SQL Server® 2014 SP1 Feature Pack  

Rong Wu

Senior Engineer Manager

SQL Server Servicing Experience Team

Comments

  • Anonymous
    April 15, 2015
    Looks like the download for SP1 is removed? A few hours ago it was there, now only a "page not found"...

  • Anonymous
    April 15, 2015
    Clicking on the link for SQL Server 2014 sp1 takes you here www.microsoft.com/.../smarterror.aspx

  • Anonymous
    April 16, 2015
    If you already installed it and you are getting errors due to the SSIS catalog bug , try this workaround. I used and worked well. The only difference is that I deleted it. social.msdn.microsoft.com/.../after-update-windows-including-sql-2012-sp2-unable-to-start-sql-serviceinstance

  • Anonymous
    April 16, 2015
    No sure where my comment from the other day vanished to, but if we need functionality that was in CU 6 for RTM, do we need to wait for CU 1 for SP1 or is it already in SP1?

  • Anonymous
    April 19, 2015
    sister's computer will not even completely boot up now. So how can it be fixed if it won't even boot?

  • Anonymous
    April 20, 2015
    CU 6 fails on as well on 'SSIS_hotfix_install.sql' if SSISDB is in an AG. To fix: Ran SQL (-T902), removed SSISDB from the AG, deleted the db and re-ran sql server and update after.

  • Anonymous
    April 20, 2015
    The comment has been removed

  • Anonymous
    May 13, 2015
    When are you guys planning to release this ?

  • Anonymous
    May 18, 2015
    Yes please let us know when it is available for the GA version. Thanks

  • Anonymous
    May 21, 2015
    I installed the new SP1 today and having the same issue now. SQL server wont start. I followed these instructions and once I remove the flag the issue is still there

  • Anonymous
    June 03, 2015
    "I installed the new SP1 today and having the same issue now. SQL server wont start. I followed these instructions and once I remove the flag the issue is still there" Same problem. Put parameter in, start service, run script, take parameter out, stop service, service never starts again. I can only get the SQL server started with the flag turned on. Do I leave the flag on and work until the next CU?

  • Anonymous
    September 18, 2015
    Hi, the symbols for 2014 SP1 appear to be missing from the public symbol server.  Can you get them added?