Have an older large environment running FileMaker Pro 10, on OSX 10.7. It's got:
java version "1.6.0_65"
Java(TM) SE Runtime Environment (build 1.6.0_65-b14-462-11M4609)
Java HotSpot(TM) 64-Bit Server VM (build 20.65-b04-462, mixed mode)
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.. Due to a 1000 seat license ($$$$), the client won't upgrade. So we're re-installing on a 10.7 server.
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...
Apple has offered a version of Java that's supposedly fixing this, (java for OSX 2014-001), but it's not fixing the issue.
The symptom is that whenever I attempt to fire up the applet, i get the following
Any ideas why it's not seeing the RE that I've got installed? Or do I have something else set incorrectly?
When I inspect Console, it shows an error flag:
com.apple.JavaWebStart: No Java Runtime present, requesting install.
However, if I hit terminal (java - version), it shows:
java version "1.6.0_65"
Java(TM) SE Runtime Environment (build 1.6.0_65-b14-462-11M4609)
Java HotSpot(TM) 64-Bit Server VM (build 20.65-b04-462, mixed mode)
Why isn't it seeing/using the RE that I've got installed?
NOTE: 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. This isn't happenning.. 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...
