I have had somehting similar happen with Pro clients. Usually this happens on a quick restart or launching application from two users on the same machine at the same time. Not much, but hope it helps.
It's a known issue.
Re-enter your license key and you should be fine until the next reboot.
Restarting a machine is a known issue that hoses the server? That seems pretty major.
Your solution didn't work for me. Re-entered the license key and I still couldn't open any of the databases. I also tried removing a database from the Admin panel (which worked) and then re-uploading a new version of it. The upload worked (which illustrates that the server is actually running) but the database can't be opened.
I'm going to uninstall FM Server, delete all of the directories in the Library, then re-install and start over. And hope I never have to restart the machine.
When you will restart the machine, try stopping FMS before do it.
As my original post mentions, I initially stopped FMS (and gave it ample time to complete the process) before shutting down the machine.
To solve this problem, computer name and FileMaker Servername should be the same.
You can change your computer name from Apple Menu -> System preferences -> Sharing.
FileMaker Server name can be changed at Admin Console -> General Settings
Don´t forget to restart your computer after changing the names.
That worked. Thanks!
Oddly enough, it still gives the same "Another copy of Filemaker Server is running with this license..." error message in the log, but the databases open and can be accessed with FM Pro Advanced (and I assume with FM Pro) and WebDirect.
it still gives the same "Another copy of Filemaker Server is running with this license..." error message in the log
Maybe it´s and old log. Check the time of that log.
No, it wasn't an old log. It used the new machine name (I had changed both the machine name and the server name) and was timestamped for when I restarted.
Sorry my misreading, I thought about it is running twice the service, but seems bonjour registering or using result in FMS bug...
I have a mac it can be updated to yosemite, but it seems not the time yet since too many users vote bad.
FileMaker Server is the first application I have experienced any problems with under Yosemite. FM Pro (Advanced) works fine.
Javier Durá's answer solved the FM Server issue and it's working properly now.
Anyway, this is only a workaround.
Probably this problem will be fixed with the next update of FileMaker Server 13.
Same problem here. Happend in the middle of the night without warning.
Is this an indicator for releasing untested software? Always and again wasting so much time with finding the source of an issue and 'work arounds' on FileMaker server installations. Why is there no beta testing before releases?
Changed computer name, and databases opening now. But error message in log still the same.
Thanks to Javier for the helpful answer.
The thing is that it doesn´t happen with every installation of FileMaker Server 13.
Some of my customers are using FMS13 + OSX 10.10 without this issue.