Any help sincerely welcome

New (first time) installing FM server on a PC running Win2000 Pro.

Installation went OK - and the sample files are open and being served across the LAN. So far so good.

Then loaded a file developed in 8.5 Adv on a mac which will not be opened by FM Server. It stays "CLOSED". While other files are running fine.

The file is set for Multi-user TCPIP sharing turned on.

I suspect it may be a permissions problem, but all of the read & write boxes are checked for all users & groups in properties.

Any idea what things might be keeping FM server from being able to open this file?

Thanks again!!

Hi

This happened to me when I first moved to server 8 and it related to the "consistency checker" feature.

The fix was to save a copy of the file as a compacted file and use this instead.

Good luck

Open filemaker pro client software. Click on File > Recover. Point to your database file. Save to a new file name. Delete the old one. Rename the new file to the database name you desire. Restart the server engine.

[color:red]Absolutely not.

After closing the files from within the SAT Tool and then stopping the service, open the file in FileMaker Pro and from under the File menu save a copy as compacted. Exit FileMaker Pro and then start the server service again to see if that addresses the issue.

The file did not open because it failed its Consistency Check. Saving as a compacted copy is the prescribed procedure. See See FMI Tech Info 5371. Recover is only a very last resort whose purpose is to extract the data so the data can be placed into a clean clone of the file.

Steven

Hi Fey,

Not a good idea to recover files and keep re-using them. There is no way of telling what the recover process deletes. Some of us have been saying this for years and it was confirmed by the engineers this year at Devcon.

Recovery is a last-ditch measure to get data out of a file and then import that data into a known good copy of the file...

Thanks to all. Creating a compacted copy worked! FMFORUMS rocks!

Do monitor that file closely. Something created problems for it earlier, and you will want to be sure that it behaves well from now on.

Steven