Trouble Applying SQL Server 2012 SP1 to SQL Server 2012 RTM on Windows Core Cluster
-
Thursday, January 17, 2013 3:25 PM
I want to update our 2K12 RTM clustered instances with SP1. There are two named instances running on node 1 and node 2 is passive. The O/S is Windows Server Core 2008 Enterprise R2 SP1.
I've tried to run the upgrade file (SQLServer2012SP1-KB2674319-x64-ENU.exe) from the command line and I get an error indicating that everything was already at the latest version. I get the same result when I use the full slipstream package specifying a configuration file with the upgrade action and the /QS flag.
Here's the message in the summary log:
Exception type: Microsoft.SqlServer.Setup.Chainer.Workflow.NoopWorkflowException
Message:
No features were updated during the setup execution. The requested features may not be installed or features are already at a higher patch level. Please review the summary.txt logs for further details.
HResult : 0x84b30002
FacilityCode : 1203 (4b3)
ErrorCode : 2 (0002)
Data:
DisableWatson = true
Stack:
at Microsoft.SqlServer.Configuration.MsiExtension.SetInstanceInstallStateAction.GetEligiableInstances()
at Microsoft.SqlServer.Configuration.MsiExtension.SetInstanceInstallStateAction.ExecuteAction(String actionId)
at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun, ServiceContainer context)I've also tried to upgrade a standalone 2008 instance to 2012 SP1 and the instance seems to have been upgraded only to the RTM level. The version information is 11.0.2100.60 and I was expecting to see 11.1.3000.0.
I haven't found explicit instructions for applying SP1 to a Cluster running on a Core operating system. I must be doing something wrong, can someone please provide the correct procedure to use on a core cluster?
All Replies
-
Thursday, January 17, 2013 5:07 PMModerator
Hello,
Please share the summary.txt log file with us.
Thank you in advance.
Regards,
Alberto Morillo
SQLCoffee.com -
Thursday, January 17, 2013 5:58 PM
Here's the file:
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): -2068643838
Exit facility code: 1203
Exit error code: 2
Exit message: No features were updated during the setup execution. The requested features may not be installed or features are already at a higher patch level. Please review the summary.txt logs for further details.
Start time: 2013-01-16 10:52:11
End time: 2013-01-16 10:53:01
Requested action: PatchCluster properties:
Machine name: AK1TVWCLN02
Product Instance Instance ID Feature Language Edition Version Clustered
SQL Server 2012 TESTDB01 MSSQL11.TESTDB01 Database Engine Services 1033 Enterprise Edition 11.0.2100.60 Yes
SQL Server 2012 TESTDB01 MSSQL11.TESTDB01 SQL Server Replication 1033 Enterprise Edition 11.0.2100.60 Yes
SQL Server 2012 TESTDB01 MSSQL11.TESTDB01 Full-Text and Semantic Extractions for Search 1033 Enterprise Edition 11.0.2100.60 Yes
SQL Server 2012 TESTDB01 MSSQL11.TESTDB01 Data Quality Services 1033 Enterprise Edition 11.0.2100.60 Yes
SQL Server 2012 TESTDB02 MSSQL11.TESTDB02 Database Engine Services 1033 Enterprise Edition 11.0.2100.60 Yes
SQL Server 2012 TESTDB02 MSSQL11.TESTDB02 SQL Server Replication 1033 Enterprise Edition 11.0.2100.60 Yes
SQL Server 2012 TESTDB02 MSSQL11.TESTDB02 Full-Text and Semantic Extractions for Search 1033 Enterprise Edition 11.0.2100.60 Yes
SQL Server 2012 TESTDB02 MSSQL11.TESTDB02 Data Quality Services 1033 Enterprise Edition 11.0.2100.60 Yes
SQL Server 2012 Client Tools Connectivity 1033 11.0.2100.60 NoMachine name: AK1TVWCLN01
Product Instance Instance ID Feature Language Edition Version Clustered
SQL Server 2012 TESTDB01 MSSQL11.TESTDB01 Database Engine Services Enterprise Edition 11.0.2100.60 Yes
SQL Server 2012 TESTDB01 MSSQL11.TESTDB01 SQL Server Replication Enterprise Edition 11.0.2100.60 Yes
SQL Server 2012 TESTDB01 MSSQL11.TESTDB01 Full-Text and Semantic Extractions for Search Enterprise Edition 11.0.2100.60 Yes
SQL Server 2012 TESTDB01 MSSQL11.TESTDB01 Data Quality Services Enterprise Edition 11.0.2100.60 Yes
SQL Server 2012 TESTDB02 MSSQL11.TESTDB02 Database Engine Services Enterprise Edition 11.0.2100.60 Yes
SQL Server 2012 TESTDB02 MSSQL11.TESTDB02 SQL Server Replication Enterprise Edition 11.0.2100.60 Yes
SQL Server 2012 TESTDB02 MSSQL11.TESTDB02 Full-Text and Semantic Extractions for Search Enterprise Edition 11.0.2100.60 Yes
SQL Server 2012 TESTDB02 MSSQL11.TESTDB02 Data Quality Services Enterprise Edition 11.0.2100.60 Yes
SQL Server 2012 Client Tools Connectivity 1033 11.1.3000.0 NoMachine Properties:
Machine name: AK1TVWCLN02
Machine processor count: 1
OS version: Windows Server 2008 R2 - ServerCore
OS service pack: Service Pack 1
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: YesProduct features discovered:
Product Instance Instance ID Feature Language Edition Version Clustered
SQL Server 2012 TESTDB01 MSSQL11.TESTDB01 Database Engine Services 1033 Enterprise Edition 11.0.2100.60 Yes
SQL Server 2012 TESTDB01 MSSQL11.TESTDB01 SQL Server Replication 1033 Enterprise Edition 11.0.2100.60 Yes
SQL Server 2012 TESTDB01 MSSQL11.TESTDB01 Full-Text and Semantic Extractions for Search 1033 Enterprise Edition 11.0.2100.60 Yes
SQL Server 2012 TESTDB01 MSSQL11.TESTDB01 Data Quality Services 1033 Enterprise Edition 11.0.2100.60 Yes
SQL Server 2012 TESTDB02 MSSQL11.TESTDB02 Database Engine Services 1033 Enterprise Edition 11.0.2100.60 Yes
SQL Server 2012 TESTDB02 MSSQL11.TESTDB02 SQL Server Replication 1033 Enterprise Edition 11.0.2100.60 Yes
SQL Server 2012 TESTDB02 MSSQL11.TESTDB02 Full-Text and Semantic Extractions for Search 1033 Enterprise Edition 11.0.2100.60 Yes
SQL Server 2012 TESTDB02 MSSQL11.TESTDB02 Data Quality Services 1033 Enterprise Edition 11.0.2100.60 Yes
SQL Server 2012 Client Tools Connectivity 1033 11.0.2100.60 NoPackage properties:
Description: Microsoft SQL Server 2012 Service Pack 1
ProductName: SQL Server 2012
Type: RTM
Version: 11
SPLevel: 1
KBArticle: KB2674319
KBArticleHyperlink:
PatchType: SP
AssociatedHotfixBuild: 0
Platform: x64
PatchLevel: 11.1.3000.0
ProductVersion: 11.0.2100.60
GDRReservedRange: 10.0.1000.0:10.0.1099.0;10.0.3000.0:10.0.3099.0
PackageName: SQLServer2012-KB2674319-x64.exe
Installation location: c:\97456731ac128f61356fcac58d8e5a26\x64\setup\User Input Settings:
ACTION: Patch
ALLINSTANCES: false
CLUSTERPASSIVE: false
CONFIGURATIONFILE:
ENU: true
HELP: false
IACCEPTSQLSERVERLICENSETERMS: true
INDICATEPROGRESS: false
INSTANCEID: <empty>
INSTANCENAME: <empty>
QUIET: false
QUIETSIMPLE: true
SQMREPORTING: false
UIMODE: Normal
X86: falseRules with failures:
Global rules:
There are no scenario-specific rules.
Rules report file: The rule result report file is not available.
Exception summary:
The following is an exception stack listing the exceptions in outermost to innermost order
Inner exceptions are being indentedException type: Microsoft.SqlServer.Setup.Chainer.Workflow.NoopWorkflowException
Message:
No features were updated during the setup execution. The requested features may not be installed or features are already at a higher patch level. Please review the summary.txt logs for further details.
HResult : 0x84b30002
FacilityCode : 1203 (4b3)
ErrorCode : 2 (0002)
Data:
DisableWatson = true
Stack:
at Microsoft.SqlServer.Configuration.MsiExtension.SetInstanceInstallStateAction.GetEligiableInstances()
at Microsoft.SqlServer.Configuration.MsiExtension.SetInstanceInstallStateAction.ExecuteAction(String actionId)
at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun, ServiceContainer context) -
Thursday, January 17, 2013 8:54 PMModerator
Hello,
Please note you have two named instances on that server, and when you apply the service pack you are not specifying an instance name. You are trying to apply the service pack on a default instance that does not exist.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com- Marked As Answer by Anthony Kascak Friday, January 18, 2013 6:51 PM
-
Friday, January 18, 2013 6:56 PM
I had tried to apply SP1 using a config file with the instancename parameter and that wasn't working. However when I specified the instancename on the command line, everything worked fine. The exact command line I used was:
SQLServer2012SP1-KB2674319-x64-ENU.exe \instancename="TestDB01" \iacceptsqlserverlicenseterms \indicateprogress \qs
The above command worked as expected when applied to the passive node first and then the active node.
- Marked As Answer by Anthony Kascak Friday, January 18, 2013 6:57 PM
-
Friday, January 18, 2013 7:02 PMModerator
Hello,
Thank you for sharing the solution with us.
Have a great weekend.
Regards,
Alberto Morillo
SQLCoffee.com

