hi all,

I was woundering is it possible to stop the filemaker service from the command line.

with something like: NET STOP Filemaker.

i tried it and it didnt work.

has anyone an idea for this. seeing i want to put this in a batch file that runs every night before an update.

I know i can just copy the files trough the task shedular to a diffrend location and still make a usefull backup. but i was just wondering.

there is an article on filemakers web site that will give you the command line code.

I also built a utility that will install all the needed files and directories to begin sharing the files at system start.

Go To http://www.mactutor.net/products

Also I have found that if I have FMS run a backup of the databases and have them stored in a different directory, say "FMS Archive", those files have been fine. But given the fact that theere is a randomity affecting the databases themselves at this time. I would not stop FMS from sharing files, but rather schedule a backup 10-15 minutes before your scheduled backup and point the back up to those saved files and to ignore the shared files.

Hope this helps.

Mac [email protected]

On Windows to stop all databases opened from folder "ActiveNEWfiles"

cd C:Program FilesFileMakerFileMaker Server 5.5

fmserver close ActiveNEWfiles*.fp5 -m "*** Closing All Files In New solution ***" -t 2

To restart files again:

cd C:Program FilesFileMakerFileMaker Server 5.5

fmserver open ActiveNEWfiles*.fp5

HTH

Anatoli

Also I have found that if I have FMS run a backup of the databases and have them stored in a different directory, say "FMS Archive", those files have been fine. But given the fact that theere is a randomity affecting the databases themselves at this time. I would not stop FMS from sharing files, but rather schedule a backup 10-15 minutes before your scheduled backup and point the back up to those saved files and to ignore the shared files.

I have found at least with OS X, that is true and the only way we are able to successfully automate nightly routines. That is, using a backup and referring to those files after shutting down the server and then scraping the other ones. Refere to the OS X Server Forum for more info. FMI is aware of the issue and addressing it finally.