then it will successfully start and be functional. "FileMaker Pro cannot start Instant Web Publishing because FileMaker Server or another instance of FileMaker Pro is running on this machine." If another version of FileMaker is already running and has taken over the FileMaker network sharing port (5003), then FMP11 will complain with the usual error dialog about IWP like this: Apparently this has something to do with FileMaker's Instant Web Publishing component. Well, in case anyone else encounters this issue, I seem to have accidentally found a workaround.
It's weird, annoying and going to be a major issue if I can't find a solution. I've tried installing the newer JREs and JDKs, made sure that the ist contains "CommandLine", "JNI" and "BundledApp" tags, etc.įMP10 works fine. Now it doesn't, and I can't figure out why. It was working pretty much perfectly before, same version of El Capitan. Removing all traces of any Java VMs just gets me back to the "You need to install Java SE 6 to run this application." And so on.
FMP11 just keeps crashing immediately after the splash screen appears. But that hasn't worked, and neither did trying to force-install the older package. Seems like the only thing I did differently a few weeks ago was to forcibly install the older Apple Java SE 6 package from the recovery partition, while this time I used the updated Apple Java SE 6 package that happily installs on El Capitan. I have tried all of the solutions that have previously been discussed in all Java threads I found in this part of the forum. Now, I have a new MacBook Pro, also running beta 6, but FileMaker Pro 11 absolutely refuses to run after installing the legacy Java SE 6 that it requires. A few days ago I had a MacBook Pro running El Capitan developer beta 6, upon which I had FileMaker Pro 11 Advanced running successfully for weeks.
0 kommentar(er)
