Jesse Barnum

OK, I haven't seen that happen in Windows before. If it seems to be a reproducible issue, contact support@360works.com and we'll get your log files to see why that's happening.

Mac or Windows server?

For empty clones, a full copy of the database is created as well as an empty clone. We wish it didn't work this way, but that's a limitation of how the fmsadmin command line tool works.

When the MirrorSync process receives a download request, it: * Pauses the database * Duplicates it into the OS temp directory. If you selected the empty clone option when creating the MirrorSync download URL, then an empty structure-only clone is also created. There is not a way to change the location currently, if you need that we can get you a quote for customizing that. * Resumes the database * Sends the duplicate to the client with gzip compression * Deletes the duplicate (on Windows. With Mac, we don't have permission to delete the duplicates because we are not running as the same user as FMS).

Here is latest build: http://s3.dualstack.us-east-1.amazonaws.com/com.prosc.support.uploads/Outbound/360Works MirrorSync 4.008112.zip?AWSAccessKeyId=AKIAIDQUCQL7APZLJCDA&Expires=1526937572&Signature=Cu%2BVqnHPkCamPsU7G0GZUYPwxlo%3D Heidi, that's great news. I've posted the latest build in case it's helpful.

Hello Heidi - I had a chance to review the log files, it clearly looks like a firewall issue, but then I can telnet in on that port, which clearly means it's not 😛 Would it be possible to give me access to some database on the FM Cloud server (could be a test database) so that I can see if I run into the same problem configuring from my own copy of MirrorSync?

OK, I would recommend setting those values in the spoke (FM) database to validate that they are not empty, that will at least stop MirrorSync from complaining about that. Regarding the foreign keys not working, I'm going to need to see the log files to help with this. To do that please: 1) Modify a record in the spoke to change its foreign key of which record it points to 2) Assuming that fails, go to the MirrorSync launch page in your browser and click the 'Send problem report and log files' link 3) In the problem report page, please be sure to specify the primary key of the child record you changed, the name of the table, the name of the foreign key field, the value you entered in the spoke, and the value that was actually stored in the hub. That will send me the MirrorSync log files, and I can review what happened during the sync to try to figure out why it's setting the wrong value. Oh, one last thing, please reply back here in FMForums with your ticket number so that I can find it easily.

Those fields shouldn't be orange... can you hover over one of them with your mouse and see if there is a tooltip message?

Heidi, can you try the configuration with FMCloud as the hub? When it fails, go to the MirrorSync launch page in your browser and select the option to send a problem report with log files.

Is it possible that you have the data types mixes up in your key fields? What style of primary keys are you using, and what is the data type for those fields in both FileMaker and SQL Server?

Try using telnet to connect to FMCloud on port 2399 - see if it hangs forever or if it connects. If it hangs, then you need to modify the AWS Security group to allow traffic on port 2399.

Try this to test your customization script: In FileMaker Pro, switch to the sync-Modifikation layout, find all records, then run the MirrorSync customization script with no parameters. It should filter your found set to just the records that need to be synced. If it doesn't, there is a problem with the customization script - try re-running with the script debugger enabled to see why it's not filtering.

When that happens we will be all over it :-)

We can't use the FM 16 REST API because it does not run scripts.

Please try this version, it includes the latest FileMaker JDBC driver: http://s3.dualstack.us-east-1.amazonaws.com/com.prosc.support.uploads/Outbound/360Works MirrorSync 4.008011.zip?AWSAccessKeyId=AKIAIDQUCQL7APZLJCDA&Expires=1524257288&Signature=KHb%2FT3E%2FrOiTCo7Z2N6%2FgX7qrMI%3D