I am trying to set up MirrorSync with a Data Separation Model setup and need a spot of help. I have the DATA file hosted on FMPHost.com, and a local copy of the UI. The documentation states that I must set up MirrorSync in the UI file, then copy that across to the DATA file. However, the setup window only gives me the option to select the DATA file. I'm a bit stuck now, could anyone shed some light on how to proceed?
Thanks in advance!
I've set up 2 previous clients with MirrorSync v3.x without problem but just trying to setup another client using v4.0.
Setting a new config for Server to Pro/Go at step 2 of the hub config (Copy scripts) it does not recognise that the scripts have been pasted in when in fact they have - it refers to 3 scripts but copies 4 - obviously an update is needed. The version of MirrorSync from the java app is "4.0 build 9400" even thought the jnlp file was named MirrorSync3ConfigClient.
I'm using FMS 16, FMPA 16
Error message is "Validation Failed: You will not be able to successfully sync. There is no script called 'MirrorSync'. That must exist before proceeding......".
I've tried from scratch multiple times. Anyone else had this problem with v4.0?
By Lewis Stairs
I noticed that on the server in which MirrorSync is installed, one of the mirrorsync.data files was 12GB+ in size. It is in the filepath formula C://Program Files/360WOrks/SyncData3_MirrorSync/FileMaker Server_x.x.x.x_FileName/mirrorsync.data
Is there any way to either reduce the size of this file, or stop it getting any bigger?
Thank you in advance for you help
Since going from version 2 to 3 of MirrorSync last year we have constantly had MirrorSync crashing the Web Publishing Engine.
Sometimes it says "Error from server: FileMaker XML WPE Web Publishing Engine is not running at <the hosted IP>. Ensure that the WPE is working correctly, and then try this operation again."
But usually it is an Error 10 error. "Error 10 while connecting to http://<the hosted IP>/sync?ping=1&config..."
Early on we made the documented suggested changes for this error, to the connectionTimeout Property in the IIS Manager application. With no noticeable effect.
Most of the time MirrorSync works as expected and does a great job and then clients can't sync and all hell breaks loose.
Do you have any other suggestions for what might be causing this issue?