Easysync conduits lost after initial install

I had the initial problems installing easysync from ISSI (internal IBM) but followed instructions in another post for deferred install, etc. and all was good, for a while. I only use Easysync to sync with my Notes Calendar, not e-mail, etc.After a week or so, I noticed that my calendar was no longer syncing, when I looked in the hotsync “custom” list, I noticed that none of the conduits for items that could possibly be synced with Notes were listed at all… no calendar or datebook, no e-mail, no to-do’s, etc.

I uninstalled Easysync, reinstalled the palm desktop and reinstalled Easysync again. Things looked reasonably ok but Easysync hung up when I tried to change datasource to my local copy of notes mail/calendar db. But still I was able to sync from home using server copy even though it took a pretty long time. Now I am back at work and the aforementioned conduits have disappeared again.

Any ideas??

Subject: Easysync conduits lost after initial install

I have experienced the same behaviour with easysync 4.2.4 in combination with my Palm Tungsten T3. After rebooting I noticed the conduit for easysync was missing in the list of conduits listed in hotsyncmanager’s Custom menu.

The following works for me:

For the first sync after a reboot (or restart of the hotsync manager), choose synchronize now from within Easy sync (either from the program or through the system tray menu).

Eaysync will prompt to press the hotsync button to start the synchronisation.

After this synchronisation is completed successfully, easysync will (until the hotsync manager is restarted) automagically synchronize Lotus Notes during following hotsyncs.

If you check hotsync manager’s custom systray menu option, you should now see that easysync is listed as a conduit.

If you restart hotsync manager, you will notice easysync is missing once more.

Hope this works for you as well.

Cheers

IRC: Woonjas on EFNet’s notes

Subject: RE: Easysync conduits lost after initial install

I also am experiencing this problem. Found this on the IBM Support site:

http://www-1.ibm.com/support/docview.wss?rs=465&context=SSKTPA&dc=DB520&uid=swg21247670&loc=en_US&cs=UTF-8&lang=en&rss=ct465lotus