Matthew F Posted May 1, 2009 Share Posted May 1, 2009 I recently came across a license conflict problem that reinforced to me the importance of properly uninstalling FMS software when migrating to a new device. After having preflighted my database using FMS 10 on a desktop Mac I shut down this server and tossed the /Library/Filemaker Server folder into the trash (not good). After this FMS was installed on a second dedicated server and ran fine until the day that I restarted my desktop machine. Apparently FMS demon automatically restarted on the desktop machine, generating a license conflict. The server abruptly shut down and refused to restart. The solution was to kill the Filemaker server processes on the desktop machine, properly uninstall the FMS using the original installer package and restart both machines. Link to comment Share on other sites More sharing options...
Steven H. Blackwell Posted May 2, 2009 Share Posted May 2, 2009 Actually, you could have just stopped the wrapper daemon from the Terminal, and that would have prevented its launching automatically. Remember that the Console controls the database server adn the WPE, not the FileMaker Server daemon itself. Steven Link to comment Share on other sites More sharing options...
Recommended Posts
This topic is 5487 days old. Please don't post here. Open a new topic instead.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now