Install SQL Server 2017 Express with configuration failed with -2055733247

Question

Install SQL Server 2017 Express with configuration failed with -2055733247

Yuebing Wu 1

I am installing SQL it failed with result:-2055733247 I searched the internet The stacktrace is
---------
(03) 2022-03-10 13:42:11 (03) 2022-03-10 13:42:11 (01) 2022-03-10 13:42:11 (01) 2022-03-10 13:42:11 (01) 2022-03-10 13:42:11 Slp: (01) 2022-03-10 13:42:11 Slp: (01) 2022-03-10 13:42:11 Slp: (01) 2022-03-10 13:42:11 Slp: (01) 2022-03-10 13:42:11 Slp: (01) 2022-03-10 13:42:11 Slp: (01) 2022-03-10 13:42:11 Slp: (01) 2022-03-10 13:42:11 Slp: (01) 2022-03-10 13:42:11 Slp: (01) 2022-03-10 13:42:11 Slp: (01) 2022-03-10 13:42:11 Slp: (01) 2022-03-10 13:42:11 Slp: (01) 2022-03-10 13:42:11 Slp: (01) 2022-03-10 13:42:11 Slp: (01) 2022-03-10 13:42:11 (01) 2022-03-10 13:42:11 (01) 2022-03-10 13:42:11 Slp: (01) 2022-03-10 13:42:11 Slp: (01) 2022-03-10 13:42:11 Slp: (01) 2022-03-10 13:42:11 Slp: (01) 2022-03-10 13:42:11 Slp: (01) 2022-03-10 13:42:11 Slp: (01) 2022-03-10 13:42:11 Slp: (01) 2022-03-10 13:42:11 Slp: (01) 2022-03-10 13:42:11 Slp: (01) 2022-03-10 13:42:11 Slp: (01) 2022-03-10 13:42:11 Slp: (01) 2022-03-10 13:42:11 Slp: (01) 2022-03-10 13:42:11 Slp: (01) 2022-03-10 13:42:11 Slp: (01) 2022-03-10 13:42:11 Slp: (01) 2022-03-10 13:42:11 Slp: (01) 2022-03-10 13:42:11 Slp: (01) 2022-03-10 13:42:11 Slp: (01) 2022-03-10 13:42:11 Slp: (01) 2022-03-10 13:42:11 Slp: (01) 2022-03-10 13:42:11 Slp: (01) 2022-03-10 13:42:11 (01) 2022-03-10 13:42:11 (01) 2022-03-10 13:42:11 (01) 2022-03-10 13:42:11 Slp: (01) 2022-03-10 13:42:11 (01) 2022-03-10 13:42:11 Slp: (01) 2022-03-10 13:42:11 Slp: (01) 2022-03-10 13:42:11 Slp: (01) 2022-03-10 13:42:11 Slp: (01) 2022-03-10 13:42:11 Slp: (01) 2022-03-10 13:42:11 Slp: (01) 2022-03-10 13:42:11 Slp: (01) 2022-03-10 13:42:11 Slp: (01) 2022-03-10 13:42:11 Slp: (01) 2022-03-10 13:42:11 Slp: (01) 2022-03-10 13:42:11 Slp: (01) 2022-03-10 13:42:11 Slp: (01) 2022-03-10 13:42:11 Slp: (01) 2022-03-10 13:42:11 Slp: (01) 2022-03-10 13:42:11 Slp: (01) 2022-03-10 13:42:11 Slp: (01) 2022-03-10 13:42:11 Slp: (01) 2022-03-10 13:42:11 Slp: (01) 2022-03-10 13:42:12 Original Parameter Values Server 2017 Express on a fresh machine with configuration.ini.

