Original date = UTC 01/01/1601

If BirdieSync 1.x constantly replaces your girlfriend's phone number with your mother's one, this forum is for you...
Post Reply
manek
Posts: 15
Joined: Fri Nov 30, 2007 2:58 pm
Location: Lewes, UK

Original date = UTC 01/01/1601

Post by manek »

I'm still have a problem with syncing events from my TyTN II back to Thunderbird. Syncing from PC to mobile works fine but every event I now create on the mobile device shows in the Birdiesync Deskop Provider log as having an original date of 01/01/1601 (see below for full entry) - even though the event's start date is usually in the future (eg 11/12/2008). What's going on and what can I do to prevent this?

AM running Birdiesync 1.7.04, XP with SP3, Thunderbird 2.0.0.18, Provider for Google Calendar 0.5.1

Original date = UTC 01/01/1601 00:00:00::0000 Local 01/01/1601 00:00:00::0000
Subject = 'Meeting with Dave'
Location = ''
Start date = UTC 17/12/2008 12:00:00::0000 Local 17/12/2008 12:00:00::0000
End date = UTC 17/12/2008 17:00:00::0000 Local 17/12/2008 17:00:00::0000
Is all day = False
Sensitivity = Normal
Meeting status = Undefined
Busy status = Busy
Is alarm set = True
Alarm offset = 135
Note = ''

Birdy
Site Admin
Posts: 3118
Joined: Tue Apr 18, 2006 11:43 am
Contact:

Re: Original date = UTC 01/01/1601

Post by Birdy »

Hello,

Don't believe the traces if it is a non recurrent event. The original date is always null for non recurrent events. This "original date" is only used for the occurrences of a recurrence.

Do you have a pop up window with "Modification failed" ?
Is you calendar read only ?
Do you use the latest version of BirdieSync (1.7.0.4) ?
Do you use the experimental cache mode of the Google calendar provider ? (not recommended)

Could you close Thunderbird. Launch it again. Then after having checked that your calendar is NOT read only,reconnect your mobile device. Then send the logs with "Tools/BirdieSync/Archive logs..." to support(at)birdiesync.com
Thanks.
Birdy

manek
Posts: 15
Joined: Fri Nov 30, 2007 2:58 pm
Location: Lewes, UK

Re: Original date = UTC 01/01/1601

Post by manek »

Hello birdie

1. There's no pop-up window
2. Calendar is not read-only
3. I'm using 1.7.0.4 (see original message)
4. I'm not using experimental cache mode

So I've sent you the logs. Thanks for your help.

Manek

Post Reply