Jump to content

filemaker mirrorsync jdbc error cloud requires version 16.0 or later


This topic is 2188 days old. Please don't post here. Open a new topic instead.

Recommended Posts

Goal - use MirrorSync with database hosted on FileMaker Cloud, using MirrorSync hosted on a Windows Server.

Error - filemaker mirrorsync jdbc error cloud requires version 16.0 or later

MirrorSync version 3.17

FileMaker Cloud 1.16.1.18

Steps to reproduce

1. run mirrorsync

2. create filemaker client to server config

3. configure mirrorsync to use hosted version

4. configure publishing engine / database server to use cloud

5. put any database user, pass or name - it doesn't matter what you put - real or not real

6. you will error -  filemaker mirrorsync jdbc error cloud requires version 16.0 or later

 

 

 

Screen Shot 2018-03-14 at 3.26.20 PM.png

Screen_Shot_2018-03-14_at_3_26_24_PM.png

Link to comment
Share on other sites

  • 4 weeks later...

Hi,

I am trying to sync an FM Cloud server and ran into the same error. Just found this posting--I downloaded the link that Jesse sent above and used the package uninstaller to uninstall and re-install MirrorSync.

No luck for me--I am still getting the same JDBC driver error as above.

Any thoughts?

Link to comment
Share on other sites

With the new version and some cleanup, I was able to get past the JDBC version error.

I now get timeout errors both when 1. setting up config to try to use FMCloud as the Hub (says I might not have 2399 open but I do), or 2. if trying to use FMCloud as the spoke instead (get this error on sync):

JDBC connection to database 'NameGeneratorPhone' on FileMaker Server at '*****.fmi.filemaker-cloud.com' timed out after 20 seconds. Try closing and re-opening the database on FileMaker Server.

Link to comment
Share on other sites

I do have 2399 open...double-checked on this:

Nmap done: 1 IP address (1 host up) scanned in 4.55 seconds

Heidis-MBP:~ heidiporter$ nmap ****.fmi.filemaker-cloud.com

Starting Nmap 7.70 ( https://nmap.org ) at 2018-04-16 18:32 EDT

Nmap scan report for *******.fmi.filemaker-cloud.com (<ip address>)

Host is up (0.047s latency).

rDNS record for ****: ec2-*****.compute-1.amazonaws.com

Not shown: 996 filtered ports

PORT     STATE SERVICE

80/tcp   open  http

443/tcp  open  https

2399/tcp open  fmpro-fdal

5003/tcp open  filemaker

 

Nmap done: 1 IP address (1 host up) scanned in 4.66 seconds

Edited by HeidiPorter
hostname and ports
Link to comment
Share on other sites

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?

Link to comment
Share on other sites

HI Jesse,

I'm moving some things over to a clean demo laptop, so will also install MirrrorSync there and see what happens.

Let me do that first, and see what happens. 

Thanks,

--Heidi

Update:   On the clean demo laptop, I am able to sync FMCloud1 to FMCloud2 just fine.

Thanks!

--Heidi

Link to comment
Share on other sites

Link to comment
Share on other sites

This topic is 2188 days old. Please don't post here. Open a new topic instead.

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
×
×
  • Create New...

Important Information

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