
The log file associate is sqlncli_Cpu64_1 Reconfiguration success or error status: 1602.įrom here we can see that issue is during installation of SQLNCLI (SQL Server Native Client) and error code is 1602. Product Name: Microsoft SQL Server 2012 Native Client. MSI (s) (5C:3C) : Windows Installer reconfigured the product.

MSI (s) (5C:3C) : Product: Microsoft SQL Server 2012 Native Client - Configuration failed. InstallPackage: MsiInstallProduct returned the result code 1602.ĮxecuteActionWithRetryHelper.Failed actionToExecute is 'Install_sqlncli_Cpu64_Action', stack trace at ._Displa圜lass2_0.b_0()Īt .(ActionWorker workerDelegate)Īt .(WorkflowObject metaDb, ActionKey action, ActionMetadata actionMetadata, TextWriter statusStream)Īt .(WorkflowObject metabase, TextWriter statusStream)Īt .(WorkflowObject metaDb, TextWriter loggingStream)Īt .()Īt ._Displa圜lass2_0.b_0()Īt .(WorkflowObject workflowObject, HandleInternalException exceptionHandler)Īt .Action.Execute(String actionId, TextWriter errorStream)Īt .Setup.RunRequestedWorkflow()Īt .Setup.Run(String args)Īt .Setup.Start(String args)Īt .Setup.Main()Įrror: Action "Install_sqlncli_Cpu64_Action" failed during execution.Ĭompleted Action: Install_sqlncli_Cpu64_Action, returned False Next step is to look at Detail.txt file for any hint about dependent feature. Next Step: Use the following information to resolve the error, and then try the setup process again. Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail. When we click on the hyperlink on the screen, it opens up setup summary file which has this information about failed component. Here is the final screen shot showing installation failure. In my lab, I downloaded ISO from download center and mounted it. Installation of SQL Server 2019 from removable media fails if SQL Server Management Studio 18.3 or earlier is installed. We would learn how to look at various log file and what are the error messages we need to look.


The purpose of this blog is to show how to confirm if you are hitting the same issue. As of now, this is already called out in the release notes. 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. After release of SQL Server 2019, one of our customer was trying to install SQL Server 2019 and encountered an error message.
