Damaged files on server

[timolous]

Hello!

If some file needs to be recoverd with filemaker, should I Import data to clean copy of the same database?

Problem is that we have many damaged, recovered databses in use with Filemaker server 5.5. And server can't keep host connection alive.. Sometimes client software says says that file is damged, even if the file is opened on other client and is working fine on another client at the same time....

So, if filemaker database is damaged should I use recovered file or clean copy of database populated with recovered data?

Is there any differenties with these methods?

[LiveOak]

For the best possibility of recovery, it is always better to recover the database with the data then import the data to a fresh, undamaged clone. Recover alone just doesn't fix everything. Very few types of corruption can travel with the data to the new file.

-bd

[Anatoli]

RE: Sometimes client software says says that file is damged, even if the file is opened on other client and is working fine on another client at the same time....

IMHO -- possibly on other area of file. What kicks one user out must kick all, but it must be in the same spot and routine.

[Vaughan]

Hold it... you say a Filemaker Server. Are users connecting in to the databases by double-clicking on the file's icons (through file sharing a networked drive) or by using the "Open Remote" command?

Connecting through a networked drive is a sure-fire way to corrupt FileMaker databases on a daily basis. Sharing through FM Server is very reliable and robust.

[timolous]

We are using Filemaker server. Users use Open Remote command.

There are no file sharing on Filemaker server.

What other operation systems are you usinng on FMserver?

How do I know wich one of our 80 databases are corrupted?

[Anatoli]

Always full Intel machines. Processor and chipset.

Newer VIA.

NEWER 2 NIC cards.

NT4 or W2K client or server.

Linux and Mac X are also viable choices.

Repair them from scratch - clone no records, export to text files import them to clones.

[gilfrith]

We are frunning FMS 5.5 on OSX Jag 10.2.1, accessed through 'Hosts'. We too are suffering FMS crashes which require a reboot of the whole server because FMS will not boot until a restart is performed. We are also suffering file corruption issues and today one file of 2M would crash FMP 6.02 when we tried to open the recovered file. I will start copying data into a clone to see if that helps. OSX Jag Server 10.2.1 file sharing has been robust even if the inherited privileges issue has not been resolved. FMS 5.5 has not been very reliable. I'll gladly accept any free advice. Thanks, Gil.

[gilfrith]

Re: Damaged files on server [re: timolous]

[Anatoli]

In 4-5 years I had zero problems with the above HW/SW.

Rock solid.

[Kurt Knippel]

Most people will say NOT to use OS X Server, as the extension set required for good database server stability and performance basically gets you back to normal OS X.

Start by striping everything you can from the base OS X install, do not run any other services, nor Filesharing.

This is just good practice for the administration of a database server, rather than anything to do with OS X itself.

[belgiumbruno]

Hi,

I have a same kind of problem.

I have several files with a tabbed interface.

Each file can open all the other by clicking a tab.

In 1 combination (from purchase to sale) the sale file doesn't open.

Message: "Sale is not a filemaker file or it is seriously damaged"

I don't have the message if I go from other files (ex. stock to sale).

It's only in the combination purchase - sales that I have problems.

even if I put the files from the server and put them on a stand-alone machine

I don't have the damagemessage if I go from purchase to sales.

Can it be a bad script in purchase although all the opening scripts are the same ? I never had crashes. another thought : maybe I have to relate these files via a constant and see what happens.

A clean clone doesn't help.

[djgogi]

Quiting FMS service on OS X corrupts served files.

Dj

[belgiumbruno]

it's a win 2k server and if it damages a file the file

can not be openend from another file too.

[belgiumbruno]

I finally found the solution myself. I think it's interesting for everyone.

I received a message that 1 file of the db (sales) was seriously damaged.

For me it was not possible because I had several links to the sales

and only 1 was not working (from purchase to sales). It only happened on my machine . All the other people (around 10) didn't have the problem.

The problem was that on my machine there was a backup of old stuff.

I deleted all fm files from my PC and the problem was solved.

Isn't this a bug in fm. Even if you open the fmfiles with the host button

it gets confused by old files that aren't working under fmserver :

Bruno

[Anatoli]

It was discussed 1000 times.

Never leave "old" files on machines. ZIP them, rename them with Developer or delete them.