locked
SQL 2014 SP2 failure RRS feed

  • Question

  • A while back I tried installing CU6 on my SQL 2014 server and it failed badly.  After working on it for a day I just gave up and restored back to before the update. I have been avoiding the CUs ever since.

    Today I tried installing SP2, hoping it would fixe whatever caused the CU to fail.  Well it died too and I can't seem to find any relevant info searching the web, most of the stuff is related to 2012 issues.  In the error log there is a reference to Cannot find the user '##MS_SSISServerCleanupJobUser##' I do not recognize this user and as far I can remember it never existed on the server, I was the one who setup and configured the server so I know I never deleted it.  Master is toast right now so any help would be greatly appreciated. 

    Here is what I got from the installer:

    Action required:
    Use the following information to resolve the error, and then try the setup process again.

    Feature failure reason:
    An error occurred during the setup process of the feature.

    Error details:
    § Error installing SQL Server Database Engine Services Instance Features
    Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
    Error code: 0x851A001A
    Visit http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.5000.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026 to get help on troubleshooting.

    The link goes to an ad for a Service Pro 4 so not very useful.  The log file says:

    Overall summary:
      Final result:                  The patch installer has failed to update the following instance: MSSQLSERVER. To determine the reason for failure, review the log files.
      Exit code (Decimal):           -2061893606
      Start time:                    2016-10-10 12:20:01
      End time:                      2016-10-10 12:38:58
      Requested action:              Patch

    Instance MSSQLSERVER overall summary:
      Final result:                  The patch installer has failed to update the shared features. To determine the reason for failure, review the log files.
      Exit code (Decimal):           -2061893606
      Start time:                    2016-10-10 12:37:59
      End time:                      2016-10-10 12:38:56
      Requested action:              Patch

    Machine Properties:
      Machine name:                  METSQLBI01
      Machine processor count:       4
      OS version:                    Windows Server 2012
      OS service pack:              
      OS region:                     United States
      OS language:                   English (United States)
      OS architecture:               x64
      Process architecture:          64 Bit
      OS clustered:                  No

    Product features discovered:
      Product              Instance             Instance ID                    Feature                                  Language             Edition              Version         Clustered  Configured
      SQL Server 2014      MSSQLSERVER          MSSQL12.MSSQLSERVER            Database Engine Services                 1033                 Business Intelligence Edition 12.2.5000.0     No         Yes      
      SQL Server 2014      MSSQLSERVER          MSAS12.MSSQLSERVER             Analysis Services                        1033                 Business Intelligence Edition 12.2.5000.0     No         Yes      
      SQL Server 2014      MSSQLSERVER          MSRS12.MSSQLSERVER             Reporting Services - Native              1033                 Business Intelligence Edition 12.2.5000.0     No         Yes      
      SQL Server 2014                                                          Management Tools - Basic                 1033                 Business Intelligence Edition 12.2.5000.0     No         Yes      
      SQL Server 2014                                                          Management Tools - Complete              1033                 Business Intelligence Edition 12.2.5000.0     No         Yes      
      SQL Server 2014                                                          Client Tools Connectivity                1033                 Business Intelligence Edition 12.2.5000.0     No         Yes      
      SQL Server 2014                                                          SQL Server Data Tools - Business Intelligence for Visual Studio 2013 1033                                      12.0.2430.0     No         Yes      
      SQL Server 2014                                                          Integration Services                     1033                 Business Intelligence Edition 12.2.5000.0     No         Yes      

    Package properties:
      Description:                   Microsoft SQL Server 2014
      ProductName:                   SQL Server 2014
      Type:                          RTM
      Version:                       12
      SPLevel:                       2
      KBArticle:                     KB3171021
      KBArticleHyperlink:            http://support.microsoft.com/?kbid=3171021
      PatchType:                     SP
      AssociatedHotfixBuild:         0
      Platform:                      x64
      PatchLevel:                    12.2.5000.0
      ProductVersion:                12.0.2000.8
      GDRReservedRange:              12.0.2200.0:12.0.2290.0;12.0.4200.0:12.0.4299.0;12.0.4830.0:12.0.4880.0
      Installation location:         f:\fa696b9bbd6496233f0814\x64\setup\

    Updated product edition:
      Instance             Edition            
      MSSQLSERVER          Business Intelligence

    User Input Settings:
      ACTION:                        Patch
      ALLINSTANCES:                  false
      CLUSTERPASSIVE:                false
      CONFIGURATIONFILE:            
      ENU:                           true
      ERRORREPORTING:                false
      HELP:                          false
      IACCEPTSQLSERVERLICENSETERMS:  true
      INDICATEPROGRESS:              false
      INSTANCEID:                    <empty>
      INSTANCENAME:                  <empty>
      QUIET:                         false
      QUIETSIMPLE:                   false
      SQMREPORTING:                  false
      UIMODE:                        Normal
      X86:                           false

    Rules with failures:

    Global rules:

    There are no scenario-specific rules.

    Rules report file:               C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20161010_122000\SystemConfigurationCheck_Report.htm

    The System Configuration Check report looks like this:

    Microsoft SQL Server 2014 - System Configuration Check Report    

    Computer Name(s): METSQLBI01
    Report Date/Time: 10/10/2016 12:20 PM
    Saved to Directory: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20161010_122000\SystemConfigurationCheck_Report.htm

    Rule Name Rule Description Result Message/Corrective Action
    PatchGlobalRules: SQL Server 2014 Setup configuration checks for rules group 'PatchGlobalRules'        
             Engine_ResourceDLLUpdateRestartCheck Checks whether shared resource DLLs will be updated, causing restarts for clustered SQL Server instances active on this node. Not applicable This rule does not apply to your system configuration.
             AclPermissionsFacet Checks if the SQL Server registry keys are consistent. Passed SQL Server registry keys are consistent and can support SQL Server installation or upgrade.
             Cluster_IsLocalNodeGroupOwner Checks if the local computer is an owner of an online cluster group for a failover cluster instance that contains the SQL Server service, Analysis Services service or a generic service. Passed The local computer is not an owner of an online cluster group for a failover cluster instance that contains the SQL Server service, Analysis Services service or a generic service. The SQL Server instances do not need to be taken offline.
             Cluster_IsOnlineIfClustered Verifies that the computer is not clustered or that the computer is clustered and the cluster service is online. Passed The computer is either not clustered or the cluster is up and online.
             RebootRequiredCheck Checks if a pending computer restart is required. A pending restart can cause Setup to fail. Passed The computer does not require a restart.
             ThreadHasAdminPrivilegeCheck Checks whether the account running SQL Server Setup has administrator rights on the computer. Passed The account running SQL Server Setup has administrator rights on the computer.
             WmiServiceStateCheck Checks whether the WMI service is started and running on the computer. Passed The Windows Management Instrumentation (WMI) service is running.

    Rules Documentation:        http://go.microsoft.com/fwlink/?LinkId=296445      
    Community:        http://go.microsoft.com/fwlink/?LinkId=296470      
    Setup Help File:        http://go.microsoft.com/fwlink/?LinkId=296452

    There are 3 error logs and one very big detail.txt file.  The error logs all look similar but are not exactly the same.  The final error that kills the process is the same in all three so I am posting only the last one.

     

    2016-10-10 12:38:49.09 Server      Microsoft SQL Server 2014 (SP2) (KB3171021) - 12.0.5000.0 (X64)
     Jun 17 2016 19:14:09
     Copyright (c) Microsoft Corporation
     Business Intelligence Edition (64-bit) on Windows NT 6.3 <X64> (Build 9600: ) (Hypervisor)

    2016-10-10 12:38:49.09 Server      UTC adjustment: -4:00
    2016-10-10 12:38:49.09 Server      (c) Microsoft Corporation.
    2016-10-10 12:38:49.09 Server      All rights reserved.
    2016-10-10 12:38:49.09 Server      Server process ID is 3128.
    2016-10-10 12:38:49.09 Server      System Manufacturer: 'VMware, Inc.', System Model: 'VMware Virtual Platform'.
    2016-10-10 12:38:49.09 Server      Authentication mode is WINDOWS-ONLY.
    2016-10-10 12:38:49.09 Server      Logging SQL Server messages in file 'D:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
    2016-10-10 12:38:49.09 Server      The service account is 'FRANCO-MFG\SQLBI_sqlsrv$'. This is an informational message; no user action is required.
    2016-10-10 12:38:49.09 Server      Registry startup parameters:
      -d D:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\master.mdf
      -e D:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Log\ERRORLOG
      -l D:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
    2016-10-10 12:38:49.09 Server      Command Line Startup Parameters:
      -s "MSSQLSERVER"
      -m "SqlSetup"
      -T 4022
      -T 4010
      -T 1905
      -T 3701
      -T 8015
    2016-10-10 12:38:49.46 Server      SQL Server detected 2 sockets with 2 cores per socket and 2 logical processors per socket, 4 total logical processors; using 4 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
    2016-10-10 12:38:49.46 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
    2016-10-10 12:38:49.46 Server      Detected 32767 MB of RAM. This is an informational message; no user action is required.
    2016-10-10 12:38:49.46 Server      Using conventional memory in the memory manager.
    2016-10-10 12:38:49.50 Server      Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033)
    2016-10-10 12:38:49.53 Server      Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
    2016-10-10 12:38:49.55 Server      The maximum number of dedicated administrator connections for this instance is '1'
    2016-10-10 12:38:49.55 Server      This instance of SQL Server last reported using a process ID of 884 at 10/10/2016 12:38:48 PM (local) 10/10/2016 4:38:48 PM (UTC). This is an informational message only; no user action is required.
    2016-10-10 12:38:49.55 Server      Node configuration: node 0: CPU mask: 0x000000000000000f:0 Active CPU mask: 0x000000000000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
    2016-10-10 12:38:49.56 Server      Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
    2016-10-10 12:38:49.56 Server      Database Instant File Initialization: disabled. For security and performance considerations see the topic 'Database Instant File Initialization' in SQL Server Books Online. This is an informational message only. No user action is required.
    2016-10-10 12:38:49.57 Server      Database Mirroring Transport is disabled in the endpoint configuration.
    2016-10-10 12:38:49.57 spid8s      Warning ******************
    2016-10-10 12:38:49.57 spid8s      SQL Server started in single-user mode. This an informational message only. No user action is required.
    2016-10-10 12:38:49.57 spid8s      Starting up database 'master'.
    2016-10-10 12:38:49.59 spid8s      5 transactions rolled forward in database 'master' (1:0). This is an informational message only. No user action is required.
    2016-10-10 12:38:49.60 spid8s      0 transactions rolled back in database 'master' (1:0). This is an informational message only. No user action is required.
    2016-10-10 12:38:49.60 spid8s      Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
    2016-10-10 12:38:49.68 Server      CLR version v4.0.30319 loaded.
    2016-10-10 12:38:49.68 spid8s      CHECKDB for database 'master' finished without errors on 2016-10-08 02:00:00.627 (local time). This is an informational message only; no user action is required.
    2016-10-10 12:38:49.68 spid8s      SQL Server Audit is starting the audits. This is an informational message. No user action is required.
    2016-10-10 12:38:49.68 spid8s      SQL Server Audit has started the audits. This is an informational message. No user action is required.
    2016-10-10 12:38:49.70 spid8s      SQL Trace ID 1 was started by login "sa".
    2016-10-10 12:38:49.71 spid8s      Server name is 'METSQLBI01'. This is an informational message only. No user action is required.
    2016-10-10 12:38:49.72 spid15s     Starting up database 'ReportServer'.
    2016-10-10 12:38:49.72 spid16s     Starting up database 'ReportServerTempDB'.
    2016-10-10 12:38:49.72 spid9s      Starting up database 'mssqlsystemresource'.
    2016-10-10 12:38:49.72 spid17s     Starting up database 'AdminFranco'.
    2016-10-10 12:38:49.72 spid18s     Starting up database 'InventoryAudit'.
    2016-10-10 12:38:49.73 spid14s     Starting up database 'msdb'.
    2016-10-10 12:38:49.73 spid19s     Starting up database 'SSISDB'.
    2016-10-10 12:38:49.73 spid9s      The resource database build version is 12.00.5000. This is an informational message only. No user action is required.
    2016-10-10 12:38:49.73 spid20s     Starting up database 'ReportingAndUtility'.
    2016-10-10 12:38:49.73 spid21s     Starting up database 'RedGate'.
    2016-10-10 12:38:49.73 spid22s     Starting up database 'GDSN'.
    2016-10-10 12:38:49.73 Server      Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
    2016-10-10 12:38:49.73 spid12s     A self-generated certificate was successfully loaded for encryption.
    2016-10-10 12:38:49.73 spid12s     Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
    2016-10-10 12:38:49.73 spid12s     Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag 7806. This is an informational message only. No user action is required.
    2016-10-10 12:38:49.74 Server      SQL Server is attempting to register a Service Principal Name (SPN) for the SQL Server service. Kerberos authentication will not be possible until a SPN is registered for the SQL Server service. This is an informational message. No user action is required.
    2016-10-10 12:38:49.78 spid9s      Starting up database 'model'.
    2016-10-10 12:38:49.79 spid16s     CHECKDB for database 'ReportServerTempDB' finished without errors on 2016-10-08 05:00:04.180 (local time). This is an informational message only; no user action is required.
    2016-10-10 12:38:49.79 Server      The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/MetSQLBI01.franco-mfg.com ] for the SQL Server service.
    2016-10-10 12:38:49.79 Server      The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/MetSQLBI01.franco-mfg.com:1433 ] for the SQL Server service.
    2016-10-10 12:38:49.80 spid15s     CHECKDB for database 'ReportServer' finished without errors on 2016-10-08 05:00:03.480 (local time). This is an informational message only; no user action is required.
    2016-10-10 12:38:49.80 spid17s     CHECKDB for database 'AdminFranco' finished without errors on 2016-10-08 05:00:00.990 (local time). This is an informational message only; no user action is required.
    2016-10-10 12:38:49.80 spid21s     CHECKDB for database 'RedGate' finished without errors on 2016-10-08 05:00:02.840 (local time). This is an informational message only; no user action is required.
    2016-10-10 12:38:49.81 spid20s     CHECKDB for database 'ReportingAndUtility' finished without errors on 2016-10-08 05:00:03.167 (local time). This is an informational message only; no user action is required.
    2016-10-10 12:38:49.81 spid22s     CHECKDB for database 'GDSN' finished without errors on 2016-10-08 05:00:01.510 (local time). This is an informational message only; no user action is required.
    2016-10-10 12:38:49.82 spid14s     CHECKDB for database 'msdb' finished without errors on 2016-10-08 02:00:01.913 (local time). This is an informational message only; no user action is required.
    2016-10-10 12:38:49.83 spid19s     24 transactions rolled forward in database 'SSISDB' (9:0). This is an informational message only. No user action is required.
    2016-10-10 12:38:49.84 spid18s     CHECKDB for database 'InventoryAudit' finished without errors on 2016-10-08 05:00:02.027 (local time). This is an informational message only; no user action is required.
    2016-10-10 12:38:49.85 spid9s      CHECKDB for database 'model' finished without errors on 2016-10-08 02:00:01.517 (local time). This is an informational message only; no user action is required.
    2016-10-10 12:38:49.85 spid9s      Clearing tempdb database.
    2016-10-10 12:38:49.85 spid19s     0 transactions rolled back in database 'SSISDB' (9:0). This is an informational message only. No user action is required.
    2016-10-10 12:38:49.85 spid19s     Recovery is writing a checkpoint in database 'SSISDB' (9). This is an informational message only. No user action is required.
    2016-10-10 12:38:49.88 spid19s     CHECKDB for database 'SSISDB' finished without errors on 2016-10-08 05:00:04.553 (local time). This is an informational message only; no user action is required.
    2016-10-10 12:38:50.07 spid9s      Starting up database 'tempdb'.
    2016-10-10 12:38:50.43 spid9s      The tempdb database has 4 data file(s).
    2016-10-10 12:38:51.50 spid8s      Database 'master' is upgrading script 'SSIS_hotfix_install.sql' from level 201330692 to level 201331592.
    2016-10-10 12:38:51.68 spid8s      ------------------------------------------------------
    2016-10-10 12:38:51.68 spid8s      Starting execution of SSIS_HOTFIX_INSTALL.SQL        
    2016-10-10 12:38:51.68 spid8s      ------------------------------------------------------
    2016-10-10 12:38:51.69 spid8s      Start applying SSIS_HOTFIX_INSTALL changes.
    2016-10-10 12:38:51.71 spid8s      Stored procedure [catalog].[create_execution] has been dropped.
    2016-10-10 12:38:51.71 spid8s      Stored procedure [catalog].[set_execution_parameter_value] has been dropped.
    2016-10-10 12:38:51.71 spid8s      Stored procedure [catalog].[configure_catalog] has been dropped.
    2016-10-10 12:38:51.72 spid8s      Stored procedure [internal].[cleanup_server_retention_window] has been dropped.
    2016-10-10 12:38:51.72 spid8s      Stored procedure [internal].[cleanup_server_log] has been dropped.
    2016-10-10 12:38:51.72 spid8s      Stored procedure [internal].[cleanup_server_execution_keys] has been dropped.
    2016-10-10 12:38:51.72 spid8s      Stored procedure [internal].[get_execution_values] has been dropped.
    2016-10-10 12:38:51.73 spid8s      Stored procedure [internal].[get_execution_property_override_values] has been dropped.
    2016-10-10 12:38:51.73 spid8s      Stored procedure [internal].[configure_execution_encryption_algorithm] has been dropped.
    2016-10-10 12:38:51.73 spid8s      Stored procedure [catalog].[set_execution_property_override_value] has been dropped.
    2016-10-10 12:38:51.87 spid8s      Stored procedure [catalog].[create_execution] has been recreated.
    2016-10-10 12:38:51.89 spid8s      Stored procedure [catalog].[set_execution_parameter_value] has been recreated.
    2016-10-10 12:38:51.90 spid8s      Stored procedure [internal].[cleanup_server_retention_window] has been recreated.
    2016-10-10 12:38:51.91 spid8s      Stored procedure [internal].[cleanup_server_log] has been recreated.
    2016-10-10 12:38:51.93 spid8s      Stored procedure [internal].[cleanup_server_execution_keys] has been recreated.
    2016-10-10 12:38:51.94 spid8s      Stored procedure [internal].[get_execution_values] has been recreated.
    2016-10-10 12:38:51.95 spid8s      Stored procedure [internal].[get_execution_property_override_values] has been recreated.
    2016-10-10 12:38:51.97 spid8s      Stored procedure [internal].[configure_execution_encryption_algorithm] has been recreated.
    2016-10-10 12:38:51.99 spid8s      Stored procedure [catalog].[configure_catalog] has been recreated.
    2016-10-10 12:38:52.01 spid8s      Stored procedure [catalog].[set_execution_property_override_value] has been recreated.
    2016-10-10 12:38:52.01 spid8s      Permissions on [catalog].[create_execution] has been granted.
    2016-10-10 12:38:52.01 spid8s      Permissions on [catalog].[set_execution_parameter_value] has been granted.
    2016-10-10 12:38:52.02 spid8s      Permissions on [catalog].[configure_catalog] has been granted.
    2016-10-10 12:38:52.02 spid8s      Error: 15151, Severity: 16, State: 1.
    2016-10-10 12:38:52.02 spid8s      Cannot find the user '##MS_SSISServerCleanupJobUser##', because it does not exist or you do not have permission.
    2016-10-10 12:38:52.02 spid8s      The failed batch of t-sql statements :
     /*
    **  SSIS_hotfix_install.SQL
    **  Patch install script for the SSIS server catalog (SSISDB).
    */

    PRINT '------------------------------------------------------'
    PRINT 'Starting execution of SSIS_HOTFIX_INSTALL.SQL         '
    PRINT '------------------------------------------------------'

    DECLARE @run_script BIT
    SET @run_script=1

    DECLARE @ssis_database_name SYSNAME
    SET @ssis_database_name = N'SSISDB'

    -- Check whether SSISDB exists
    IF(DB_ID(@ssis_database_name) IS NULL)
    BEGIN
        SET @run_script=0
        PRINT 'Database SSISDB does not exist in current SQL Server instance'
    END

    -- Check whether SSISDB is online
    IF @run_script <> 0
    BEGIN
     DECLARE @state_online SYSNAME
     SET @state_online = 'ONLINE'
     SELECT @state_online = UPPER(@state_online COLLATE SQL_Latin1_General_CP1_CI_AS)

     IF NOT EXISTS (SELECT state_desc FROM master.sys.databases WHERE name = @ssis_database_name AND
               UPPER(state_desc COLLATE SQL_Latin1_General_CP1_CI_AS) LIKE @state_online)
     BEGIN
      SET @run_script=0   
      PRINT 'WARNING! The database SSISDB is not ONLINE. SSIS_HOTFIX_INSTALL.SQL will not be applied. Please run the script manually after the upgrade.'
     END
    END

    -- Check whether SSISDB is corrupted
    IF @run_script <> 0
    BEGIN
     IF OBJECT_ID (N'SSISDB.internal.catalog_properties', N'U') IS NULL
     BEGIN
      SET @run_script=0
      PRINT 'Database SSISDB is missing the catalog properties table. The database may be corrupted, or it is not an SSIS Catalog.'
     END
    END

    IF  @run_script = 0
    BEGIN
     PRINT 'Database SSISDB was not patched.'
    END
    ELSE
    BEGIN
     PRINT 'Start applying SSIS_HOTFIX_INSTALL changes.'

     DECLARE @rawCmd NVARCHAR(MAX), @cmd NVARCHAR(MAX)

     DECLARE @targetVersion NVARCHAR(256)
     SELECT @targetVersion = CONVERT(NVARCHAR,SERVERPROPERTY(N'ProductVersion'))

        --Version handler for PCU2
     --1. drop the old SP
     IF OBJECT_ID (N'SSISDB.[catalog].[create_execution]', N'P') IS NOT NULL
     BEGIN
      SET @rawCmd = N'DROP PROCEDURE [catalog].[cre...
    2016-10-10 12:38:52.02 spid8s      Error: 912, Severity: 21, State: 2.
    2016-10-10 12:38:52.02 spid8s      Script level upgrade for database 'master' failed because upgrade step 'SSIS_hotfix_install.sql' encountered error 15151, state 1, severity 16. 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.
    2016-10-10 12:38:52.02 spid8s      Error: 3417, Severity: 21, State: 3.
    2016-10-10 12:38:52.02 spid8s      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.
    2016-10-10 12:38:52.02 spid8s      SQL Server shutdown has been initiated
    2016-10-10 12:38:52.02 spid8s      SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
    2016-10-10 12:38:53.03 spid8s      Error: 25725, Severity: 16, State: 1.
    2016-10-10 12:38:53.03 spid8s      An error occurred while trying to flush all running Extended Event sessions.  Some events may be lost.
    2016-10-10 12:38:53.07 spid12s     The SQL Server Network Interface library successfully deregistered the Service Principal Name (SPN) [ MSSQLSvc/MetSQLBI01.franco-mfg.com ] for the SQL Server service.
    2016-10-10 12:38:53.07 spid12s     The SQL Server Network Interface library successfully deregistered the Service Principal Name (SPN) [ MSSQLSvc/MetSQLBI01.franco-mfg.com:1433 ] for the SQL Server service.

    Monday, October 10, 2016 5:38 PM

