Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

1 Neutral

About joevmartin

  • Rank

Recent Profile Visitors

1,586 profile views
  1. joevmartin

    Are there System Requirements for Server with 360Deploy

    Hey Duane, We were seeing similar errors with 360Deploy when only one of the migration zip files was stored in the 360Deploy FileMaker file. We have fixed that issue in the latest development build, available here: 360Deploy 2.006.zip If that link doesn't work, try this one: http://s3-external-1.amazonaws.com/com.prosc.support.uploads/Outbound/360Deploy%202.006.zip?AWSAccessKeyId=AKIAIDQUCQL7APZLJCDA&Expires=1534002521&Signature=WVHeTjyCUMRpAYPtTupkvHk183o%3D If you are still having problems, feel free to reach out to our support team at: support at 360works.com Or give us a call at: (770) 234-9293 Thanks, Joe Martin
  2. pfroelicher and I worked this out, this was an issue confined to a developer build of Zulu, this should not affect anyone using the store version of Zulu.
  3. 360Works Support here, We were able to identify the issue, this time OS X Server was completely innocent. There was an exception thrown when trying to read registration info from a preferences file. It's likely that a bad install of Zulu cleared this registration info, but not completely, leaving it in an unknown state. When a later installation tried to load the info, it would fail and Zulu would never start. This fix will be pushed to the store within a few weeks, and the issue itself is rather rare and I doubt anyone else will run into this in the meantime, but if you think you are experiencing this issue, or one like it, email us at: support@360works.com
  4. joevmartin

    Zulu and Google Calendar

    You will need to re-publish your calendars, and reconfigure them in the Zulu admin console, as the process for this has changed. If you want to take advantage of adding attendees to Google events, you will need to map those fields on your field mapping layout, but these are optional. I would download the demo, and install it as a hosting provider so you can test it out before replacing your production version of Zulu
  5. We set up a Google Developer Account, which is necessary to leverage the Google Calendar API. They give you a quota limit, i.e. number of requests you can make per day against their Calendar API. We had to request and increase to this limit as Zulu began to get close to hitting it.
  6. joevmartin

    Zulu and Google Calendar

    The official place for Zulu support is our internal support ticket system. You can open a new ticket by going to the Zulu admin page, and clicking the "Email Log File" link. This will send in your logs as well. We will take a look and get back to you as soon as we can.
  7. If there were no more software updates to Zulu from this point forward, it would continue to work as long as Google did not shut down Calendar API V3. There is currently no mention of Calendar API V4, and V3 will probably be good until V5 is released. So Zulu will work in its current state for a while. Furthermore, we are a small, but strong company with no intention of going anywhere. We have been around for almost 20 years, and we plan to be around for much longer. Zulu is one of our main products and I expect to see continued development on it as long as we are in business.
  8. Halburn, Sorry we missed your post on the 16th. We try to stay on top of these forums, but our internal ticket system is where we focus our primary support. To open a ticket with us and send in your logs, Go to the Zulu admin page, and click the "Email Log File" link. We will take a look at the logs and get back to you as soon as we can
  9. joevmartin

    Zulu and Google Calendar

    Zulu is able to perform a two-way sync with Google, so events created in FileMaker will be added to Google, and when those events are edited in Google, the changes will be synced back to FileMaker. There is some documentation on how to set up Zulu and integrate it into your own solution here: http://docs.360works.com/index.php/zulu Zulu can also filter which events are synced to which calendar, so you can sync an appointment only to the calendar that belongs to a specific manager. This is a bit more advanced than standard syncing, so after you have Zulu set up and running, check out how to filter calendars here: http://docs.360works.com/index.php/Zulu_Multiple_Calendars Zulu reads data from FileMaker and syncs it with calendars, which is a complicated process. I advise using the sample file we provide and getting that set up to get a feel for how zulu works before integrating it into your own solution. Zulu will run, fully-featured, for 2 hours after install in demo mode. So test this out and make sure it is right for you before purchase. The best way to get another 2 hours is to run the installer again. If you have any questions, feel free to contact us at support@360works.com or call at (866) 662-9185 Thanks, Joe Martin
  10. Zulu 2 supports syncing to an existing Google calendar, you can download it here: http://360works.com/filemaker-calendar/ If you have any problems or questions, send us an email at: support@360works.com Thanks, Joe Martin 360 Works
  11. Halburn, We never got repeating events working quite right. They are supported in iCal and other CalDAV applications, but not for Google. These are on our roadmap, and we do hope to have these implemented in the future. Thanks, Joe Martin 360 Works
  12. joevmartin

    FMS14 compatibility

    At the bottom of the "Publish" script, find the script step: Set Variable [$port; Value:If ( $installationOption = "Plugin" ; ":8040" )] Change it to: Set Variable [$port; Value:42424] That should do it, run the script and let me know if that works. Thanks, Joe Martin
  13. joevmartin

    FMS14 compatibility

    Can you access Zulu over port 42424? http://localhost:42424/zulu OSX Server and FMS server running in conjunction isn't a supported configuration for Zulu, but if you can live with accessing it over port 42424 that might be the best way to go about it. Thanks, Joe Martin
  14. joevmartin

    FMS14 compatibility

    The Filemaker Web Server is really a very customized configuration of the Apache Web Server, instantiating it's own web root (/Library/Filemaker Server/HTTPServer/htdocs) and server root variable, among other things. In order for Zulu to work, Filemaker Web Server needs to be up and running, redirecting our requests to the proper channel. While it is possible to further configure the Filemaker Web Server to use a different web root, and open directory, but typically the computer where Filemaker is installed should only be used for Filemaker Server. If you would like to poke around, the conf files for the Web Server reside at: /Library/FileMaker Server/HTTPServer/conf/httpd.conf /Library/FileMaker Server/Admin/admin-helper/WEB-INF/conf/mod-proxy.conf Thanks, Joe Martin Certified FileMaker Developer 360 Works (866) 662-9185
  15. joevmartin

    FMS14 compatibility

    We resolved this issue in a ticket, but I would like to post the answer here as well: First, let's get you on the latest version so we are not running into previously resolved issues, you can download it here: https://s3.amazonaws.com/static.360works.com/360Works+Zulu+1.357.zip After you run the installer, navigate to the file below: Windows: Program Files/360Works/Application/webapps/Zulu/META-INF/context.xml Mac: Library/360Works/Application/webapps/Zulu/META-INF/context.xml remove the port number from this line: Parameter name="jdbc.host" value="" overide="false" So that it reads: Parameter name="jdbc.host" value="" overide="false" Let me know if that fixes the issue. Thanks, Joe Martin Certified FileMaker Developer 360 Works (866) 662-9185

Important Information

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