3 Replies Latest reply on Jul 1, 2016 5:58 AM by daveatoh

    Error 959 when using the Filemaker API

    daveatoh

      Hoping someone here is experienced with the Filemaker API and will have a solution to an irritating problem that's developed since an upgrade.

       

      We've implemented a script for a client that pulls data from their Filemaker instance over the Filemaker API and imports it as content in their PHP-based website. All worked well until they upgraded to Filemaker Server 15 (on OS X El Capitan), after which the image URLs (the value of the image field when a record is fetched) that are returned no longer work.

       

      The URLs previously returned image data, but now they just give an XML document like the following:

       

      <fmresultset version="1.0"><error code="959"/><datasource database="" date-format="" layout="" table="" time-format="" timestamp-format="" total-count="0"/><metadata/><resultset count="0" fetch-size="0"/></fmresultset>

       

      Error 959 looks to mean like a certain technology or setting is disabled, but our client is unable to find anything related switched-off in their settings. What do we need to advise them to do to get images working again? Or is there a different way of fetching images over the API in the new version, perhaps?

       

      Many thanks in advance for any thoughts or assistance.

        • 1. Re: Error 959 when using the Filemaker API
          mikebeargie

          You can try re-running the filemaker server deployment wizard. Chances are the OS upgrade disabled something used by the web publishing engine as part of it's security protocols. Running the deployment wizard or reinstalling filemaker server would correct these settings.

           

          Make sure to save your filemaker server config to a file and backup your files before starting.

          • 2. Re: Error 959 when using the Filemaker API
            mikebeargie

            As a quick check, you could also run the following commands in terminal to restart the filemaker server and WPE services to see if it's that simple:

             

            fmsadmin restart server

            fmsadmin restart wpe

             

            Since those would have restarted anyways after a reboot of OSX, I don't think they would work, but it's easy enough that it's worth a try. (note the first command will require the server admin console login user/password, and will also boot anyone that's connected to a database).

            • 3. Re: Error 959 when using the Filemaker API
              daveatoh

              Thanks for your thoughts on this, Mike - really appreciate it.

               

              I'll pass these suggestions on and see what comes of them.