and could not find what this error code means.
Slp: Running Action: PackageDownloadAction
Slp: Error: Action "Microsoft.SqlServer.Configuration.SmartSetupExtension.PackageDownloadAction" threw an exception during execution.
Slp: Error: Action "Microsoft.SqlServer.Configuration.BootstrapExtension.ExecuteWorkflowAction" threw an exception during execution.
Slp: Microsoft.SqlServer.Setup.Chainer.Workflow.ActionExecutionException: A publishing loop has been detected by the PublishingQueue, which has LoopThreshold=10000, while publishing to the subscribed delegate "Microsoft.SqlServer.Configuration.SmartSetupExtension.SelectedUpdatesSetting : Void CalculateValue()". ---> Microsoft.SqlServer.Deployment.PrioritizedPublishing.PublishingLoopException: A publishing loop has been detected by the PublishingQueue, which has LoopThreshold=10000, while publishing to the subscribed delegate "Microsoft.SqlServer.Configuration.SmartSetupExtension.SelectedUpdatesSetting : Void CalculateValue()".
at Microsoft.SqlServer.Deployment.PrioritizedPublishing.PublishingQueue.CallQueuedSubscriberDelegates()
at Microsoft.SqlServer.Deployment.PrioritizedPublishing.PublishingQueue.Publish(Publisher publisher)
at Microsoft.SqlServer.Chainer.Infrastructure.Setting1.set_Value(T value) (01) 2022-03-10 13:42:11 Slp: at Microsoft.SqlServer.Configuration.SetupExtension.ComponentUpdateProgressMsgFormatter.SetProgressMessage(Object notification, Object[] objectArray) (01) 2022-03-10 13:42:11 Slp: at Microsoft.SqlServer.Chainer.Infrastructure.NotificationService.OnNotify(Object eventKey, Object notification, Object[] objectArray) (01) 2022-03-10 13:42:11 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionMetadata.NotifySkipped(ActionKey skippedAction) (01) 2022-03-10 13:42:11 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.SequenceStep.EvaluateState(Boolean noisy, TextWriter logging) (01) 2022-03-10 13:42:11 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionScheduler.SequenceReadyActions(List1 readyActions, TextWriter logging)
at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionEngine.RunActionQueue()
at Microsoft.SqlServer.Setup.Chainer.Workflow.Workflow.RunWorkflow(WorkflowObject workflowObject, HandleInternalException exceptionHandler)
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)
at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionEngine.RunActionQueue()
Slp: Error: Action "Microsoft.SqlServer.Configuration.BootstrapExtension.ExecuteWorkflowAction" threw an exception during execution.
Slp: Microsoft.SqlServer.Setup.Chainer.Workflow.ActionExecutionException: A publishing loop has been detected by the PublishingQueue, which has LoopThreshold=10000, while publishing to the subscribed delegate "Microsoft.SqlServer.Configuration.SmartSetupExtension.SelectedUpdatesSetting : Void CalculateValue()". ---> Microsoft.SqlServer.Deployment.PrioritizedPublishing.PublishingLoopException: A publishing loop has been detected by the PublishingQueue, which has LoopThreshold=10000, while publishing to the subscribed delegate "Microsoft.SqlServer.Configuration.SmartSetupExtension.SelectedUpdatesSetting : Void CalculateValue()".
at Microsoft.SqlServer.Deployment.PrioritizedPublishing.PublishingQueue.CallQueuedSubscriberDelegates()
at Microsoft.SqlServer.Deployment.PrioritizedPublishing.PublishingQueue.Publish(Publisher publisher)
at Microsoft.SqlServer.Chainer.Infrastructure.Setting1.set_Value(T value) (01) 2022-03-10 13:42:11 Slp: at Microsoft.SqlServer.Configuration.SetupExtension.ComponentUpdateProgressMsgFormatter.SetProgressMessage(Object notification, Object[] objectArray) (01) 2022-03-10 13:42:11 Slp: at Microsoft.SqlServer.Chainer.Infrastructure.NotificationService.OnNotify(Object eventKey, Object notification, Object[] objectArray) (01) 2022-03-10 13:42:11 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionMetadata.NotifySkipped(ActionKey skippedAction) (01) 2022-03-10 13:42:11 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.SequenceStep.EvaluateState(Boolean noisy, TextWriter logging) (01) 2022-03-10 13:42:11 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionScheduler.SequenceReadyActions(List1 readyActions, TextWriter logging)
at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionEngine.RunActionQueue()
at Microsoft.SqlServer.Setup.Chainer.Workflow.Workflow.RunWorkflow(WorkflowObject workflowObject, HandleInternalException exceptionHandler)
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)
at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionEngine.RunActionQueue()
at Microsoft.SqlServer.Setup.Chainer.Workflow.Workflow.RunWorkflow(WorkflowObject workflowObject, HandleInternalException exceptionHandler)
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)
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)
Slp: Received request to add the following file to Watson reporting: C:\Users\Automation\AppData\Local\Temp\1\tmp45C6.tmp
Slp: The following is an exception stack listing the exceptions in outermost to innermost order
Slp: Inner exceptions are being indented

