Click here to view and discuss this page in DocCommentXchange. In the future, you will be sent there automatically.

SAP Sybase SQL Anywhere 16.0 » Error Messages » MobiLink Replay utility error messages

 

MobiLink Replay utility error messages sorted by message text


%1 is an incompatible recorded protocol version with this version of MLReplay
%1 is an incompatible recorded protocol version with this version of the Replay API Generator
A file I/O error occurred while MLReplay was accessing the specified simulated client information file
An error occurred while accessing the recorded protocol
An error occurred while trying to read the recorded protocol
An unknown SQL domain type was found while determining the transaction information from the recorded protocol
Column '%1' in table '%2' cannot be NULL
Invalid liveness timeout value %1. The value must be between 0 and 65535
Memory allocation failed
MLReplay could not generate a GUID for the remote ID
MLReplay failed due to the following network error: '%1'
MLReplay failed to initialize correctly
MLReplay failed to initialize correctly for the following reason: '%1'
MLReplay failed to prepare repetition %1
MLReplay failed to prepare repetition %1 for the following reason: '%2'
MLReplay failed to replay a download because MLReplay timed out while waiting for the MobiLink server
MLReplay failed to upload data to the MobiLink server
MLReplay has received an unexpected progress offset mismatch warning from the MobiLink server
MLReplay is sending an unexpected amount of data to the MobiLink server
MLReplay received unexpected data from the MobiLink server
MLReplay timed out while waiting for the MobiLink server to respond
MLReplay was unable to close the recorded protocol file
MLReplay was unable to close the specified simulated client information file
MLReplay was unable to connect to the MobiLink server for the following reason: '%1'
MLReplay was unable to load %1
MLReplay was unable to load the CreateAndInitMLReplayUploadTransaction callback. The CreateAndInitMLReplayUploadTransaction callback is required to use the GetUploadTransaction callback
MLReplay was unable to load the DestroyMLReplayUploadTransaction callback. The DestroyMLReplayUploadTransaction callback is required to use the GetUploadTransaction callback
MLReplay was unable to load the FiniIdentifySimulatedClient callback, which is a required callback
MLReplay was unable to load the FreeAllUploadRows callback. The FreeAllUploadRows callback is required to use the GetUploadTransaction callback
MLReplay was unable to load the GetNumRows callback. The GetNumRows callback is required to use the GetUploadTransaction callback
MLReplay was unable to load the GetNumUploadTables callback. The GetNumUploadTables callback is required to use the GetUploadTransaction callback
MLReplay was unable to load the GetRow callback. The GetRow callback is required to use the GetUploadTransaction callback
MLReplay was unable to load the GetUploadTable callback. The GetUploadTable callback is required to use the GetUploadTransaction callback
MLReplay was unable to load the IdentifySimulatedClient callback, which is a required callback
MLReplay was unable to open the file %1 to get the simulated client information
MLReplay was unable to open the recorded protocol file %1
No error or unknown error
Replay API version '%1' is not valid
Spatial library error: '%1'
Support for spatial is not available for this CPU
The CreateAndInitMLReplayUploadTransaction callback failed. The CreateAndInitMLReplayUploadTransaction callback is required to use the GetUploadTransaction callback
The format of the specified simulated client information file does not match the expected format, which should consist of lines of the form '[username],[password],[remote ID],[last download time]'
The GetUploadTransaction callback failed
The GlobalInit callback failed
The IdentifySimulatedClient callback failed
The number of simulated clients specified using the -n option is greater than the number of simulated clients specified in the simulated client information file
The recorded protocol file is corrupted
The Replay API Generator failed to create %1
The Replay API Generator failed to generate the replay API
The Replay API Generator failed to initialize successfully
The Replay API Generator was unable to close the file, %1
The Replay API Generator was unable to open the file, %1
The Replay API Generator was unable to write to the file, %1
The replay failed
The ReportEndOfReplay callback returned false even though MLReplay determined that the simulated client was successful
The schema information could not be retrieved from the recorded protocol
The schema information read from the recorded protocol could not be parsed successfully
The specified password is too long
The specified remote ID is too long
The specified script version is too long
The specified username is too long
Unable to determine the transaction information from the recorded protocol
Unable to determine whether or not the recorded protocol came from a DBMLSync client
Unable to initialize the log
Unable to open the log file, %1