May 6, 201510 yr I am trying to set up the program and when I click choose database I get an error saying "Couold not get names for filemaker server. XML web publishing not enabled." I have it enabled on my server...not sure what to do.
May 7, 201510 yr Author on windows server. Would rather not have to re install fms. Its a production server.
May 7, 201510 yr Put in this URL, replacing your server's IP address for yourServer: http://yourServer/fmi/xml/FMPXMLRESULT.xml?-dbnames Let me know what you get when you do that.
May 7, 201510 yr Author this is what i get: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE FMPXMLRESULT SYSTEM "http://192.168.10.60:80/fmi/xml/FMPXMLRESULT.dtd" PUBLIC "-//FMI//DTD FMPXMLRESULT//EN"> -<FMPXMLRESULT xmlns="http://www.filemaker.com/fmpxmlresult"> <ERRORCODE>959</ERRORCODE> <PRODUCT VERSION="13.0.2.296" NAME="FileMaker Web Publishing Engine" BUILD="4/20/2014"/> <DATABASE NAME="" TIMEFORMAT="" RECORDS="0" LAYOUT="" DATEFORMAT=""/> <METADATA/> <RESULTSET FOUND="0"/> </FMPXMLRESULT>
May 7, 201510 yr 959 means XML Web Publishing not enabled. Re-run the deployment assistant (this is not the same as a reinstall). Be sure to check the box for XML Web Publishing. After it finished, repeat that URL query, and verify that the error code is 0 instead of 959. Once you get that working, MirrorSync should be fine.
May 7, 201510 yr Author this is going to sound stupid...but I have been out of this for awhile...where is the deployment assistant again...
May 7, 201510 yr In the web-based server admin console, at the top right corner, click 'server' and select 'edit deployment' from the submenu.
May 7, 201510 yr Author I went through the process but I cant sync. I Get a message that says "Sync failed/aborted" ant the following text: Unexpected response from MirrorSync server: <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html><head><meta http-equiv="refresh" content="0;url=http://finder.cox.net/main?InterceptSource=0&ClientLocation=us&ParticipantID=96e687opkbv4scrood8k84drs6gw5duf&FailureMode=1&SearchQuery=&FailedURI=http%3A%2F%2Faci-fms-02.hosting.cloud%2FMirrorSync%2Fsync%3Fping%3D1%26configurationId%3D2cbbdda1-da0c-4730-821d-108e80b9c9e3%26clientToken%3D%26messageToken%3D%26sessionId%3D12%3A56%3A16x95312802353873848915%26lastSessionId%3D%26random%3D14385474706068634987&AddInType=4&Version=2.1.8-1.90base&Referer=&Implementation=0&method=GET"/><script type="text/javascript">url="http://finder.cox.net/main?InterceptSource=0&ClientLocation=us&ParticipantID=96e687opkbv4scrood8k84drs6gw5duf&FailureMode=1&SearchQuery=&FailedURI=http%3A%2F%2Faci-fms-02.hosting.cloud%2FMirrorSync%2Fsync%3Fping%3D1%26configurationId%3D2cbbdda1-da0c-4730-821d-108e80b9c9e3%26clientToken%3D%26messageToken%3D%26sessionId%3D12%3A56%3A16x95312802353873848915%26lastSessionId%3D%26random%3D14385474706068634987&AddInType=4&Version=2.1.8-1.90base&Referer=&Implementation=0&method=GET";if(top.location!=location){var w=window,d=document,e=d.documentElement,b=d.body,x=w.innerWidth||e.clientWidth||b.clientWidth,y=w.innerHeight||e.clientHeight||b.clientHeight;url+="&w="+x+"&h="+y;}window.location.replace(url);</script></head><body></body></html>
May 7, 201510 yr The error message contains this text: http://finder.cox.net/main?InterceptSource That makes me think that somehow your ISP is blocking or intercepting the message. Can you try syncing on the same local network as where MirrorSync is installed? If you continue to have problems, please use the 'send problem report' link on the main MirrorSync launch page - this will send us your server logs, which has more detailed troubleshooting information.
May 11, 201510 yr Author Still having some issues. I sent in a bug report this morning. Just waiting to here back.
May 11, 201510 yr I haven't see any tickets from mgm75 - did you submit the bug reports with a different name?
May 11, 201510 yr I did not notice any tickets with that name - did you get a ticket # emailed back to you after you submitted the issue?
May 11, 201510 yr Jesse, I responded to marc's ticket in the support system. Marc, regarding this error: both the error in your support ticket and the one listed here look to be problems with resolving the 'act-fms-02.hosting.cloud' hostname. This looks like an internal hostname to me. You may need to configure a separate external hostname/IP address in the hub portion of configuration to be able to sync from outside your network.
May 12, 201510 yr Author think we are almost there. I submitted something this morning. I changed the configuration and the sync starts to work but I get an error and it aborts because of a created date error (i submitted it) and the download link the system generates still has the internal address.
May 12, 201510 yr Author thanks so much for the very responsive support. Everything seems to be working very well now.
September 19, 201510 yr Newbies I am getting the same error. I just updated FMS to 14 and lost connection. This is my readout. 0 error and a list of my database. Still no connection. <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE FMPXMLRESULT SYSTEM "http://localhost:80/fmi/xml/FMPXMLRESULT.dtd" PUBLIC "-//FMI//DTD FMPXMLRESULT//EN"> <FMPXMLRESULT xmlns="http://www.filemaker.com/fmpxmlresult"><ERRORCODE>0</ERRORCODE><PRODUCT VERSION="14.0.1.147" NAME="FileMaker Web Publishing Engine" BUILD="4/24/2015"/><DATABASE NAME="DBNAMES" TIMEFORMAT="" RECORDS="7" LAYOUT="" DATEFORMAT=""/><METADATA><FIELD NAME="DATABASE_NAME" TYPE="TEXT" MAXREPEAT="1" EMPTYOK="NO"/></METADATA><RESULTSET FOUND="7"><ROW RECORDID="0" MODID="0"><COL><DATA>FMServer_Sample</DATA></COL></ROW><ROW RECORDID="0" MODID="0"><COL><DATA>ISP</DATA></COL></ROW><ROW RECORDID="0" MODID="0"><COL><DATA>SHESHA4</DATA></COL></ROW><ROW RECORDID="0" MODID="0"><COL><DATA>SHESHA4Test1</DATA></COL></ROW><ROW RECORDID="0" MODID="0"><COL><DATA>SHESHA4Train</DATA></COL></ROW><ROW RECORDID="0" MODID="0"><COL><DATA>TSSCMar42015</DATA></COL></ROW><ROW RECORDID="0" MODID="0"><COL><DATA>TSSCSC</DATA></COL></ROW></RESULTSET></FMPXMLRESULT>
September 21, 201510 yr Brian, I just responded to your ticket in our support system with instruction for submitting a bug report. If you could do that, we should be able to help you figure this out! Thanks.
September 21, 201510 yr Newbies I found out that my ver. needed to be updated. I was using 2.4 and needed 2.5. 2.4 was looking on port 16020 and MFS 14 did not use that port. Anyway the fix is to upgrade my MirrorSync to 2.5 or better.
Create an account or sign in to comment