SQL Server 2019 Installation Error - An error occurred for a dependency of the feature

Published Nov 11 2019 01:52 AM 94.7K Views

After release of SQL Server 2019, one of our customer was trying to install SQL Server 2019 and encountered an error message. Since I was able to reproduce the issue in my lab, I contacted SSMS product group and they were kind enough to fix this issue very quickly. As of now, this is already called out in the release notes. The purpose of this blog is to show how to confirm if you are hitting the same issue. We would learn how to look at various log file and what are the error messages we need to look.

Issue Description:

Installation of SQL Server 2019 from removable media fails if SQL Server Management Studio 18.3 or earlier is installed. In my lab, I downloaded ISO from download center and mounted it. Here is the final screen shot showing installation failure.

  sql2019-setup-01.jpg

When we click on the hyperlink on the screen, it opens up setup summary file which has this information about failed component. (Database Engine Services)

Detailed results:
  Feature:                       Database Engine Services
  Status:                        Failed
  Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
  Next Step:                     Use the following information to resolve the error, and then try the setup process again.

Next step is to look at Detail.txt file for any hint about dependent feature. (Search for “at Microsoft” keyword)

Target package: "E:\1033_ENU_LP\x64\setup\x64\sqlncli.msi"
InstallPackage: MsiInstallProduct returned the result code 1602.

No retry-able MSI return code detected.
ExecuteActionWithRetryHelper.Failed actionToExecute is 'Install_sqlncli_Cpu64_Action', stack trace    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.<>c__DisplayClass2_0.<ExecuteActionWithRetryHelper>b__0()
   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.ActionInvocation.<>c__DisplayClass2_0.<ExecuteActionWithRetryHelper>b__0()
   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__DisplayClass2_0.<ExecuteActionWithRetryHelper>b__0()
   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__DisplayClass2_0.<ExecuteActionWithRetryHelper>b__0()
   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.Setup.Setup.RunRequestedWorkflow()
   at Microsoft.SqlServer.Chainer.Setup.Setup.Run(String[] args)
   at Microsoft.SqlServer.Chainer.Setup.Setup.Start(String[] args)
   at Microsoft.SqlServer.Chainer.Setup.Setup.Main()
Error: Action "Install_sqlncli_Cpu64_Action" failed during execution.
Completed Action: Install_sqlncli_Cpu64_Action, returned False

…Trimmed lines…

MSI (s) (5C:3C) [06:42:01:134]: Note: 1: 1729
MSI (s) (5C:3C) [06:42:01:134]: Product: Microsoft SQL Server 2012 Native Client  -- Configuration failed.

MSI (s) (5C:3C) [06:42:01:134]: Windows Installer reconfigured the product. Product Name: Microsoft SQL Server 2012 Native Client. Product Version: 11.4.7462.6. Product Language: 1033. Manufacturer: Microsoft Corporation. Reconfiguration success or error status: 1602.

From here we can see that issue is during installation of SQLNCLI (SQL Server Native Client) and error code is 1602. The log file associate is sqlncli_Cpu64_1

MSI (s) (5C:3C) [06:42:01:009]: Note: 1: 2203 2: E:\sqlncli.msi 3: -2147287038
MSI (s) (5C:3C) [06:42:01:009]: Source is incorrect. Unable to open or validate MSI package E:\sqlncli.msi.
MSI (s) (5C:3C) [06:42:01:009]: Note: 1: 2203 2: E:\sqlncli.msi 3: -2147287038
MSI (s) (5C:3C) [06:42:01:009]: Source is incorrect. Unable to open or validate MSI package E:\sqlncli.msi.
Please insert the disk:

MSI (s) (5C:3C) [06:42:01:025]: Note: 1: 2265 2:  3: -2147287035
MSI (s) (5C:3C) [06:42:01:025]: User policy value 'DisableRollback' is 0
MSI (s) (5C:3C) [06:42:01:025]: Machine policy value 'DisableRollback' is 0
Action ended 6:42:01: InstallFinalize. Return value 2.
MSI (s) (5C:3C) [06:42:01:025]: Note: 1: 2318 2:
 

There we can see an interesting error : “Please insert the disk”.

If we check control panel, I already have SQL Server Native Client and mind you, this was installed when I installed SSMS 18.1.

sql2019-setup-02.jpg

Solution:

By now you would have understood the reason of the blog. If you are seeing messages in various logs, which are shown above, then you can conclude that you are hitting the issue due to preinstalled SSMS. Here is the screenshot from the release notes.

https://docs.microsoft.com/en-us/sql/sql-server/sql-server-version-15-release-notes

 

sql2019-setup-03.jpg

Here are my additional notes.

We have seen this issue earlier when we have SSMS 18.3 already installed and SQL 2019 setup is invoked from ISO mounted as drive. It was combination of few situations.

  • SSMS 18.3 already installed AND
  • SQL Server 2019 Setup was running from a mounted ISO.

We have below workarounds:

  • On existing machines, where SSMS 18.3 or lower is already installed.
    • Uninstall SQL Server 2012 Native Client which got installed with SSMS. Then install SQL Server 2019. OR
    • Instead of running setup from mounted ISO, copy the content of media to a local drive or a network share and start setup.exe from those locations.
  • On new machines, where SSMS is NOT installed.
    • First install SQL Server 2019 and then install SSMS 18.3 OR
    • Install version of SSMS greater than 18.3.1 and then install SQL Server 2019

I hope this blog would help someone find solution without contacting Microsoft Product Support team. Please comment and let me know.

  • Cheers,
  • Balmukund Lakhani
  • Twitter @blakhani
