[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1133
  • Last Modified:

FileMaker Server Console not accessible after Install IIS

Hi there,

I have been running File Maker Server 9 today just fine. Its all been working. I installed IIS on the server and now it will not launch the console. The path it uses is http://localhost:16000 or http://127.0.0.1:16000. If I open a web browser and paste that in I will get the Admin Console Start Page. I then click open console and i get the Application Error: Unable to Launch Application. Name etc.. From : http://localhost:16000

Seems IIS is probably blocking it somehow. Not really that savvy with IIS 7.
0
lemonville
Asked:
lemonville
  • 2
1 Solution
 
lemonvilleAuthor Commented:
Uninstalled IIS and then reinstall FileMaker Server and still getting the same issue. The exception log contains:

java.lang.reflect.InvocationTargetException
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
      at java.lang.reflect.Method.invoke(Unknown Source)
      at com.sun.javaws.Launcher.executeApplication(Unknown Source)
      at com.sun.javaws.Launcher.executeMainClass(Unknown Source)
      at com.sun.javaws.Launcher.doLaunchApp(Unknown Source)
      at com.sun.javaws.Launcher.run(Unknown Source)
      at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.ClassCircularityError: com/oaklandsw/util/c
      at com.oaklandsw.http.Handler.openConnection(Handler.java:19)
      at java.net.URL.openConnection(Unknown Source)
      at sun.net.www.protocol.jar.JarURLConnection.<init>(Unknown Source)
      at com.sun.jnlp.JNLPCachedJarURLConnection.<init>(Unknown Source)
      at com.sun.javaws.net.protocol.jar.Handler.openConnection(Unknown Source)
      at java.net.URL.openConnection(Unknown Source)
      at com.sun.deploy.util.URLUtil.checkTargetURL(Unknown Source)
      at com.sun.deploy.security.DeployURLClassPath$JarLoader.checkResource(Unknown Source)
      at com.sun.deploy.security.DeployURLClassPath$JarLoader.getResource(Unknown Source)
      at com.sun.deploy.security.DeployURLClassPath.getResource(Unknown Source)
      at java.net.URLClassLoader$1.run(Unknown Source)
      at java.security.AccessController.doPrivileged(Native Method)
      at java.net.URLClassLoader.findClass(Unknown Source)
      at com.sun.jnlp.JNLPClassLoader.findClass(Unknown Source)
      at java.lang.ClassLoader.loadClass(Unknown Source)
      at java.lang.ClassLoader.loadClass(Unknown Source)
      at java.lang.ClassLoader.loadClass(Unknown Source)
      at com.oaklandsw.http.Handler.openConnection(Handler.java:19)
      at java.net.URL.openConnection(Unknown Source)
      at sun.net.www.protocol.jar.JarURLConnection.<init>(Unknown Source)
      at com.sun.jnlp.JNLPCachedJarURLConnection.<init>(Unknown Source)
      at com.sun.javaws.net.protocol.jar.Handler.openConnection(Unknown Source)
      at java.net.URL.openConnection(Unknown Source)
      at com.sun.deploy.util.URLUtil.checkTargetURL(Unknown Source)
      at com.sun.deploy.security.DeployURLClassPath$JarLoader.checkResource(Unknown Source)
      at com.sun.deploy.security.DeployURLClassPath$JarLoader.getResource(Unknown Source)
      at com.sun.deploy.security.DeployURLClassPath.getResource(Unknown Source)
      at java.net.URLClassLoader$1.run(Unknown Source)
      at java.security.AccessController.doPrivileged(Native Method)
      at java.net.URLClassLoader.findClass(Unknown Source)
      at com.sun.jnlp.JNLPClassLoader.findClass(Unknown Source)
      at java.lang.ClassLoader.loadClass(Unknown Source)
      at java.lang.ClassLoader.loadClass(Unknown Source)
      at java.lang.ClassLoader.loadClass(Unknown Source)
      at com.filemaker.adminconsole.ui.clients.AdminConsoleJnlpLauncher.<init>(AdminConsoleJnlpLauncher.java:217)
      at com.filemaker.adminconsole.ui.clients.AdminConsoleJnlpLauncher.main(AdminConsoleJnlpLauncher.java:106)
      ... 9 more
0
 
Will LovingPresidentCommented:
The number one issue with the FileMaker Server Admin Console not launching is updating Java to a version later than Java 6 Update 7. Any version later than that with FMS 9 will prevent the Admin Console from launching. Most likely in the course of installing IIS, you updated to a newer version of Java. You will need to roll back the version of Java to the correct version and prevent any future updates. Sometimes this involves just disabling newer version in the Java Control panel, other times it means doing a complete uninstall of Java and sometimes of FMS. Make sure you do a machine restart after re-installing, it sometimes seems to fix things even when a restart is not indicated as needed.
0
 
lemonvilleAuthor Commented:
Genius.

Thanks, well done.
0

Featured Post

Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now