Hi,

I have a dbmlsync service that is running every minute. Normally the
sync will work fine, but once a while, a tcpip 10054 error is
encountered followed by a "SQL statement failed: (-101) Not connected
to a database" and the dbmlsync service will just died. Only after
restarting the service, will the synchronisation carry on.

Appreciate some help here in identifying why the service will die off
instead of resuming the sync on the next minute after the tcpip error.

Thanks.

PS : Connecting to cons DB via wireless Access Point
Remote DB : ASA 9.0.1.1751 running on Win XP
Cons DB : ASA 9.0.1.1922 running on Windows 2003

Log as attached below. Sometimes a "No log operation at offset" is also
encountered
like the one below, but sometimes it does not appear with the tcpip
error.
--------------------------------------------------------------------------
I. 01/21 17:46:01. Begin synchronizing 'REGULAR_SYNC' for MobiLink user
'USER1'
I. 01/21 17:46:01. Connecting to MobiLink server at
'host=SERVER1;port=2439' using 'dbmlsock9.dll'
I. 01/21 17:46:01. Uploading header
I. 01/21 17:46:01. Begin upload
I. 01/21 17:46:01. Uploading table operations
I. 01/21 17:46:01. Log scan ended at offset 0025516865
I. 01/21 17:46:01. Waiting for MobiLink to apply upload
E. 01/21 17:46:53. Communication error occurred while receiving data
from the MobiLink server
E. 01/21 17:46:53. Unable to read from the 'tcpip' network connection.
Unable to read 2 bytes. The system-specific error code is 10054 (hex
00002746).
I. 01/21 17:46:53. The user authentication value is 1000.
E. 01/21 17:46:53. Download aborted
I. 01/21 17:46:53. Disconnecting from MobiLink server
I. 01/21 17:46:53. Discarded memory to be recovered at next complete
rescan: 0 bytes.
I. 01/21 17:46:53. Complete log scan required.
I. 01/21 17:46:53. Synchronization completed
I. 01/21 17:46:53. Disconnecting from remote database
I. 01/21 17:46:53. Connecting to remote database
I. 01/21 17:46:53. Disconnecting from remote database
I. 01/21 17:46:53. Next sync scheduled on Jan 21 05:47:00pm
I. 01/21 17:46:53. Log scan starting at offset 0025516432
I. 01/21 17:46:53. Processing transaction logs from directory
"c:\data\"
I. 01/21 17:46:54. Processing transactions from active transaction log
I. 01/21 17:46:57. Transaction log renamed to: c:\data\060121AA.LOG
I. 01/21 17:46:57. Processing transaction logs from directory
"c:\data\"
I. 01/21 17:46:57. Transaction log "c:\data\050117AA.LOG" starts at
offset 0015781831
I. 01/21 17:46:57. Processing transactions from transaction log
"c:\data\050117AA.LOG"
E. 01/21 17:46:57. No log operation at offset of 0025517202 in the
current transaction log
I. 01/21 17:46:57. Hovering at end of active log
I. 01/21 17:46:57. Discarded memory to be recovered at next complete
rescan: 0 bytes.
I. 01/21 17:46:57. Complete log scan required.
I. 01/21 17:46:57. Synchronization completed
E. 01/21 17:46:57. SQL statement failed: (-101) Not connected to a
database