Answers

  • Thanks for the help.

    Your link did not answer my question but it did point me in the right direction. The link tells you how to make a ##MS_SSISServerCleanupJobLogin## login but I was missing the ##MS_SSISServerCleanupJobUser## user which the linked to post assumes you have.  No clue why I don't have it, my SSIS Server Maintenance Job been working fine without it.  I found this http://billfellows.blogspot.com/2014/09/behind-scenes-with-integration-services.html link that showed how the ##MS_SSISServerCleanupJobUser## use should be configured.  I restored the database to pre-service pack condition, added the ##MS_SSISServerCleanupJobUser## user configuring as listed in the link and then the SP ran fine.

    • Marked as answer by P at franco Monday, October 10, 2016 10:06 PM
    Monday, October 10, 2016 10:06 PM

All replies

  • That error is a symptom of restoring SSISDB.

    Please see "6.1":

    https://blogs.msdn.microsoft.com/mattm/2012/03/23/ssis-catalog-backup-and-restore/

    Monday, October 10, 2016 5:54 PM
  • you need to share detail.txt and summary.txt
    ref-https://msdn.microsoft.com/en-us/library/ms143702.aspx

    It talks about Database SSISDB- can you please check is there any issues on this  and also SQL Server 2012 Integration Services (SSIS) includes the SSISDB database (fyi..)

    if login dont there see if if you can

    . Create login [##MS_SSISServerCleanupJobLogin##] using CREATE LOGIN TSQL statement. 
    https://msdn.microsoft.com/en-us/library/ms189751(v=sql.110).aspx

    This login is for internal use in SSISDB maintenance then you Map SSISDB user ##MS_SSISServerCleanupJobUser## to server login ##MS_SSISServerCleanupJobLogin##

     USE SSISDB
     ALTER USER [##MS_SSISServerCleanupJobUser##] with LOGIN = [##MS_SSISServerCleanupJobLogin##]

    if you want to know more about above login then please check

    Backup, Restore, and Move the SSIS Catalog
    https://msdn.microsoft.com/en-in/library/hh213291(v=sql.120).aspx

    some link says this
    http://answers.flyppdevportal.com/MVC/Post/Thread/fc594d9f-d26c-4469-8840-5b2e1cf2d21f?category=sqlsetupandupgrade
    not sure does it helps here.

    Regards, S_NO "_"


    • Edited by S_NO Monday, October 10, 2016 6:11 PM +
    Monday, October 10, 2016 6:09 PM
  • Thanks for the help.

    Your link did not answer my question but it did point me in the right direction. The link tells you how to make a ##MS_SSISServerCleanupJobLogin## login but I was missing the ##MS_SSISServerCleanupJobUser## user which the linked to post assumes you have.  No clue why I don't have it, my SSIS Server Maintenance Job been working fine without it.  I found this http://billfellows.blogspot.com/2014/09/behind-scenes-with-integration-services.html link that showed how the ##MS_SSISServerCleanupJobUser## use should be configured.  I restored the database to pre-service pack condition, added the ##MS_SSISServerCleanupJobUser## user configuring as listed in the link and then the SP ran fine.

    • Marked as answer by P at franco Monday, October 10, 2016 10:06 PM
    Monday, October 10, 2016 10:06 PM