BUG: SQL Desktop Edition: Shared memory fails to connect after you install MDAC 2.6

Article translations Article translations
Article ID: 290820 - View products that this article applies to.
This article was previously published under Q290820
BUG #: 101341 (SQLBUG_70)
BUG #: 225640 (SHILOH_BUGS)
Expand all | Collapse all

SYMPTOMS

A standalone computer (without any network protocols installed) fails to connect locally to the Microsoft SQL Server 7.0 Desktop Edition. If you attempt to connect by using either Query Analyzer or SQL Enterprise Manager, the following error message occurs:
Unable to connect to server \\SRVNAME:

Server: Msg 17, Level 16, State 1
[Microsoft][ODBC SQL Server Driver][Shared Memory]SQL Server does not exist or access denied.
Attempting to connect by using ODBCPING causes this error message to occur:
COULD NOT CONNECT TO SQL SERVER

SQLState: 08001 Native Error: 17
Info. Message: [Microsoft][ODBC SQL Server Driver][Shared Memory]SQL
Server does not exist or access denied.

SQLState: 01000 Native Error: 53
Info. Message: [Microsoft][ODBC SQL Server Driver][Shared
Memory]ConnectionOpen(Connect()).
ISQL can still connect, when you specify the SQL Server machine name. ISQL makes a DB Library connection and uses shared memory.

CAUSE

The inability to connect locally, by using the machine name, occurs after Microsoft Data Access Components (MDAC) 2.6 has been applied to the desktop computer and the connection attempts to make the connection by using the Shared Memory protocol. Shared Memory is used when you specify the machine name to connect and no network protocols are installed on the desktop computer.

WORKAROUND

To work around this problem, you can either:
  • Set up the Multiprotocol Network library for use by the client and the SQL Server server. To enable the Multiprotocol Network library using both the Client Network Utility and the Server Network Utility, follow these steps:
    1. Start the Client Network Utility located under the Microsoft SQL Server 7.0 Program Group.
    2. Click Add, click Multiprotocol, type server alias, and then click OK.

      The server alias appears in the Configurations list.
    3. Click OK.
    4. Start the Server Network Utility under the Microsoft SQL Server 7.0 Program Group. Click Add, and then select the Multiprotocol option button. Click OK. A row should appear in the SQL Server Network Utility dialog box with Multiprotocol and the machine name. To save and exit, click OK.
    5. Stop and then restart the SQL Server server to load the Multiprotocol Network Library.
  • Downgrade the SQL Server ODBC driver from the 2.6 version (version 3.80.0194 of Sqlsrv32.dll) to the 2.5 version of the SQL Server ODBC driver (version 3.70.0820), or downgrade to the prior version of MDAC. To download a prior version of MDAC, use the MDAC Component Checker, which you can download from:
    http://msdn2.microsoft.com/en-us/data/aa937730.aspx

STATUS

Microsoft has confirmed this to be a problem in SQL Server 7.0.

Properties

Article ID: 290820 - Last Review: April 25, 2007 - Revision: 2.5
APPLIES TO
  • Microsoft SQL Server 7.0 Standard Edition
Keywords: 
kbbug kbpending KB290820

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com