I am running Mirror Sync 2 on my developer macbook.  Everything works fine when I'm at the office where I first installed FMServer 14 and Mirrorsync 2.  However, when I change locations and get a different IP address things go south.   FMServer still works, however I can no longer sync to Mirror Sync (even when changing the custom URL variables in the client).  More importantly - I can no longer run the Mirrorsync Configuration java client to modify the configuration.   I can navigate to http://myserver/MirrorSync/ and re-download the client - but it fails with a “Could not parse the launch file. Error at line 0.” when trying to run it.   Everything reverts to normal when I go back to my original network.   I did notice that the configuration embeds the IP address of the FM Server - so I can see why that will be a problem.  However, after changing networks - I cannot even access the configuration to make the changes.

Any ideas of how to handle changing of IP address when moving to different networks?  This mostly happens for demos, and showing a client the sync functionality.

Hi Noel - I was not able to reproduce the problem. Here are the steps that I took:

* Run MirrorSync at my home IP address (192.168.1.100), and access via the MirrorSync admin tool via http://192.168.1.100/MS (I've renamed MirrorSync to just MS to save some typing)

* Leave MirrorSync running, put the computer to sleep and take it to work.

* At work, the configuration client does not work (because it's still pointing to the 192.168.1.100 address). Quit the configuration client, go back to the browser at my work IP address http://96.38.234.11/MS

* Download the MirrorSync client again, it opens and works correctly.

===

If this is different than what you're experiencing, please try these tips:

* If you're on a Mac, use your .local address which can be obtained from System Preferences -> Sharing. If you access it this way, then your IP address shouldn't matter and you can freely switch IP addresses without even needing to relaunch the config client. This is how I normally access MirrorSync, since I do all of my development on a laptop and I often switch locations.

* When you get that error message, there should be some other tabs that show more detailed information about the error. If you want to copy and paste the entire message from each tab, I might be able to offer some advice about the problem.

Hi Jessie - I really appreciate your quick response.   I thought perhaps you had dealt with this issue before - moving to client locations and demoing MirrorSync.  Using my Laptop.local name in place of an IP address solved my problem.  This is an elegant solution.

Unfortunately if I follow your suggested steps to access the config client when changing networks -  I get the above mentioned error - instead of the behavior you would expect.    Suffice it to say - using name resolution instead of a static IP eliminate my pain :-)

On a separate note (perhaps I should start a new topic) I am having difficulty with the Mirrorsync installation on my client's production server.  I sent an email to [email protected] 4 days ago but haven't gotten a response yet.  I have a similar issue - not able to run the config client after installation on a Windows Server 2012 R2, FMS 14 installation.   The initial installation completed successfully (the 360Works service is running and says everything is ok) - however 2 weird things happened.  First, It tried to install apache tomcat although it is obviously an IIS machine.  Second, after the install - the FMS web direct functionality was disabled.  After several hours of trouble shooting I determined that the install process erased the contents of c:\program files\Filemaker Server\Web Publishing\conf\jwpc_prefs.xml.   Luckily I am paranoid about backups.  I simply restored the file and webdirect/publishing started working again.   I tried running the MirrorSync again (without uninstalling first) - this time it detected IIS correctly and did not attempt to install tomcat.   Still no joy on the config client though - so I can't move my dev project into production.  I pride myself in being able to solve these OS/network related issues - but I'm stumped.   I will continue to wait to hear from your support team - or on Monday when I get back to the office - I could copy the error text from the 3 tabs in to this message board and let you take a look at it.   I hate to bother you because I'm sure you have better things to do. - Noel

 

I thought my problem was solved - but I had the same thing happen today using the Laptop.local name resolution for MirrorSync.  My network IP was 10.150.20.209.    I will paste in the error file tab info.

Launch File

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE jnlp PUBLIC "-//Sun Microsystems, Inc//DTD JNLP Discriptor 1.5//EN" "http://java.sun.com/dtd/JNLP-6.0.dtd">
<jnlp spec="6.0+" codebase="http://fouts-family-macbook-pro.local/MirrorSync/" version="1.5" href="MirrorSyncConfigClient.jnlp">
    <information>
        <title>MirrorSync</title>
        <vendor>360Works</vendor>
        <homepage href="http://www.360works.com/MirrorSync"/>
        <description>MirrorSync Configuration Client</description>
        <icon href="MirrorSyncLogo.png" height="300" width="300" />
        <icon href="MirrorSyncLogo.png" height="300" width="300" kind="splash" />
    </information>
    <security>
        <all-permissions/>
    </security>
    
    <update check="always" />
    <resources os="Mac OS X">
        <property name="apple.laf.useScreenMenuBar" value="true"/>
        <property name="com.apple.mrj.application.apple.menu.about.name" value="MirrorSync"/>
    </resources>
    <resources>
        <!--<j2se version="1.6+" initial-heap-size="32M" max-heap-size="256M" java-vm-args="-Xdock:icon=/tmp/MirrorSyncLogo.icns" /> -Xdock:icon does not seem to work-->
        <j2se version="1.6+" />
        <jar href="ConfigClient.jar" download="eager" main="true"/>
        <property name="sun.rmi.transport.proxy.eagerHttpFallback" value="true"/>
        <property name="java.rmi.server.useCodebaseOnly" value="false"/> <!-- See http://stackoverflow.com/questions/17171978/how-do-i-implement-a-plug-in-architecture-using-rmi -->
    </resources>
    <application-desc main-class="com.prosc.mirror.config.ConfigClient">
    </application-desc>
</jnlp>

EXCEPTION

