You are currently offline, waiting for your internet to reconnect

Error message when you install SQL Server cluster on Windows Server 2003-based computers where Terminal Services is installed: "Setup failed to perform required operations on the cluster nodes"

Support for Windows Server 2003 ended on July 14, 2015

Microsoft ended support for Windows Server 2003 on July 14, 2015. This change has affected your software updates and security options. Learn what this means for you and how to stay protected.

Extended support for SQL Server 2005 ended on April 12, 2016

If you are still running SQL Server 2005, you will no longer receive security updates and technical support. We recommend upgrading to SQL Server 2014 and Azure SQL Database to achieve breakthrough performance, maintain security and compliance, and optimize your data platform infrastructure. Learn more about the options for upgrading from SQL Server 2005 to a supported version here.

This article was previously published under Q301520
This article has been archived. It is offered "as is" and will no longer be updated.
You cannot install SQL Server clusteron a computer that runs Microsoft Windows Server 2003 and that has Terminal Server installed on a server cluster. After you provide all the correct information to SQL Server Setup program (and provide the VirtualServer name, IP address and licensing information), you may receive the following error message:

Setup failed to perform required operations on the cluster nodes.

You may also receive one of the following error messages in the SQLSTP or the SQLCLST log files:
Process Exit Code: (2) The system cannot find the file specified.
13:28:59 C:\WINDOWS\TEMP\SqlSetup\Bin\remsetup.exe C:\Documents and Settings\user name\WINDOWS\remsetup.ini
13:28:59 Process Exit Code: (-1) 13:28:59 Begin Action : GetRemsetupRetCode
13:28:59 Installation return status on HQUCHBI040 : -1
13:28:59 Installation return status on HQUCHBI041 : -1
The Windows Server 2003-based computer that has Terminal Server installed causes the SQL Server Setup to try to copy files to the Windows folder of the user who is currently logged on instead of the Windows (%SystemRoot%) folder. If the administrator is logged on, the path is similar to the following path:
C:\Documents and Settings\Administrator\Windows
Clustered instances of SQL Server 2000 or of SQL Server 2005 are not supported for installation on Windows Server 2003 if the Terminal Server component is installed. Although "Remote Desktop" is a related techonology, its configuration and use do not usually affect SQL Server. Only the Terminal Server component (installed through the Add/Remove Programs tool in Control Panel) prevents SQL Server from being installed.

For more information about SQL Server cluster and Windows Server 2003 Terminal Server Application Server operating systems, see the following article in the Microsoft Knowledge Base:
327270 SQL Server 2000 Is Not Supported on Windows Server 2003 Terminal Server Application Server

Note The preceding information does not apply to the use of a Windows 2003 terminal session for remote administration. SQL Server Setup is fully supported when you are running Setup from a remote administration terminal session. Windows Server 2003 does not require the installation of Terminal Services from Add/Remove Programs for remote administration. Remote administration can be enabled on the Remote tab of the System tool in Control Panel.

For additional information about Terminal Services and Remote Desktop, click the following article number to view the article in the Microsoft Knowledge Base:
282936 Terminal Server Options Are Not Listed in Add/Remove Programs In Control Panel
mscs sql2000 shiloh terminalsrv appmode WTS

Article ID: 301520 - Last Review: 12/06/2015 03:23:26 - Revision: 12.7

Microsoft Windows Server 2003, Enterprise Edition (32-bit x86), Microsoft Windows Server 2003, Datacenter Edition (32-bit x86), Microsoft SQL Server 2000 Enterprise Edition, Microsoft SQL Server 2000 Developer Edition, Microsoft SQL Server 2005 Standard Edition, Microsoft SQL Server 2005 Developer Edition, Microsoft SQL Server 2005 Enterprise Edition

  • kbnosurvey kbarchive kbsql2005cluster kbbug kberrmsg kbsetup KB301520