We have been having a strange problem. We have been attempting to install
SQL Server 2005 Enterprise Edition on a two-node cluster. The install runs
successfully but when we check SQL Server we see that Standard Edition was
installed and not Enterprise. We then uninstalled it and re-installed it
only to have Standard installed. We have done Enterprise installs from this
location before and they were successful.

Thinking that something must have gone wrong with the setup files we deleted
them and had them downloaded again. When using the new downloaded
installation files Standard was still installed.

We have the installation files residing in these folders:

\Servers
\Standard
\Tools

All of these folders reside at the same root directory. We run the setup
under the Servers folder for an Enterprise install. When we open the
Splash.hta file it says Enterprise.

We have a 2 node cluster running Windows 2003.
The operating system is:

Windows 2003 R2 Enterprise X64 Edition. Version 5.2 Build 3790 SP2.
Each node has 8.6 GB of RAM
Each node has 8 processors: Intel Xeon E5450 # 3.0 GHz

In the registry we noticed this key:

HKLM\Software\Microsoft\Microsoft SQL Server\MSSQL.3

From my experience, SQL Server goes under MSSQL.1 and Reporting Services
goes under MSSQL.2
What is MSSQL.3 for? Could it be trying to install another instance?

Any help with this strange problem would be most appreciated.

Just out of curiosity, what makes you think that the SQL Server installed is
Standard Edition? What happen if you run:

SELECT @@VERSION

Also where do you get the files? Is it downloaded from the MSDN?

As for the MSSQL.3, it could be the Integration Service.

Also, I'd triple check the install media to make sure it's enterprise
edition. Check the install log files also to see what edition was identified.

Linchi

"Lucas Kartawidjaja" wrote:

I ran:
SELECT @@VERSION

It returned:

Microsoft SQL Server 2005 - 9.00.1399.06 (X64) Oct 14 2005 00:35:21
Copyright (c) 1988-2005 Microsoft Corporation Standard Edition (64-bit) on
Windows NT 5.2 (Build 3790: Service Pack 2)



"Lucas Kartawidjaja" <LucasKartawidjaja (AT) discussions (DOT) microsoft.com> wrote in
message news:18F71731-B659-4B2D-9285-FFA0AD3A6E48 (AT) microsoft (DOT) com...

On Aug 26, 9:50*am, "Loren Z" <anonym... (AT) discussions (DOT) microsoft.com>
wrote:
I believe the other instance MSSQL.3 is due to the mutiple installs.
If I remember correctly, SQL 2005 does not clean itself up nicely on
an unistall and subsequent installs will just start at the next
number. I have no idea why your getting Standard installed instead of
Enterprise though.

I looked in SQLSetup0003_ServerName_SQL.log.

It references Standard Edition various times. eg:
Property(S): Namechecksum.7354AFCB_913B_4E9F_B76C_2376101FDE0C = Standard
Edition (64-bit)
Property(S): Namechecksum.CB2C9331_83B7_4803_97B5_442EFDC583D7 = Standard
Edition (64-bit)
Property(S): SqlStateManaged = 2
Property(S): SqlActionManaged = 3
Property(S): Namechecksum.B2156BC9_6CE8_422F_A957_E99A65256B1D = Standard
Edition (64-bit)

Also ran the install from:
X:\SQL2005_64\Servers\Setup.exe

However the log file contains the line:
******* Product: X:\SQL2005_64Bit\Standard\Setup\SqlRun_SQL.msi

This directory is referenced various time in this log file. We have re-run
the installation various times from the Servers directory. It appears to be
installing from the standard folder even though we are running the setup
from the servers folder which should be the Enterprise Edition.

"Linchi Shea" <LinchiShea (AT) discussions (DOT) microsoft.com> wrote