Problems after Java & Safari Update

[Tom Kennedy]

I just fininshed with the most recent updates to Leopard Server. When I try to start the FileMaker Admin Console, I get a TextEdit box labeled admin_console_webstart.jnlp. I do not get into the Admin Console.

The IWP part of the server is working, but I cannot get to Admin part of FileMaker 10 Server Advanced.

[mr_vodka]

There seems to be an issue with the Java update.

John May reported it the other day.

http://fmforums.com/forum/showtopic.php?tid/209654/post/333701

Its seems as though the answer is to rebuild the Mac OS X Launch Services database.

[Tom Kennedy]

I tried what I think was covered in the discussion and I still have the same problem when I go to "http://server:16000".

I had to use "localhost" instead of "server" in order to access the "Start Admin Console" page. I also tried "myserver.private" instead of "server" with the same result. I admit that I am a lightweight when it comes to FileMaker Server and Leopard server.

Any ideas?

[Steven H. Blackwell]

The correct syntax is one or the other of these, the first working only when the console is on the same machine as FileMaker Server.

http://localhost:16000

or

http://00.00.00.00:16000

where you substitute the actual Server IP address for the 00 construct. Remember if you are inside the LAN, frequently the IP address will be the internal NAT address and not the public facing IP address.

Steven

[Tom Kennedy]

I have been able to get to the console from another computer in the same network by using the 'http://00.00.00.00:16000' method.

However, I am unable to get to the console from the server itself even if I use the first method 'http://localhost:16000'. I get the same behavior that I got in my first post. I suspect that the only reason I can get to it from another computer is that I have not updated the Java on it yet.

Is there any way I can get to the console on the server where FileMaker Server is installed?

Edited June 25, 2009 by Guest

[Steven H. Blackwell]

I sent a Tweet on this issue last night. Try associating the webstart.jnlp file with the Java Webstart app by telling it to sue that app to open itself. That may well fix the issue.

Steven

[Tom Kennedy]

I don't know how to "associate the webstart.jnlp file with the Java Webstart app" and I have googled for the last 30 min. to see if I can find out how.

Could you provide a few more details?

[Steven H. Blackwell]

On Macintosh OS, do a get info on the webstart,jnlp file and tell it to open with the Java Webstart application.

On Windows, right click and do the same.

Steven

[Tom Kennedy]

Not only can I not find the file "webstart.jnlp", I cannot find the application called "Jave Webstart" on my Leopard server. Is there a step by step remedy available?

Any help will be appreciated.

[bcooney]

I don't think that John May would mind if I quote his fix which worked for me:

"If you're running Leopard (10.5), try entering this in the Terminal

application:

/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/Support/lsregister

-kill -r -domain local -domain system -domain user

(All on one line)

You may need to preface with "sudo" and enter your administrator

password when prompted.

This clears out your Launch Services database, which is responsible for

the associations of documents to apps, which I believe is what has

gotten messed up with the Java update.

- John"

[Tom Kennedy]

Thank you so much.

[dysong3]

HI,

I am trying to resolve this issue too. When I enter "/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/Support/lsregister-kill -r -domain local -domain system -domain user" into Terminal I get a "command not found" message. I am not very au fait with Terminal but I get the feeling that "domain local -domain system -domain user" should be replaced with path names from the computer the server is on, but I am not sure what they should be. Could someone put me on the right track ?

[dysong3]

Try associating the webstart.jnlp file with the Java Webstart app by telling it to sue that app to open itself. That may well fix the issue.

Just to add another pinch of salt, the Java update appears to have eliminated Java Web Start entirely, so this solution is doesn't seem to be a viable one.

[bcooney]

did you start with sudo?

[dysong3]

Yes I did. I either get a "command not found" message or else an invitation to enter my password only to find that I can't enter anything besides "enter" or "return" which of course gets us nowhere.

[lance123]

Hi To All,

I am getting the same problem here with the console .jlnp file not starting. I associated it with the java web start application because it was firing up dashcode. But this had no positive effect. Nothing appears to start at all. Any help here much appreciated.

Thanks,

Lance

Edited July 17, 2009 by Guest