Solved

FileMaker Server Console not accessible after Install IIS

Posted on 2011-03-16
3
1,120 Views
Last Modified: 2012-05-11
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
Comment
Question by:lemonville
  • 2
3 Comments
 
LVL 1

Author Comment

by:lemonville
ID: 35153509
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
 
LVL 25

Accepted Solution

by:
Will Loving earned 500 total points
ID: 35153686
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
 
LVL 1

Author Closing Comment

by:lemonville
ID: 35161592
Genius.

Thanks, well done.
0

Featured Post

VMware Disaster Recovery and Data Protection

In this expert guide, you’ll learn about the components of a Modern Data Center. You will use cases for the value-added capabilities of Veeam®, including combining backup and replication for VMware disaster recovery and using replication for data center migration.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Having just upgraded from Filemaker 11 to Filemaker 12 over the weekend, we thought we would add some tips for others making the same move.  In general, our installation went without incident. Please note that this is not a replacement for Chapter 5…
This article explains how to install and use the NTBackup utility that comes with Windows Server.
This tutorial will give a an overview on how to deploy remote agents in Backup Exec 2012 to new servers. Click on the Backup Exec button in the upper left corner. From here, are global settings for the application such as connecting to a remote Back…
This tutorial will walk an individual through the steps necessary to configure their installation of BackupExec 2012 to use network shared disk space. Verify that the path to the shared storage is valid and that data can be written to that location:…

785 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question