Server made Pro 7 crash

[Heckate]

Quick question. If i'm running FM Pro 7v3 on the same machine (Mac G5) as Server 7v3 whey does it crash when i do a backup. Did i miss something i the documentation?

[Reed]

How are you doing the backup? Using Server, or using Save a copy... on FMP?

It's not generally recommended that you run the client and server on the same machine.... for one thing, it's too likely that you might directly open a file that's being hosted, which will cause corruption. Also, you will have problems if you try to turn on sharing for the client while the server is running.

[Vaughan]

It's also possible that you've corrupted the files already. Seriously consider restoring a known-good backup.

[cdr-dev]

Hey Reed,

Wouldn't it be possible to just do a "Remote" open from the FM Pro 7 Client on the server and access the file as if you were a true "client"??

I would think that if you run FM Server 7 and treat your databases in the same manner as a true remote client that if you opened the file in that manner, you would still be able to perform the necessary operations in a reliable and safe manner.

Has anyone else used a Fat Client of FileMaker Pro 7 loaded on the Server??

Chris

[BruceJ]

Everything I've always read says this is a big no-no.

You're playing with fire if you run Server and use the client on the same machine.

[Heckate]

Hi all, thanks for all your replies. I don't see why FMP and Server can't run on the same machine as i've been doing it for the last week and a half. I've opened the db on the server machine though 'Open Remote...' so i think it is a "true" client, as cdr-dev says.

The file isn't corrupt yet. Is it possible it would run fine for a week and a half and then become corrupt? So far the only problem i've had is FMP crashing when server admin runs a backup through it's scheduler, but since i've disabled that everything has been fine.

Does FileMaker explicitly say you shouldn't run FMS and FMP on the same machine?

[cdr-dev]

FileMaker might say it is not recommended but if you access your application correctly using open remote, you should not have any problems. The minute the users try and open it up as a file, that is when you would have an issue. So everyone else that would stray from it, they have a valid point also, no right or wrong here. The only reason I have FileMaker Pro 7 client loaded on the server, is because my client only has one fax number and does faxing from FM pro and does not want to spend money to setup the other client workstations with faxmodems to do faxing, they want it done from one central location so this leaves me with this only option. It is unfortunate that you cannot setup a "fax" printer in Windows 2003 Server, to be networkable.

I have been playing with creating a shortcut on the desktop to open a database file remotely without having to go through the FileMaker launch icon, then "File", "Open Remote", and select the server, then the file you want and have not been too successful. I know that when you open a remote file, and you select the server/filename, it shows the "network path" below and have attempted to make shortcuts with this and have had no success.

What would be the proper method for having that done?

[Heckate]

I had the same idea about a shortcut. I created a new filemaker file that runs one script when it opens. This script does an 'open remote' to open the served file and then closes itself. It seems to be working so far