This was the scenario when I arrived at the office this morning:
- One database on our FMS 10 server was accessible just fine.
- The other one was not. Trying to access it made FileMaker Pro 10 hang (icon kept spinning).
- Trying to load FMS admin console resulted in some error code which unfortunately I did not record. I think it had to do with Java. This was on my workstation
- On the server machine itself, trying to start the admin console resulted in... nothing. It opened, and promptly closed without fanfare.
Resolution (on Mac OS X):
- I manually stopped and re-started the FileMaker Server processes:
- Open the terminal.
- Type "sudo launchctl stop com.filemaker.fms".
- Authenticate.
- Type "sudo launchctl start com.filemaker.fms".
- Voila'! Well, not quite. Now the admin console was giving me the same error on the server machine.
- Reboot.
- Voila'! This time, really truly! :-)
No comments:
Post a Comment