| Warning code
|
Level
|
Warning message
|
|---|
| 10040
|
2
|
%1!lu! row(s) were ignored in updating table %2!s!
|
| 10050
|
4
|
%1!s!
|
| 10044
|
5
|
A row in table '%1!s!' could not be updated because it no longer exists in the consolidated database
|
| 10033
|
2
|
An error occurred reading the remote client's synchronization log
|
| 10047
|
4
|
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
|
| 10036
|
2
|
Client synchronization logs will be shown in the MobiLink synchronization server output file or the console
|
| 10039
|
2
|
Error detected while using multi-row cursor -- retrying with single row cursor
|
| 10013
|
4
|
Expecting %1!ld! parameter(s) in cursor, but found %2!ld!
|
| 10014
|
4
|
Expecting at most %1!ld! parameter(s) in cursor, but found %2!ld!
|
| 10002
|
1
|
If needed, ODBC cursors will be used, via the Microsoft ODBC Cursor Library, to simulate SQLSETPOS for inserts, updates, and deletes
|
| 10037
|
5
|
Ignoring updated row (new values)
|
| 10038
|
5
|
Ignoring updated row (old values)
|
| 10025
|
5
|
Invalid character data encountered in upload -- substituting '?'
|
| 10026
|
5
|
Invalid character data encountered in upload -- using NULL
|
| 10027
|
5
|
Invalid character data encountered in upload -- using empty string
|
| 10001
|
1
|
Maximum number of database connections set to %1!lu! (must be at least the number of worker threads plus one)
|
| 10009
|
2
|
MobiLink table '%1!s!' is damaged
|
| 10028
|
5
|
Multi-byte characters truncated on upload
|
| 10042
|
1
|
NT Performance Monitor data area failed to initialize
|
| 10010
|
2
|
No handle_error script is defined. The default action code (%1!ld!) will decide the error behavior
|
| 10003
|
1
|
ODBC Isolation level (%1!s!) is not supported
|
| 10004
|
1
|
ODBC function %1!s! is not supported by the driver
|
| 10006
|
1
|
ODBC statement option %1!s! has changed from %2!lu! to %3!lu!
|
| 10005
|
1
|
ODBC statement option %1!s! has changed from %2!s! (%3!lu!) to %4!s! (%5!lu!)
|
| 10022
|
3
|
Publication '%1!s!' is not referenced by any table
|
| 10008
|
2
|
Retry on deadlock is disabled. The MobiLink synchronization server is using an internal workaround which requires this setting
|
| 10007
|
2
|
Retrying the begin_connection transaction after deadlock in the consolidated database
|
| 10048
|
2
|
Retrying the begin_synchronization transaction after deadlock in the consolidated database
|
| 10049
|
2
|
Retrying the end_synchronization transaction after deadlock in the consolidated database
|
| 10045
|
2
|
Retrying the upload after deadlock in the consolidated database
|
| 10046
|
2
|
Retrying the upload. Working around a known ODBC driver problem
|
| 10016
|
3
|
Table '%1!s!' has at least one timestamp column. Due to a timestamp precision mismatch, downloaded timestamps can lose precision, resulting in inconsistent data
|
| 10015
|
3
|
Table '%1!s!' has at least one timestamp column. Due to a timestamp precision mismatch, uploaded timestamps can lose precision, defeating download filtering
|
| 10024
|
3
|
Table '%1!s!' has no entry in the %2!s! table
|
| 10053
|
1
|
The -zac switch is deprecated. It is strongly recommended that you use the -za switch instead
|
| 10054
|
1
|
The -zec switch is deprecated. It is strongly recommended that you use the -ze switch instead
|
| 10055
|
2
|
The client has provided %1!d! authentication parameter(s), but no authenticate_parameters script exists
|
| 10012
|
2
|
The consolidated and remote databases disagree on when the last synchronization took place. The remote is being asked to send a new upload that starts at the last known synchronization point
|
| 10017
|
3
|
The consolidated and remote databases have different timestamp precisions. Consolidated database timestamps are precise to %1!d! digit(s) in the fractional second while the remote database timestamps are precise to %2!d! digit(s)
|
| 10021
|
3
|
The remote and consolidated databases have different timestamp precisions, and a timestamp value with a precision higher than the lower-precision side was used for conflict detection purposes. Consider using the -zp option
|
| 10035
|
2
|
The remote client's synchronization log ended prematurely, and was probably truncated
|
| 10019
|
3
|
The remote database is not capable of matching the timestamp precision of the consolidated database. Your application, schema, and scripts must contain logic that copes with the precision mismatch
|
| 10020
|
3
|
The timestamp precision mismatch may affect upload conflict detection. Use the -zp option to cause the MobiLink synchronization server to use the lowest timestamp precision for conflict detection purposes
|
| 10018
|
3
|
The timestamp precision mismatch may be resolved by setting the DEFAULT_TIMESTAMP_INCREMENT option on the remote database to %1!d! and TRUNCATE_TIMESTAMP_VALUES to 'On'
|
| 10041
|
2
|
The upload will be committed and the synchronization aborted. The next time this remote synchronizes, it will ask what happened to the previous upload
|
| 10023
|
3
|
The upload will be rolled back and the synchronization aborted. The next time this remote synchronizes, it will ask what happened to the previous upload
|
| 10052
|
1
|
The upload_cursor, new_row_cursor, and old_row_cursor scripts are deprecated. It is strongly recommended that you use the statement-based upload scripts instead
|
| 10056
|
4
|
There is no download data script defined for table: %1!s!. Synchronization has the risk of potentially losing download data
|
| 10057
|
4
|
There is no upload data script defined for table: %1!s!. Synchronization has the risk of potentially losing upload data
|
| 10029
|
5
|
Unable to convert character data for download -- substituting '?'
|
| 10030
|
5
|
Unable to convert character data for download -- using NULL
|
| 10031
|
5
|
Unable to convert character data for download -- using empty string
|
| 10043
|
4
|
Unable to determine current timestamp from consolidated database
|
| 10032
|
2
|
Unable to open the file to store the client synchronization logs. The filename is '%1!s!'
|
| 10034
|
2
|
Unable to write to the local file that contains remote synchronization logs
|
| 10051
|
1
|
Unrecognized ODBC driver '%1!s!'. The functionality and quality of ODBC drivers varies greatly. This driver may lack functionality required for successful synchronizations. Use at your own risk
|
| 10011
|
2
|
Unrecognized value (%1!ld!) in ml_user.commit_state. The state information for this user is probably corrupted
|