JNLParseException[ Could not parse launch file. Error at line 0.]
    at com.sun.javaws.jnl.XMLFormat.parse(Unknown Source)
    at com.sun.javaws.jnl.LaunchDescFactory.buildDescriptor(Unknown Source)
    at com.sun.javaws.jnl.LaunchDescFactory.buildDescriptor(Unknown Source)
    at com.sun.javaws.Main.launchApp(Unknown Source)
    at com.sun.javaws.Main.continueInSecureThread(Unknown Source)
    at com.sun.javaws.Main.access$000(Unknown Source)
    at com.sun.javaws.Main$1.run(Unknown Source)
    at java.lang.Thread.run(Thread.java:745)
Caused by: org.xml.sax.SAXException: Unexpected end of file from server
java.net.SocketException: Unexpected end of file from server
    at com.sun.deploy.xml.XMLParser.parse(Unknown Source)
    ... 8 more
Caused by: java.net.SocketException: Unexpected end of file from server
    at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:792)
    at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:647)
    at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:789)
    at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:647)
    at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1535)
    at sun.net.www.protocol.http.HttpURLConnection.access$200(HttpURLConnection.java:90)
    at sun.net.www.protocol.http.HttpURLConnection$9.run(HttpURLConnection.java:1432)
    at sun.net.www.protocol.http.HttpURLConnection$9.run(HttpURLConnection.java:1430)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.security.AccessController.doPrivilegedWithCombiner(AccessController.java:782)
    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1429)
    at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity(XMLEntityManager.java:646)
    at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.startEntity(XMLEntityManager.java:1300)
    at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.startDTDEntity(XMLEntityManager.java:1267)
    at com.sun.org.apache.xerces.internal.impl.XMLDTDScannerImpl.setInputSource(XMLDTDScannerImpl.java:263)
    at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$DTDDriver.dispatch(XMLDocumentScannerImpl.java:1164)
    at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$DTDDriver.next(XMLDocumentScannerImpl.java:1050)
    at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(XMLDocumentScannerImpl.java:964)
    at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:606)
    at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:510)
    at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:848)
    at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:777)
    at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:141)
    at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1213)
    at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:649)
    at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl.parse(SAXParserImpl.java:333)
    ... 9 more

WRAPPED EXCEPTION

org.xml.sax.SAXException: Unexpected end of file from server
java.net.SocketException: Unexpected end of file from server
    at com.sun.deploy.xml.XMLParser.parse(Unknown Source)
    at com.sun.javaws.jnl.XMLFormat.parse(Unknown Source)
    at com.sun.javaws.jnl.LaunchDescFactory.buildDescriptor(Unknown Source)
    at com.sun.javaws.jnl.LaunchDescFactory.buildDescriptor(Unknown Source)
    at com.sun.javaws.Main.launchApp(Unknown Source)
    at com.sun.javaws.Main.continueInSecureThread(Unknown Source)
    at com.sun.javaws.Main.access$000(Unknown Source)
    at com.sun.javaws.Main$1.run(Unknown Source)
    at java.lang.Thread.run(Thread.java:745)
Caused by: java.net.SocketException: Unexpected end of file from server
    at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:792)
    at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:647)
    at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:789)
    at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:647)
    at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1535)
    at sun.net.www.protocol.http.HttpURLConnection.access$200(HttpURLConnection.java:90)
    at sun.net.www.protocol.http.HttpURLConnection$9.run(HttpURLConnection.java:1432)
    at sun.net.www.protocol.http.HttpURLConnection$9.run(HttpURLConnection.java:1430)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.security.AccessController.doPrivilegedWithCombiner(AccessController.java:782)
    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1429)
    at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity(XMLEntityManager.java:646)
    at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.startEntity(XMLEntityManager.java:1300)
    at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.startDTDEntity(XMLEntityManager.java:1267)
    at com.sun.org.apache.xerces.internal.impl.XMLDTDScannerImpl.setInputSource(XMLDTDScannerImpl.java:263)
    at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$DTDDriver.dispatch(XMLDocumentScannerImpl.java:1164)
    at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$DTDDriver.next(XMLDocumentScannerImpl.java:1050)
    at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(XMLDocumentScannerImpl.java:964)
    at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:606)
    at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:510)
    at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:848)
    at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:777)
    at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:141)
    at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1213)
    at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:649)
    at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl.parse(SAXParserImpl.java:333)
    ... 9 more

 

 

Hi Noel - I'm sorry but I'm kind of stumped on this issue. I have not had it happen myself, despite switching IP addresses very often. The only advice I can think of is that if it happens again, try the URL manually that you see in the JNLP file. In this section:

 

"http://fouts-family-macbook-pro.local/MirrorSync/" version="1.5" href="MirrorSyncConfigClient.jnlp"

Try combining that into a single URL: http://fouts-family-macbook-pro.local/MirrorSync/MirrorSyncConfigClient.jnlp

Test that in your browser when you get the error message. If it works, then I have no idea what to tell you. If it fails, then hopefully you get some error message explaining the problem.

Hi Jesse - I thought I would update you on this issue.   It appears to be limited to just one location's internal network.  If I access MirrorSync from the external public adddress everything is fine.   This appears to be a singularity, localized to a specific LAN.   Although I haven't determined the cause - it definitely is NOT a MirrorSync issue.  Thank you taking the time to give your input.   Happy to know that the customer is still using MirrorSync with 10 devices syncing 18 tables.  They are very happy. We just have to run future configurations from the public address.  Syncs work both on the private and public IP. - Noel

That is excellent! Thanks for letting me know about the details, and about the happy client :-)