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?
By David Hollander
I successfully deployed SuperContainer (SC) via the Web Publishing Engine (WPE) of FileMaker Server 11 for years, on a Mac mini (2010) running OS 10.6.8 (Snow Leopard), with no problems. But I ran into the following problem with Mavericks and SC: I upgraded to more modern versions of OS X and FMS by doing a completely clean installation: Formatted the Mac mini's drive; Did a clean installation of OS X 10.9.1 (Mavericks); and Installed FileMaker Server 12v6 without problems. Next, I downloaded the latest SuperContainer from 360Works (v2.896). When I double-clicked the "Mac Installer.app" (also known as "SCInstaller") to deploy SC with FMS, as I did before with FMS11, I was surprised to see this alert pop up: "'Mac installer' is damaged and can't be opened. You should move it to the Trash." Mac Installer is damaged.tiff I tried downloading a fresh copy, using Safari and Firefox; same error. I’d never seen this message before when installing any software, and I found no reports of it in this forum or in TechNet. The icon displayed in the alert window indicated that it was originating from Mac OS Gatekeeper. So the solution I tried was to change the "Security & Privacy" System Preference of Mavericks, under the "General" tab, to "Allow apps downloaded from Anywhere", rather than the more restrictive "Mac App Store and identified developers" option. (Perhaps another option would have been just to control-click the app icon and then select “Open”, to exempt the app from Gatekeeper; I didn't test that.) Apple’s support article on Gatekeeper mentions this “Damaged” app warning message is an indication that “the app has been altered by something other than the developer.” I doubt that any “true damage” is present in the Mac Installer for SC. I think the message appeared because AppleScript scripts get modified after they’re signed. An Apple support article on Mavericks security states: “Some apps and tools, such as AppleScript applications and some legacy tools, modify themselves after signing. These types of apps cannot be opened unless the Gatekeeper setting in Security & Privacy preferences is set to Anywhere” I had only tried the SC Installer on Mavericks, but I suppose the same error might have occurred on Mountain Lion or Lion, since Gatekeeper was introduced with Lion. It appears, for now, that we may need to temporarily disable Gatekeeper (by choosing the "Anywhere" option) in order for SC's Mac Installer to work. David M. Hollander, MD Combined Fields Consulting
According to the following KB article, FMS12 isn't compatible with 10.9:
However, it is possible to get it to work with a few adjustments. The database server works just fine, but WPE does not.
Here is how to get WPE working (based on http://fmforums.com/forum/topic/89802-109-mavericks/#6 with a few corrections)
Open up Terminal
cd /Library/Server/Web/Config/apache2/ Add the following lines to the end of the httpd_server_app.conf file:
Note: they may already be there, commented out, after installing the FileMaker Server
<IfDefine WEBSERVICE_ON> Include '/Library/FileMaker Server/Admin/admin-helper/WEB-INF/conf/fmi-test.conf' Include '/Library/FileMaker Server/Admin/admin-helper/WEB-INF/conf/fm-server-status.conf' LoadModule proxy_ajp_module libexec/apache2/mod_proxy_ajp.so Include '/Library/FileMaker Server/Admin/admin-helper/WEB-INF/conf/mod_proxy.conf' </IfDefine> Some of the modules may be commented out with
#FMI_Configuration_V1 which you will need to uncomment.
Restart your Web server
Restart the FileMaker Server
Restart the Web Publishing Engine
Go to http://<your_server_url>:16000 and perform FileMaker Server 12 Technology Tests in the Troubleshooting section.
Tested 10.9, 10.9.1, FMS 12.0v4. Not tested with 12.0v5, but it should work as well.