BUG: Desktop Exception on Connects with Server Name

Last reviewed: April 30, 1997
Article ID: Q119913

The information in this article applies to:

  - Microsoft SQL Server version 4.2

BUG# NT: 903 (4.2)

SYMPTOMS

If multiple connections are made to a Desktop SQL Server where the server name was specified, SQL Server may fail with an access violation.

If a user attempts four concurrent connections to a Desktop SQL Server, where they specify the server name, the fourth connection will fail with a 17835 error (Configured for Local Access Only). SQL Server will generate a Dr. Watson window:

   SQLSERVR.EXE had an access violation (0xc0000005), address: 0x00282832.

WORKAROUND

Do not specify the server name when making a connection to a Desktop server. Always leave the server name blank, or in the SQL Tools connect box, select the (local) entry.

STATUS

Microsoft 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 Base as it becomes available.

Additional query words: Windows NT
Keywords : kbbug4.20 kbother SSrvWinNT
Version : 4.2
Platform : WINDOWS
Issue type : kberrmsg

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: April 30, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.