I used mirrorsync and fms17 without any database corruption for a full year (and fms16 for a year too)

Since I upgraded to fms 18 the database got corrupted twice.

Both times there was the sequence of events like this example of yesterday

9:48 PM a user seems to cancel a sync

1. User canceled action (JDBC URL: jdbc:fmp360://mysite/mydb, SSL: false / SQL statement: SELECT _gSync1, lastErrorMessage FROM MirrorSync WHERE -script='MirrorSync (HeliCloud)' AND -script.param=? / SQL params: [doServerAction

One minute later the user retried

1. Error 802: Unable to open file - Check to make sure that the database file is hosted on FileMaker Server

 In the events.log file

1. 2019-10-16 21:48:49.848 -0400 Error 618 mysite Database or temporary file "filewin:/C:/Windows/Temp/FMTEMPFM2932_5.tmp" is damaged and has been closed. (4294967295)
2. 2019-10-16 21:48:49.848 -0400 Error 681 mysite Closing database "mydb" due to damaged temporary file...

 Any idea of a way to fix this ?

Hey sfpx,

If you submit your logs, I can see the full query, and potentially the cause of the issue.  This error seems difficult to reproduce, so it would be best if you could send in logs for the last day this error occurred.

You can do this by going to your MirrorSync launch page:

http://<your server ip>/MirrorSync

Then click the button labeled:

Send problem report and log files

On the following screen, target the date of when this issue last occurred, so we can examine what happened that day.  This will also open a ticket with us so we can respond to you directly.

 

Thanks,

Joe Martin

 

Out of interest: after the file is closed and you try to open it, what happens?  Does it refuse to open?

(not saying to re-use the bad file at all but I'm trying to get a feel for the severity of the corruption)

4 hours ago, Wim Decorte said:

Out of interest: after the file is closed and you try to open it, what happens?  Does it refuse to open?

(not saying to re-use the bad file at all but I'm trying to get a feel for the severity of the corruption)

Hi Wim,

We had  a bit of discussion about this in the filemaker forums.

The database can be opened using the "option" command. Filemaker then "repairs" the db. No recover needed.