SeedCode Support Forum

I just installed the update on our fmserver and scaled back to a single cal. I followed the remove google cal steps and re-published that single table.
If I move an event in google, I end up with a new record in fm and then find a duplicate of the moved event (two of the same) on the new date.

Any ideas on what's going on?

Hi Martin,

This is usually what we see when we get out of sync somehow (obviously). Are you seeing any errors in the zulu admin page?

The most common cause of this is the calendarlist records not having their UUID reset, but that's part of the GoogleReset steps, and it sounds like you went through those. Just in case the steps are here:

http://www.seedcode.com/pmwiki/pmwiki.p ... oogleReset

Let us know,
Thanks!

By Resetting the uuid, does that mean deleting the data in that field for the found set? This is what I did.

Thanks

Hi,

Right the event UUIDs should be cleared, but also the calendarlist UUIDs need to be changed to something Google hasn't "seen" before. Even though the calendar has been deleted from Google, it seems to remember the UUID, so if it gets referenced again, this can cause sync problems.

hth,
Jason

I am having a similar issue. I followed the GoogleReset tips and cleard the event and calendarlist UUIDs. When I do the initial sync all works fine, but when I change an event via gCal I get the error below and then dups in filemaker.

"Mon Jan 09 17:23:59 EST 2012: Sync failed: java.lang.IllegalStateException: Hub ID 44 is now mapped to node ID 200001200 instead of the old node ID: 200001198. It is incorrect for a hub ID to point to different node IDs within a SyncJoin. This could potentially be caused by duplicate node IDs / primary keys. Node: com.prosc.fmcaldav.EventsCollectionResource@b717f2"

Hi Justin,

This is a known bug we've found, and will be releasing a new build shortly to correct. If you'd like me to send you a pre-release copy, please contact me at [email protected].

Thanks,
Jason

I had given up on this a while ago. I'd love a copy of the update as well if it works.

JasonYoung wrote:Hi Justin,

This is a known bug we've found, and will be releasing a new build shortly to correct. If you'd like me to send you a pre-release copy, please contact me at [email protected].

Thanks,
Jason

Hi Jason - has this bug been corrected? I am getting the same error.

Chris

Hi Chris,

This has been solved for a few builds back. I sent you a copy of 1.3403 which we'll be releasing publicly in a few days as it also addresses the "-" date separator issue you reported.

Thanks!