FIX: Unable to Perform Automated Installation of SQL 7.0 Using File Images

ID: Q229875

The information in this article applies to:

Microsoft SQL Server version 7.0

BUG #: 52146 (SQLBUG_70)

SYMPTOMS

During a mass rollout of Windows NT Server or Workstation, you may elect to install SQL Server 7.0 using image files. This streamlines the installation process by automating and standardizing across all company servers. A problem with this type of installation can occur because of a conflict with the Windows NT Server name and the following registry entry:


   HKEY_LOCAL_MACHINE\Software\Microsoft\MSSQLServer\MSSQLServer\CurrentVersion\checksum

During startup, SQL Server reads this registry value and compares it to the Windows NT Server name. If a conflict occurs, the server startup is stopped and the following error message appears:

Your SQL Server installation is either corrupt or has been tampered with (unknown package id). Please rerun Setup.

You have no option but to acknowledge this dialog box by clicking the OK button.

To correct this problem, you must rerun SQL Server 7.0 setup from the original installation CD and perform an upgrade, essentially overwriting the registry with the correct server name. However, running an unattended upgrade is not supported in the retail build of SQL Server 7.0, thereby prohibiting a fully automated installation using image files.

CAUSE

Unattended upgrade was originally not allowed in the retail build of SQL Server 7.0 to help prevent piracy.

RESOLUTION

A supported fix that corrects this problem is now available from Microsoft, but it has not been fully regression tested and should be applied only to systems experiencing this specific problem. If you are not severely affected by this specific problem, Microsoft recommends that you wait for the next SQL Server service pack that contains this fix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:

http://www.microsoft.com/support/supportnet/overview/overview.asp

The English version of this fix should have the following file attributes or later:


   Date      Time    Version      Size    File name   Platform
   -----------------------------------------------------------

   04/06/99  2:32PM  7.00.657     216KB   Setup.ins   Intel
   04/06/99  2:32PM  7.00.657     216KB   Setup.ins   Alpha

NOTE: Due to file dependencies, the most recent hotfix or feature that contains the above files may also contain additional files.

WORKAROUND

On each computer, rerun SQL Server 7.0 setup from the original installation CD and perform an attended upgrade.

STATUS

Microsoft has confirmed this to be a problem in SQL Server version 7.0.

MORE INFORMATION

Following are the steps required to automate the installation of SQL Server 7.0 using an image installation utility. Note that all steps must be performed. It is assumed that the utility has some scripting capabilities that enables it to run SQL Server 7.0 setup in an unattended mode.

The SQL Server 7.0 image files must be created using a setup server, called "ServerA" in the following steps. The image files need to be copied to a destination server, called "ServerB".

Install SQL Server 7.0 on ServerA by running setup from the SQL Server 7.0 CD. Verify that the installation was successful.

Change the Windows NT Server name on ServerA. Verify that SQL Server will not start.

On ServerA, run SQL Server 7.0 Setup from the CD and perform an upgrade. This creates a Setup.iss file, which will be used during the unattended setup performed in these steps. Note that this Setup.iss file will be created in the MSSQL7\Install directory. Verify that SQL Server will start.

Create the file images on ServerA and then copy them to ServerB using the imaging utility.

When installing SQL Server 7.0 Standard edition on Windows NT Server 4.0, copy the following files from the SQL Server 7.0 CD to a temporary directory on ServerB:

\Binn\Regrebld.exe
\Binn\Setupex.dll
\Binn\Sqlboot.dll
\Binn\Sqlsusk.dll
\Setup\Layout.bin
\Setup\Os.dat
\Setup\Setup.ini
\Setup\Setup.lid
\Setup\Setupsql.exe
\Setup\Sqlstp.exe
\Setup\_isdel.exe
\Setup\_setup.dll
\Setup\_sys1.cab
\Setup\_user1.cab
Intel-specific instructions:

Copy the \Setup\_inst32i.ex_ file to the same directory.

NOTE: Files should be copied from subdirectories under the X86 directory on the CD. For example, copy the X86\Binn\Regrebld.exe file to ServerB_temp_directory\X86\Binn\Regrebld.exe.

Alpha-specific instructions:

Copy the file \Setup\_inst32a.ex_ to the same directory.

NOTE: Files should be copied from subdirectories under the Alpha directory on the CD. For example, copy the Alpha\Binn\Regrebld.exe file to ServerB_temp_directory\Alpha\Binn\Regrebld.exe.

IMPORTANT: When installing any other edition/platform combination, copy all files from the appropriate directory (X86 or Alpha) on the SQL Server 7.0 CD to a temporary directory on ServerB.

Copy the Setup.ins file from the hotfix to ServerB's temporary \Setup directory.

Run the following command to start unattended setup on ServerB:


start /wait D:\sphinx\x86\setup\SETUPSQL.EXE -f1 C:\MSSQ7\Install\setup.iss -SMS -s

Verify that SQL Server starts on ServerB.

Additional query words:

Keywords :
Version : winnt:7.0
Platform : winnt
Issue type : kbbug