unable to install sql server 2005 enterprise edition on windows vista home premium

Tech-Archive recommends: Fix windows errors by optimizing your registry

Hi,

I am trying to install sql server 2005 EE on Windows Vista home Basic.
After running the setup, the System Configuation Check succeeds with
three warnings mentioned at the end of this post.

After providing the license key, in the Components to Install dialog
box, only the last component is enabled.
i.e. Workstation components, books online and development tools.
All the others, including database services are disabled.

I want to install SQL Server 2005 instance and start creating
databases. Please help me in installing sql server 2005 for doing
this.

What if i select the component available for install now and later
install Sql Server 2005 SP2. Will i be able to start my sql 2005
server instance, create databases etc. then?

System Configuration Check

- SQL Server Edition Operating System Compatibility (Warning)
Messages
* SQL Server Edition Operating System Compatibility

* Some components of this edition of SQL Server are not supported on
this operating system. For details, see 'Hardware and Software
Requirements for Installing SQL Server 2005' in Microsoft SQL Server
Books Online.

- IIS Feature Requirement (Warning)
Messages
* IIS Feature Requirement

* Microsoft Internet Information Services (IIS) is either not
installed or is disabled. IIS is required by some SQL Server
features. Without IIS, some SQL Server features will not be available
for installation. To install all SQL Server features, install IIS from
Add or Remove Programs in Control Panel or enable the IIS service
through the Control Panel if it is already installed, and then run SQL
Server Setup again. For a list of features that depend on IIS, see
Features Supported by Editions of SQL Server in Books Online.

- Edition Change Check (Warning)
Messages
* Edition Change Check

* To change an existing instance of Microsoft SQL Server 2005 to a
different edition of SQL Server 2005, you must run SQL Server 2005
Setup from the command prompt and include the SKUUPGRADE=1 parameter.




.

Relevant Pages

  • Re: Missing IIS (PLEASE HELP)
    ... You basically have to go into the Windows features and find IIS and find that feature and enable it. ... I selected Windows Authentication, which is what I specified when I installed SQL Server, and all it tells me when I click Test Connection is that it failed. ... Prior to installation, I uninstalled SQL Server Management Studio Express, SQL Server Express, and SQL Server Native Client. ...
    (microsoft.public.dotnet.framework.adonet)
  • SQL 2008 install error code 1608
    ... Yes, I am Yao. ... I have an unofficial work-around ???inspired??? ... Install SQL Server 2008 again, which is developer version for me, and it ... I am getting the following error when I try and install SQL Server 2008. ...
    (microsoft.public.sqlserver.setup)
  • Re: Missing IIS (PLEASE HELP)
    ... In two sessions with Microsoft support, I determined that A) there was no SQL Server login account associated with my Windows account, and B) the SqlDataServer connection string in machine.config had to be overridden to work with SQL Server 2005. ... You basically have to go into the Windows features and find IIS and find that feature and enable it. ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Missing IIS (PLEASE HELP)
    ... In two sessions with Microsoft support, I determined that A) there was no SQL Server login account associated with my Windows account, and B) the SqlDataServer connection string in machine.config had to be overridden to work with SQL Server 2005. ... You basically have to go into the Windows features and find IIS and find that feature and enable it. ...
    (microsoft.public.dotnet.framework.adonet)
  • Sql server express SP2 Bootstrapper package
    ... Bootstrapper package files as I did with SP1 ... When i try to install SQL server as part of my VS 2005 deployment app I get ... Express Edition requires Internet Explorer version 6.0 with SP1 or later. ...
    (microsoft.public.dotnet.languages.vb)