Backup Server Error Messages 2.1.2 - 3.55.2

2.1.2

2

Open Server initialization failed.  Unable to start %1!.

Explanation: The user should check the installation. This error can also arise from memory and swap space shortage.

2.2.4

4

Open Server Server Fatal Error: %1!.%2!.%3!: %4!

Explanation: This indicates a fault within the Open Server layer that forces program exit. The error code placeholder should be matched to the Open Server error codes for diagnosis. Check installation.

2.3.2

2

Open Server Session Fatal Error: %1!.%2!.%3!: %4!

Explanation: Interpret as for 2.2.4, except only the session exits, not the whole Server.

2.4.2

2

Open Server Error: %1!.%2!.%3!: %4!

Explanation: Interpret as for 2.2.4, except Server and session processing continue. Example: missing localization file.

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.

2.12.2

2

The diagnostic option specifier must be an integer. Option  is `%1!'

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.13.2

2

Unable to get connection endpoint. srv_thread_props()  returned an error.

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.14.2

2

Unable to determine connection type. fstat() returned an error: %1!

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.15.2

2

Connection refused. The owner id of the connection named pipe  is not the same user id as that of the Backup Server process. 

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.16.2

2

Error: unable to disable registered procedures.

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.17.2

2

Unrecognized security option `%1!'.

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.18.4

4

