//  home   //  advanced search   //  news   //  categories   //  sql build chart   //  downloads   //  statistics
 ASP FAQ 
Home
ASP FAQ Tutorials

   8000XXXX Errors
   ASP.NET 2.0
   Classic ASP 1.0
   Databases
      Access DB & ADO
      General SQL Server & Access Articles
      MySQL
      Other Articles
      Schema Tutorials
      Sql Server 2000
      Sql Server 2005
   General Concepts
   Search Engine Optimization (SEO)

Contact Us
Site Map

Search

Web
aspfaq.com
tutorials.aspfaq.com
sqlserver2000.databases.aspfaq.com

ASP FAQ Tutorials :: Databases :: Sql Server 2000 :: Why can't I install SQL Server on Windows Server 2003?


Why can't I install SQL Server on Windows Server 2003?

SQL Server 2000 / MSDE 2000 
 
Chances are, setup cannot continue, because you are using Windows Server 2003 Web Edition. If so, you are probably seeing this error: 
 
Windows cannot install this program because it has been disabled. 
 
or 
 
Windows cannot open this program because it has been disabled.
 
This version of Windows Server 2003 is meant explicitly to be a *web server*... not a database and/or application server. This is not a bug in SQL Server's setup program, this is intentional enforcement of the end user licensing agreement. (See KB #819258 for clarification.) 
 
If you want to run a true database server on Windows Server 2003, you're going to have to buy Standard or Enterprise. Or, run your web pages on 2003 Web Edition, and run the database on a different, Windows 2000 Server. 
 
That said, if your application can deal with its limitations (see Article #2343 and Article #2345), you can run the Desktop edition of SQL Server (MSDE) on Windows Server 2003 Web Edition. 
 
If you are installing MSDE 2000 on any version of Windows, please make sure you obtain a current version (SP3 or better). The same applies for any other flavor of SQL Server 2000, of course; however, be wary of applications coming from vendors who may not have considered it a top priority to update the version of MSDE that ships with their application(s). 
 
If you *are* installing SQL Server 2000 on the standard or enterprise version of Windows Server 2003, then you're probably here because, when starting the install, you saw the following dialog: 
 
SQL Server 2000 SP2 and below  
SQL Server 2000 SP2 and below is not supported by this version of Windows. To run the program, click continue. For more information, click Details.
 
You can safely ignore this error message, as long as you upgrade to SP3a. Windows Server 2003 knows about Slammer and wants to make sure you are aware that you need to be responsible for getting your product up to date immediately. Hopefully, we will soon have installation CDs with SP3 slipstreamed into the product (though I recently received a 'new' SQL Server 2000 disc in my MSDN Universal shipment, and it is still RTM and not SP3). 
 
For information about this dialog, see KB #329329. You can suppress the message from appearing, if you plan to run an unattended installation; see KB #815430 for more information. 
 
You might also be having a problem because of a Windows Server 2003 Terminal Server issue. If the server you are installing on has Terminal Server installed and it is a cluster, see KB #327270
 
SQL Server 7.0 / MSDE 1.0, SQL Server 6.x 
 
These flavors of SQL Server are simply not supported on Windows Server 2003. The reasons are primarily security-based; when SQL Server 7.0's product lifetime ends, and Microsoft is no longer supporting it (e.g. shipping security patches), Windows Server 2003 customers would be left vulnerable to the next Slammer-like attack. So, rather than commit to supporting legacy versions of SQL Server for the foreseeable future, they decided to nip it in the bud. For more information, see KB #810391
 
Having said all that, it is quite possible you can get it to install (though I haven't tried it, and don't recommend it). You can try using the apcompat tool to fool setup into believing you are running Windows 2000 or NT 4.0. (I believe apcompat.exe is in the Windows Server 2003 Resource Kit, or on the Windows Server 2003 CD, or you might have to fetch a version from the Windows 2000 CD.)

Related Articles

Are there tools available for auditing changes to SQL Server data?
Can I create an index on a BIT column?
Can I have optional parameters to my stored procedures?
Can I implement an input mask in SQL Server?
Can I make SQL Server format dates and times for me?
Can I start IDENTITY values at a new seed?
Can SQL Server tell me which row was inserted most recently?
How can I learn more about undocumented SQL Server stored procedures?
How can I make my SQL queries case sensitive?
How do I audit changes to SQL Server data?
How do I connect to a non-default instance of SQL Server?
How do I connect to SQL Server on a port other than 1433?
How do I create a cross-tab (or "pivot") query?
How do I determine if a table exists in a SQL Server database?
How do I drop a SQL Server database?
How do I find all the available SQL Servers on my network?
How do I get a list of SQL Server tables and their row counts?
How do I get rid of Named Pipes / DBNMPNTW errors?
How do I get the correct date/time from the msdb.sysjob* tables?
How do I get the nth row in a SQL Server table?
How do I get the result of dynamic SQL into a variable?
How do I handle REPLACE() within an NTEXT column in SQL Server?
How do I hide system tables in SQL Server's Enterprise Manager?
How do I know which version of SQL Server I'm running?
How do I limit the number of rows returned in my resultset?
How do I load text or csv file data into SQL Server?
How do I manage changes in SQL Server objects?
How do I monitor SQL Server performance?
How do I prevent linked server errors?
How do I reclaim space in SQL Server?
How do I recover data from SQL Server's log files?
How do I search for special characters (e.g. %) in SQL Server?
How do I start SQL Server Agent from ASP?
How do I time my T-SQL code?
How do I upsize from Access to SQL Server?
How do I upsize my MSDE database to full-blown SQL Server 2000?
How do I use a variable in a TOP clause in SQL Server?
How do I use GETDATE() within a User-Defined Function (UDF)?
How should I store an IP address in SQL Server?
Schema: How do I find all the foreign keys in a database?
SQL Server & MSDE
What are reserved Access, ODBC and SQL Server keywords?
What are the capacities of Access, SQL Server, and MSDE?
What are the main differences between Access and SQL Server?
What do I need to know about SQL Server 2000 SP4?
Where else can I learn about SQL Server?
Where is SP4 for SQL Server 2000?
Why am I having problems with SQL Server 2000 SP3 / SP3a?
Why can't I install SQL Server on Windows XP?
Why can't I use LIKE '%datepart%' queries?
Why do I get "Login failed for user '\'."?
Why do I get 'object could not be found' or 'invalid object name'?
Why do I get errors about master..spt_values?
Why do I get script errors in Enterprise Manager's 'taskpad' view?
Why do I get SQLSetConnectAttr Failed errors?
Why do I have problems with views after altering the base table?
Why does EM crash when I get an error in a stored procedure?
Why does Enterprise Manager return 'Invalid cursor state'?
Why does my DELETE query not work?
Why does sp_spaceused return inaccurate values?
Why is Enterprise Manager slow at expanding my database list?
Why is my app slow after upgrading from SQL Server 7 to 2000?
Why is tempdb full, and how can I prevent this from happening?
Why should I consider using an auxiliary calendar table?
Why should I consider using an auxiliary numbers table?

 

 


Created: 6/22/2003 | Last Updated: 3/16/2004 | broken links | helpful | not helpful | statistics
© Copyright 2006, UBR, Inc. All Rights Reserved. (186)

 

Copyright 1999-2006, All rights reserved.
Finding content
Finding content.  An error has occured...