SQL Server Express 2008 R2 installer fails to complete.
-
Thursday, April 12, 2012 3:46 PM
I am trying to upgrade an application that uses SQL Express 2008 R2 64 bit. When the application installs it runs SQLEXPR_x64_ENU.exe to see if SQL server needs an update. Unfortunately the SQL check / update never completes and the application does not install. Below are the Summary.txt log and the excerpts from Detail log from the failed instillation:
Thanks.
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: 2012-04-11 09:12:11
End time: 2012-04-11 09:13:16
Requested action: PatchMachine Properties:
Machine name: VCENTER
Machine processor count: 2
OS version: Windows Server 2008 R2
OS service pack: Service Pack 1
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: NoProduct features discovered:
Product Instance Instance ID Feature Language Edition Version Clustered
Sql Server 2008 R2 VIM_SQLEXP MSSQL10_50.VIM_SQLEXP Database Engine Services 1033 Express Edition 10.51.2500.0 No
Sql Server 2008 R2 VIM_SQLEXP MSSQL10_50.VIM_SQLEXP SQL Server Replication 1033 Express Edition 10.51.2500.0 NoPackage properties:
Description: SQL Server Database Services 2008 R2
ProductName: SQL2008
Type: RTM
Version: 10
SPLevel: 1
KBArticle: KB2528583
KBArticleHyperlink: http://support.microsoft.com/?kbid=2528583
PatchType: SP
AssociateHotfixBuild: 0
Platform: x64
PatchLevel: 10.51.2500.0
ProductVersion: 10.50.1600.1
GDRReservedRange: 10.0.1000.0:10.0.1099.0;10.0.3000.0:10.0.3099.0
PackageName: SQLServer2008-KB2528583-x64.exe
Installation location: c:\addbdc680a16eace5ad6e3bf9ab9\PCUSOURCE\x64\setup\User Input Settings:
ACTION: Patch
ALLINSTANCES: False
CLUSTERPASSIVE: False
CONFIGURATIONFILE:
ENU: True
FARMACCOUNT: <empty>
FARMADMINPORT: 0
FARMPASSWORD: *****
HELP: False
INDICATEPROGRESS: False
INSTANCEID: <empty>
INSTANCENAME: VIM_SQLEXP
PASSPHRASE: *****
QUIET: False
QUIETSIMPLE: True
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.
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)DETAIL TEXT LOG Excerpt:
2012-04-11 09:13:07 Slp: The highest installed patch version is 10.51.2500.0
2012-04-11 09:13:07 Slp: Instance Name: VIM_SQLEXP PatchState: Installed ReadyToInstallPatch: False ReadyToRemovePatch: True ReadyToUpgradeMsi: False
2012-04-11 09:13:07 Slp: Shared Features PatchState: Installed ReadyToInstallPatch: False ReadyToRemovePatch: True ReadyToUpgradeMsi False
2012-04-11 09:13:07 Slp: Error: Action "Microsoft.SqlServer.Configuration.MsiExtension.SetInstanceInstallStateAction" threw an exception during execution.
2012-04-11 09:13:07 Slp: Microsoft.SqlServer.Setup.Chainer.Workflow.ActionExecutionException: 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. ---> Microsoft.SqlServer.Setup.Chainer.Workflow.NoopWorkflowException: 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.
2012-04-11 09:13:07 Slp: at Microsoft.SqlServer.Configuration.MsiExtension.SetInstanceInstallStateAction.GetEligiableInstances()
2012-04-11 09:13:07 Slp: at Microsoft.SqlServer.Configuration.MsiExtension.SetInstanceInstallStateAction.ExecuteAction(String actionId)
2012-04-11 09:13:07 Slp: at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
2012-04-11 09:13:07 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun)
2012-04-11 09:13:07 Slp: --- End of inner exception stack trace ---
2012-04-11 09:13:07 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun)
2012-04-11 09:13:07 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionWithRetryHelper(WorkflowObject metaDb, ActionKey action, ActionMetadata actionMetadata, TextWriter statusStream)
2012-04-11 09:13:07 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
2012-04-11 09:13:07 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
2012-04-11 09:13:15 Slp: Received request to add the following file to Watson reporting: C:\Users\bxsadmin\AppData\Local\Temp\2\tmp5B63.tmp
2012-04-11 09:13:15 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
2012-04-11 09:13:15 Slp: Inner exceptions are being indented
2012-04-11 09:13:15 Slp:
2012-04-11 09:13:15 Slp: Exception type: Microsoft.SqlServer.Setup.Chainer.Workflow.NoopWorkflowException
2012-04-11 09:13:15 Slp: Message:
2012-04-11 09:13:15 Slp: 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.
2012-04-11 09:13:15 Slp: Data:
2012-04-11 09:13:15 Slp: DisableWatson = true
2012-04-11 09:13:15 Slp: Stack:
2012-04-11 09:13:15 Slp: at Microsoft.SqlServer.Configuration.MsiExtension.SetInstanceInstallStateAction.GetEligiableInstances()
2012-04-11 09:13:15 Slp: at Microsoft.SqlServer.Configuration.MsiExtension.SetInstanceInstallStateAction.ExecuteAction(String actionId)
2012-04-11 09:13:15 Slp: at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
2012-04-11 09:13:15 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun)
2012-04-11 09:13:15 Slp:
2012-04-11 09:13:15 Slp: ----------------------------------------------------------------------
2012-04-11 09:13:15 Slp:
2012-04-11 09:13:15 Slp: Error result: -2068643838
2012-04-11 09:13:15 Slp: Result facility code: 1203
2012-04-11 09:13:15 Slp: Result error code: 2
All Replies
-
Friday, April 13, 2012 12:10 AM
This might be more a problem with the install (like Installshield) as opposed to the actual SQL Express install. The message returned is clear enough
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.
The install then could consider this a failure, and stop on failure, despite an instance existing. Yet the Express install has done the job.
Does the application install with /? give you an option to run the install against an existing SQL instance?
Best Wishes, The Redman; If something helps, please help show it by voting, if it solves, bonus!
- Proposed As Answer by Peja TaoModerator Friday, April 13, 2012 5:43 AM
-
Friday, April 13, 2012 1:23 PM
The actual install is for VMware Update Manger. Unfortunately there is no command line switch to disable the SQL check or run the installer against the SQL instance. The Command line switches are limited see below. The only thing I think of is to uninstall SP1 for SQL Server 2008 R2 that WSUS installed and see if maybe the patch level is higher than the imbedded SQL installer in the VMware Update Manger application. Do you think that is worth trying / what problems could occur if this was removed?
msiexec /Option <Required Parameter> [Optional Parameter]
Install Options
</package | /i> <Product.msi>
Installs or configures a product
/a <Product.msi>
Administrative install - Installs a product on the network
/j<u|m> <Product.msi> [/t <Transform List>] [/g <Language ID>]
Advertises a product - m to all users, u to current user
</uninstall | /x> <Product.msi | ProductCode>
Uninstalls the product
Display Options
/quiet
Quiet mode, no user interaction
/passive
Unattended mode - progress bar only
/q[n|b|r|f]
Sets user interface level
n - No UI
b - Basic UI
r - Reduced UI
-
Monday, April 16, 2012 3:36 PM
check this link this ma help ou
http://forums.iis.net/p/1168787/1994914.aspx#1994914

