Sybase 11.9.x-12.5 - Manual (Page 29)

CHAPTER 4 Backup Server Error Messages
703
2.5.2 2 Couldn't define %1! event; Backup Server must exit.
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic. The session must exit.
2.6.2 2 Login information unavailable.
Explanation: The Backup Server could not access
the session login information to perform
authentication due to unauthorized session initiator or
programming bug. Contact Sybase Technical Support.
2.7.2 2 Remove server TDS version must be equal to or greater
than 4.6. This session must exit.
Explanation: Connection was attempted with an
obsolete TDS version. Backup Server communicates
reliably only with System 10 Adaptive Servers and
other Backup Servers.
2.8.2 2 Couldn't create semaphore for session %1!. This
session must exit.
Explanation: Indicates Open Server MUTEX
initialization failure or session limit reached.
2.9.4 4 The number of connections must be an integer.
Explanation: Indicates illegal -C (/connections in
Digital OpenVMS) option value for the backupserver
command. Check the line in your RUN_servername
file.
2.10.2 2 A trace flag specifier must be an integer.
Explanation: UNIX only: The argument to the
backupserver command's -T (/trace in Digital
OpenVMS) option was not an integer. Check the line
in your RUN_servername file.
2.11.2 2 Failed to get lock to send packet to client, spid: %1!,
lockstatus %2!.
Explanation: Internal error, contact Sybase
Technical Support. An error occurred when attempting
to lock an Open Server MUTEX (mutually exclusive
object) which only one user at a time can lock. Refer to
the Backup Server error log for more information.
Number Severity Text and Explanation