Files crashing constantly sometime taking down the server too

[gillian]

I have written a bespoke solution for a client called ADG. This has a two file structure, interface and a data file. These are constantly crashing and taking down the server too; this has become so bad that the client has resorted to client copy as a host as while this still crashes often the files do not corrupt when doing so. The situation is no longer workable, I have tried everything I know to resolve this problem including a complete rewrite of the data file, checking all of the layouts and rewriting many of the scripts along with the following, which has been sent to FileMaker support who also cannot help me, saying they cannot reproduce the problem:

SYSTEM ENVIRONMENT (put anything that might be relevant)

FileMaker Product = FileMaker Server 10 and FileMaker Pro 10 Clients

OS = Mac OS X versions 10.5x and 10.6

Computer =

RAM =

Any applicable 3rd party hardware/software = SMTPit plugin version 4.1.4

Configuration/ Network settings/ Outside system settings =

Browser or email client (if applicable) =

Include sysinfo file if applicable

STEPS TO REPRODUCE: There is nothing specific that can reproduce the problems, system will crash when machine left standing, when user prints, reviews lists or uses back button within the files.

EXPECTED RESULT: Database specific tasks

ACTUAL RESULT: FileMaker crashes, sometimes the FileMaker server crashes.

SUMMARY OF WHAT TROUBLESHOOTING HAS BEEN DONE SO FAR:

- FileMaker server was upgraded to version 10

- Clients patched to latest version

- Client mac stripped down to only running FileMaker 10

- Clean server Mac mini installed for the sole purpose of running FMS

- Print drivers removed

- Database Files sent to FileMaker support to replicate the problem; without success.

- Scripts rewritten in the files whenever one that caused a crash was reported.

- Rebuilt navigation tables within the database files.

- FileMaker files saved as clones and data reimported to clean versions

- Files operate fine as stand alone, but this is not a practical resolve for a company wide solution.

- Data saved in Excel format and then reimported.

HISTORY OF FILE (Is this a converted file? How many files in solution? How many tables in file, ect?):

There are two files, a data file and an interface file.

Files originally developed from version 9 templates, using FileMaker Pro Advanced version 10 developer tools to create new files to further develop.

ADDITIONAL NOTES:

Attached database developer report, system logs and machine spec's.

I am desperate for any help that may pinpoint the problem. They are all mac clients x 4 running OSX.4+ ; mac mini server currently (but they have the same affect on another server in the same building). Mac mini only running FM server and only Apple apps, brand new clean machine.

Is there a feature within FileMaker that could be causing this? Is there something on the network that could be causing this?

Please note that as a single user no hosting the files work just fine!

Any thoughts greatly appreciated.

Many thanks

Gill

DB_Report.zip

Filemaker_Server.spx.zip

[IdealData]

Eliminate FMS from the equation and host the file(s) using FMP on one of the Macs temporarily. If you still get the same problems then it looks like the DB is damaged.

[gillian]

The files do still crash using pier to pier sharing, although they do not corrupt. I have completely rewritten the data file from scratch, no copying, no importing tables or scripts. When I linked this back to the interface I effectively had to re-do the relationships and revisit every script to relocate the fields and re-save every one of them. Each layout was also revisited to relink the correct fields in the views. The only part of the interface file I didn't re-do was the layouts themselves - this file has no data and no bad blocks can what is effectively an empty file be causing the problems?

[IdealData]

The files do still crash using pier to pier sharing, although they do not corrupt

Just because FM can recover the files does not mean to say they are not damaged. These files have actually been damaged many times - every time there has been a crash.

Do your original release master files crash?

What is most surprising is FMS crashing, it's normally very robust.

[IdealData]

Just a thought... is someone opening the files directly through OS sharing - that definitely would mess things up.