Filter
Top Products
Backup Server Error Messages 2.1.2 - 3.55.2
706
3.8.2 2 %1!: May not begin phase %2! before completing an
earlier phase, number %3!, for which there is
uncompleted work.
Explanation: Internal error, contact Sybase
Technical Support. Violation of the dump
synchronization protocol of the RPC API.
3.9.2 2 %1!: May not initiate Backup Server scanning for a
phase for which run-lists have been queued.
Explanation: Internal error, contact Sybase
Technical Support. Violation of the dump
synchronization protocol of the RPC API.
3.10.2 2 %1!: phase %2! not active.
Explanation: Internal error, contact Sybase
Technical Support. Violation of the dump
synchronization protocol of the RPC API.
3.11.2 2 %1! SANITY: PHASE for phase no. %2! not at head
of list.
Explanation: Internal error, contact Sybase
Technical Support. Violation of the dump
synchronization protocol of the RPC API.
3.12.2 2 May not submit RPC %1! unless performing a DUMP.
Explanation: Internal error, contact Sybase
Technical Support. Violation of the dump
synchronization protocol of the RPC API.
3.13.2 2 %1!: Illegal phase number %2!.
Explanation: Internal error, contact Sybase
Technical Support. Violation of the dump
synchronization protocol of the RPC API.
3.14.2 2 Logical page %1! is not in the given database map.
Explanation: Internal error, contact Sybase
Technical Support. Violation of the dump
synchronization protocol of the RPC API.
3.15.2 2 The disk piece for page %1! does not belong to phase
%2!.
Explanation: Internal error, contact Sybase
Technical Support. Violation of the dump
synchronization protocol of the RPC API.
3.16.2 2 %1!: There is no session of id %2! in progress.
Explanation: Internal error, contact Sybase
Technical Support. Violation of the dump
synchronization protocol of the RPC API.
Number Severity Text and Explanation