SQL Server 2000 is not supported on Windows Server 2003 Terminal Server application server (327270)
The information in this article applies to:
- Microsoft SQL Server 2000 Developer Edition
- Microsoft SQL Server 2000 Enterprise Edition
- Microsoft SQL Server 2005 Developer Edition
- Microsoft SQL Server 2005 Standard Edition
- Microsoft SQL Server 2005 Enterprise Edition
This article was previously published under Q327270 SUMMARYMicrosoft SQL Server does not support the installation or
use of SQL Server Failover Clustering on Microsoft Windows Server 2003-based
server clusters where the Windows Server 2003-based server clusters have
Terminal Server installed on the cluster. This configuration was known as
Application Mode in Microsoft Windows 2000. However, SQL Server 2000 instance
installation is supported as a stand-alone instance for Windows Server 2003 Terminal
Services Mode (Application Mode).
For Windows Server 2003 Terminal Server
Remote Desktop for Administration Mode, SQL Server 2000 installation is fully
supported as both a clustered instance and a stand-alone instance.
Note SQL Server 2005 Server Cluster instances are currently not supported on Windows Server 2003 Terminal Server Server Cluster installations.MORE INFORMATION Terminal Server provides remote computers with access to
Windows-based programs running on Windows Server 2003 Standard Server, Windows
Server 2003 Enterprise Server, or Windows Server 2003 Datacenter Server. With
Terminal Server, you can provide a single point of installation that gives
multiple users access to any computer that is running one of the operating
systems listed earlier. Users can run programs, save files, and use network
resources, all from a remote location as if these resources were installed on
their own computers. This functionality is now available on server clusters in
Windows Server 2003. Remote Desktop for Administration is another
part of the Terminal Services technology that is offered in Windows Server
2003. You can enable remote administration of servers with Remote Desktop for
Administration on any computer that is running the Windows Server 2003 family
of products, even if Terminal Server is not installed. Note In Microsoft Windows 2000 Server, the Terminal Server component
is named Terminal Services in Application Server mode. In Microsoft Windows
2000 Server, the Remote Desktop for Administration component is named Terminal
Services in Remote Administration mode. To determine if the Terminal
Server service is running on the computer, follow these steps: - Open Control Panel.
- Double-click Add/Remove Programs.
- On the left side of the screen, double click
Add/Remove Windows Components.
- Under Components, scroll down the list
until you find Terminal Server. If Terminal Server is not selected, the service
that is running is the "Remote Desktop" service and you can continue with your
SQL Server installation. If Terminal Server is selected, you must clear the
check box to remove the Terminal Server service in the application before you
continue with the SQL Server installation.
For more information about the supportability of SQL Server failover
clusters on Windows Server 2003 clusters, click the following article number to view the article in the Microsoft Knowledge Base:
313037
Upgrading SQL Server clusters to Windows Server 2003
Example log behavior if Terminal Server is installedIf Windows Server 2003 Terminal Server is installed and you try to
install SQL Server, no log files exist in the %windir% folder. However, the log
files are stored in the %userprofile%\Windows folder. When you check the log
files and you compare the log to the system variables, you see results that are
similar to the following in the Sqlstp.log file: 19:41:44 Begin Action: SetupInstall
19:41:44 Reading Software\Microsoft\Windows\CurrentVersion\CommonFilesDir
...
19:41:44 CommonFilesDir=C:\Program Files\Common Files
19:41:44 Windows Directory=C:\Documents and Settings\<user_name>\WINDOWS\
19:41:44 Program Files=C:\Program Files\
19:41:44 TEMPDIR=C:\DOCUME~1\<user_nam~1>\LOCALS~1\Temp\1\
From system variables - USERPROFILE=C:\Documents and Settings\<user_name> windir=C:\WINDOWS Note This example does not apply to servers that are running Windows 2003 Service Pack 1 (SP1) or a later version. We recommend that you check manually for a Windows directory in the %USERPROFILE% directory.
Modification Type: | Minor | Last Reviewed: | 8/4/2006 |
---|
Keywords: | kbinfo KB327270 kbAudDeveloper kbAudITPRO |
---|
|