The number of service threads must be a positive integer up  to the maximum of %1!. Specified value was `%2!'. 

Explanation: The value specified for -P option is invalid. Restart backup server with a valid value.

2.19.2

2

Invalid verbosity level: A verbosity level specifier must  be an integer from 0 to 3.

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.

3.1.2

2

Unrecognized RPC received--ignored.

Explanation: The session initiator sent an unrecognized RPC. Indicates ad hoc RPC was sent, or a programming bug in Adaptive Server or Backup Server. Contact Sybase Technical Support.

3.2.2

2

Symbol %1! not found in TDS table.

Explanation: Internal message; customers will likely never see it; it is only included here for completeness.

3.3.2

2

%1!: May not specify Backup Server scanning or free-page  clearing for a secondary phase.

Explanation: Internal error, contact Sybase Technical Support. These errors indicate a violation of the dump synchronization protocol of the RPC API.

3.4.2

2

%1!: Must specify Backup Server scanning in order  to clear free pages at LOAD time.

Explanation: Internal error, contact Sybase Technical Support. These errors indicate a violation of the dump synchronization protocol of the RPC API.

3.5.2

2

%1!: Could not lock session %2! to begin  phase. 

Explanation: Internal error, contact Sybase Technical Support. This indicates an error or bug in the Open Server MUTEX mechanism.

3.6.1

1

%1!: Phase %2! is currently active.  Only  one phase may be active at a time.

Explanation: Internal error, contact Sybase Technical Support. Violation of the dump synchronization protocol of the RPC API.

3.7.2

2

%1!: phase %2! already concluded.

Explanation: Internal error, contact Sybase Technical Support. Violation of the dump synchronization protocol of the RPC API.

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.

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.

3.24.2

2

%1!: RPC rejected, phase %2! already concluded.

Explanation: Internal error, contact Sybase Technical Support. Violation of the dump synchronization protocol of the RPC API.

3.25.2

2

%1!: May not submit run lists for phases in which  Backup Server conducts the scan.

Explanation: Internal error, contact Sybase Technical Support. Violation of the dump synchronization protocol of the RPC API.

3.26.2

2

%1! SANITY: parameter data overflows I/O  block.

Explanation: Internal error, contact Sybase Technical Support. Error with dump header or trailer processing in either Server. The total parameter sizes are defined to equal the I/O block size.

3.27.2

2

Invalid RPC sequence at RPC %1!.

Explanation: Internal error, contact Sybase Technical Support. Error in the session initiator (Adaptive Server or Backup Server), a violation of the RPC API.

3.28.2

2

Non-contiguous database map, session %1!, lpn %2!.

Explanation: Internal error, contact Sybase Technical Support. These errors indicate an Adaptive Server programming bug, defective database disk mapping information sent.

3.29.2

2

No virtual mapping for logical page %1!.

Explanation: Internal error, contact Sybase Technical Support. These errors indicate an Adaptive Server programming bug, defective database disk mapping information sent.

3.30.2

2

Bs_normdbmap received an overlapping disk piece.

Explanation: Internal error, contact Sybase Technical Support. These errors indicate an Adaptive Server programming bug, defective database disk mapping information sent.

3.31.2

2

Improper parameter count %1! for RPC %2!.

Explanation: Internal error, contact Sybase Technical Support. Error in the session initiator (Adaptive Server or Backup Server), a violation of the RPC API.

3.32.2

2

Incorrect type for parameter #%1! for RPC %2!;  expected %3! got %4!.

Explanation: Internal error, contact Sybase Technical Support. Error in the session initiator (Adaptive Server or Backup Server), a violation of the RPC API.

3.33.2

2

SANITY: premature last run list.

Explanation: Internal error, contact Sybase Technical Support.

3.34.2

2

SANITY: more stripes than extents.

Explanation: Internal error, contact Sybase Technical Support.

3.35.2

2

RPC %1! refused following previous FAILURE return.

Explanation: Internal error, contact Sybase Technical Support. Error in the session initiator (Adaptive Server or Backup Server), a violation of the RPC API.

3.36.2

2

RPC %1!: parameter %2! may not be NULL.

Explanation: Internal error, contact Sybase Technical Support. Error in the session initiator (Adaptive Server or Backup Server), a violation of the RPC API.

3.37.2

2

SANITY: RPC %1!: expected parameter %2!  got parameter %3!.

Explanation: Internal error, contact Sybase Technical Support. Error in the session initiator (Adaptive Server or Backup Server), a violation of the RPC API.

3.38.2

2

There is no primary phase %1! for secondary phase %2!.

Explanation: Internal error, contact Sybase Technical Support. Violation of the dump synchronization protocol of the RPC API.

3.39.2

2

RPC %1! can only be executed in a slave server. 

Explanation: These errors indicate an Adaptive Server programming error, violation of the RPC API.

3.40.2

2

Illegal length for parameter #%1! for RPC %2!;  expected %3! got %4!.

Explanation: Internal error, contact Sybase Technical Support. Error in the session initiator (Adaptive Server or Backup Server), a violation of the RPC API.

3.41.2

2

Illegal max-length for parameter #%1! for  RPC %2!; expected %3! got %4!.

Explanation: Internal error, contact Sybase Technical Support. Error in the session initiator (Adaptive Server or Backup Server), a violation of the RPC API.

3.42.1

1

%1! is complete (database %2!).

Explanation: Informational message that Backup Server processing for the session is complete (the dump or load command may continue to run, for example, to clear the region of the loaded database above the dump-time high page).

3.43.1

1

Dump phase number %1! completed.

Explanation: Informational message that a dump synchronization phase has completed.

3.44.2

2

The Backup Server is already performing a deferred shutdown;  only one may be active at a time.

Explanation: Shutdown is in progress and will occur when all dumps and loads have completed.

3.45.1

1

Attention received: cancelling deferred shutdown.

Explanation: Internal error, contact Sybase Technical Support.

3.46.2

2

Deferred shutdown wait failed, cancelling deferred shutdown.

Explanation: Internal error, contact Sybase Technical Support.

3.47.2

2

The Backup Server is undergoing shutdown.  Your session will  terminate immediately.  Please reattempt connection later.

Explanation: This message is issued in response to a dump or load command after a shutdown request has been sent but before the Backup Server has actually shut down.

3.48.1

1

The Backup Server will go down immediately.  Terminating sessions.

Explanation: This is the final message sent to the session that issued the shutdown command.

3.49.2

2

RPC %1! does not allow option %2!. 

Explanation: An RPC inconsistency was detected. This could be caused by incompatible releases of Backup Server and Adaptive Server.

3.50.2

2

Non-privileged connection is not authorized to execute privileged  RPC `%1!'.

Explanation: Some RPCs are “privileged,” that is, they can only occur in the context of an Adaptive Server-initiated dump. Users who attempt to programmatically duplicate one of these RPCs are prevented from doing so.

3.51.2

2

Database device #%1!, name %2!  has already been declared as #%3!, name %4!.

Explanation: Internal error, contact Sybase Technical Support. The dump or load command as translated by Adaptive Server does not make sense. The sysdevices table may be corrupt.

3.52.2

2

Database device #%1! has not been declared.

Explanation: Internal error, contact Sybase Technical Support. The dump or load command as translated by Adaptive Server does not make sense. The sysdevices table may be corrupt.

3.53.2

2

Malformed option list received, RPC: %1!.

Explanation: Internal error, contact Sybase Technical Support. The dump or load options as passed from Adaptive Server do not make sense. The problem may be possible to work around by rearranging, adding or removing options to the dump or load command.

3.54.1

1

Waiting for processes to complete.

Explanation: This message is sent to the session issuing a shutdown command if there are outstanding dump or load requests and nowait was not specified.

3.55.2

2

RPC %1!, parameter `%2!': `%3!' is  an invalid value.

Explanation: Internal error, contact Sybase Technical Support. Adaptive Server requested an unknown function.