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,
[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
SQLState: 08001 Native Error: 17
[Microsoft][ODBC SQL Server Driver][Shared Memory]SQL
Server does not
exist or access denied.
SQLState: 01000 Native Error: 53
Message: [Microsoft][ODBC SQL Server Driver][Shared
ISQL can still connect, when you
specify the SQL Server machine name. ISQL makes a DB Library connection and
uses shared memory.
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
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
- Start the Client Network Utility located under the Microsoft SQL Server 7.0 Program Group.
- Click Add, click Multiprotocol, type server alias, and then click OK.
The server alias appears in the Configurations list.
- Click OK.
- 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.
- 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
Microsoft has confirmed this to be a problem in SQL Server