Re: Problem with Calendar copy to pilot

[JP Rosevear <jpr novell com>]

On Mon, 2004-12-27 at 16:31 +0100, Binerf wrote:
> Hi again,
> 
> I've a new problem with gpilot (2.0.12) to copy my PC calendar to My
> Pilot. See the log of "gpilotd -d":
> ecalconduit-Message:
> ---------------------------------------------------------
> 
> ecalconduit-Message: pre_sync: Calendar Conduit v.0.1.6
> ecalconduit-Message:   Using
> timezone: /softwarestudio.org/Olson_20011030_5/Europe/Paris
> 
> (lt-gpilotd:12127): gpilotd-WARNING **: Copy to pilot failed!
> backupconduit-Message: Making backup of DatebookDB
> backupconduit-Message: Wrote 0 of 0 records, which is good
> backupconduit-Message: Speed1.0_dilP not modified since last sync
> backupconduit-Message: History1.0_dilP not modified since last sync
> backupconduit-Message: ExpenseDB not modified since last sync
> backupconduit-Message: locLDefLocationDB not modified since last sync
> backupconduit-Message: Making backup of MemoDB
> backupconduit-Message: Wrote 2 of 2 records, which is good
> backupconduit-Message: ConnectionMgr50DB not modified since last sync
> backupconduit-Message: NetworkDB not modified since last sync
> backupconduit-Message: npadDB not modified since last sync
> backupconduit-Message: Making backup of PIMsSupportStatus-pdmE
> 
> (lt-gpilotd:12127): backupconduit-WARNING **: error (Cannot Open) in
> opening 'PIMsSupportStatus-pdmE'
> backupconduit-Message: PhoneRegistryDB not modified since last sync
> etodoconduit-Message:
> ---------------------------------------------------------
> 
> Do you have some information about this problem please ?

The problem is unrelated to the calendar syncing.  The backup conduit is
failed to open a particular database on the device.

-JP
-- 
JP Rosevear <jpr novell com>
Novell, Inc.