31 Comments
%3CLINGO-SUB%20id%3D%22lingo-sub-998033%22%20slang%3D%22en-US%22%3ESQL%20Server%202019%20Installation%20Error%20-%20An%20error%20occurred%20for%20a%20dependency%20of%20the%20feature%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-998033%22%20slang%3D%22en-US%22%3E%3CP%3EAfter%20release%20of%20SQL%20Server%202019%2C%20one%20of%20our%20customer%20was%20trying%20to%20install%20SQL%20Server%202019%20and%20encountered%20an%20error%20message.%20Since%20I%20was%20able%20to%20reproduce%20the%20issue%20in%20my%20lab%2C%20I%20contacted%20SSMS%20product%20group%20and%20they%20were%20kind%20enough%20to%20fix%20this%20issue%20very%20quickly.%20As%20of%20now%2C%20this%20is%20already%20called%20out%20in%20the%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fsql%2Fsql-server%2Fsql-server-version-15-release-notes%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Erelease%20notes%3C%2FA%3E.%20The%20purpose%20of%20this%20blog%20is%20to%20show%20how%20to%20confirm%20if%20you%20are%20hitting%20the%20same%20issue.%20We%20would%20learn%20how%20to%20look%20at%20various%20log%20file%20and%20what%20are%20the%20error%20messages%20we%20need%20to%20look.%3C%2FP%3E%0A%3CH3%20id%3D%22toc-hId-1657021815%22%20id%3D%22toc-hId-1657053432%22%20id%3D%22toc-hId-1657053432%22%20id%3D%22toc-hId-1657053432%22%20id%3D%22toc-hId-1657053432%22%20id%3D%22toc-hId-1657053432%22%20id%3D%22toc-hId-1657053432%22%20id%3D%22toc-hId-1657053432%22%20id%3D%22toc-hId-1657053432%22%20id%3D%22toc-hId-1657053432%22%20id%3D%22toc-hId-1657053432%22%20id%3D%22toc-hId-1657053432%22%20id%3D%22toc-hId-1657053432%22%20id%3D%22toc-hId-1657053432%22%20id%3D%22toc-hId-1657053432%22%20id%3D%22toc-hId-1657053432%22%20id%3D%22toc-hId-1657053432%22%20id%3D%22toc-hId-1657053432%22%20id%3D%22toc-hId-1657053432%22%20id%3D%22toc-hId-1657053432%22%20id%3D%22toc-hId-1657053432%22%20id%3D%22toc-hId-1657053432%22%20id%3D%22toc-hId-1657053432%22%20id%3D%22toc-hId-1657053432%22%20id%3D%22toc-hId-1657053432%22%20id%3D%22toc-hId-1657053432%22%20id%3D%22toc-hId-1657053432%22%20id%3D%22toc-hId-1657053432%22%20id%3D%22toc-hId-1657053432%22%3EIssue%20Description%3A%3C%2FH3%3E%0A%3CP%3EInstallation%20of%20SQL%20Server%202019%20from%20removable%20media%20fails%20if%20SQL%20Server%20Management%20Studio%2018.3%20or%20earlier%20is%20installed.%20In%20my%20lab%2C%20I%20downloaded%20ISO%20from%20download%20center%20and%20mounted%20it.%20Here%20is%20the%20final%20screen%20shot%20showing%20installation%20failure.%3C%2FP%3E%0A%3CBLOCKQUOTE%3E%0A%3CP%3E%26nbsp%3B%26nbsp%3B%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20804px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F156076iD8E18D663AC7F848%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22sql2019-setup-01.jpg%22%20title%3D%22sql2019-setup-01.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3C%2FBLOCKQUOTE%3E%0A%3CP%3EWhen%20we%20click%20on%20the%20hyperlink%20on%20the%20screen%2C%20it%20opens%20up%20setup%20summary%20file%20which%20has%20this%20information%20about%20failed%20component.%20(Database%20Engine%20Services)%3C%2FP%3E%0A%3CBLOCKQUOTE%3E%0A%3CP%3E%3CFONT%20face%3D%22Consolas%22%20size%3D%223%22%3EDetailed%20results%3A%20%3CBR%20%2F%3E%26nbsp%3B%20Feature%3A%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20Database%20Engine%20Services%20%3CBR%20%2F%3E%26nbsp%3B%20Status%3A%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20Failed%20%3CBR%20%2F%3E%26nbsp%3B%20Reason%20for%20failure%3A%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20An%20error%20occurred%20for%20a%20dependency%20of%20the%20feature%20causing%20the%20setup%20process%20for%20the%20feature%20to%20fail.%20%3CBR%20%2F%3E%26nbsp%3B%20Next%20Step%3A%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20Use%20the%20following%20information%20to%20resolve%20the%20error%2C%20and%20then%20try%20the%20setup%20process%20again.%3C%2FFONT%3E%3C%2FP%3E%0A%3C%2FBLOCKQUOTE%3E%0A%3CP%3ENext%20step%20is%20to%20look%20at%20%3CSTRONG%3E%3CU%3EDetail.txt%20%3C%2FU%3E%3C%2FSTRONG%3Efile%20for%20any%20hint%20about%20dependent%20feature.%20(Search%20for%20%E2%80%9Cat%20Microsoft%E2%80%9D%20keyword)%3C%2FP%3E%0A%3CBLOCKQUOTE%3E%0A%3CP%3E%3CFONT%20face%3D%22Consolas%22%3E%3CSTRONG%3E%3CFONT%20color%3D%22%23ff0000%22%3ETarget%20package%3A%20%22E%3A%5C1033_ENU_LP%5Cx64%5Csetup%5Cx64%5Csqlncli.msi%22%20%3CBR%20%2F%3EInstallPackage%3A%20MsiInstallProduct%20returned%20the%20result%20code%201602.%3C%2FFONT%3E%3C%2FSTRONG%3E%20%3C%2FFONT%3E%3CFONT%20face%3D%22Consolas%22%3E%20%3CBR%20%2F%3ENo%20retry-able%20MSI%20return%20code%20detected.%20%3CBR%20%2F%3EExecuteActionWithRetryHelper.Failed%20actionToExecute%20is%20'Install_sqlncli_Cpu64_Action'%2C%20stack%20trace%26nbsp%3B%26nbsp%3B%26nbsp%3B%20at%20Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.%26lt%3B%26gt%3Bc__DisplayClass2_0.%3CEXECUTEACTIONWITHRETRYHELPER%3Eb__0()%20%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%20at%20Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker%20workerDelegate)%20%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%20at%20Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionWithRetryHelper(WorkflowObject%20metaDb%2C%20ActionKey%20action%2C%20ActionMetadata%20actionMetadata%2C%20TextWriter%20statusStream)%20%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%20at%20Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject%20metabase%2C%20TextWriter%20statusStream)%20%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%20at%20Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject%20metaDb%2C%20TextWriter%20loggingStream)%20%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%20at%20Microsoft.SqlServer.Setup.Chainer.Workflow.ActionEngine.RunActionQueue()%20%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%20at%20Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.%26lt%3B%26gt%3Bc__DisplayClass2_0.%3CEXECUTEACTIONWITHRETRYHELPER%3Eb__0()%20%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%20at%20Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker%20workerDelegate)%20%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%20at%20Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionWithRetryHelper(WorkflowObject%20metaDb%2C%20ActionKey%20action%2C%20ActionMetadata%20actionMetadata%2C%20TextWriter%20statusStream)%20%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%20at%20Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject%20metabase%2C%20TextWriter%20statusStream)%20%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%20at%20Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject%20metaDb%2C%20TextWriter%20loggingStream)%20%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%20at%20Microsoft.SqlServer.Setup.Chainer.Workflow.ActionEngine.RunActionQueue()%20%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%20at%20Microsoft.SqlServer.Setup.Chainer.Workflow.Workflow.RunWorkflow(WorkflowObject%20workflowObject%2C%20HandleInternalException%20exceptionHandler)%20%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%20at%20Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String%20actionId%2C%20TextWriter%20errorStream)%20%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%20at%20Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.%26lt%3B%26gt%3Bc__DisplayClass2_0.%3CEXECUTEACTIONWITHRETRYHELPER%3Eb__0()%20%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%20at%20Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker%20workerDelegate)%20%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%20at%20Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionWithRetryHelper(WorkflowObject%20metaDb%2C%20ActionKey%20action%2C%20ActionMetadata%20actionMetadata%2C%20TextWriter%20statusStream)%20%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%20at%20Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject%20metabase%2C%20TextWriter%20statusStream)%20%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%20at%20Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject%20metaDb%2C%20TextWriter%20loggingStream)%20%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%20at%20Microsoft.SqlServer.Setup.Chainer.Workflow.ActionEngine.RunActionQueue()%20%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%20at%20Microsoft.SqlServer.Setup.Chainer.Workflow.Workflow.RunWorkflow(WorkflowObject%20workflowObject%2C%20HandleInternalException%20exceptionHandler)%20%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%20at%20Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String%20actionId%2C%20TextWriter%20errorStream)%20%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%20at%20Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.%26lt%3B%26gt%3Bc__DisplayClass2_0.%3CEXECUTEACTIONWITHRETRYHELPER%3Eb__0()%20%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%20at%20Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker%20workerDelegate)%20%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%20at%20Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionWithRetryHelper(WorkflowObject%20metaDb%2C%20ActionKey%20action%2C%20ActionMetadata%20actionMetadata%2C%20TextWriter%20statusStream)%20%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%20at%20Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject%20metabase%2C%20TextWriter%20statusStream)%20%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%20at%20Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject%20metaDb%2C%20TextWriter%20loggingStream)%20%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%20at%20Microsoft.SqlServer.Setup.Chainer.Workflow.ActionEngine.RunActionQueue()%20%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%20at%20Microsoft.SqlServer.Setup.Chainer.Workflow.Workflow.RunWorkflow(WorkflowObject%20workflowObject%2C%20HandleInternalException%20exceptionHandler)%20%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%20at%20Microsoft.SqlServer.Chainer.Setup.Setup.RunRequestedWorkflow()%20%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%20at%20Microsoft.SqlServer.Chainer.Setup.Setup.Run(String%5B%5D%20args)%20%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%20at%20Microsoft.SqlServer.Chainer.Setup.Setup.Start(String%5B%5D%20args)%20%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%20at%20Microsoft.SqlServer.Chainer.Setup.Setup.Main()%20%3CBR%20%2F%3E%3CSTRONG%3E%3CFONT%20color%3D%22%23ff0000%22%3EError%3A%20Action%20%22Install_sqlncli_Cpu64_Action%22%20failed%20during%20execution.%20%3CBR%20%2F%3ECompleted%20Action%3A%20Install_sqlncli_Cpu64_Action%2C%20returned%20False%3C%2FFONT%3E%3C%2FSTRONG%3E%3C%2FEXECUTEACTIONWITHRETRYHELPER%3E%3C%2FEXECUTEACTIONWITHRETRYHELPER%3E%3C%2FEXECUTEACTIONWITHRETRYHELPER%3E%3C%2FEXECUTEACTIONWITHRETRYHELPER%3E%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3E%3CFONT%20face%3D%22Consolas%22%20color%3D%22%23ff0000%22%3E%3CEM%3E%E2%80%A6Trimmed%20lines%E2%80%A6%20%3C%2FEM%3E%3C%2FFONT%3E%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3E%3CFONT%20face%3D%22Consolas%22%3EMSI%20(s)%20(5C%3A3C)%20%5B06%3A42%3A01%3A134%5D%3A%20Note%3A%201%3A%201729%20%3CBR%20%2F%3EMSI%20(s)%20(5C%3A3C)%20%5B06%3A42%3A01%3A134%5D%3A%20Product%3A%20Microsoft%20SQL%20Server%202012%20Native%20Client%26nbsp%3B%20--%20Configuration%20failed.%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%3CFONT%20face%3D%22Consolas%22%3EMSI%20(s)%20(5C%3A3C)%20%5B06%3A42%3A01%3A134%5D%3A%20Windows%20Installer%20reconfigured%20the%20product.%20Product%20Name%3A%20Microsoft%20SQL%20Server%202012%20Native%20Client.%20Product%20Version%3A%2011.4.7462.6.%20Product%20Language%3A%201033.%20Manufacturer%3A%20Microsoft%20Corporation.%20Reconfiguration%20success%20or%20error%20status%3A%201602.%3C%2FFONT%3E%3C%2FP%3E%0A%3C%2FBLOCKQUOTE%3E%0A%3CP%3EFrom%20here%20we%20can%20see%20that%20issue%20is%20during%20installation%20of%20SQLNCLI%20(SQL%20Server%20Native%20Client)%20and%20error%20code%20is%201602.%20The%20log%20file%20associate%20is%20%3CSTRONG%3Esqlncli_Cpu64_1%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CBLOCKQUOTE%3E%0A%3CP%3E%3CFONT%20face%3D%22Consolas%22%3EMSI%20(s)%20(5C%3A3C)%20%5B06%3A42%3A01%3A009%5D%3A%20Note%3A%201%3A%202203%202%3A%20E%3A%5Csqlncli.msi%203%3A%20-2147287038%20%3CBR%20%2F%3E%3CFONT%20color%3D%22%23ff0000%22%3E%20MSI%20(s)%20(5C%3A3C)%20%5B06%3A42%3A01%3A009%5D%3A%20Source%20is%20incorrect.%20Unable%20to%20open%20or%20validate%20MSI%20package%20E%3A%5Csqlncli.msi.%20%3CBR%20%2F%3EMSI%20(s)%20(5C%3A3C)%20%5B06%3A42%3A01%3A009%5D%3A%20Note%3A%201%3A%202203%202%3A%20E%3A%5Csqlncli.msi%203%3A%20-2147287038%20%3CBR%20%2F%3EMSI%20(s)%20(5C%3A3C)%20%5B06%3A42%3A01%3A009%5D%3A%20Source%20is%20incorrect.%20Unable%20to%20open%20or%20validate%20MSI%20package%20E%3A%5Csqlncli.msi.%20%3CBR%20%2F%3EPlease%20insert%20the%20disk%3A%3C%2FFONT%3E%20%3CBR%20%2F%3EMSI%20(s)%20(5C%3A3C)%20%5B06%3A42%3A01%3A025%5D%3A%20Note%3A%201%3A%202265%202%3A%26nbsp%3B%203%3A%20-2147287035%20%3CBR%20%2F%3EMSI%20(s)%20(5C%3A3C)%20%5B06%3A42%3A01%3A025%5D%3A%20User%20policy%20value%20'DisableRollback'%20is%200%20%3CBR%20%2F%3EMSI%20(s)%20(5C%3A3C)%20%5B06%3A42%3A01%3A025%5D%3A%20Machine%20policy%20value%20'DisableRollback'%20is%200%20%3CBR%20%2F%3EAction%20ended%206%3A42%3A01%3A%20InstallFinalize.%20Return%20value%202.%20%3CBR%20%2F%3EMSI%20(s)%20(5C%3A3C)%20%5B06%3A42%3A01%3A025%5D%3A%20Note%3A%201%3A%202318%202%3A%3C%2FFONT%3E%26nbsp%3B%3C%2FP%3E%0A%3C%2FBLOCKQUOTE%3E%0A%3CP%3EThere%20we%20can%20see%20an%20interesting%20error%20%3A%20%E2%80%9CPlease%20insert%20the%20disk%E2%80%9D.%3C%2FP%3E%0A%3CP%3EIf%20we%20check%20control%20panel%2C%20I%20already%20have%20SQL%20Server%20Native%20Client%20and%20mind%20you%2C%20this%20was%20installed%20when%20I%20installed%20SSMS%2018.1.%3C%2FP%3E%0A%3CBLOCKQUOTE%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F156077iDDF8E42234E53636%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22sql2019-setup-02.jpg%22%20title%3D%22sql2019-setup-02.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3C%2FBLOCKQUOTE%3E%0A%3CH3%20id%3D%22toc-hId--895135146%22%20id%3D%22toc-hId--895103529%22%20id%3D%22toc-hId--895103529%22%20id%3D%22toc-hId--895103529%22%20id%3D%22toc-hId--895103529%22%20id%3D%22toc-hId--895103529%22%20id%3D%22toc-hId--895103529%22%20id%3D%22toc-hId--895103529%22%20id%3D%22toc-hId--895103529%22%20id%3D%22toc-hId--895103529%22%20id%3D%22toc-hId--895103529%22%20id%3D%22toc-hId--895103529%22%20id%3D%22toc-hId--895103529%22%20id%3D%22toc-hId--895103529%22%20id%3D%22toc-hId--895103529%22%20id%3D%22toc-hId--895103529%22%20id%3D%22toc-hId--895103529%22%20id%3D%22toc-hId--895103529%22%20id%3D%22toc-hId--895103529%22%20id%3D%22toc-hId--895103529%22%20id%3D%22toc-hId--895103529%22%20id%3D%22toc-hId--895103529%22%20id%3D%22toc-hId--895103529%22%20id%3D%22toc-hId--895103529%22%20id%3D%22toc-hId--895103529%22%20id%3D%22toc-hId--895103529%22%20id%3D%22toc-hId--895103529%22%20id%3D%22toc-hId--895103529%22%20id%3D%22toc-hId--895103529%22%3ESolution%3A%3C%2FH3%3E%0A%3CP%3EBy%20now%20you%20would%20have%20understood%20the%20reason%20of%20the%20blog.%20If%20you%20are%20seeing%20messages%20in%20various%20logs%2C%20which%20are%20shown%20above%2C%20then%20you%20can%20conclude%20that%20you%20are%20hitting%20the%20issue%20due%20to%20preinstalled%20SSMS.%20Here%20is%20the%20screenshot%20from%20the%20release%20notes.%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fsql%2Fsql-server%2Fsql-server-version-15-release-notes%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fsql%2Fsql-server%2Fsql-server-version-15-release-notes%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CBLOCKQUOTE%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20862px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F156078iCB2C7F2C5AEE7E1E%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22sql2019-setup-03.jpg%22%20title%3D%22sql2019-setup-03.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3C%2FBLOCKQUOTE%3E%0A%3CP%3EHere%20are%20my%20additional%20notes.%3C%2FP%3E%0A%3CP%3EWe%20have%20seen%20this%20issue%20earlier%20when%20we%20have%20SSMS%2018.3%20already%20installed%20and%20SQL%202019%20setup%20is%20invoked%20from%20ISO%20mounted%20as%20drive.%20It%20was%20combination%20of%20few%20situations.%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3ESSMS%2018.3%20already%20installed%20%3CSTRONG%3E%3CU%3EAND%3C%2FU%3E%3C%2FSTRONG%3E%3C%2FLI%3E%0A%3CLI%3ESQL%20Server%202019%20Setup%20was%20running%20from%20a%20mounted%20ISO.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3EWe%20have%20below%20workarounds%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EOn%20%3CU%3Eexisting%20machines%3C%2FU%3E%2C%20where%20SSMS%2018.3%20or%20lower%20is%20already%20installed.%3C%2FLI%3E%0A%3CUL%3E%0A%3CLI%3EUninstall%20SQL%20Server%202012%20Native%20Client%20which%20got%20installed%20with%20SSMS.%20Then%20install%20SQL%20Server%202019.%20%3CSTRONG%3E%3CU%3EOR%3C%2FU%3E%3C%2FSTRONG%3E%3C%2FLI%3E%0A%3CLI%3EInstead%20of%20running%20setup%20from%20mounted%20ISO%2C%20copy%20the%20content%20of%20media%20to%20a%20local%20drive%20or%20a%20network%20share%20and%20start%20setup.exe%20from%20those%20locations.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CLI%3EOn%20%3CU%3Enew%20machines%3C%2FU%3E%2C%20where%20SSMS%20is%20NOT%20installed.%3C%2FLI%3E%0A%3CUL%3E%0A%3CLI%3EFirst%20install%20SQL%20Server%202019%20and%20then%20install%20SSMS%2018.3%20%3CSTRONG%3E%3CU%3EOR%3C%2FU%3E%3C%2FSTRONG%3E%3C%2FLI%3E%0A%3CLI%3EInstall%20version%20of%20SSMS%20greater%20than%2018.3.1%20and%20then%20install%20SQL%20Server%202019%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3C%2FUL%3E%0A%3CP%3EI%20hope%20this%20blog%20would%20help%20someone%20find%20solution%20without%20contacting%20Microsoft%20Product%20Support%20team.%20Please%20comment%20and%20let%20me%20know.%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3ECheers%2C%3C%2FLI%3E%0A%3CLI%3EBalmukund%20Lakhani%3C%2FLI%3E%0A%3CLI%3ETwitter%20%3CFONT%20style%3D%22font-size%3A%209pt%3B%22%3E%3CA%20style%3D%22href%3A%20'http%3A%2F%2Ftwitter.com%2Fblakhani'%3B%22%20target%3D%22_blank%22%3E%3CFONT%20color%3D%22%230000ff%22%3E%3CU%3E%40blakhani%3C%2FU%3E%3C%2FFONT%3E%3C%2FA%3E%3C%2FFONT%3E%3C%2FLI%3E%0A%3C%2FUL%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-998033%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20804px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F156079i960244E40C7AACD9%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22sql2019-setup-01.jpg%22%20title%3D%22sql2019-setup-01.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-998033%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3Esetup%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESQL%202019%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ETroubleshooting%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1016110%22%20slang%3D%22en-US%22%3ERe%3A%20SQL%20Server%202019%20Installation%20Error%20-%20An%20error%20occurred%20for%20a%20dependency%20of%20the%20feature%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1016110%22%20slang%3D%22en-US%22%3E%3CP%3EI%20was%20running%20into%20the%20same%20issue%20as%20you%20were%20with%20that%20cryptic%20error%20message%20and%20really%20no%20details%20when%20you%20look%20at%20the%20log%20it%20references.%26nbsp%3B%20I%20did%20have%20SSMS%20installed%20from%20before%20(went%20from%20pre%2018%20versions%20all%20the%20way%20to%20the%20current%20one).%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EThe%20solution%20that%20I%20went%20with%20was%20copying%20the%20ISO%20to%20a%20local%20drive%20and%20running%20it%20from%20there%2C%20then%20it%20worked%20without%20any%20problems.%26nbsp%3B%20I%20was%20worried%20about%20removing%20the%20SQL%20Server%202012%20Native%20Client%20to%20figure%20out%20if%20that%20broke%20anything.%26nbsp%3B%20It%20also%20works%20if%20you%20partially%20were%20able%20to%20upgrade%20certain%20parts%20of%20SQL%20Server%20(like%20the%20shared%20components)%20and%20not%20tried%20to%20roll%20it%20back%20to%20the%20prior%20version%20when%20encountering%20the%20error%20the%20first%20time.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThankfully%20your%20post%20was%20there%20to%20help%20me%20out%20when%20my%20brain%20failed%20to%20make%20the%20connection%20with%20the%20SSMS%20issue%20(since%20I%20was%20already%20running%2018.4).%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1041249%22%20slang%3D%22en-US%22%3ERe%3A%20SQL%20Server%202019%20Installation%20Error%20-%20An%20error%20occurred%20for%20a%20dependency%20of%20the%20feature%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1041249%22%20slang%3D%22en-US%22%3E%3CP%3EIt's%20perfect%20-%20it's%20so%20useful%20that%20this%20must%20be%20converted%20into%20a%20KB%20article!%3C%2FP%3E%3CP%3EAlso%2C%20I%20understands%20that%20separating%20SSMS%20from%20core%20SQL%20Server%20installer%20provides%20flexibility%2C%20but%20frequent%20releases%20that%20block%20upgrades%20is%20not%20a%20good%20thing.%20Trust%20the%20SSMS%20team%20has%20taken%20a%20note%20of%20this%20and%20will%20be%20addressing%20the%20same.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1041400%22%20slang%3D%22en-US%22%3ERe%3A%20SQL%20Server%202019%20Installation%20Error%20-%20An%20error%20occurred%20for%20a%20dependency%20of%20the%20feature%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1041400%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F474350%22%20target%3D%22_blank%22%3E%40sqltwins%3C%2FA%3E%26nbsp%3B-%20Sure.%20Thanks%20for%20your%20comment.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1063563%22%20slang%3D%22en-US%22%3ERe%3A%20SQL%20Server%202019%20Installation%20Error%20-%20An%20error%20occurred%20for%20a%20dependency%20of%20the%20feature%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1063563%22%20slang%3D%22en-US%22%3E%3CP%3EThank%20you%20so%20much!%26nbsp%3B%20I%20can't%20imagine%20how%20many%20more%20hours%20I%20would've%20spent%20trying%20to%20figure%20the%20error%20out.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1109344%22%20slang%3D%22en-US%22%3ERe%3A%20SQL%20Server%202019%20Installation%20Error%20-%20An%20error%20occurred%20for%20a%20dependency%20of%20the%20feature%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1109344%22%20slang%3D%22en-US%22%3E%3CP%3EThanks.%20This%20indeed%20should%20converted%20to%20a%20KB%20article.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1198160%22%20slang%3D%22en-US%22%3ERe%3A%20SQL%20Server%202019%20Installation%20Error%20-%20An%20error%20occurred%20for%20a%20dependency%20of%20the%20feature%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1198160%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20the%20same%20issue%2C%20but%20in%20my%20case%20the%20solution%20is%20not%20working.%20I%20had%20an%20Enterprise%202016%20instance%20and%20trying%20an%20upgrade%20to%202019.%20I%20had%20SSMS%2018.4%20installed%20on%20the%20server.%20When%20my%20upgrade%20failed%20with%20the%20mentioned%20error%20(%3CSPAN%20class%3D%22lia-message-unread%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fsql-server-support%2Fsql-server-2019-installation-error-an-error-occurred-for-a%2Fba-p%2F998033%22%20target%3D%22_blank%22%3EAn%20error%20occurred%20for%20a%20dependency%20of%20the%20feature%3C%2FA%3E)%2C%20i%20followed%20your%20instructions%20and%20uninstalled%26nbsp%3B%3CSPAN%3ESQL%20Server%202012%20Native%20Client%2C%20followed%20by%20a%20restart%20on%20the%20machine.%20Tried%20again%20from%20command%20prompt%26nbsp%3B%20to%20run%26nbsp%3Bsetup%20%2Faction%3Drepair%20%2Finstancename%3DMSSQLSERVER%20and%20got%20another%20error%3A%26nbsp%3B%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-message-unread%22%3EOverall%20summary%3A%3CBR%20%2F%3EFinal%20result%3A%20Failed%3A%20see%20details%20below%3CBR%20%2F%3EExit%20code%20(Decimal)%3A%20-2146232828%3CBR%20%2F%3EExit%20facility%20code%3A%2019%3CBR%20%2F%3EExit%20error%20code%3A%205636%3CBR%20%2F%3EExit%20message%3A%20Exception%20has%20been%20thrown%20by%20the%20target%20of%20an%20invocation.%3CBR%20%2F%3EStart%20time%3A%202020-02-27%2011%3A18%3A27%3CBR%20%2F%3EEnd%20time%3A%202020-02-27%2011%3A19%3A36%3CBR%20%2F%3ERequested%20action%3A%20Repair%3CBR%20%2F%3EException%20help%20link%3A%20%3CA%20href%3D%22https%3A%2F%2Fgo.microsoft.com%2Ffwlink%3FLinkId%3D20476%26amp%3BProdName%3DMicrosoft%2BSQL%2BServer%26amp%3BEvtsrc%3Dsetup.rll%26amp%3BEvtID%3D50000%26amp%3BProdVer%3D15.0.2000.5%26amp%3BEvtType%3D0x55494D32%25400x11428655%26amp%3BEvtType%3D0x55494D32%25400x11428655%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fgo.microsoft.com%2Ffwlink%3FLinkId%3D20476%26amp%3BProdName%3DMicrosoft%2BSQL%2BServer%26amp%3BEvtsrc%3Dsetup.rll%26amp%3BEvtID%3D50000%26amp%3BProdVer%3D15.0.2000.5%26amp%3BEvtType%3D0x55494D32%25400x11428655%26amp%3BEvtType%3D0x55494D32%25400x11428655%3C%2FA%3E%3CBR%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20entire%20message%20is%3A%3C%2FP%3E%3CP%3EConfiguration%20file%3A%20C%3A%5CProgram%20Files%5CMicrosoft%20SQL%20Server%5C150%5CSetup%20Bootstrap%5CLog%5C20200227_111827%5CConfigurationFile.ini%3C%2FP%3E%3CP%3ERules%20with%20failures%20or%20warnings%3A%3C%2FP%3E%3CP%3ERules%20report%20file%3A%20C%3A%5CProgram%20Files%5CMicrosoft%20SQL%20Server%5C150%5CSetup%20Bootstrap%5CLog%5C20200227_111827%5CSystemConfigurationCheck_Report.htm%3C%2FP%3E%3CP%3EException%20summary%3A%3CBR%20%2F%3EThe%20following%20is%20an%20exception%20stack%20listing%20the%20exceptions%20in%20outermost%20to%20innermost%20order%3CBR%20%2F%3EInner%20exceptions%20are%20being%20indented%3C%2FP%3E%3CP%3EException%20type%3A%20System.Reflection.TargetInvocationException%3CBR%20%2F%3EMessage%3A%3CBR%20%2F%3EException%20has%20been%20thrown%20by%20the%20target%20of%20an%20invocation.%3CBR%20%2F%3EHResult%20%3A%200x80131604%3CBR%20%2F%3EData%3A%3CBR%20%2F%3EHelpLink.EvtType%20%3D%200x55494D32%400x11428655%3CBR%20%2F%3EDisableWatson%20%3D%20true%3CBR%20%2F%3EStack%3A%3CBR%20%2F%3Eat%20System.RuntimeMethodHandle.InvokeMethod(Object%20target%2C%20Object%5B%5D%20arguments%2C%20Signature%20sig%2C%20Boolean%20constructor)%3CBR%20%2F%3Eat%20System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object%20obj%2C%20Object%5B%5D%20parameters%2C%20Object%5B%5D%20arguments)%3CBR%20%2F%3Eat%20System.Reflection.RuntimeMethodInfo.Invoke(Object%20obj%2C%20BindingFlags%20invokeAttr%2C%20Binder%20binder%2C%20Object%5B%5D%20parameters%2C%20CultureInfo%20culture)%3CBR%20%2F%3Eat%20Microsoft.SqlServer.Configuration.SetupExtension.ObjectDatastoreIntegration.SetInputSettingInputPropertiesOnObject(Object%20pendingObject%2C%20TextWriter%20loggingStream)%3CBR%20%2F%3Eat%20Microsoft.SqlServer.Configuration.SetupExtension.ActionDatastoreIntegration.SetPropertiesOnRunningAction(ActionKey%20key%2C%20TextWriter%20loggingStream)%3CBR%20%2F%3Eat%20Microsoft.SqlServer.Setup.Chainer.Workflow.ActionMetadata.NotifyInExecution(ActionKey%20actionRunning%2C%20TextWriter%20loggingStream)%3CBR%20%2F%3Eat%20Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker%20workerDelegate)%3CBR%20%2F%3EInner%20exception%20type%3A%20System.ArgumentNullException%3CBR%20%2F%3EMessage%3A%3CBR%20%2F%3EValue%20cannot%20be%20null.%3CBR%20%2F%3EParameter%20name%3A%20InstallMediaPath%3CBR%20%2F%3EHResult%20%3A%200x80004003%3CBR%20%2F%3EStack%3A%3CBR%20%2F%3Eat%20Microsoft.SqlServer.Configuration.MsiExtension.InitializeMsiExtension.set_InstallMediaPath(String%20value)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-message-unread%22%3EStill%20struggling%20with%20this%20error..%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1198164%22%20slang%3D%22en-US%22%3ERe%3A%20SQL%20Server%202019%20Installation%20Error%20-%20An%20error%20occurred%20for%20a%20dependency%20of%20the%20feature%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1198164%22%20slang%3D%22en-US%22%3E%3CP%3EForgot%20to%20mention%2C%20i%20did%20also%20tried%20and%20uninstalled%20SSMS%2018.4%20from%20the%20machine.%3C%2FP%3E%3CP%3EHere%20is%20the%20screenshot%20with%20the%20error%20when%20trying%20to%20repair%3A%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22gabrielasarbu_0-1582804362751.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F173862i8344DC54421C8D3F%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20title%3D%22gabrielasarbu_0-1582804362751.png%22%20alt%3D%22gabrielasarbu_0-1582804362751.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1198204%22%20slang%3D%22en-US%22%3ERe%3A%20SQL%20Server%202019%20Installation%20Error%20-%20An%20error%20occurred%20for%20a%20dependency%20of%20the%20feature%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1198204%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20is%20NOT%20the%20same%20error.%20Message%20which%20I%20see%20is%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSPAN%3EValue%20cannot%20be%20null.%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3EParameter%20name%3A%20InstallMediaPath%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1250297%22%20slang%3D%22en-US%22%3ERe%3A%20SQL%20Server%202019%20Installation%20Error%20-%20An%20error%20occurred%20for%20a%20dependency%20of%20the%20feature%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1250297%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20for%20this%20article!%20Very%20helpful%20for%20SSAS%20also!%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1312717%22%20slang%3D%22en-US%22%3ERe%3A%20SQL%20Server%202019%20Installation%20Error%20-%20An%20error%20occurred%20for%20a%20dependency%20of%20the%20feature%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1312717%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F461458%22%20target%3D%22_blank%22%3E%40jnikaido%3C%2FA%3E%26nbsp%3BYour%20solution%20worked%20for%20me.%20My%20situation%20was%20existing%20SSMS%2018.4%2C%20error%20message%20was%20enigmatic%20%22use%20information%20not%20present%20to%20correct%20unknown%20scenario%22...%20and%20copying%20ISO%20to%20drive%2C%20and%20installing%20off%20the%20drive%2C%20solved%20%22it%22.%20Thanks!%20How%20did%20you%20even%20come%20up%20with%20that%20totally%20illogical%20move%20to%20correct%20it%3F%20What%20a%20leap%20of%20cognitive%20functioning%20-%20%22its%20failing%2C%20maybe%20running%20from%20elsewhere%20won't%20fail%3F%20-%20lets%20try%20it!%22%20-%20way%20beyond%20my%20meager%20click%20skills.%20*bow*%20to%20the%20master!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1312788%22%20slang%3D%22en-US%22%3ERe%3A%20SQL%20Server%202019%20Installation%20Error%20-%20An%20error%20occurred%20for%20a%20dependency%20of%20the%20feature%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1312788%22%20slang%3D%22en-US%22%3E%3CP%3EI%20think%20that's%20what%20I%20have%20documented.%3C%2FP%3E%0A%3CP%3E%22%3CSPAN%3EInstead%20of%20running%20setup%20from%20mounted%20ISO%2C%20copy%20the%20content%20of%20media%20to%20a%20local%20drive%20or%20a%20network%20share%20and%20start%20setup.exe%20from%20those%20locations.%22%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1313164%22%20slang%3D%22en-US%22%3ERe%3A%20SQL%20Server%202019%20Installation%20Error%20-%20An%20error%20occurred%20for%20a%20dependency%20of%20the%20feature%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1313164%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Balmukund%20Lakhani%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESorry-%20did%20not%20see%20that%20-%20as%20I%20glossed%20over%20the%20bullet%20list%20due%20to%20not%20having%20SSMS%2018.3%20installed.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20guess%20this%20means%20that%20its%20applicable%20to%20all%20machines%2C%20not%2018.3%20and%20below.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMicrosoft%20packaged%20an%20installer%20for%20their%20latest%20SQL%20Server%20version%2C%3C%2FP%3E%3CP%3Ethat%20is%20broken%20for%20all%20machines%26nbsp%3Bfor%20people%20who%20have%20their%20product%20for%20managing%20SQL%20Server%20installations%20(SSMS)%20installed.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20again%20for%20the%20solution%20nonetheless%20-%20solved%20a%20frustrating%20issue%20for%20me.%20*bow*%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1508662%22%20slang%3D%22en-US%22%3ERe%3A%20SQL%20Server%202019%20Installation%20Error%20-%20An%20error%20occurred%20for%20a%20dependency%20of%20the%20feature%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1508662%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22elzahirova_0-1594210908688.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F204090iED3275FEE436D68A%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20title%3D%22elzahirova_0-1594210908688.png%22%20alt%3D%22elzahirova_0-1594210908688.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3EHello.%20I%20couldn't%20find%20a%20way%20to%20solve%20this%20problem.%20Can%20you%20help%20me%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1623795%22%20slang%3D%22en-US%22%3ERe%3A%20SQL%20Server%202019%20Installation%20Error%20-%20An%20error%20occurred%20for%20a%20dependency%20of%20the%20feature%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1623795%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22tyous_88_0-1598903709497.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F215680i374299DD98DF054B%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20title%3D%22tyous_88_0-1598903709497.png%22%20alt%3D%22tyous_88_0-1598903709497.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3EDoes%20anyone%20know%20how%20to%20resolve%20this%20issue%3F%20I%20have%20been%20searching%20for%20solutions%20all%20night%2C%20and%20I%20just%20really%20need%20to%20install%20this%20for%20my%20college%20course.%20My%20errors%20state%20%22The%20Windows%20Management%20Instrumentation%20service%20cannot%20be%20started%22%20and%20%22This%20machine%20is%20clustered%2C%20but%20the%20cluster%20is%20not%20online%20or%20cannot%20be%20accessed%20from%20one%20of%20its%20nodes%22.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1623799%22%20slang%3D%22en-US%22%3ERe%3A%20SQL%20Server%202019%20Installation%20Error%20-%20An%20error%20occurred%20for%20a%20dependency%20of%20the%20feature%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1623799%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F777310%22%20target%3D%22_blank%22%3E%40tyous_88%3C%2FA%3E%3CBR%20%2F%3E%26nbsp%3BThis%20would%20need%20investigation%20of%20setup%20logs.%20Would%20you%20be%20able%20to%20share%20them%20to%20some%20public%20file%20sharing%20site%20and%20provide%20link%3F%20It%20would%20be%20better%20to%20open%20a%20thread%20on%20forums%20so%20that%20it%20can%20be%20tracked.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1623852%22%20slang%3D%22en-US%22%3ERe%3A%20SQL%20Server%202019%20Installation%20Error%20-%20An%20error%20occurred%20for%20a%20dependency%20of%20the%20feature%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1623852%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F83971%22%20target%3D%22_blank%22%3E%40Balmukund%20Lakhani%3C%2FA%3E%26nbsp%3B%20Thanks%20for%20your%20hel%3CSPAN%3Ep!%20I%20did%20create%20a%20new%20forum.%20Yes%2C%20I%20am%20willing%20to%20share.%20But%20I%20don't%20really%20know%20the%26nbsp%3Bprocess%20for%20doing%20this.%20Let%20me%20do%20some%20research.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1623857%22%20slang%3D%22en-US%22%3ERe%3A%20SQL%20Server%202019%20Installation%20Error%20-%20An%20error%20occurred%20for%20a%20dependency%20of%20the%20feature%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1623857%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F777310%22%20target%3D%22_blank%22%3E%40tyous_88%3C%2FA%3E%26nbsp%3B-%20Thanks.%20Please%20share%20the%20link%20of%20forum%20thread.%20Let%20me%20see%20what%20can%20be%20done.%20Feel%20free%20to%20send%20me%20an%20email%20-%20blakhani%20at%20microsoft%20dot%20com.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1624151%22%20slang%3D%22en-US%22%3ERe%3A%20SQL%20Server%202019%20Installation%20Error%20-%20An%20error%20occurred%20for%20a%20dependency%20of%20the%20feature%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1624151%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F83971%22%20target%3D%22_blank%22%3E%40Balmukund%20Lakhani%3C%2FA%3E%26nbsp%3B%20Here%20is%20the%20link%20to%20my%20new%20forum%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fsql-server%2Fsql-server-2019-installation-issues-wmi%2Fm-p%2F1623830%2Fhighlight%2Ffalse%23M732%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fsql-server%2Fsql-server-2019-installation-issues-wmi%2Fm-p%2F1623830%2Fhighlight%2Ffalse%23M732%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1687011%22%20slang%3D%22en-US%22%3ERe%3A%20SQL%20Server%202019%20Installation%20Error%20-%20An%20error%20occurred%20for%20a%20dependency%20of%20the%20feature%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1687011%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22SQL%20Server%20Installer%2009_19_20%201_45_02%20PM.png%22%20style%3D%22width%3A%20845px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F219813i876ADBEBEF2A590A%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%22SQL%20Server%20Installer%2009_19_20%201_45_02%20PM.png%22%20alt%3D%22SQL%20Server%20Installer%2009_19_20%201_45_02%20PM.png%22%20%2F%3E%3C%2FSPAN%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20How%20do%20I%20solve%20This%20issue%20%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1768729%22%20slang%3D%22de-DE%22%3ESubject%3A%20SQL%20Server%202019%20Installation%20Error%20-%20An%20error%20occurred%20for%20a%20dependency%20of%20the%20feature%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1768729%22%20slang%3D%22de-DE%22%3E%3CP%3EI%20had%20the%20same%20problem%3C%2FP%3E%3CP%3EI%20got%20the%20error%20message%20in%20English%2C%20when%20I%20wanted%20to%20upgrade%20SQL%20Server%202017%20Express%20to%20SQL%20Server%202019%20Standard%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3EStatus%3A%20Error.%20Detailed%20information%20can%20be%20found%20in%20the%20logs%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%3CSTRONG%3EReason%20for%20failure%3A%20Because%20a%20dependency%20of%20the%20function%20caused%20an%20error%2C%20the%20setup%20operation%20for%20the%20function%20was%20not%20successful.%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%3CSTRONG%3ENext%20Step%3A%20Fix%20the%20error%20using%20the%20following%20information%20and%20try%20the%20setup%20process%20again.%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20solution%20of%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F461458%22%20target%3D%22_blank%22%3E%40jnikaido%3C%2FA%3E%20helped%3A%20I%20had%20to%20copy%20the%20contents%20of%20the%20virtual%20ISO%20file%20somewhere%20to%20the%20C%3A%20drive%20and%20ran%20setup.exe%20from%20there.%3CBR%20%2F%3EThis%20is%20definitively%20something%20Microsoft%20should%20fix.%20I%20mean%2C%20the%20ISO%20is%20the%20official%20file%20and%20thousands%20of%20people%20will%20try%20to%20run%20setup.exe%20out%20of%20the%20ISO%3F!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1895575%22%20slang%3D%22en-US%22%3ERe%3A%20SQL%20Server%202019%20Installation%20Error%20-%20An%20error%20occurred%20for%20a%20dependency%20of%20the%20feature%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1895575%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F827951%22%20target%3D%22_blank%22%3E%40danielmarschall%3C%2FA%3E%26nbsp%3B-%20This%20was%20an%20issue%20with%20SSMS%20installation%20which%20has%20been%20fixed%20in%20later%20version.%20If%20you%20have%20latest%20version%20of%20SSMS%2C%20this%20should%20not%20cause%20trouble.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2200682%22%20slang%3D%22en-US%22%3ERe%3A%20SQL%20Server%202019%20Installation%20Error%20-%20An%20error%20occurred%20for%20a%20dependency%20of%20the%20feature%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2200682%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20trying%20to%20install%20mssql%20server%202019%20developer%20version%20and%20there%20was%20error%20popping.%20Please%20help%20me.%20note%3A%20I%20have%20not%20installed%20SSMS%20yet.%26nbsp%3B%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22Screenshot%202021-03-10%20155751.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F262608iCA842A8096778463%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22Screenshot%202021-03-10%20155751.png%22%20alt%3D%22Screenshot%202021-03-10%20155751.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2201666%22%20slang%3D%22en-US%22%3ERe%3A%20SQL%20Server%202019%20Installation%20Error%20-%20An%20error%20occurred%20for%20a%20dependency%20of%20the%20feature%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2201666%22%20slang%3D%22en-US%22%3E%3CP%3ERestart%20your%20computer%20and%20run%20Setup%20again.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Version history
Last update:
‎Dec 02 2019 12:32 AM
Updated by: