[missing-sync-palmos-talk] Conduit Manager Transport Lib broken during Sync

[Henry Seiden]

After a failed attempt at sync (due to Filemaker Mobile Conduit), the next
sync using Missing Sync broke the Conduit Manager but did not produce a
failure message in Missing Sync's log. Why?

Here's the log where Sync just stopped and failed. Now the Conduit Manager
won't run at all... Gives me a Transport Lib error.

How can I best recover from this? There are several conduits that should
have run and didn't, so I assume that the last that did run somehow broke
the Conduit Manager. Possible???

Notice how the messages about Epocrates follows the first entry while
Filemaker sub-entries precede it. I've always complained about this and now
it seems that it's related to the individual conduits not TMS. Vindication
for you guys!
------------------------------------------------------------------
Sync starting at 2/3/06 8:55 AM (08:55:31) on USB
OK Install
OK Epocrates Install
Syncing Address Book
Syncing Address Book
Syncing Notes
Syncing Notes
Syncing Calendar
Syncing Calendar
Syncing Tasks
Syncing Tasks
OK Entourage Conduit
Epocrates AutoUpdate
OK Epocrates AutoUpdate
   Some records contain characters that are not supported by the device.
   OK Parts TECHWORKS.fp7
   OK MX Records TECHWORKS.fp7
OK FileMaker Mobile 7 with 1 message(s)
Media did nothing
OK MPG
OK SplashID