FIX: ODBC Only Uses Named Pipes if Non-Admin Win NT Account |
Q141086
The information in this article applies to:
- Microsoft SQL Server version 6.0
BUG# NT: 12169 (6.00)
SYMPTOMS
When running under a non-Administrator NT account, the Microsoft SQL Server ODBC Driver and ODS ODBC Driver may only make named pipe connections.
STATUS
Microsoft has confirmed this to be a problem in the Microsoft SQL Server ODBC Driver version 2.50.0121. This problem has been corrected in Microsoft ODBC Driver version 2.65.0201.
MORE INFORMATION
The Microsoft SQL Server ODBC Driver and ODBC ODS Driver may not correctly read the SQL Server advanced client connection entries when running under a Windows NT account that is not in an administrators group. In these circumstances, the drivers can only make named pipe connections. Non- administrative clients can connect if the following conditions are met:
- The SQL Server they are connecting to is listening on named pipes.
- The client is set up to support named pipe connections to the server. Named pipes will map down over protocol stacks such as the NWLink stack or Microsoft's TCP/IP stack, and netbeui. See the SQL Server 6.0 "Setup" and "Administrator's Companion" manuals for further information.
- The ODBC data source has the name of the Windows NT server running SQL Server in the SERVER entry, or on a SQLDriverConnect the SERVER= parameter names the Windows NT server running SQL Server.
WORKAROUND
Log on to the client using an NT Admin account. Using RegEdit, focus on the key:
HKEY_LOCAL_MACHINE
SOFTWARE
Microsoft
MSSQLServer
Client
ConnectTo
Using the Security/Permissions menu, either give the Everyone account Full Control of the key, or add the non-Admin account to the permissions list with Full Control of the key.
Additional query words: sql6 SQLExecDirect SQLExecute iis internet server idc .idc socket sockets connector
Keywords : kbinterop kbnetwork
Issue type : kbbug
Technology : kbSQLServSearch kbAudDeveloper kbSQLServ600
Last Reviewed: March 30, 2000 |
