Registered: Feb 2000
Location:
Posts: 8

In performing some low-level analysis on the sync log, I determined that many problems are the result of corrupted data (unrecognizable text string) transferred into the "alarm" field on the Visor. When the Visor encounters the corrupt data in the alarm field, sync stops working. My workaround: (1)in your conduit software,(EasySync, IntelliSync, etc.), temporarily disable the alarm field mapping, (2) resync, (3) re-enable the alarm field, (4) resync again. (5)with luck, problem is resoloved.
A warm resetDOES NOT fix the problem.

Specifics of my environment:
(1)Visor deluxe
(2)NT 4.0 desktop
(3)serial crable
(4)Conduit is Puma's Intelli-sync
(5)Lotus Notes 4.5 (calendar & email).