Slp: Exception type: Microsoft.SqlServer.Deployment.PrioritizedPublishing.PublishingLoopException
Message:
A publishing loop has been detected by the PublishingQueue, which has LoopThreshold=10000, while publishing to the subscribed delegate "Microsoft.SqlServer.Configuration.SmartSetupExtension.SelectedUpdatesSetting : Void CalculateValue()".
HResult : 0x85780001
FacilityCode : 1400 (578)
ErrorCode : 1 (0001)
Data:
Threshold = 10000
DelegateDescription = Microsoft.SqlServer.Configuration.SmartSetupExtension.SelectedUpdatesSetting : Void CalculateValue()
WatsonData = Microsoft.SqlServer.Deployment.PrioritizedPublishing.PublishingLoopException@1
Stack:
at Microsoft.SqlServer.Deployment.PrioritizedPublishing.PublishingQueue.CallQueuedSubscriberDelegates()
at Microsoft.SqlServer.Deployment.PrioritizedPublishing.PublishingQueue.Publish(Publisher publisher)
at Microsoft.SqlServer.Chainer.Infrastructure.Setting1.set_Value(T value) (01) 2022-03-10 13:42:11 Slp: at Microsoft.SqlServer.Configuration.SetupExtension.ComponentUpdateProgressMsgFormatter.SetProgressMessage(Object notification, Object[] objectArray) (01) 2022-03-10 13:42:11 Slp: at Microsoft.SqlServer.Chainer.Infrastructure.NotificationService.OnNotify(Object eventKey, Object notification, Object[] objectArray) (01) 2022-03-10 13:42:11 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionMetadata.NotifySkipped(ActionKey skippedAction) (01) 2022-03-10 13:42:11 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.SequenceStep.EvaluateState(Boolean noisy, TextWriter logging) (01) 2022-03-10 13:42:11 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionScheduler.SequenceReadyActions(List1 readyActions, TextWriter logging)
at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionEngine.RunActionQueue()
at Microsoft.SqlServer.Setup.Chainer.Workflow.Workflow.RunWorkflow(WorkflowObject workflowObject, HandleInternalException exceptionHandler)
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)
Slp: Watson Bucket 1

(01) 2022-03-10 13:42:12 Slp: Parameter 0 : SQL Server 2017@rtm @

(01) 2022-03-10 13:42:12 Slp: Parameter 1 : Microsoft.SqlServer.Deployment.PrioritizedPublishing.PublishingQueue.CallQueuedSubscriberDelegates

(01) 2022-03-10 13:42:12 Slp: Parameter 2 : Microsoft.SqlServer.Deployment.PrioritizedPublishing.PublishingQueue.CallQueuedSubscriberDelegates

(01) 2022-03-10 13:42:12 Slp: Parameter 3 : Microsoft.SqlServer.Deployment.PrioritizedPublishing.PublishingLoopException@1400@1

(01) 2022-03-10 13:42:12 Slp: Parameter 4 : Microsoft.SqlServer.Deployment.PrioritizedPublishing.PublishingLoopException@1400@1

(01) 2022-03-10 13:42:12 Slp: Parameter 5 : ExecuteOuterSetupComponentUpdate

(01) 2022-03-10 13:42:12 Slp: Parameter 7 : Microsoft.SqlServer.Deployment.PrioritizedPublishing.PublishingLoopException@1

(01) 2022-03-10 13:42:12 Slp: Parameter 8 : Microsoft.SqlServer.Deployment.PrioritizedPublishing.PublishingLoopException@1

(01) 2022-03-10 13:42:12 Slp:
Final Parameter Values

