| -5077 |
The Replay API Generator failed to create %1
|
| -5076 |
%1 is an incompatible recorded protocol version with this version of the Replay API Generator
|
| -5075 |
%1 is an incompatible recorded protocol version with this version of MLReplay
|
| -5074 |
MLReplay has received an unexpected progress offset mismatch warning from the MobiLink server
|
| -5073 |
Invalid liveness timeout value %1. The value must be between 0 and 65535
|
| -5072 |
The specified script version is too long
|
| -5071 |
Replay API version '%1' is not valid
|
| -5070 |
Spatial library error: '%1'
|
| -5069 |
MLReplay failed to prepare repetition %1 for the following reason: '%2'
|
| -5068 |
MLReplay failed to prepare repetition %1
|
| -5067 |
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
|
| -5066 |
Support for spatial is not available for this CPU
|
| -5065 |
MLReplay failed due to the following network error: '%1'
|
| -5064 |
MLReplay failed to initialize correctly for the following reason: '%1'
|
| -5062 |
Unable to determine whether or not the recorded protocol came from a DBMLSync client
|
| -5061 |
The GlobalInit callback failed
|
| -5060 |
The ReportEndOfReplay callback returned false even though MLReplay determined that the simulated client was successful
|
| -5059 |
MLReplay was unable to load the GetRow callback. The GetRow callback is required to use the GetUploadTransaction callback
|
| -5058 |
MLReplay was unable to load the GetNumRows callback. The GetNumRows callback is required to use the GetUploadTransaction callback
|
| -5057 |
MLReplay was unable to load the GetUploadTable callback. The GetUploadTable callback is required to use the GetUploadTransaction
callback
|
| -5056 |
MLReplay was unable to load the GetNumUploadTables callback. The GetNumUploadTables callback is required to use the GetUploadTransaction
callback
|
| -5055 |
MLReplay was unable to load the FreeAllUploadRows callback. The FreeAllUploadRows callback is required to use the GetUploadTransaction
callback
|
| -5054 |
Column '%1' in table '%2' cannot be NULL
|
| -5053 |
The Replay API Generator failed to generate the replay API
|
| -5052 |
The Replay API Generator was unable to close the file, %1
|
| -5051 |
The Replay API Generator was unable to write to the file, %1
|
| -5050 |
MLReplay was unable to load the DestroyMLReplayUploadTransaction callback. The DestroyMLReplayUploadTransaction callback is
required to use the GetUploadTransaction callback
|
| -5048 |
MLReplay was unable to load the FiniIdentifySimulatedClient callback, which is a required callback
|
| -5047 |
The IdentifySimulatedClient callback failed
|
| -5046 |
The GetUploadTransaction callback failed
|
| -5045 |
The CreateAndInitMLReplayUploadTransaction callback failed. The CreateAndInitMLReplayUploadTransaction callback is required
to use the GetUploadTransaction callback
|
| -5044 |
An unknown SQL domain type was found while determining the transaction information from the recorded protocol
|
| -5043 |
MLReplay received unexpected data from the MobiLink server
|
| -5042 |
MLReplay failed to upload data to the MobiLink server
|
| -5039 |
MLReplay was unable to load the IdentifySimulatedClient callback, which is a required callback
|
| -5038 |
MLReplay was unable to load the CreateAndInitMLReplayUploadTransaction callback. The CreateAndInitMLReplayUploadTransaction
callback is required to use the GetUploadTransaction callback
|
| -5036 |
MLReplay was unable to load %1
|
| -5035 |
An error occurred while accessing the recorded protocol
|
| -5034 |
MLReplay was unable to close the recorded protocol file
|
| -5032 |
MLReplay was unable to close the specified simulated client information file
|
| -5031 |
MLReplay failed to replay a download because MLReplay timed out while waiting for the MobiLink server
|
| -5030 |
MLReplay timed out while waiting for the MobiLink server to respond
|
| -5029 |
The Replay API Generator failed to initialize successfully
|
| -5028 |
Unable to determine the transaction information from the recorded protocol
|
| -5026 |
The schema information read from the recorded protocol could not be parsed successfully
|
| -5024 |
The schema information could not be retrieved from the recorded protocol
|
| -5023 |
The recorded protocol file is corrupted
|
| -5022 |
The Replay API Generator was unable to open the file, %1
|
| -5020 |
A file I/O error occurred while MLReplay was accessing the specified simulated client information file
|
| -5019 |
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]'
|
| -5018 |
MLReplay was unable to open the file %1 to get the simulated client information
|
| -5017 |
Unable to initialize the log
|
| -5016 |
Unable to open the log file, %1
|
| -5012 |
The specified password is too long
|
| -5011 |
The specified remote ID is too long
|
| -5010 |
The specified username is too long
|
| -5009 |
Memory allocation failed
|
| -5008 |
MLReplay could not generate a GUID for the remote ID
|
| -5007 |
MLReplay is sending an unexpected amount of data to the MobiLink server
|
| -5006 |
An error occurred while trying to read the recorded protocol
|
| -5005 |
MLReplay was unable to open the recorded protocol file %1
|
| -5003 |
MLReplay was unable to connect to the MobiLink server for the following reason: '%1'
|
| -5002 |
MLReplay failed to initialize correctly
|
| -5001 |
The replay failed
|
| 0 |
No error or unknown error
|
