| 10001 |
1 |
Maximum number of database connections set to %1 (must be at least the number of database worker threads plus one)
|
| 10003 |
1 |
ODBC Isolation level (%1) is not supported
|
| 10004 |
1 |
ODBC function %1 is not supported by the driver
|
| 10005 |
1 |
ODBC statement option %1 has changed from %2 (%3) to %4 (%5)
|
| 10006 |
1 |
ODBC statement option %1 has changed from %2 to %3
|
| 10007 |
2 |
Retrying the begin_connection transaction after deadlock in the consolidated database
|
| 10009 |
2 |
MobiLink table '%1' is damaged
|
| 10010 |
2 |
No handle_error script is defined. The default action code (%1) will decide the error behavior
|
| 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
|
| 10014 |
4 |
Expecting at most %1 parameter(s) in cursor, but found %2
|
| 10015 |
3 |
Table '%1' has at least one timestamp column. Due to a timestamp precision mismatch, uploaded timestamps can lose precision,
defeating download filtering
|
| 10016 |
3 |
Table '%1' has at least one timestamp column. Due to a timestamp precision mismatch, downloaded timestamps can lose precision,
resulting in inconsistent data
|
| 10017 |
3 |
The consolidated and remote databases have different timestamp precisions. Consolidated database timestamps are precise to
%1 digit(s) in the fractional second while the remote database timestamps are precise to %2 digit(s)
|
| 10018 |
3 |
Resolve the timestamp precision mismatch by setting the SQL Anywhere DEFAULT_TIMESTAMP_INCREMENT option on the remote database
to %1 and TRUNCATE_TIMESTAMP_VALUES to 'On'. UltraLite remotes must set the TIMESTAMP_INCREMENT option to %1
|
| 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 server to
use the lowest timestamp precision for conflict detection purposes
|
| 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
|
| 10022 |
3 |
Publication '%1' is not referenced by any table
|
| 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
|
| 10024 |
3 |
Table '%1' has no entry in the ml_table table
|
| 10032 |
2 |
Unable to open the file to store the client synchronization logs. The filename is '%1'
|
| 10033 |
2 |
An error occurred reading the remote client's synchronization log
|
| 10034 |
2 |
Unable to write to the local file that contains remote synchronization logs
|
| 10035 |
2 |
The remote client's synchronization log ended prematurely, and was probably truncated
|
| 10036 |
2 |
Client synchronization logs will be shown in the MobiLink server message log file or the MobiLink server messages window
|
| 10037 |
5 |
Ignoring updated row (new values)
|
| 10038 |
5 |
Ignoring updated row (old values)
|
| 10039 |
2 |
Error detected during multi-row operation, performing rollback before retrying in single row mode
|
| 10040 |
2 |
%1 row(s) were ignored in uploading data into table %2
|
| 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
|
| 10043 |
4 |
Unable to determine current timestamp from consolidated database
|
| 10044 |
5 |
A row in table '%1' could not be updated because it no longer exists in the consolidated database
|
| 10045 |
2 |
Retrying the upload 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
|
| 10050 |
4 |
%1
|
| 10051 |
1 |
Unrecognized ODBC driver '%1'. The functionality and quality of ODBC drivers varies greatly. This driver may lack functionality
required for successful synchronizations. Use at your own risk
|
| 10055 |
2 |
The client has provided %1 authentication parameter(s), but no authenticate_parameters script exists
|
| 10056 |
4 |
There is no download data script defined for table: %1. Synchronization has the risk of potentially losing download data
|
| 10057 |
4 |
There is no upload data script defined for table: %1. Synchronization has the risk of potentially losing upload data
|
| 10064 |
1 |
Unknown users will be added automatically (when there is no authenticate_user script)
|
| 10066 |
1 |
mlstop will not be able to stop this server
|
| 10068 |
5 |
'%1'
|
| 10069 |
5 |
All insert rows for table '%1' will be ignored because there is no upload_insert script for this table
|
| 10070 |
5 |
All update rows for table '%1' will be ignored because there is no upload_update script for this table
|
| 10071 |
5 |
All delete rows for table '%1' will be ignored because there is no upload_delete script for this table
|
| 10072 |
5 |
The update row for table '%1' is a conflict update and this row is ignored
|
| 10073 |
1 |
Windows XP Firewall is enabled, and the MobiLink server is not in the exception list. Clients on remote machines may not
be able to connect to this server
|
| 10074 |
4 |
Unable to fetch the download timestamp from the consolidated database
|
| 10075 |
1 |
Unable to access ORACLE table 'v_$transaction'. Access is needed in order to ensure no data is missed if using timestamp-based
downloads
|
| 10076 |
5 |
A conflict detection script is defined for table '%1', but there is no conflict resolution script
|
| 10077 |
1 |
You are using a DSN created using an out-of-date ODBC driver '%1'. Please use a DSN created with a recommended driver described
at http://www.sybase.com/detail?id=1011880
|
| 10078 |
1 |
Unable to access Microsoft SQL Server virtual table 'sys.dm_tran_active_transactions'. The MobiLink server will not use snapshot
isolation
|
| 10079 |
1 |
The command line option '%1' is ignored
|
| 10080 |
5 |
Retrying the upload after conflicting update in the consolidated database
|
| 10081 |
3 |
Unable to retrieve the column data types for table '%1' from the consolidated database
|
| 10082 |
1 |
MobiLink server has swapped data pages to disk out:%1 in:%2 concurrently used pages:%3
|
| 10083 |
1 |
MobiLink server has suspended network reads on this synchronization due to a limit on concurrent synchronizations
|
| 10084 |
1 |
MobiLink server restarted network reads on this synchronization due to a drop in the number of concurrent synchronizations
|
| 10085 |
1 |
For table '%1', the number of entries in the ml_column table is greater than the number of columns in the remote table
|
| 10086 |
1 |
The ODBC driver '%1' is deprecated
|
| 10087 |
1 |
Unable to access ASE table 'master..systransactions'. The MobiLink server will use system time for download
|
| 10088 |
5 |
The current SQL statement has been running for too long in the consolidated database. The connection ID is %1
|
| 10089 |
1 |
Performance warning -- database connections have been recycled at a rate of %1%%
|
| 10090 |
1 |
Invalid liveness value '%1' -- the minimum value is '%2'. Now the MobiLink server uses the default value '%2'
|
| 10091 |
2 |
A passthrough script failed at the remote client. run_order:'%1' script_id:'%2' error_code:'%3' error_text:'%4'
|
| 10092 |
2 |
Invalid log verbosity options: '%1'
|
