Error code
|
Error message
|
---|
-10094
|
Expecting %1!ld! authentication parameter(s) from client, but received %2!ld! for script %3!s!
|
-10093
|
There is no download data script defined for table: %1!s!. If you want to be able to synchronize anyway, with the risk of potentially losing download data, use the -fr switch
|
-10092
|
There is no upload data script defined for table: %1!s!. If you want to be able to synchronize anyway, with the risk of potentially losing upload data, use the -fr switch
|
-10091
|
This connection will be abandoned due to previous errors
|
-10090
|
The client cannot find the consolidated progress offset from the client transaction log(s)
|
-10089
|
Client is unable to process truncate table request for table '%1!s!'
|
-10088
|
Unable to load entry points from dll: '%1!s!'
|
-10087
|
Version mismatch with dll : '%1!s!'\nExpected version: %2!d! got version: %3!d!
|
-10086
|
Cannot load dll: '%1!s!' for Script Language: '%2!s!'
|
-10085
|
LANG: %1!s! = Failed to allocate database connection
|
-10084
|
LANG: %1!s! - Failed to attach worker thread
|
-10083
|
Unable to delete user name '%1!s!' from the ml_user_table
|
-10082
|
Unable to initialize the resource DLL '%1!s!'
|
-10081
|
The MobiLink synchronization server DLL version does not match the data layer DLL version
|
-10080
|
Unable to execute script '%1!s!'
|
-10079
|
The length of the name of a publication, table, or column cannot be retrieved from the upload stream
|
-10078
|
The publication, table, or column name received from the client is too long: the length is %1!d!
|
-10077
|
The MobiLink synchronization server was unable to modify the error message using the modify_error_message script
|
-10076
|
The MobiLink synchronization server was unable to calculate the timestamp precision on the consolidated database using the ml_scripts_modified table. Timestamp precision related warnings will not be generated
|
-10075
|
Required ODBC function %1!s! is not supported by the driver
|
-10074
|
Unable to update table '%1!s!' using %2!s!
|
-10073
|
Unable to delete from table '%1!s!' using %2!s!
|
-10072
|
Unable to insert into table '%1!s!' using %2!s!
|
-10071
|
Unable to fetch from table '%1!s!' using %2!s!
|
-10070
|
No server connection string specified
|
-10069
|
Unable to initialize consolidated database interface
|
-10068
|
Unable to initialize authentication subsystem
|
-10067
|
Unable to allocate a connection
|
-10066
|
Unable to initialize ODBC
|
-10065
|
Unable to COMMIT Transaction: %1!s! -- Attempting to ROLLBACK
|
-10064
|
Unable to ROLLBACK Transaction: %1!s!
|
-10063
|
An error occurred while uploading an updated row into table '%1!s!'. The updated column values are as follows:
|
-10062
|
An error occurred while uploading a deleted row into table '%1!s!'. The deleted column values are as follows:
|
-10061
|
An error occurred while uploading an insert row into table '%1!s!'. The inserted column values are as follows:
|
-10060
|
Memory allocation failed
|
-10059
|
A protocol error occurred when attempting to retrieve the remote client's synchronization log
|
-10058
|
Unable to open %1!s!
|
-10057
|
Invalid password for user %1!s!
|
-10056
|
User name '%1!s!' not found in the ml_user table
|
-10055
|
Unable to authenticate user %1!s!
|
-10054
|
Unable to insert user name '%1!s!' into the ml_user table
|
-10053
|
The user name '%1!s!' is already synchronizing. Concurrent synchronizations using the same user name are not allowed
|
-10052
|
The %1!s! script returned %2!ld!
|
-10051
|
Internal error: wrong function '%1!s!' called. Please contact technical support
|
-10050
|
Expecting %1!ld! columns in cursor, but found %2!ld!
|
-10049
|
Too many bind parameters in script (expecting %1!ld! but found %2!ld!): %3!s!
|
-10048
|
Expecting at least %1!ld! parameters in script, but only found %2!ld!: %3!s!
|
-10047
|
Expecting %1!ld! parameters in script, but only found %2!ld!: %3!s!
|
-10046
|
Unable to allocate an input/output cursor
|
-10045
|
Cannot directly determine the name of the table referenced by the cursor. The table name is required for inserts, updates, and deletes when using the Microsoft ODBC Cursor Library
|
-10044
|
INTERNAL ERROR: occurred while storing a BLOB -- write
|
-10043
|
INTERNAL ERROR: occurred while retrieving a BLOB -- zero length
|
-10042
|
INTERNAL ERROR: occurred while retrieving a BLOB -- null
|
-10041
|
INTERNAL ERROR: occurred while retrieving a BLOB -- read
|
-10040
|
Extraneous data found in upload stream
|
-10039
|
Scripts cannot be defined as NULL
|
-10038
|
A downloaded value for table %1!s! (column #%2!ld!) was either too big or invalid for the remote schema type
|
-10037
|
Unable to launch the command: (%1!s!). The system error code is %2!d!
|
-10036
|
Download stream encountered error in remote database
|
-10035
|
Download failed with client error %1!d!
|
-10034
|
No download confirmation from remote database
|
-10033
|
The row is too big. The size (%1!ld! bytes) exceeds the maximum allowable size (%2!ld! bytes)
|
-10032
|
Upload failed with client error %1!d!
|
-10031
|
An error occurred when trying to store progress information in the consolidated database
|
-10030
|
A network read failed. Unable to read data from the remote client
|
-10029
|
Attempt to set non-null column to null
|
-10028
|
Unable to connect to the consolidated database. Aborting the synchronization
|
-10027
|
Unable to generate scripts for version '%1!s!'
|
-10026
|
The upload stream is too short: should be at least %1!d! bytes, but received %2!d! bytes
|
-10025
|
The %1!s! cursor is unexpectedly undefined
|
-10024
|
Unrecognized domain id %1!d!
|
-10023
|
The remote database may have been restored from backup, or perhaps user name '%1!s!' is being used by different remote databases. Set ml_user.commit_state to zero to re-enable synchronizations for this user
|
-10022
|
The synchronization sequence number stored in ml_user.commit_state is negative. Set this value to zero (0) to re-enable synchronizations for user '%1!s!'
|
-10021
|
Unable to retry the current transaction after deadlock in the consolidated database. The retry limit has been reached
|
-10020
|
Unable to flush scripts
|
-10019
|
Error fetching table script %1!s!.%2!s!
|
-10018
|
Error fetching connection script %1!s!
|
-10017
|
Protocol error: there is no publication that contains table '%1!s!'
|
-10016
|
Cannot convert '%1!s!' to Unicode
|
-10015
|
Protocol error: client requests an unsupported capability (%1!s!)
|
-10014
|
Protocol error: an invalid timestamp precision of %1!d! was sent from the remote
|
-10013
|
Version '%1!s!' not found in the ml_script_version table. Cannot synchronize
|
-10012
|
There are no registered script versions. Unable to synchronize a client created prior to version 7.0.0
|
-10011
|
Unable to determine the remote version
|
-10010
|
Unable to determine the remote user password
|
-10009
|
Unable to determine the remote user name
|
-10008
|
Unable to load UNILIB collation expansion factor: error %1!d!
|
-10007
|
Unable to load UNILIB collation %1!d!: error %2!d!
|
-10006
|
Collation not supported by this server
|
-10005
|
Old versions of MobiLink clients cannot ping the MobiLink synchronization server
|
-10004
|
Protocol version mismatch
|
-10003
|
Memory allocation failed, attempted to allocate %1!lu! bytes
|
-10002
|
Consolidated database server or ODBC error: %1!s!
|
-10001
|
Protocol error
|
0
|
No error or unknown error
|