3 Replies Latest reply on Mar 25, 2013 3:33 AM by wedge-eagle

    Same user timeout-idle problem FMGO - Server


      I am using FMGO 12 off a hosted FM12 server at 888. only been going about 1 month. But just resently (provider did patches last week end may be related ?) have had a couple of times where when entering some data into a layout/record got this error - "your the record changes cannot be saved because this record was being modified by another user while you were disconnected" with Cancel or Revert as only options. There is only one user on the database at present and certainly only one on the record (new record))) this is set up over wifi then over internet with pretty good performance. I am pretty sure it relates to a timeout or disconnect issue with longer times between field entries ? . I have fmreauthenticate set and a long timeout ~ 2 hours.


      Just to clarify- My application is a Client data entry situation but it happens over about a 1 hour period. filling in the layout associated with 1 "new" record" So there can be quite long gaps between feild entry with the Ipad going to sleep.

      But I have managed to re-create the issue after just a couple of minutes when I use poor wi-fi coverage.


      no commit happens untill the layout if finished. So you could enter the top half of the layout have a delay . reopen the ipad at the same place. then enter the bottom half of the layout then commit at the end - only to have to revert and lose the bottom half of the data entry.


      Any idea's - or just re-clarify what I should check. Oh and so far this has happened with a different layouts and differect recoords. - No scripttrigger or portals on these Layouts - At least not associated with the field being entered.


      The record change while disconnected Other user I assume must be the same user.. and FM server is having trouble re-associating the session.


      I do no know what if anything i need to do in the design (to catter better for disconnects ) to have this work better or if its a bug in the patched server sofware.


      Help Please -Thanks Heaps

        • 1. Re: Same user timeout-idle problem FMGO - Server

          Further info -  I just checked the settings on the privilage set for the user.  I have -


          "require re-authentication after the specified minutes in sleep/background. Go only (fmreauthenticate180)"


          and I also have set on - 

          "disconnect user from filemaker server when idle"   Which I have now just changed to off.  hopefully this may be the issue ? more testing tommorow

          • 2. Re: Same user timeout-idle problem FMGO - Server

            This is still happening regardless of disconnect when idle.   I have had to go back to a local db till this can be resolved. (Which is liimting further deplyment of course)

            • 3. Re: Same user timeout-idle problem FMGO - Server

              Bit sad that nobody could give me any idea's . Anyway 888 said that they would set the Cache size smaller - Previously it was set to the maximum.

              I made some changes to commit the records and move to next feild - through many more fileds througout the layouts. As the users would not be hitting blank areas of the layout. This allowed for more data to be saved should they get the "record has been updated error." And get the session less likly to go idle as well.   Been running two weeks the error has not resurfaced.


              I don't understand why a cache would cause the system to hold onto a users session longer. thought it would just allow more data to be held before requiringing a commit.  Anyway its currently working.  A sync based solution would have been better and more robust I believe - But out of my $budget / experience at present.