Home     Knowledge Base Suche     FAQs     Downloads     Newsgroups     Kontakt  
Microsoft Knowledge Base Article - 823492
Allgemeine Informationen
Microsoft kontaktieren

Telefonnummern, Anfrage via Internet

Microsoft Newsgroups

Newsgroups - User helfen Usern

"Connection Could Not Be Established" Error Message When You Connect to a Windows NT 4.0-Based Computer That Is Running SQL Server 2000 or SQL Server 7.0

Die Informationen in diesem Artikel beziehen sich auf:


Important This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry

SYMPTOMS

When you connect to a Windows NT 4.0-based computer that is running either Microsoft SQL Server 2000 or Microsoft SQL Server 7.0, you may receive an error message that is similar to one of the following:
Connection could not be established.
SQL Server does not exist.

-or-


Connection could not be established.
Access is denied.
You do not experience these symptoms if you use TCP/IP to connect to the server.

CAUSE

This problem may occur if all the following conditions are true:
  • You are running Windows NT 4.0 Service Pack 6 (SP6) or later.
  • You apply the Microsoft SQL Server update that is documented in the following article in the Microsoft Knowledge Base:

    815495 MS03-031: Cumulative Security Patch for SQL Server

  • You are not a member of the Administrators group on the client computer.

RESOLUTION

Update Information

Download Information

The following file is available for download from the Microsoft Download Center:
Windows NT 4.0 Server
DownloadDownload the 823492 package now.
Windows NT 4.0 Terminal Server Edition
DownloadDownload the 823492 package now.

Release Date: July 23, 2003

For additional information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base:

119591 How to Obtain Microsoft Support Files from Online Services

Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help to prevent any unauthorized changes to the file.

Prerequisites

This update requires Windows NT 4.0 Service Pack 6 (SP6) or Windows NT 4.0 Service Pack 6a (SP6a).

Update Replacement Information

This update does not replace any other updates.

File Information

The English version of this update has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Windows NT 4.0 Server
Date         Time   Version        Size    File name
----------------------------------------------------
25-Jun-2003  09:03  4.0.1381.7220  38,736  Npfs.sys
Windows NT 4.0 Terminal Server Edition
Date         Time   Version        Size    File name
----------------------------------------------------
25-Jun-2003  09:06  4.0.1381.33548 38,608  Npfs.sys

To Activate the Update

After you install the update on the server, you must edit the registry to activate the update. After you do so, users can connect to the server by using named pipes. To activate the update, add the EnhancedSecurityLevelNamedPipes registry value to the following registry key, and then set the value to 1:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager

To do so, follow these steps.WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
  1. Click Start, and then click Run.
  2. In the Open box, type regedit, and then click OK.
  3. Locate and then click the following registry entry:

    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager

    Note Look at the key carefully. There may be a key named SessionManager (no space) rather than Session Manager (with a space). Do not use the SessionManager key; only use the Session Manager key.
  4. On the Edit menu, point to New, and then click DWORD Value.
  5. Type EnhancedSecurityLevelNamedPipes, and then press ENTER.
  6. On the Edit menu, click Modify.
  7. In the Value data box, type 1, and then click OK.
  8. Quit Registry Editor.
  9. Restart the server.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

The information in this article applies to:

  • Microsoft Windows NT Server 4.0
  • Microsoft Windows NT Server 4.0 Terminal Server Edition, when used with:
      Microsoft SQL Server 7.0
      Microsoft SQL Server 2000 Standard Edition
      Microsoft SQL Server 2000 Enterprise Edition
Last Reviewed:10/3/2003 (4.0)
Keywords:kberrmsg kbQFE kbfix kbBug KB823492 kbAudITPRO