![]() ![]()
But it's weird that FMP10 doesn't stop the crash even if it's actively connected to a remote database on port 5003. I'm guessing FileMaker Server or any other process that binds port 5003 might also cause FMP11 to avoid starting its Instant Web Publishing component and thus bypass this startup crash. I don't have any other versions available to test. This seems to work with FMP12 and FMP13 but not with FMP10 for some reason. It's not necessary to actually open a remote file, just attempt to connect to any valid remote FileMaker server process. #Filemaker server 12 java proThe workaround requires that you run the other FileMaker Pro version and at least open the "Open Remote." dialog which causes the application to bind to port 5003. If the other instance is still running then there is no crash on exit. #Filemaker server 12 java updateIf you have JRE 6 update 31 installed, uninstall JRE 6. If the other FileMaker instance quits while FMP11 is running then FMP11 will keep running fine but crash on exit with the same kind of error as the startup crash. On Windows, the FileMaker Server 12 installer installs Java Runtime Environment 6 (JRE 6) update 29. 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. #Filemaker server 12 java installRemoving 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. ![]() It worked fine until this server HDD decided to die, and as they have a half-dozen backup units, they're not interested in dropping the financial equivalent of a midsize car into software.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. This is a legacy issue, please skip and save yourself a headache if you intend to recommend a newer version of Java or Filemaker Pro. Why isn't it seeing/using the RE that I've got installed? However, if I hit terminal (java - version), it shows: When I inspect Console, it shows an error flag:Ĭom.apple.JavaWebStart: No Java Runtime present, requesting install. The symptom is that whenever I attempt to fire up the applet, i get the followingĪny ideas why it's not seeing the RE that I've got installed? Or do I have something else set incorrectly? The issue is that when initializing FMP10, you have to have the Console Admin, and it won't fire up withoutthe correct flavor of Java happy.Īpple has offered a version of Java that's supposedly fixing this, (java for OSX 2014-001), but it's not fixing the issue. #Filemaker server 12 java licenseDue to a 1000 seat license ($$$$), the client won't upgrade. The problem is that within Filemaker Server, the database Admin Console is a Java applet and ONLY runs in legacy versions, and only runs on OSX Server 10.5-10.7. Java HotSpot(TM) 64-Bit Server VM (build 20.65-b04-462, mixed mode) Have an older large environment running FileMaker Pro 10, on OSX 10.7. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |