BUG: Remote Setup Removes \sql\binn;\sql\dll From Path

  - Microsoft SQL Server version 4.21

BUG# NT: 9834 (4.21)

SYMPTOMS

SQL Server may fail to start with the following error displayed in a message box on the server:

   SQLSERVR.EXE - Unable to Locate DLL
   The dynamic link library opendsnt.dll could not be
   found in the specified path c:\winnt\system32;
   c:\winnt\system;c:\winnt.

   SQL Service Manager
   An error 1053 - (The service did not respond to the
   start or control request in a timely fashion) occurred
   while performing this service operation on the
   SQLServer service.

CAUSE

If using the remote option of SQL Server setup to change configuration options such as,

   Auto Start Server At Boot Time,

You can verify whether SQL Server has failed to start because of missing path entries by using the Control Panel System applet and inspecting the System Environment Variables: listbox. You should see in your system path environment variable something like this:

   %SystemRoot%\system32;%SystemRoot%;C:\SQL\BINN;C:\SQL\DLL

WORKAROUND

Below are three different techniques to restore the SQL entries to your path system environment variable.

The first technique involves using the RegistryRebuild option of SQL Server setup to rebuild the pathname entries, as follows:

1. On the server machine, from an operating system prompt, type:

   cd \sql\binn setup /t RegistryRebuild = ON

   NOTE: The command must be typed exactly as entered, including spacing and capitalization.

2. Follow the on-screen directions.

   This procedure is also documented on page 144 of the SQL Server "Configuration Guide."

   Use the Control Panel System applet to append the SQL entries to
   the path system environment variable.

   See the printed or on-line documentation for the Control Panel System
   applet for more information.

   Since this problem also causes the path entries that are removed from
   the remote machine to be added to the local machine, a similar
   technique using the Windows NT version 3.5 Control Panel System
   applet can be used to remove these extra entries.

WARNING: Do not use Regedt32 unless you are familiar with it; a mistake could render your system inoperable.

1. From an operating system prompt, type:

   start regedt32

2. Navigate to the following key:

   hkey_local_machine\system\CurrentControlSet\Control \Session Manager\Environment

3. Double-click the Path environment variable to edit it.

   The existing entry will be highlighted.

4. Press the "end" key to select the end of line, and type in a semicolon followed by the correct path including the drive letter on which SQL Server is installed.

   For example:

   ;c:\sql\binn;c:\sql\dll

5. Exit Registry Editor to save.

6. Reboot the machine.

STATUS

Microsoft has confirmed this to be a problem in SQL Server version 4.21. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.