Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. SQL Server 2008 setup may fail with "Setup Failure in SetupActionName: cusetfeatureinstallstateaction " error message

SQL Server 2008 setup may fail with "Setup Failure in SetupActionName: cusetfeatureinstallstateaction " error message

Source: Microsoft Support

↑ Back to the top

RAPID PUBLISHING

RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.

↑ Back to the top

Symptom



SQL Server 2008 setup may fail with the following error message




Setup Failure in SetupActionName: cusetfeatureinstallstateaction.




Additionally, users will be presented with an exception similar to the following:




Exception type: Microsoft.SqlServer.Chainer.Infrastructure.ChainerInvalidOperationException


Message: Unable to open Windows Installer file [folder]\setup\sql_engine_core_inst_msi\sql_engine_core_inst.msi'.




Note: The installer file in the exception message(s) will vary depending on which file(s) met the relevant error condition.


 

↑ Back to the top

Cause



The files mentioned in the error message are inaccessible for some reason. The following are the most common reasons:


 


1.     An anti-virus software program may have a lock on the installer file(s) to scan the file(s) for viruses.


 


2.     The files on the media (either the hard disk or DVD media) are corrupt.


 

↑ Back to the top

Resolution



To resolve this issue, use one of the following options:


 


Warning The first workaround may make your computer or your network more vulnerable to attack by malicious users or by malicious software such as viruses. We do not recommend this workaround but are providing this information so that you can implement this workaround at your own discretion. Use this workaround at your own risk.


 


Option 1:  On the system where SQL is being installed, temporarily stop or disable any antivirus software, and other applications that may place locks on the SQL installation files. You can use tools like Process explorer or Handle to get information about which handles and DLLs processes have opened or loaded.


 


Option 2:  Recopy the files from original media to a reliable destination.

↑ Back to the top

More Information


·          SQL Server Troubleshooting and Support

 

↑ Back to the top

DISCLAIMER

MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, RELIABILITY OR ACCURACY OF THE INFORMATION CONTAINED IN THE DOCUMENTS AND RELATED GRAPHICS PUBLISHED ON THIS WEBSITE (THE “MATERIALS”) FOR ANY PURPOSE. THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE.


TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.

↑ Back to the top

Keywords: kb, kbnomt, kbrapidpub, kbnoloc

↑ Back to the top

Article Info
Article ID : 970667
Revision : 5
Created on : 8/19/2020
Published on : 8/20/2020
Exists online : False
Views : 70