ggt667 Posted January 2, 2017 Posted January 2, 2017 I have a MacMini running macOS Sierra with FM11PA that works; however this FM11PA was installed when there was MacOS X 10.10 on the MacMini. Attempting to install FM11PA on my MB15R fails, well the installer appears to work fine( as pr attached image, ) but launching the app( as pr attached image ) tells me somebody has been fiddling with the installation and that I have to reinstall the application.
ernst Posted January 2, 2017 Posted January 2, 2017 (edited) The installer will indeed not run correctly on Sierra, this appears to be due to the installation package not being compatible with the new installer application. One of the symptoms is that the serial number entry part of the installation script is skipped. Installing on a machine with an older MacOS and then dragging the application over to the machine running Sierra seems to work OK though, just like having Filemaker 11 installed before upgrading to Sierra. Edited January 2, 2017 by ernst
ggt667 Posted January 3, 2017 Author Posted January 3, 2017 (edited) 16 hours ago, ernst said: Installing on a machine with an older MacOS and then dragging the application over to the machine running Sierra seems to work OK though, just like having Filemaker 11 installed before upgrading to Sierra. I tried copying a working FM11PA application and ~/Library/FileMaker from Mavericks and receive the same error as above after dragging in the app to Sierra. This work for me In /Applications folder of the system running Mavericks compress FileMaker Pro 11 Advanced Copy the archive and the ~/Library/Application\ Support/FileMaker folder to the sierra system's /Applications and Application Support folder respectively Decompress Launch For some reason copying the folder did not. Edited January 3, 2017 by ggt667
ernst Posted January 4, 2017 Posted January 4, 2017 Probably some permission thing that got resolved by de-compressing the folder on the target machine.
MonkeybreadSoftware Posted January 4, 2017 Posted January 4, 2017 Maybe someone at FileMaker could find the time to code sign all old installers with current certificate? Not sure if they do, but we could of course sign them ourselves.
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now