I am having a problem stopping the FMS service via a script on a Windows box. FMS Advanced 10.0.1.51 running under Windows Server 2003. I can't even stop it manually. I am aware of the known issue with the Server 10 Admin console. Could this be related and has anyone found a solution? Note: No problems with a server running FMS 11. Thanks in advance

Previous to running FileMaker 11 Server my scripts that called the fmsadmin tool often stopped all admin functions, including when I launched the GUI. All I could do is reboot and then everything was fine for a while until the fmsadmin command was used to a certain number of times again.

Does rebooting help you? I could never find a fix.

Please update Server 10 to the latest v-rev.

Steven

Make sure your OS script kicks off the clients first and then closes the files before trying to stop the server.

What command are you using:

net stop "filemaker server"

or

fmsadmin stop server

?

Server 11 is a lot more stable in this respect.

The problems in 10 can be alleviated a little bit by making sure the box has enough disk space and RAM.

You suggest:

"Make sure your OS script kicks off the clients first and then closes the files before trying to stop the server."

How can I do that from the OS? I am finding it impossible to dc clients and close files from the FMS Admin Console. Restarting the server is damaging my files so I want to be able to do this. As I indicated in my original post, I can't even stop the service in Windows. I have since determined that this occurs when clients are connected. I have a 30 min. dc set in FMS Admin console but that isn't working either. Seems the Console is poorly implemented in Server 10. I never had these issues with earlier versions of server. It's quite frustrating.

Thanks in adavance

The problem is largely due to FMS10 so even disconnecting from the command line is sometimes iffy but works more reliably than from the admin console. So upgrade to FMS11.

To use the OS, you need to talk to FMS through its "fmsadmin" CLI:

fmsadmin disconnect -y -u account -p password

Then you let your OS script go into a loop until this commands returns nothing:

fmsadmin list clients (same switches largely)

when all the clients are gone you do:

fmsadmin close (same switches)

and put your script in a loop again until this command returns nothing:

fmsadmin list files (again, same swichtes)

when all the files are closed you finish up with

fmsadmin stop server

and

net stop "filemaker server"

My VTC video tutorial on FileMaker Server comes with a VBscript that does this.

Do take a close look at Wim's VTC videos on server. They are most excellent.

Steven