# BUG: Site Handlers Not Freed After Network Error

Last reviewed: April 30, 1997
Article ID: Q121727

###

The information in this article applies to:

      - Microsoft SQL Server version 4.2 for OS/2

BUG# OS/2: 1888 (4.2)

## SYMPTOMS

When attempting to issue RPCs to a remote server, the RPC attempt fails with error 7205:

       Can't open a connection to site '%.*s'. See the error log file in
       the SQL Server boot directory.

The error log file will contain the error:

       nconnect: no site i/o buffers are available

This error will occur despite the number of requested site handlers (connections to remote SQL Servers) being less than the configured number of remote sites.

## WORKAROUND

Increasing the configured number of site handlers on the local server will increase the pool of available site handlers, delaying or preventing an occurrence of a 7205 error. If the local server is cycled, the site handlers are re-initialized. This may be used to re-enable the local server to issue RPC requests.

This problem does not occur when issuing RPCs from SQL Server for Windows NT.

## STATUS

Microsoft has confirmed this to be a problem in SQL Server for OS/2 version 4.2. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

## MORE INFORMATION

If site handlers in use by the local server are abnormally terminated, SQL Server for OS/2 can fail to free the site handler resource for use in subsequent RPC attempts.

> Additional query words: remote procedure call
> Keywords : kbbug4.20 kbother SSrvServer
> Version : 4.2
> Platform : OS/2
> 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.