(01) 2022-03-10 13:42:12 Slp: Parameter 0 : SQL Server 2017@rtm @

(01) 2022-03-10 13:42:12 Slp: Parameter 1 : 0x96EE48B5

(01) 2022-03-10 13:42:12 Slp: Parameter 2 : 0x96EE48B5

(01) 2022-03-10 13:42:12 Slp: Parameter 3 : 0x826066CA@1400@1

(01) 2022-03-10 13:42:12 Slp: Parameter 4 : 0x826066CA@1400@1

(01) 2022-03-10 13:42:12 Slp: Parameter 5 : ExecuteOuterSetupComponentUpdate

(01) 2022-03-10 13:42:12 Slp: Parameter 7 : 0x469D6AB5

(01) 2022-03-10 13:42:12 Slp: Parameter 8 : 0x469D6AB5

-------------

The Summary is as below
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2055733247
Exit facility code: 1400
Exit error code: 1
Exit message: A publishing loop has been detected by the PublishingQueue, which has LoopThreshold=10000, while publishing to the subscribed delegate "Microsoft.SqlServer.Configuration.SmartSetupExtension.SelectedUpdatesSetting : Void CalculateValue()".
Start time: 2022-03-10 13:42:05
End time: 2022-03-10 13:42:12
Requested action: Install
Exception help link: https://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=14.0.1000.169&EvtType=0x96EE48B5%400x826066CA%401400%401&EvtType=0x96EE48B5%400x826066CA%401400%401

Machine Properties:
Machine name: TESTMACHINE1
Machine processor count: 4
OS version: Microsoft Windows Server 2022 Standard (10.0.20348)
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

Package properties:
Description: Microsoft SQL Server 2017
ProductName: SQL Server 2017
Type: RTM
Version: 14
SPLevel: 0
Installation location: C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\SQLExpressInstallTmp-SQLEXPRESSSYMC\x64\setup\
Installation edition: Express

Product Update Status:
Failure to download updates.

User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: true
AGTSVCACCOUNT: NT AUTHORITY\NETWORK SERVICE
AGTSVCPASSWORD: <empty>
AGTSVCSTARTUPTYPE: Disabled
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSERVERMODE: TABULAR
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: <empty>
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: <empty>
ASTELSVCACCT: <empty>
ASTELSVCPASSWORD: <empty>
ASTELSVCSTARTUPTYPE: 0
ASTEMPDIR: Temp
BROWSERSVCSTARTUPTYPE: Disabled
CLTCTLRNAME: <empty>
CLTRESULTDIR: <empty>
CLTSTARTUPTYPE: 0
CLTSVCACCOUNT: <empty>
CLTSVCPASSWORD: <empty>
CLTWORKINGDIR: <empty>
COMMFABRICENCRYPTION: 0
COMMFABRICNETWORKLEVEL: 0
COMMFABRICPORT: 0
CONFIGURATIONFILE: C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\SQLExpressInstallTmp-SQLEXPRESSSYMC\ConfigurationFile-SA-UTF8.ini
CTLRSTARTUPTYPE: 0
CTLRSVCACCOUNT: <empty>
CTLRSVCPASSWORD: <empty>
CTLRUSERS: <empty>
ENABLERANU: true
ENU: true
EXTSVCACCOUNT: <empty>
EXTSVCPASSWORD: <empty>
FEATURES: SQLENGINE, REPLICATION, SNAC_SDK
FILESTREAMLEVEL: 2
FILESTREAMSHARENAME: SQLEXPRESSSYMC
FTSVCACCOUNT: <empty>
FTSVCPASSWORD: <empty>
HELP: false
IACCEPTPYTHONLICENSETERMS: false
IACCEPTROPENLICENSETERMS: false
INDICATEPROGRESS: false
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\db
INSTANCEID: SQLEXPRESSSYMC
INSTANCENAME: SQLEXPRESSSYMC
ISMASTERSVCACCOUNT: NT AUTHORITY\Network Service
ISMASTERSVCPASSWORD: <empty>
ISMASTERSVCPORT: 8391
ISMASTERSVCSSLCERTCN: <empty>
ISMASTERSVCSTARTUPTYPE: Automatic
ISMASTERSVCTHUMBPRINT: <empty>
ISSVCACCOUNT: NT AUTHORITY\Network Service
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
ISTELSVCACCT: <empty>
ISTELSVCPASSWORD: <empty>
ISTELSVCSTARTUPTYPE: 0
ISWORKERSVCACCOUNT: NT AUTHORITY\Network Service
ISWORKERSVCCERT: <empty>
ISWORKERSVCMASTER: <empty>
ISWORKERSVCPASSWORD: <empty>
ISWORKERSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
MRCACHEDIRECTORY:
NPENABLED: 0
PBDMSSVCACCOUNT: <empty>
PBDMSSVCPASSWORD: <empty>
PBDMSSVCSTARTUPTYPE: 0
PBENGSVCACCOUNT: <empty>
PBENGSVCPASSWORD: <empty>
PBENGSVCSTARTUPTYPE: 0
PBPORTRANGE: <empty>
PBSCALEOUT: false
PID: *****
QUIET: false
QUIETSIMPLE: true
ROLE: AllFeatures_WithDefaults
RSINSTALLMODE: DefaultNativeMode
RSSVCACCOUNT: <empty>
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: SQL
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: NT Service\MSSQL$SQLEXPRESSSYMC
SQLSVCINSTANTFILEINIT: false
SQLSVCPASSWORD: <empty>
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: <empty>
SQLTELSVCACCT: <empty>
SQLTELSVCPASSWORD: <empty>
SQLTELSVCSTARTUPTYPE: 0
SQLTEMPDBDIR: <empty>
SQLTEMPDBFILECOUNT: 0
SQLTEMPDBFILEGROWTH: -1
SQLTEMPDBFILESIZE: -1
SQLTEMPDBLOGDIR: <empty>
SQLTEMPDBLOGFILEGROWTH: -1
SQLTEMPDBLOGFILESIZE: -1
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SUPPRESSPRIVACYSTATEMENTNOTICE: false
TCPENABLED: 1
UIMODE: AutoAdvance
UpdateEnabled: true
UpdateSource: MU
USEMICROSOFTUPDATE: true
X86: false

