Jump to content
woz

Version 4.0 and Copy Scripts setup step

Recommended Posts

Posted (edited)

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?

Edited by woz
typo

Share this post


Link to post
Share on other sites

Hey Woz,

Would you be available sometime this week for a screen sharing session? We are interested in this as well and would like to see what is going on.

Best,

Zach Lee

360Works Support Team

Share this post


Link to post
Share on other sites

Thanks for your reply Zach and offer to help. I've just solved the problem which was a stoopid one - a permissions problem for the DB's mirrorsync user's priv set. I should have noticed this earlier - Doh!

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


  • Who Viewed the Topic

    1 member has viewed this topic:
    jpscharf 
  • Similar Content

    • By 360Works

      How to Sync with FileMaker Cloud Using 360Works MirrorSync Today we want to let you know that it is completely possible to sync a FileMaker solution hosted on FileMaker Cloud! MirrorSync has been able to handle this task since the release of 3.1. The current version is 4.0 and it remains compatible with FileMaker Cloud.
      FileMaker Cloud leverages Amazon Web Services (AWS) to host your FileMaker solutions in the cloud. Many people are moving to the cloud to cut back on server maintenance time and money. Here at 360Works, we are big fans of AWS - we actually moved all of our hosting to AWS and couldn't be happier. (Jesse Barnum, president of 360Works, presented on the topic of deploying FileMaker Server with AWS at last year?s FileMaker Developers conference.)
      Getting started with MirrorSync for FileMaker Cloud is extremely simple: There's nothing to install and only a couple of steps to get up and running!
      Step 1: Host MirrorSync Elsewhere
      You will need to run MirrorSync on a separate computer from your FileMaker Server, because FileMaker Cloud does not allow the installation of 3rd party software other than plug-ins (MirrorSync is not a plug-in).

      Once you've launched your FileMaker Cloud instance, 360Works can host MirrorSync on a managed AWS server for just $29 a month. There are several other approved hosting providers willing to host MirrorSync as well (see documentation). Alternatively, knowledgeable Linux administrators can host on their own Linux instance with Amazon Web Services.
      Step 2: Enable xDBC
      Because there is no XML Web Publishing Engine with FileMaker Cloud, you must enable incoming access (to port 2399) on your FileMaker Cloud instance in order for MirrorSync to communicate with it using xDBC. You can do this in the AWS console, follow along with this short video:
       
       
      A Few Final Notes
      *You will want to reference our MirrorSync and FileMaker Cloud documentation for complete technical guidelines.
      *Users running regular FileMaker Server on a Mac or Windows computer can install MirrorSync 4 on their own server.
      *We've designed MirrorSync to be something that even a novice user can integrate, but we're standing by when you need more advanced help. If you just want your sync integration to be completed as quickly as possible, we're available to do the work for you directly at our hourly consulting rates. Fill out our message form for advanced help!
       
        Download MirrorSync 4  
       
       
       
       
       
      Connect with us on Social Media for news and updates:


       
         
    • By guit4eva
      Hi guys,
       
      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!
    • By doughogg
      Hi, 
      Our Filemaker database is hosted by 360Works using MirrorSync 3. The owner wants to upgrade to MirrorSync 4 asap. Any idea on when it will be available for hosted databases?
      :-)
      Doug
    • By Lewis Stairs
      Hello,
      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
      Lewis
    • By amallison
      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?
×

Important Information

By using this site, you agree to our Terms of Use.