MobiLink Synchronization Reference
MobiLink Synchronization Server Warning Messages
This section provides a full listing of warning messages and descriptions.
Warnings with an ODBC state marked "handled by ODBC driver" are not returned to ODBC applications, as the ODBC driver carries out the required actions.
%1!lu! row(s) were ignored in updating table %2!s!
%1!s!
A row in table '%1!s!' could not be updated because it no longer exists in the consolidated database
An error occurred reading the remote client's synchronization log
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
Client synchronization logs will be shown in the MobiLink synchronization server output file or the console
Error detected while using multi-row cursor -- retrying with single row cursor
Expecting %1!ld! parameter(s) in cursor, but found %2!ld!
Expecting at most %1!ld! parameter(s) in cursor, but found %2!ld!
If needed, ODBC cursors will be used, via the Microsoft ODBC Cursor Library, to simulate SQLSETPOS for inserts, updates, and deletes
Ignoring updated row (new values)
Ignoring updated row (old values)
Invalid character data encountered in upload -- substituting '?'
Invalid character data encountered in upload -- using NULL
Invalid character data encountered in upload -- using empty string
Maximum number of database connections set to %1!lu! (must be at least the number of worker threads plus one)
MobiLink table '%1!s!' is damaged
Multi-byte characters truncated on upload
NT Performance Monitor data area failed to initialize
No handle_error script is defined. The default action code (%1!ld!) will decide the error behavior
ODBC Isolation level (%1!s!) is not supported
ODBC function %1!s! is not supported by the driver
ODBC statement option %1!s! has changed from %2!lu! to %3!lu!
ODBC statement option %1!s! has changed from %2!s! (%3!lu!) to %4!s! (%5!lu!)
Publication '%1!s!' is not referenced by any table
Retry on deadlock is disabled. The MobiLink synchronization server is using an internal workaround which requires this setting
Retrying the begin_connection transaction after deadlock in the consolidated database
Retrying the begin_synchronization transaction after deadlock in the consolidated database
Retrying the end_synchronization transaction after deadlock in the consolidated database
Retrying the upload after deadlock in the consolidated database
Retrying the upload. Working around a known ODBC driver problem
Table '%1!s!' has at least one timestamp column. Due to a timestamp precision mismatch, downloaded timestamps can lose precision, resulting in inconsistent data
Table '%1!s!' has at least one timestamp column. Due to a timestamp precision mismatch, uploaded timestamps can lose precision, defeating download filtering
Table '%1!s!' has no entry in the %2!s! table
The -zac switch is deprecated. It is strongly recommended that you use the -za switch instead
The -zec switch is deprecated. It is strongly recommended that you use the -ze switch instead
The client has provided %1!d! authentication parameter(s), but no authenticate_parameters script exists
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
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)
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
The remote client's synchronization log ended prematurely, and was probably truncated
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
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
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'
The upload will be committed and the synchronization aborted. The next time this remote synchronizes, it will ask what happened to the previous upload
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
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
There is no download data script defined for table: %1!s!. Synchronization has the risk of potentially losing download data
There is no upload data script defined for table: %1!s!. Synchronization has the risk of potentially losing upload data
Unable to convert character data for download -- substituting '?'
Unable to convert character data for download -- using NULL
Unable to convert character data for download -- using empty string
Unable to determine current timestamp from consolidated database
Unable to open the file to store the client synchronization logs. The filename is '%1!s!'
Unable to write to the local file that contains remote synchronization logs
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
Unrecognized value (%1!ld!) in ml_user.commit_state. The state information for this user is probably corrupted