Configuration file: C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20220310_134203\ConfigurationFile.ini

Rules with failures:

Global rules:

Scenario specific rules:

Rules report file: C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20220310_134203\SystemConfigurationCheck_Report.htm

Exception summary:
The following is an exception stack listing the exceptions in outermost to innermost order
Inner exceptions are being indented

Exception type: Microsoft.SqlServer.Deployment.PrioritizedPublishing.PublishingLoopException
Message:
A publishing loop has been detected by the PublishingQueue, which has LoopThreshold=10000, while publishing to the subscribed delegate "Microsoft.SqlServer.Configuration.SmartSetupExtension.SelectedUpdatesSetting : Void CalculateValue()".
HResult : 0x85780001
FacilityCode : 1400 (578)
ErrorCode : 1 (0001)
Data:
Threshold = 10000
DelegateDescription = Microsoft.SqlServer.Configuration.SmartSetupExtension.SelectedUpdatesSetting : Void CalculateValue()
WatsonData = Microsoft.SqlServer.Deployment.PrioritizedPublishing.PublishingLoopException@1
DisableWatson = true
Stack:
at Microsoft.SqlServer.Deployment.PrioritizedPublishing.PublishingQueue.CallQueuedSubscriberDelegates()
at Microsoft.SqlServer.Deployment.PrioritizedPublishing.PublishingQueue.Publish(Publisher publisher)
at Microsoft.SqlServer.Chainer.Infrastructure.Setting1.set_Value(T value) at Microsoft.SqlServer.Configuration.SetupExtension.ComponentUpdateProgressMsgFormatter.SetProgressMessage(Object notification, Object[] objectArray) at Microsoft.SqlServer.Chainer.Infrastructure.NotificationService.OnNotify(Object eventKey, Object notification, Object[] objectArray) at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionMetadata.NotifySkipped(ActionKey skippedAction) at Microsoft.SqlServer.Setup.Chainer.Workflow.SequenceStep.EvaluateState(Boolean noisy, TextWriter logging) at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionScheduler.SequenceReadyActions(List1 readyActions, TextWriter logging)
at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionEngine.RunActionQueue()
at Microsoft.SqlServer.Setup.Chainer.Workflow.Workflow.RunWorkflow(WorkflowObject workflowObject, HandleInternalException exceptionHandler)
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)
------

