Jump to content

JackLKochJr

Members
  • Content Count

    6
  • Joined

  • Last visited

Community Reputation

0 Neutral

About JackLKochJr

  • Rank
    newbie
  1. I am sending the log file right now. I am using the same credential to connect my calendars to my iMacs and my iPhone. None of the privileges that I have set up are specific for iPhone vs. my iMac or MacBook Pro. This was working fine until a couple of weeks ago and I don't remember having changed anything. Thank you again for your ongoing assistance in trying to figure this out.
  2. It is iOS 12 (12.2). The phone (correctly) connects to port 443 and turns on SSL. (It is my iMacs that leave the port field empty (but still turn on SSL) despite my entering it when I created the CalDav account). But, it is only the iPhone that is not synch'ing the Telephone Account calendar (but does synch the other 10 calendars). The iMacs are now (for whatever reason) synch'ing all the calendars.
  3. No problem with the delay. I truly appreciate your effort to help figure this out. I did delete 3 Telephone Contact appointments with the name you indicated. While I can't tell a difference thus far, I do need to make you aware of a slight change that I have noticed since I tried the recommendations you made. I deleted the account on my computers and added them back using System Preferences->Internet Accounts. Apparently, my iPhone is not synch'ing with my iCloud account as I have had to delete it and add it back separately. Interestingly, iCal on my iMacs is now working perfectly and Google Calendar continues to work perfectly. The only place the Telephone Contacts are not showing up is on my iPhone. The only difference I have noticed in the setup is that the iPhone account automatically makes the port number 443 (which is, I believe, correct) whereas the port is empty on my iMacs. But, I would think that if that was the problem, it wouldn't be synch'ing at all.
  4. Thank you for the suggestions. I have tried the recommendations to no avail. I will send you the log file. JLKochJr Zulu.2019-04-12.log.zip
  5. I have been using Zulu for years and have not made recent changes to my set up. In the last week, however, one calendar (my Telephone Contacts calendar) is no longer sync'ing to iCal but does show up in Google Calendar. iCal gives a 500 error (CalDAVAccountRefreshQueueableOperation) but, apparently, only for this calendar (as the rest of the ~7 calendars are sync'ing fine - with both iCal and Google Calendar). Several months ago, I was getting this same iCal error after having updated to Mojave but corrected this by installing a SSL certificate. However, when this occurred, none of the calendars sync'd and they have all been working fine since I installed the SSL certificate. I am using version 1 of Zulu, have it installed on FileMaker Server 16 on an iMac running High Sierra. I tried to re-publish the calendars from the server but this did not fix the problem. Any ideas why only one calendar would not sync?
  6. I integrated a credit care payment gateway (by Nelix Transax) into my database solution about two years ago. What I was not aware of at the time was the fact that the gateway provider requires my server to be scanned on a quarterly basis by ControlScan (even though I do not record or maintain any credit card information in my database). My solution also includes SeedCode's Zulu software creating an iCal server (using port 80). My most recent scan failed as a result of two vulnerabilities: the web server autoindex is enabled and the Apache ETag header discloses inode numbers. In my web server deployment, I have turned off PHP and Instant Web Publishing but I have to use XML (for Zulu). Since FileMaker is using it's own copy of Apache, I can't find how to correct the two vulnerabilities causing my scans to fail. I would certainly appreciate any guidance or insights that anyone might have. (I am hosting my database solution via FileMaker Server Advanced 12.0.5.551 [although the About window STILL says 12.0.3.327] on OSX 10.8.5. I have not upgraded my server machine to Mavericks due to the issue with FM Server 12 and Mavericks preventing the server from sending e-mails.)
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.