The information in this article applies to:
SYMPTOMSWhen attempting a remote procedure call (RPC) from one server to another (for example, by executing a stored procedure on a remote computer with a statement such as EXEC SERV_REMOTE.pubs..byroyalty), you may receive the following error message:
CAUSEThis error occurs when SQL Server cannot execute a remote procedure call. This can be caused by an improperly configured local server. To make a remote procedure call, SQL Server first determines who the local server is by looking for the server name with srvid = 0 in sysservers. If an entry with srvid = 0 is not found in sysservers, or if the server name with srvid = 0 belongs to a server name that is different from the local Windows NT computer name, you will receive the error. WORKAROUND
To determine if the local server is configured correctly, examine the srvstatus column in master..sysservers. This value should be 0 for the local server.
In the preceding output, SERV_LOCAL is the local server, but it has a srvid of 1; it should be 0. To correct this, perform the following steps:
Note that server ID (srvid) should be 0 for the local server.
MORE INFORMATION
You may receive this error message when installing replication because the
installation process makes remote procedure calls between the servers involved in replication. Additional query words: rpcs
Keywords : kbSQLServ650 |
Last Reviewed: November 6, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |