Microsoft KB Archive/104623

-

The information in this article applies to:


 * Microsoft SQL Server Programmer's Toolkit, version 4.2

-

When attempting to connect to a SQL Server running on a Windows NT Advanced Server and the user does not have an account on the Advanced Server, the domain in which the server is a part or a domain trusted by the server, the client may be unable to connect.

Errors from the client application will be:

DB-Library error:

"Unable to connect: SQL Server is unavailable or does not exist"

Net-Library:

"Error 5 ConnectionOpen (DosOpen)."

The READPIPE utility will fail to connect to MAKEPIPE running on the Windows NT server with:

"READPIPE status = 5 (accessdenied)."

These errors may be due to an inactive Guest account on the Windows NT Advanced Server. This account defaults to inactive when Windows NT Advanced Server is installed.

To enable the guest account:


 * 1) From the Administrative Tools group, select User Manager.
 * 2) Double-click on the entry for Guest.
 * 3) Clear the Account Disabled check box in the User Properties dialog box and press OK.

Clients without global or local accounts will now be able to successfully connect to SQL Server on the Windows NTAS server.

Additional query words: SAF ISQL SQL Admin Object Manager

Keywords : kberrmsg kbother

Version : 4.2

Platform : WINDOWS

Issue type :