SQL Server 2000 Setup program configuration server failed

The first of these methods

Installing SQL Server 2000 today encountered a very BT problem, prompting the following:

Setup failed to configure the server. Refer to Server error logs and C:\Windows\sqlstp.log for more information.

Removing the installed directory with the forward installation directory is resolved, but this time it restarts five times or so (I really have patience-_-;)

Go to Baidu, in a blog comment found a solution.

First step: Remove the "previous program installation has created pending file operations on the installation computer" prompt (otherwise you need to restart the machine)
Open Registry Editor and locate the PendingFileRenameOperations project in Hkey_local_machine\system\currentcontrolsetcontrol\session Manager. and delete it. This allows you to clear the Install pending project.

The second step: Start the installation program, the difference is that the installation of the time select "Advanced Options" and click "Rebuild registry Key", and then continue to install, the directory continues to specify the last installed directory, so that the installation is successful.

The second method of

"Configuration server failed, please refer to the System log Instructions" and the installation process progress bar returned
If it is a windowsxp system, you can view the Sqlstp.log file in the C:\WINDOWS directory, there is an error message, I have encountered several situations, reference to some network information, is now organized as follows:

Failure situation One:
Error message in the Sqlstp.log file:
Working with service?
Driver={sql Server};server=zhl; Uid=sa; pwd=;d Atabase=master
[Microsoft] [ODBC Driver Manager] driver Sqlallochandle on Sql_h
Driver={sql Server};server=zhl; Uid=sa; pwd=;d Atabase=master
[Microsoft] [ODBC Driver Manager] driver Sqlallochandle on Sql_h
Driver={sql Server};server=zhl; Uid=sa; pwd=;d Atabase=master
[Microsoft] [ODBC Driver Manager] driver Sqlallochandle on Sql_h
SQL Server configuration?
#######################
13:40:06 Process Exit Code: (-1)
13:40:09 Setup failed to configure the server. Refer to Server error logs and C:\WINNT\sqlstp.log for more information.
13:40:09 Action Cleanupinstall:

WORKAROUND: When this error occurs, try reloading the system files: Repair the system instead of the new installation. This error message does not appear after you repair a system file and then install SQL Server

My machine is Win2000, re-run the Win2000 installation under DOS, and then select Repair instead of the new installation

This error message does not appear after you repair a system file and then install SQL Server

Failure Scenario Two:
Error message in the Sqlstp.log file:
In with the service?
Driver={sql Server};server=zhl; Uid=sa; pwd=;d Atabase=master
[Microsoft] [ODBC SQL Server Driver] [Named Pipes] connection?
[Microsoft] [ODBC SQL Server Driver] [Named Pipes] Connectionread (ReadFile ()).
Driver={sql Server};server=zhl; Uid=sa; pwd=;d Atabase=master
[Microsoft] [ODBC SQL Server Driver] [Named Pipes] connection?
[Microsoft] [ODBC SQL Server Driver] [Named Pipes] Connectionread (GetOverlappedResult ()).
Driver={sql Server};server=zhl; Uid=sa; pwd=;d Atabase=master
[Microsoft] [ODBC SQL Server Driver] [Named Pipes] connection?
[Microsoft] [ODBC SQL Server Driver] [Named Pipes] Connectionread (GetOverlappedResult ()).
SQL Server configuration?
################################
17:17:41 Process Exit Code: (-1)
17:17:45 Setup failed to configure the server. Refer to Server error logs and

When this error occurs, you must install the ODBC Repair tool
ODBC Repair tool: 211.101.4.50/download/canyin/tools/mdac_typ. Exe

I did not find the installation of ODBC driver related content in data Sources (ODBC) under Administrative Tools. This problem occurs because some programs that use ODBC data sources will remove the odbcdriver information when they are uninstalled.
In fact, we just need to use Odbcconf.exe to re-register the ODBC driver.
There are several script files in the Windows/system32 directory that can be used to complete the registration of the driver:
odbcconf.exe/s/lv odbcconf.log/f%SYSTEMROOT%\SYSTEM32\MDACCORE.RSP
odbcconf.exe/s/lv odbcconf.log/f%SYSTEMROOT%\SYSTEM32\SQLCLNT.RSP
odbcconf.exe/s/lv odbcconf.log/f%SYSTEMROOT%\SYSTEM32\ODBCCONF.RSP
odbcconf.exe/s/lv odbcconf.log/f%SYSTEMROOT%\SYSTEM32\REDIST.RSP
By running the above command on the DOS command line, the ODBC driver is registered.

Failure Scenario Three:
Error message in the Sqlstp.log file:
Driver={sql Server};server=soyo; Uid=sa; pwd=;d Atabase=master
[Microsoft] [ODBC SQL Server Driver] [Shared Memory] General network error.
[Microsoft] [ODBC SQL Server Driver] [Shared Memory] Connectionread (Wrapperread ()).
Driver={sql Server};server=soyo; Uid=sa; pwd=;d Atabase=master
[Microsoft] [ODBC SQL Server Driver] [Shared Memory] General network error.
[Microsoft] [ODBC SQL Server Driver] [Shared Memory] Connectionread (Wrapperread ()).
Driver={sql Server};server=soyo; Uid=sa; pwd=;d Atabase=master
[Microsoft] [ODBC SQL Server Driver] [Shared Memory] General network error.
[Microsoft] [ODBC SQL Server Driver] [Shared Memory] Connectionr
################################
13:50:07 Process Exit Code: (-1)
13:50:10 Setup failed to configure the server. Refer to Server error logs and C:\WINNT\sqlstp.log for more information.
13:50:10 Action Cleanupinstall:

This problem is said to be a SQL Server2000 bug, mainly the computer name contains lowercase letters. You can change the computer name to uppercase. Modifying the computer name can be done either by invoking the control Panel or by invoking the Registry Editor. For example, to change the computer name from ' Holyrong ' to ' holyrong ', you can do this by doing the following: Open the hkey_local_machine\system\ in the registry (Cmd-->regedit) Currencontrolset\control\computername
\ComputerName, change the value of the primary key named ' ComputerName ' from the original ' Holyrong ' to ' Holyrong ', which will take effect after logging off the user or restarting Windows

2005 SQL Server 3417 bug fix pack

If your SQL Server database prompts for a specific service error code 3417 error, then using this patch will resolve the

Workaround:

1, directly find a normal SQL, find the SQL installation directory under the master database overwrite can start the database.
2, download after the decompression cover to C:\Program Files\Microsoft SQL Server\mssql.1\mssql\data below can.

Related error:

"Windows Cannot start SQL Server (MSSQLSERVER) on the local computer," MSSQLSERVER when you start server. For more information, consult the system event log. If this is a non-Microsoft service, please contact the service vendor and refer to the specific service error code 3417 ", generally because the master database in the database directory is broken, the workaround is to find a normal SQL, Locate the master database overwrite under the SQL installation directory to start the database.

Common methods:

For example, all MDF and LDF in C:\ProgramFiles\Microsoft SQL Server\mssql.1\mssql\data are saved by the uncompressed method, You only need to right-click each file---properties---advanced---compress the content to conserve disk space, and change the way the database is logged on as a local user system, and so on.

SQL Server 2000 Setup program configuration server failed