Amber360Works

This can occur if XML is not enabled. In FileMaker Server 17 you have to enable XML via the command line or terminal using the following command: fmsadmin set cwpconfig enablexml=true

MirrorSync is not currently compatible with NetSuite.

Good Afternoon, Make sure that the tables that the value lists are based on are being synced. If the issue persists after confirming this, please go the the MirrorSync launch page in your web browser (IPAddress/MirrorSync) and select "Send Problem Report and Log Files".

These are located at the following file path. Library/360Works/Applications/Logs/Zulu.YYYY-MM-DD.log

When auto-sync stops working, please select "Email Log File" on the Zulu Sync Admin page and we can look at the logs to see what caused the sync to fail.

This error is indicative of corrupt sync data. In order to fix this, you can try to Repair the sync data. To do so, right-click on the configuration name in the MirrorSync Config Client and select "Repair SyncData". While the sync data is repairing, no syncs can be executed. Try to sync again after this process is complete. If you still get the error, then you will need to "Reset SyncData". Doing so will require new offline files to be distributed.

If you clear out that field on the hosted database, the users will not get prompted to download a new database version.

Try the new build from the link below. This should resolve the issue. If not, please let me know. http://sc.360works.com/SuperContainer/Files/pro/360/NewMirrorSyncBuild

Okay. We are working on a fix for this and I will send you a new build when it is available. Can I get your email address so I can send it to you directly? As long as you do not change the "Database Version" field in the hosted database, the users will not be prompted to download a new file after a sync.

Also, what is the file name?

Do you have a multi-file solution?

Hey Jerry, There is currently no workaround for this, but we could make a custom build that would accomplish this.

That is perfectly fine. We can generate a trial license for you whenever you are ready.

Hi Andrew, Our FileMaker Server to FileMaker server configuration type would accomplish this task. If you would like, we can set up a trial license for you. If you are interested in that, then I will need an email address to send the trial license info to. Also, I would like to note that for long distance syncs, XML is typically the better option, over JDBC.

Good Afternoon, Any errors would be logged in the MirrorSync logs at the following location: Mac: Library/360Works/Applications/logs/MirrorSync.YYYY-MM-DD.log Windows: Program Files\360Works\Applications\logs\MirrorSync.YYYY-MM-DD.log If you want to send those logs to support@360works.com, or submit a bug report, by going to the MirrorSync launch page and selecting "Send Problem Report and Log Files", we could take a look at them also.