Files crashing FMS9 and local machine

[gillian]

Please can you help I have files that were originally developed in version 9 but have been further developed in version 10. They run without issue as stand alone databases but when the are used via FMS9 the local machines crash. Sometimes it is so bad it takes the server down with it. The local machines have no specific task that they crash on and have been everything from old Powerbooks to new Intel iMac's. The FMS9 is also running on a Mac, and was without problems until the version 10 clients and/or these files were introduced.

I have run recover and compressed the files and none of this has any impact. The recover process does not find problems with the files.

Is there something obvious that I am missing?

Thanks

[jamesducker]

Doesn't sound overly good, to be honest.

First things first, though: eliminate the server as the cause of the problem. Do a fresh installation of FMS on to another mac, host the files on there and see if there is any improvement.

If you can, go back to a version of the files before you started using the 'Recover' command. 'Recover' is a minefield that is best avoided...

Hope that helps

James

[gillian]

Thanks James, we have tried several different places hosting the files all with the same results. What I find difficult to understand is that FileMaker does not quit when it is run locally, so I suspect it is something to do with the networking options but as this is my first real FM10 site I am not sure exactly what I am dealing with.

Well any other thoughts would be appreciated.

[Steven H. Blackwell]

I have run recover and compressed the files and none of this has any impact.

Well it has actually, and the impact probably was to damage the files further.

While files are hosted on server and no users are connected, run a backup and select verification as part of the process. See what that report tells you.

Please keep us posted.

Steven

[gillian]

I am feel that maybe I should rebuild the data file, this has no layout or scripts within it just the tables which I draw into an interface file. If I create a new file and import the tables will this import the problems? Would I be better to use the developer tools to create a new version from the original?

I will run the backup report in the mean time.

Thanks

[jamesducker]

If rebuilding is in any way practical, that is always the best option.

And archive, archive, archive -)

J

[gillian]

If I create a new file and import the tables will this import the problems? Would I be better to use the developer tools to create a new version from the original?

[support]

Hi There Some further info..

See also my original post 06-24-09 03:44 AM - Post#334155.

I have upgraded the Server and Desktop to the lastest versions of Mac OS . The Server has also been upgraded to the lastest OS and FMP

I have done the recovery and actual rebuilt 1 of 37 databases (I don't really want to rebuild the other 36 databases) and the problem is still there even with a complete new file.

When you go into some databases and some layouts FMP crashes... the desktop needs to be restarted by the power on off button (Mac restart command not working). If you don't restart the desktop Filemaker thinks you are using the same licence key.

This is my Hardware and software versions for FMP to crash on

The desktop is a Mac Mini 1.42GHZ Power PC G4

also

Mac Mini 1.83GHZ Intel core Duo

Mac OSx version 10.5.6

FMP Version 10.0V3

The server does not appear to crash

The Server Hardware and Software

Server Mac Mini 1.83 GHZ Intelcore 2 Duo

Mac Server version 10.5.7

FMP Server version 10.0.2.206

Now having written all that... I can modify layouts (especially in the databases that crashes on the above mentioned machine) on a laptop with the following configuration...

Powerbook 1.67 GHZ Power PC G4

Mac OSx 10.4.11

FMP 10.0V1

this really makes no sense at all for FMP to crash on some machines and not other... unless it has something to do with Leopard

Any one got any ideas....

[gillian]

I have logged a support issue with FileMaker. I was advised to clone the files as this ensures that they are true version 10 and then reimport the data. This has definitely improved things, by about 90% I would say, but the crashing hasn't gone away completely. I have two theories that it is either because this client has many unusual print drivers (they are a large format output company) or it is something conflicting with the sharing.

I'll let you know if I get any further with this.

Still would appreciate any further input from wise heads!

[support]

Just to let you know that I can modify FMP layouts on Intel or Non intel machines, any layout of any database...

SO LONG AS THE MAC OS IS no higher than 10.4.11

[Vaughan]

Does the solution use any plug-ins? Are all versions of FMP and FMS patched up to date?

Does FMS have the Leopard patch installed?

[support]

Not using any plug ins

All desktop and server running all latest updates from FM and Apple

I can modify layouts if using FMpro with latest patches on a machine Mac os 10.4.11 without the desktop crashing. It seams to be something to do with Leopard...

Next week Im moving FMs off the OS10 (Leopard) server and onto a machine just running Leopard, to see if it maybe has an issue with the OS10 (leopard) server