FIX: Failed RPC Call from SQL Server Generates Error 18481

ID: Q163452

The information in this article applies to:
BUG #: 16506 (Windows: 6.5)

SYMPTOMS

When you make a remote procedure call (RPC) to a SQL Server that does not exist or is not started, you receive the following error message:

Msg 18481, Level 9, State 2
Unable to connect to site 'MyServer' because it is unavailable or does
not exist.

The process terminates the remainder of the batch, but only returns a severity of 9. DB-Library considers severity levels 0 to 10 as informational, and does not cause functions like dbsqlexec, dbrpcexec, and dbsqlok to return FAIL, but rather SUCCEED.


WORKAROUND

To work around this problem, trap for errors 18481 through 18485 in your SQL Server message handler, and handle them appropriately.


STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server version 6.5. This problem has been corrected in U.S. Service Pack 3 for Microsoft SQL Server version 6.5. For more information, contact your primary support provider.

Additional query words: counter sequence random timestamp generating 


Keywords          : kbusage SSrvGen kbbug6.50 
Version           : 6.5
Platform          : WINDOWS 
Issue type        : kbbug

Last Reviewed: April 8, 1999