3 answers

Your answer

Answer 1

Erland Sommarskog 121.4K MVP Volunteer Moderator

Select the option Download media and try again, this time by starting Setup.exe. That may or may not resolve the issue, but the diagnostics may be a little bit better.

Yuebing Wu 1 Reputation point

2022-03-22T22:58:34.58+00:00

Thank you for your reply. We may not be able to try your method.
We have this run for tens of times daily automatically, but could only reproduce the issue with possibility 1%. We can not run the setup.exe manually because we could not reproduce by it.
Do you know a method to search out by error code?

Thank you again.
Erland Sommarskog 121.4K Reputation points MVP Volunteer Moderator

2022-03-22T23:01:28.577+00:00

Not sure what you mean here? Are you saying that most of the time install succeeds? If so, what is your problem?

The error code is not very useful as such, To understand why an installation failed you need to read the log files. And that can be quite a daunting task too!
Yuebing Wu 1 Reputation point

2022-03-22T23:30:50.633+00:00

Yes, 99% it success. I am going figure out why the 1% failed :(.

I compare two failed logs so far. It failed at PackageDownloadAction and PackageExtractAction

Both failed at
publishing loop has been detected by the PublishingQueue, which has LoopThreshold=10000, while publishing to the subscribed delegate "Microsoft.SqlServer.Configuration.SmartSetupExtension.SelectedUpdatesSetting
Erland Sommarskog 121.4K Reputation points MVP Volunteer Moderator

2022-03-23T22:29:33.943+00:00

Yes, 99% it success. I am going figure out why the 1% failed

Again, why? What are you actually trying to achieve?

And if you run it 100 times, how do you run it? The error message sounds like a bit that you are overtaxing the computer.
Yuebing Wu 1 Reputation point

2022-03-24T03:50:51.483+00:00

we have automation testing against the our software which deploy the sql server express. The test runs very frequently.
The sql server express install fails intermediately (at about 1% rate). We want to ensure our software working properly, so we want the sql server express to be installed 100% properly.
They are on different computers in virtual environment.
Erland Sommarskog 121.4K Reputation points MVP Volunteer Moderator

2022-03-24T22:30:57.347+00:00

So how you run the test? Do you install/uninstall in a swift fashion? That could cause some interesting effect.

But is that a valid use case? Sometimes when testing, you may run into issues that are due to the test setup, but which does not reflect actual an issue in a production situation.

Maybe it would be better to run a test where you start with reverting to a snapshot of virtual machine, so that you always have the same starting point.

By the way, it is not entirely uncommon that installations of SQL Server fail - there are questions about this daily. However, I don't think I've seen your particular error before. In most cases when installations fail, it is because there is some problem on the machine.

Answer 2

Hi YuebingWu-5389,
Welcome to Microsoft Q&A.
Instead of running setup from mounted ISO or a network drive, please copy the content of media to a local drive. And please disable any antivirus/security software on the machine for the time that the installation is running.

99% it success. I am going figure out why the 1% failed

If the problem persists, you can open a ticket to a professional engineer who can check your environment to see if we're missing something, and they will deal with your problem separately and confidentially. https://support.serviceshub.microsoft.com/supportforbusiness

Best Regards,
Amelia

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Yuebing Wu 1 Reputation point

2022-03-23T04:06:47.92+00:00

The setup is not from mounted ISO or network. It is a very clean environment.

Answer 3

Olaf Helper 47,436

Installation location: C:\Program Files (x86)\ Symantec \Symantec Endpoint Protection Manager\SQLExpressInstallTmp-SQLEXPRESSSYMC\ x64 \setup\

Seems the SQL Server installation is packaged with a Symantec product, and I also wonder why a 64 bit installer is located in a 32 bit system folder.
You may better contact Symantec support, maybe it's a know issue with their installer.

Share via

Install SQL Server 2017 Express with configuration failed with -2055733247

3 answers

Your answer