3 Replies Latest reply on Aug 15, 2016 1:47 PM by jdbranum

    Getting Error 307 with FMP 13 client and FMS 15 Host when executing Delete All


      I recently moved a FMP 13.0v5 file to a FMSA 15 host (Windows 2008 Server) and when updating with a separate robot client (FMPA 13.0v5) a script is failing on the Delete All Records script step, capturing error code 307, which translates to "Transaction could not be locked because of a communication error with the host."  This error goes away after running the script a couple times, but comes back if the same file is opened on another client using FMPA 15.  It is repeatable but a bit intermittent, but definitely seems to be associated with files originally developed in FMPA 13 but moved to a FMSA 15 host and accessed by FMP 13 clients after FMP 15 clients have accessed that same file.


      I have observed some similar-type script step failures to execute when an original FMP 13 file was opened by a FMP 14 client and then accessed by another FMP 13 client. 


      Without setting up separate 13 and 15 servers and keeping the solutions and host versions the same, is there any solution to this behavior?



      James Branum

        • 1. Re: Getting Error 307 with FMP 13 client and FMS 15 Host when executing Delete All

          It looks like you may encounter this issue until you upgrade the clients to at least version 14.0.4.


          From TS Gal, on a thread I'll reference:




          The 307 error will show up with any version of FileMaker Pro prior to 14.0.4.  Our Development and Testing department has discovered this occurs when modifying a field on a form in Form view that contains a sorted portal that shows either 0 or 1 row of related data.  A workaround is to go to another record and then back again.


          I have attached this thread as well as thread mentioned by "Markus Schneider" (Thank you!) to the original report.  When more information becomes available, I will post again.



          FileMaker, Inc.


          Error 307 FM 14 Server Upgrade?

          • 2. Re: Getting Error 307 with FMP 13 client and FMS 15 Host when executing Delete All

            Solved (at least for us)


            We had the same problem and it has been a challenge to resolve it. 


            First, it only happened to us on Windows (7.x or 8.x) users.  It started when we enforced a policy of only installing the 64-bit versions of FIleMaker Pro.  It happened to one user, then two, then four ... and it started to get out of control.


            We rolled back about 100 FIleMaker Pro 14.x 64-bit installs to the 32-bit version and the problem stopped immediately.



            • 3. Re: Getting Error 307 with FMP 13 client and FMS 15 Host when executing Delete All

              Thanks to all for your replies. 


              I have developed a workaround, which is to add steps to the script running on the remote file to explicitly display and refresh the window for that file.  I discovered that the error 307 would not occur if I first opened the remote file before running the script on the robot control file running locally on the robot.  The debugger showed that the window for the remote file was remaining hidden during script execution on that file after being triggered from the robot control file.  The remote file script now fully opens that files window and refreshes the window before the delete all step is executed, then closes that window when the script completes.  No errors on two robots now using this technique.  Something apparently "magical" about having a visible window for the remote file. 


              While this workaround technique is OK for a robot, where visibility of a remote file's window has no impact on the "user", it would not be satisfactory in many instances where there is a real human user looking at the screen, when it is desirable for the remote file window to remain hidden during script execution.


              I haven't done enough research yet to conclude whether the error 307 affects only Delete steps, or whether other script step types may also be impacted by the underlying cause.


              James Branum