While installing the SQL Server 2014 SP3 we experience the following error:
SQL Server Setup has encountered the following error:
Exception has been thrown by the target of an invocation.
Here is the cmdlet we use:
SQLEXPR_x64_ENU.exe /ACTION=Patch /AllInstances /IAcceptSQLServerLicenseTerms
Looking at the SQL Setup Bootstrap log we have an exception:
C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\<Timestamp>\Detail.txt
Error: Action “Microsoft.SqlServer.Configuration.UIExtension.StartAction” threw an exception during execution.
Microsoft.SqlServer.Setup.Chainer.Workflow.ActionExecutionException: Thread was being aborted. —> System.Threading.ThreadAbortException: Thread was being aborted.
at System.Threading.WaitHandle.WaitOneNative(SafeWaitHandle waitHandle, UInt32 millisecondsTimeout, Boolean hasThreadAffinity, Boolean exitContext)
at System.Threading.WaitHandle.WaitOne(Int64 timeout, Boolean exitContext)
at Microsoft.SqlServer.Configuration.UIExtension.ShowActiveObjectTemplate.Show(String moniker)
Microsoft.SqlServer.Configuration.UIExtension.UserInterfaceService.Start(String moniker, Predicate`1 pageFilter)
at Microsoft.SqlServer.Configuration.UIExtension.StartAction.ExecuteAction(String actionId)
at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.<>c__DisplayClasse.<ExecuteActionWithRetryHelper>b__b()
at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)
— End of inner exception stack trace —
at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)
at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionWithRetryHelper(WorkflowObject metaDb, ActionKey action, ActionMetadata actionMetadata, TextWriter statusStream)
at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
You might also have the following in the Event Viewer > Application:
Log Name: Application
Source: Windows Error Reporting
Date: 26/02/2019 16:23:50
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: sfbfe01.recore.lab
Description:
Fault bucket , type 0
Event Name: SQL120Exception
Response: Not available
Cab Id: 0
Problem signature:
P1: SQL Server 2014@RTM@KB3171021
P2: 0x028C33E7
P3: 0x8D8AE474
P4: 0xCF353DCD
P5: 0xB7EAF00B
P6: PatchWizard
P7: Unknown
P8: Unknown
P9: Unknown
P10:
Attached files:
C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20190226_162225\Watson_1\LogFiles.cab
To successfully install the SQL Server 2014 SP3 we can use the /Q parameter:
SQLEXPR_x64_ENU.exe /Q /ACTION=Patch /AllInstances /IAcceptSQLServerLicenseTerms
Using this parameter we won’t have the user interface but the update will be successful:
Invoke-Sqlcmd -query “Select @@VERSION” -ServerInstance “.\RTCLOCAL”
Invoke-Sqlcmd -query “Select @@VERSION” -ServerInstance “.\LYNCLOCAL”
For Standard Edition the RTC should also be updated:
Invoke-Sqlcmd -query “Select @@VERSION” -ServerInstance “.\RTC”
For additional parameter please check the following article:
Install SQL Server from the Command Prompt
https://docs.microsoft.com/sql/database-engine/install-windows/install-sql-server-from-the-command-prompt
