BUG: Error 17835 Received When Connecting LocallyLast reviewed: April 29, 1997Article ID: Q110080 |
The information in this article applies to:
SYMPTOMSAttempting to connect to the Desktop version of SQL Server for Windows NT causes error 17835,
Configured for local access onlyto be received by the front end. This occurs despite attempting to connect from the same machine running the desktop SQL Server.
CAUSEIf a user who does not have administrative privileges on the Windows NT machine running SQL Server specifies the server name when attempting to connect, the login attempt will be rejected with error 17835.
WORKAROUNDUsers who do not have administrative privilege should not specify a server name when connecting to the Desktop version of SQL Server for Windows NT. Users with administrative privilege can connect both with and without specifying a server name.
STATUSMicrosoft has confirmed this to be a problem in Microsoft SQL Server version 4.2. We are researching this problem and will post new information here in the Microsoft Knowledge as it becomes available.
|
Additional query words: local pipe pipes connection connections Windows NT
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |