filemaker server 5.5 on windows 2003 server

[DBasine]

According to the documentation, Filemaker Server 5.5 on Windows 2003 Server Standard Edition should be compatible.

Indeed, I was able to install, also installed the patch to uninstall, and I can perfectly work with the FileMaker Console.

But the FileMaker server.exe command prompt does not work... When I double-click this application, it remains open for a few seconds, but then this task is suddenly ended, before I can enter any command!

Also on Windows 2000 SP4!

Edited October 20, 2005 by Guest

[RPCia]

I am not sure I understand your problem?

I am running server 5.5 on a 2003 standard box and had no problems installing or running the server. I do not know what the server.exe file is your referencing when I wish to restart or start the server I do so through the services tab.

I don't have the client installed on my server though maybe that has something to do with it?

[Steven H. Blackwell]

But the FileMaker server.exe command prompt does not work... When I double-click this application,

That's not the way you start the service. Go into the Services Control Panel, right click on the FMServer service, and select Start.

HTH

Steven

[DBasine]

Thanks! Indeed, now I can start the service.

In a previous version, you could start up the .exe application, in which you had to enter DOS commands such as:

FMSERVER OPEN

FMSERVER CLOSE

FMSERVER PAUSE

But now, I cannot choose which files to open in the Server or not? How do I do that (besides from doing it remotely)? Because now it opens ALL databases on the FileMaker Server disk.

Edited October 20, 2005 by Guest

[RPCia]

To my knowledge all files in the database folder will open when the server starts up. Then the only way to close them is to use the remote admin from another computer and close the files but you would have to do this everytime the server started up

[DBasine]

Indeed, only the ones in the FileMaker Server folder. I was just looking for a way to display the databases in the server list without the ugly '.fp5' in the names...

Thanks for your help!

[Steven H. Blackwell]

Because now it opens ALL databases on the FileMaker Server disk.

That's what it is supposed to do. Otherwise they would not be available. However, on a file by file basis, you can hide their names in the Open Remote dialog but setting them to be multi-user [hidden] in their individual sharing preferences.

I'd recommend you move to the modern versions of the products. Filemaker Server (formerly FMS 5.5) along with FMP 5/5.5/6 are all officially EOL.

Steven