Filter
Top Products
CHAPTER 4 Backup Server Error Messages
697
1.34.1 1 Unable to set one or more trace flags; continuing.
Explanation: Attempt to set the Open Server run-
time trace flags failed. Check to see that the trace flags
are valid and in the proper format.
1.35.0 0 <new_volume_name>
Explanation: This informational text may be a
component of another message. No action is
necessary.
1.36.1 1 Unable to configure Async IO. If Adaptive Server is
using Async IO on block special devices, then dump
and loads may be inconsistent. Refer to the server
release notes.
Explanation: HP only: could not initialize and
configure the asynchronous I/O system to be used
when accessing database devices. Check the Backup
Server error log and contact Sybase Technical Support.
1.37.4 4 Could not allocate event flag, server %1!: code %2!
message %3!.
Explanation: This is an Digital OpenVMS error only.
An attempt to allocate an event flag failed. Backup
Server cannot start. Probably an internal error.
1.38.4 4 Could not get master lock on server name, server %1!:
code %2! message %3!.
Explanation: Digital OpenVMS only: an attempt to
obtain a lock identifying this as the “master” Backup
Server failed for the reason specified in %3!. Backup
Server cannot start.
1.39.4 4 This backup server is unnamed, and so cannot acquire
the master lock it needs to boot successfully. Backup
Server must shut down.
Explanation: Digital OpenVMS only: no Server
name was given when attempting to acquire an
exclusive lock on the master lock name, which is
constructed from the Server name. Use
showserver to
check whether Backup Server was started with a
Server name by means of the /SERVER_NAME
qualifier or the translation of the DSLISTEN logical
name.
Number Severity Text and Explanation