Article ID: 233337 - View products that this article applies to.
This article was previously published under Q233337
This article has been archived. It is offered "as is" and will no longer be updated.
You can automate the installation of SQL Server or Microsoft Data Engine (MSDE) by using an .iss file that records the responses and selections that would be provided by a user during an interactive install. An unattended installation of SQL Server 7.0 or MSDE 1.0 does not provide any graphical feedback of installation progress or of success or failure. If you want to determine when an unattended setup has completed or get additional information about the cause of a failed install you can use the files Sqlstp.log and Setup.log, which are automatically created during the setup.
This article applies only to SQL Server 7.0/MSDE 1.0. If you need to detect when the installation of SQL Server 2000 Desktop Engine/MSDE 2.0 completes, see the following article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/315463/EN-US/ )HOW TO: Implement a SQL Server 2000 Desktop Engine Callback Function and Example
Sqlstp.log is a detailed log file that the InstallShield setup program creates in the Windows root directory and updates throughout the installation to detail the setup progress. When an MSDE/SQL Server setup has completed successfully, a line like the following will be seen at the end of Sqlstp.log:
For an explanation of the contents of this file, see the SQL Server 7.0 Books Online article "Contents of the Sqlstp.log file". Sqlstp.log is very verbose and is a good place to start when troubleshooting installation issues. However, if you need to programmatically determine whether setup succeeded, you should use Setup.log, not Sqlstp.log. A sample Setup.log file would be:
18:04:48 Installation Succeeded
Note that Setup.log has the structure of a standard Windows .ini file.
[InstallShield Silent] Version=v5.00.000 File=Log File [Application] Name=MSDE Version=7.00.000 Company=Microsoft [Status] Completed=1 RebootRequired=0 [ResponseResult] ResultCode=0
The following steps should be taken to programmatically determine whether setup was successful:
Other possible ResultCode values are:
Collapse this tableExpand this table
This list can be found in the SQL Server 7.0 Books Online article titled "Scripting".
If setup completes successfully, the Setup.log file will also have a RebootRequired entry in the [Status] section. If RebootRequired=1, the computer will need to be rebooted to fully install all new components. If RebootRequired=0, no reboot is necessary.
The Setup.log file will be created in the Windows root directory (for example, C:\WINDOWS or C:\WINNT). The following Microsoft Knowledge Base article describes how to retrieve the path to this directory with the GetWindowsDirectory Windows API function:
210158Sample .iss files that have been tested are available with both MSDE and SQL Server. The file Unattend.iss automates a typical install of MSDE, and the SQL Server CD includes sample .iss files for the installation of common variations of SQL Server installs (client utilities only, Desktop edition/Standard edition, and so forth).
(https://support.microsoft.com/kb/210158/EN-US/ )ACC2000: How to Find the Windows and System Paths
REFERENCESFor additional information on an unattended installation, see the SQL Server 7.0 Books Online articles "Unattended Installation" and "How to run an unattended installation (Command Prompt)".
SQL Server 7.0 Books Online are available at the following URL: