This is filemaker's official response:
The problem you describe sounds similar to the server.pem file issue on windows for older installers, but I've never heard of it on mac before. That issue is covered here:
I can have him buy a FMP 11 updater, but can't figure out why he should have to do so.
Really? FM10 is almost 4 years old and Mountain Lion is brand new. You can't expect old software to always work on brand new Operating Systems. Especially not given Apple's propensity to not care much about backward compatibility.
To be fair, the same applies to Windows. Even FMS12 will not work on Windows Server 2012 when you use the new filesystem for that OS.
Time to buy FM 11 problem solved. As Wim said you can't expect old softwre to work on new OS's just the way it is.
Thanks everybody. FM 11 it is (unti I sell him on a FM12 upgrade).
I have run into the same issue, when installing FM 10 on a 10.8 machine.
The solution is to copy the server.pem file form a FileMaker version which is installed under an
older version of OSX
Go to FileMaker Pro in the Program folder, then rightclick on the FileMaker Pro app and select 'Show Packet Contents'
Navigate to Contents/MacOS and copy the file 'server.pem' copy this file to the same place in the newly installed
Hope this helps,
Ruben van den Boogaard
install server pem.png 107.2 K
well, at least my response was in the ballpark.
Still the recommendation is to upgrade!
I've had exactly the same issue with a new Mac. FM10 installed and then wouldn't access the remote server. Updated the FM software to 11 and it works with no problem.
P.s. Any idea if the 'server.pem' fix above works with FM9 on Mountain Lion?
P.s.s. Just found this link which explains it: http://bogner.sh/?p=319