Filter
Top Products
CHAPTER 4 Backup Server Error Messages
733
5.8.2 2 RPC as_cmd execution failed - slave server: %1!,
device: %2!, command type: %3!.
Explanation: These messages point to difficulties in
issuing an RPC to a remote Backup Server. Probable
cause is an Open Server programming error.
5.9.2 2 RPC as_pagerun execution failed - slave server: %1!,
device: %2!.
Explanation: These messages point to difficulties in
issuing an RPC to a remote Backup Server. Probable
cause is an Open Server programming error.
5.11.2 2 RPC bs_end_load execution failed - slave server: %1!,
device: %2!.
Explanation: These messages indicate failure to
deliver the named RPCs to the remote Backup Server.
Adjacent messages provide more detail. Probable
causes are sudden death of the remote Backup Server,
or a programming error.
5.12.2 2 Missing device name parameter @devname, RPC:
%1!, command: %2!.
Explanation: Internal error, contact Sybase
Technical Support. Check the compatibility of local
and remote Backup Servers.
5.13.2 2 Received an unknown command. RPC: %1!,
command: %2!.
Explanation: Internal error, contact Sybase
Technical Support. Check the compatibility of local
and remote Backup Servers.
5.14.2 2 Cannot set the value of an RPC return parameters,
RPC: %1!
Explanation: Internal error, contact Sybase
Technical Support. Check the compatibility of local
and remote Backup Servers.
5.15.2 2 Slave server received %1! bytes of data that is more
than @count %2! specified in as_pagerun.
Explanation: Internal error, contact Sybase
Technical Support. Violation of the RPC API.
5.16.2 2 DB-Library error, error number %1!, severity %2!:
%3!
Explanation: The installed DB-Library error
handling function returns this error. Adjacent
messages provide more detail.
Number Severity Text and Explanation