Hi folks!

We've experienced a very interesting problem but have been able to work around: Our solution has been running on FMS 7 and FMS 8 fine under Windows Server 2003 with AMD Athlon. When we were installing our solution at a client's server (also Windows Server2003) it kept crashing. We tried to solve that and gave them a MacMini with Mac OS X 10.4.9 & Intel Core Duo, didn't solve the problem, it kept crashing. Then we ran a couple of tests at the office and figured out that the server can only run stable on a NOT Intel Core Duo mashine regardless of the operating system, when heavy operations with global fields & relationships to them are involved. My opinion is that this is an undocumented bug in FMS inself. Anyone else experiencing similar problems?

I've attached one of the crash reports.

fmserverd.crash.log.txt

Edited May 22, 200718 yr by Guest

Put it on a real server and see how it behaves. You may also have dmaaged files that are causing the problem.

Steven

We have been running a 2 CPU Intel Dualcore 3Ghz MacPro with 2 GB ram and FMS8 for about 6 months now. 106 databases with 15-20 users daily. Many, many globals and many complex relationships. Crashes = 0. You may need to look elsewhere for your problem cause.

Hey Julian,

It would be helpful to know more about your deployment. Like:

How many clients are typically connected when it fails (or if this was failing in your text environment, how you tested the load)?

What is the network speed?

Does your server version have the latest update?

What version of FMP are the clients running?

What is the hard drive configuration of the server?

Anyway, I tend to agree with Steven on this. The Mini is really not a good machine for a FileMaker server. And your earlier crashes could have caused corruption in the files leading to more crashes. It's not clear what steps you took to rebuild the files are each failure.