If you havent already, try rebooting the server. The file may be corrupt so you may have to recover the file, export data, and import into clean clone.
Hi Mr vodka
We have rebooted several times, moved servers to make sure its not a hardware / os issue and recovered and re-imported that file.
We are currently trying to recover / import some of the other files to check those as well.
Export the data out as .mer or better yet XML then import into clean clone backups.
I would suggest Save as Compact, but your issue seems more like a true corruption issue.
Hi Mr Vodka
We have done the following:
Clone the database
Import from the old Filemaker database to the new clone and re-host it.
Is doing an export to .xml then re-importing a better option or does it just achieve the same result as the method we have taken?
The safest way is to export out to text based file.
Also the clone should be from a backup copy that you know was "clean". There is no point of cloning your current copy.
Cool - we are currently trying this.
Is there any way you know of of monitoring what is happening on Filemaker Server, iE, what user is running what scripts etc.
The logging in FMserver is pretty minimal.
We would like to try and find what is causing the errors etc.
I am not sure if there is a way to capture each user's script calls. There is a debug mode that can be turned on for the server, but those logs that is produces from debug mode dont do it either.
How would I turn on the debug mode on the server?
What information would this give us?
If I dont reply for a bit its because I am on holiday as of 2 hours time! :o)
I would contact FMI support directly about this.