Jump to content
Server Maintenance This Week. ×

FM Server 12 crashes approx every 2 weeks on MySQL import scheduled script


This topic is 4109 days old. Please don't post here. Open a new topic instead.

Recommended Posts

Hi,


We are severely regretting the Filemaker Server 12 upgrade. It has
been one issue after another since doing so. Most of the petty issues
are worked out now except for one major recurring issue that we never,
ever had a problem with in FMS10 or 11. We have a scheduled script that
imports orders from 2 websites every 5 minutes throughout the day. This
script and our server had run for 2 years with FMS 11 without stopping
and without any issues of any kind. The machine was restarted on
occasion for updates, but the FMServer never stopped running once on its
own. About a week after upgrading, the script froze and somehow emptied
Primary Key field in the entire Line Items table so we had all of the
orders with no line items. We modified the script to not include any
script steps referencing this field in the final Line Items table(set
the field in a Temp table first then imported). Approximately 2 weeks
later, the exact same thing happened again, all line item Primary Keys
gone. It  occurred on an approximately bi-weekly basis for 2 months so
we shut the script off and now have been running it manually about every
10 minutes to 30 minutes with no issues for 6 weeks. We do not want to
have to keep doing this manually. The script itself seems to work
beautifully as long as 2 weeks have not elapsed on the server schedule
or if it is run manually. Since the script is quite long and
complicated, it is difficult to pinpoint what step(s) might be causing
this. The server log just ends after the script starts and adds no more
entries. If we restart FM Server it freezes again on the first run. If
we restart the computer, it runs for 2 weeks again. There are no other
scheduled scripts running when the freeze happens.  We are now going to
go through and painstakingly log the script steps to see if we can
record when the stoppage is happening in the script. Although since it
runs a few hundred times without error, I'm thinking this will not shed
any light on the actual cause of the issue.  Any other suggestions?


Mac OS 10.7.5


2Ghz i7


8GB RAM


Thanks in advance for any help,


Dave

 

Link to comment
Share on other sites

I would close the files, stop the database service, and open the files in FileMaker Pro Advanced.  I would then run a consistency check on them.. A consistency check, not a recover operation.  I'd then read the log generated by the consistency check to see what it has to say.

 

Steven

Link to comment
Share on other sites

This topic is 4109 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

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