Jump to content
Claris Engage 2025 - March 25-26 Austin Texas ×

This topic is 6718 days old. Please don't post here. Open a new topic instead.

Recommended Posts

  • Newbies
Posted

I have been having a problem lately and I thought I should ask about it.

When I have had to stop my FM server ( running on Mac OS X) to pull files down it often will tell me that it is shutting down, but can take hours before it actually shuts down. I do not have hours to wait, so in the past, I have had to resort to less than friendly means for shutting down the system. I worry as the last time this happened it causes major corruption in one of my databases. Is this a known bug? Is there are work around?

Also, when I try to close just one file via the Administration databases it also sits there for hours saying that it is closing. Then I have to shut the entire system down to even get at that one file.

I really could use some help here.

Cheers,

Jeannie

Posted

To confirm if the FileMaker Server Dameon is still running launch the process viewer, you can see if it is running.

Remember the Server is seperate from the Config App need not be running whilst the server is running.

You also might be able to start and stop the server from the command line as well.

Posted

In this aspect Windows FM Server has sometimes the same problem.

When I was last time stopping the service, one file was stuck and the FM server service didn

  • 4 months later...
  • Newbies
Posted

I'm experiencing the same issue.

Config=...FMS 5.5v1 on XServe w OSX Server 10.2.5

Issue:...all of a sudden yesterday, it or someone dropped our main db that links to a boatload of other dbs. I looked and saw that the main db wasn't being hosted, thought I'd stop and restart fms to grab it again.....it stopped ok...when i restarted,..it only grabbed 2 out of 55 dbs. I tried to shut down again and it got stuck...had to shut down the server. Restarted fms,.. only grabbed the same 2 dbs as before.....tried to shut down again....got stuck...went home....13hrs later...still stuck. Shut down server again to stop fms. Now I'm trying to figure out how to uninstall fms on the xserver. Can't move the folder to the trash.....says "fms cannot be moved to the trash because it cannot be deleted" I'm a newbie to both fms and mac. Can anyone tell me how to remove and reinstall fms?

Posted

Doubleclick the Error.log in the Filemaker Server Directory.

This wil open the Console and will give you 'live' feedback about what Filemaker Server is actually doing.

Posted

5.5v2 Updater!!

When I updated to Server 5.5v2 (v2 updater is free download from FMI) ALL of my major problems went away... The updated includes instructions for 'un-installing' Server - FOLLOW THEM.

The best thing to do is fix your files (put data from recent backups in previously backed up 'clone' files - or use good backups, if you have them and are SURE they're not damaged)

Then uninstall Server, reinstall 5.5 from CD, then run the 5.5v2 update and then open good files...

things should be much better after that.

Posted

Also in dealing with OS X (especially after a crash - or 'unfriendly' shut down) it can REALLY help to repair permissions on your boot drive.

This can be done by booting off of your 10.2 CD and when the installer starts go up to the menu (file or Installer not sure which one) and open the Disk Utility, you can then run the repair disk permissions on your boot volume. Then quit Disk Utility, and quit the installer, it will force you to reboot.

I also HIGHLY RECOMMEND keeping your DBs on a separate drive, or at least a separate partition... NEVER ON YOUR BOOT VOLUME - as OS X (especially in low ram situations) does a lot of vm paging to the boot volume...

-Arin

  • 9 months later...
Posted

Ocean West said:

To confirm if the FileMaker Server Dameon is still running launch the process viewer, you can see if it is running.

Remember the Server is separate from the Config App need not be running whilst the server is running.

You also might be able to start and stop the server from the command line as well.

This is part of the reason for my post for reference materials elsewhere on this board.

Could you give some pointers on this issue. We have clients who try to launch Server from Server Config in OS X and it will say that it can't because it is already running. There are clients out there who "think" they know what they are doing and use Terminal to do the coding so that server will launch on startup and then when something happens can't get it to shut down because if they do a Hard shut down, it just starts up again when they restart.

Could someone out there, who is a bit more versed in Server for OS X give me some advice so I can clean up these messes?

Thank you so very much!

Platform: / Version:

FileMaker Version:

Platform: / Version:

FileMaker Version:

  • 2 years later...
Posted

Bringing this back to the top. Anyone have any suggestions as to how to shut down FM Server when someone goes into Terminal and has it automatically start up? I couldn't find the info on the FM site and I have clients who are "too clever" and have it set to go on but can't turn it off when I ask them to.

Posted

I am actually have the opposite problem and can not get FMS 5.5 to launch with OSX Server 10.4. I also tried just opening FMP5 to shar the database and you can not see it on the network. Any suggestions?

This topic is 6718 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 account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.