Solution to system security failure in Server installation and configuration

The following error message is displayed when installing SQL Server 2000: An error occurred while installing the file configuration Server.

When you want to reinstall SQL Server and the prompt "your computer has an instance installed" appears, you can delete the program filesMicrosoft SQL Server folder and registry information, then install.

XX Dynamic Link file not found

When a dynamic link file cannot be found, try to find the file in the installation file of SQL server, copy the file to the system and system32 folders in the system directory. (when this error message is displayed, the system prompts which folders do not contain this file ).

When the installation program fails to configure the server, you can try the following methods:

This error message can be found in the system directory. For example, if my system is windowXP, the file is in the C: WINDOWS
Sqlstp. log.

The following are three possible errors:

Failed 1:

Working with service?

Driver = {SQL server}; server = ZHL; UID = sa; PWD =; database = master [Microsoft] [ODBC driver manager] SQLAllocHandle on SQL _H driver = {SQL server}; server = ZHL; UID = sa; PWD =; database = master [Microsoft] [ODBC driver manager] SQLAllocHandle on SQL _H driver = {SQL server}; server = ZHL; UID = sa; PWD =; database = master [Microsoft] [ODBC driver manager] SQLAllocHandle on SQL _H of the driver

SQL Server configuration?

13:40:06 Process Exit Code: (-1) 13:40:09 installation program configuration server failed. For more information, see Server Error log and C: WINNTsqlstp. log. 13:40:09 Action CleanUpInstall:

When this error occurs, try to reinstall the system file. My host is windows, and I re-run Windows installation under dos, and then choose to fix it, instead of completely installing it. After the system file is repaired and SQL server is installed, the error message is not displayed.

Failure 2:

Working with service?

Driver = {SQL server}; server = ZHL; UID = sa; PWD =; database = master [Microsoft] [ODBC driver manager] No data source driver found = {SQL server }; server = ZHL; UID = sa; PWD =; database = master [Microsoft] [ODBC driver manager] No data source driver found = {SQL server}; server = ZHL; UID = sa; PWD =; database = master [Microsoft] [ODBC driver manager] No data source found

SQL Server configuration?

13:50:07 Process Exit Code: (-1) 13:50:10 installation program configuration server failed. For more information, see Server Error log and C: WINNTsqlstp. log. 13:50:10 Action CleanUpInstall:

This error occurs when HKEY_LOCAL_MACHINESOFTWAREODBC is deleted from the registry.

Failure 3:

In connection with the service?

Driver = {SQL server}; server = ZHL; UID = sa; PWD =; database = 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 =; database = 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 =; database = 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 installation program configuration server failed. For more information, see Server Error log and C: WINDOWSsqlstp. log.

When this error occurs, it is because the SQL Server Content in HKEY_LOCAL_MACHINESOFTWAREODBC is deleted in the registry. You can fix the registry or install the ODBC Repair Tool.

Check the sqltp. log file generated on my machine. The second error is found.

I did not find the content for installing ODBC Driver in "Data Source (ODBC)" under "Administrative Tools. This problem occurs because some programs that use the ODBC Data Source will delete the ODBC Driver information during uninstallation.

Later, we only need to use odbcconf.exe to re-register the ODBC Driver.

There are several script files in the Windows/System32 directory to complete the registration of the driver:

odbcconf.exe /S /Lv odbcconf.log /F %systemroot%system32mdaccore.rsp odbcconf.exe /S /Lv odbcconf.log /F %systemroot%system32sqlclnt.rsp odbcconf.exe /S /Lv odbcconf.log /F %systemroot%system32odbcconf.rsp odbcconf.exe /S /Lv odbcconf.log /F %systemroot%system32edist.rsp

By running the preceding command in the doscommand line, the ODBC driver is registered.

Odbc is good, but the re-installation of SQL has the same problem as the first time. I started to feel a little discouraged, and then I put the installation disk into it, I found that there was an advanced option during installation. I clicked it and checked the rebuild registry option. So I backed up the registry and chose this option again, as a result, My SQL can be used this time. I am very happy for several days.

If the installation fails after the "advanced options", we recommend that you run the SQL Server Installation program again. This time, select the "upgrade, delete, or add components to an existing SQL Server instance" item, "Add a component to an existing installation ". After the installation is complete, Run "Enterprise Manager". If the user selected authentication is "SQL Server and Windows ", in addition, the User-Defined secret is entered during the "advanced options" Installation Process (note that the authentication method is not selected during the "add component installation" process) when registering SQL Server, the following problems may occur:

---------------------------

SQL Server Enterprise Manager

---------------------------

Unable to establish connection with ZOU.

Cause: User sa logon fails. Verify that SQL Server is running, check SQL Server Registration attributes (by right-clicking the ZOU node), and then try again.

---------------------------

OK