Filter
Top Products
CHAPTER 4 Backup Server Error Messages
707
3.17.2 2 Pathname parameter must specify an absolute
pathname. Rejected value: %1!
Explanation: Adaptive Server sent its present
working directory to the Backup Server and that
directory was not recognized as an absolute path
specifier.
3.18.2 2 Adaptive Server Enterprise did not specify absolute
pathname root before sending the relative device
pathname %1!.
Explanation: Adaptive Server sent a device
specification that was not recognized as an absolute
path specification, and had not previously sent its
present working directory.
3.19.2 2 Combining device pathnames %1! and %2! exceeds
the maximum pathname length.
Explanation: The combination of Adaptive Server's
present working directory and the relative device name
is too long for Backup Server's internal buffer.
3.20.2 2 %1!: RPC rejected--missing parameters.
Explanation: The number of parameters passed to
Backup Server for the specified RPC does not match
the number of parameters expected for that RPC. If
you are sending Backup Server the RPC via your own
customized mechanism, check that mechanism for the
correct RPC count. Otherwise, contact Sybase
Technical Support.
3.21.2 2 %1! SANITY: run list size > %2!.
Explanation: The total size of the run lists for the
bs_run_list RPC will exceed the size used to store the
run lists internally within Backup Server. If you are
sending Backup Server the RPC via your own
customized mechanism, check that mechanism for the
correct size of the run lists. Otherwise, contact Sybase
Technical Support.
3.22.2 2 %1!: Session %2! does not exist.
Explanation: Internal error, contact Sybase
Technical Support. Violation of the dump
synchronization protocol of the RPC API.
3.23.2 2 %1!: Could not queue run list for session %2!.
Explanation: Internal error, contact Sybase
Technical Support. Violation of the dump
synchronization protocol of the RPC API.
Number Severity Text and Explanation