Hi,

we successfully use the begin_synchronization, end_synchronization and
report_error script events to log the activity of UltraLite clients in
our own audit tables in the consolidated database. Works fine.

Unfortunately, there seems to be an error situation that doesn't
trigger any script event. When the progress counter in the UltraLite
and in the consolidated do not match (which happens when you restore
the disks of the device), the following error occurs on the UltraLite:

SQL Anywhere UltraLite Database Synchronize Utility Version
11.0.1.2405
Sync failed: Synchronization server failed to commit the upload
Results of this synchronization:
Failed with error: SQLE_UPLOAD_FAILED_AT_SERVER (SQLCODE -794)
Download timestamp: 2010-07-28 12:03:46.282000
Upload failed
No ignored rows
No part download remaining
Authentication value: 0 (0x0)

This is what I expected. Here is what you find in the MobiLink log
file:

I. 2010-07-28 11:30:26. <9> Request from "UL 11.0.1.2405" for: remote
ID: d383010c-25d7-4fec-8f48-72eb03ff507b, user name: rdbs01, version:
AurubisPostenMobile_001
I. 2010-07-28 11:30:26. <9> The current synchronization is using a
connection with SPID '5'
I. 2010-07-28 11:30:26. <9> authenticate_user <connection> (no script)
I. 2010-07-28 11:30:26. <9> authenticate_user_hashed <connection> (no
script)
I. 2010-07-28 11:30:26. <9> authenticate_parameters <connection> (no
script)
I. 2010-07-28 11:30:26. <9> modify_user <connection> (no script)
W. 2010-07-28 11:30:26. <9> [10012] 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
I. 2010-07-28 11:30:26. <9> Progress offsets for the publications that
are explicitly involved in the current synchronization
I. 2010-07-28 11:30:26. <9> Subscription id 2: consolidated progress 4
and remote progress 3
I. 2010-07-28 11:30:26. <9> Synchronization failed

Again, as expected. What puzzles me is the fact that the report_error
script is not triggered. How do I know in my consolidated database
that something went wrong?

TIA,

Michael Fischer