Just setting up a new implementation of Zulu and am running into a problem that I am sure is very simple, but can't seem to find the fix.

I followed the instructions for "Adding iCal support to your filemaker file." Was able to publish and get the verification page in my web browser. However, when I attempt to Subscribe to the calendar in iCal, I get the following error message from iCal:

"There was an unexpected error with the request on subscribed calendars (error -1)"

If I attempt to connect to via CalDav, I am able to create the account, but get this error:

"The server responded with
“500”
to operation CalDAVAccountRefreshQueueableOperation."

Sample Calendar is working correctly.

FMP 12 server 12.0.1.178, Zulu 1.316

Thanks in advance for any advice.

--> Rusty

Looking at the error logs in FMP server here is what I see:

localhost 127.0.0.1 Admin XML 105 496 "/fmi/xml/FMPXMLRESULT.xml?-db=HeraCalendar&-lay=ProscNoSuchTable&-view"


I also tried deleting the record in ZuluCalendarList and republishing. And, logging in as a different user with the same result.

Hi Rusty,

The 105 error means layout is missing. Zulu looks for layouts twice. The first time is looking for the ZuluCalendarList layout itself which is why that layout name is required. Zulu then loops through those records and uses the zulu_layoutname field to find the events associated with that calendar, so one of those operations is failing. Usually it's a CalendarList record that has either a bad or empty layout name referenced in that field that causes this, so I would check them and see if that's the culprit.

Let me know if that helps.
-Jason

I just double checked. The ZuluCalendarList layout is there and it is showing the ZuluCalendarList table. The actual record for the calendar exists, and it has ZuluCalendar as the name of the layout in zulu_layoutName. This does match the name of the actual layout. That layout shows my Appointments table. And uses the layout I copied from the sample database with fields mapped etc... Both layouts are hidden if this matters.

Just deleted the ZuluCalendarList record, and republished. I didn't change anything this time (was adding a filter before and changing the zulu_displayname.

Here are the errors:

localhost 127.0.0.1 ReadOnly XML HTTP:401 0 "/fmi/xml/FMPXMLRESULT.xml?-db=HeraCalendar&-lay=ProscNoSuchTable&-view"
localhost 127.0.0.1 Admin XML 105 496 "/fmi/xml/FMPXMLRESULT.xml?-db=HeraCalendar&-lay=ProscNoSuchTable&-view"

Hmmm, not sure then. Can I get a copy of the file at [email protected] and I'll run it here and see what's going on.
-Thanks

Sure.

If at all possible it would be great if you could take a look at this before the weekend. Would love to have this running on Monday when I see the client.

Thanks!!

Hi Rusty,

I'll do my best, but I'm actually on the road right now so might be tricky. I'll be home on Saturday and will do this Weekend for sure.

-Jason

No pressure haha.

Thank you!

We're all set here. The 105 from the server log was a red herring. We really need to go to the Catalina log for zulu stuff. I sent Rusty the specifics offline...

The issues were a few events that had an end date/time specified without a start date/time. We also need to make sure that the the zulu_ModificationTimestamp field is populated as that's what Zulu uses to determine which events to sync.

Cheers!

Thank you for your help!!