We have a - two machines - FM 11.02 install on a Windows 2008R2 Server with IIS7.5.

PHP was installed on the webserver by the FM installation procedure.

This is a fresh install and not other applications are running on this webserver and/or

on the other machine, the database server.

The webserver has a certificate installed and two virtual directories, one for

images and another one for php-scripts used to upload images into the FM

database.

Every hour or so we have two events logged in the Windows event log. As the webserver

crashes approx. every day (irregular intervals) and the whole machine needs to be

rebooted we assume that these two events might show the reason for the webserver crash:

1. Warning

Application Error, Event ID 1000

Name of faulty application: w3wp.exe, name of faulty module: ntdll.dll

exception code: 0xc0000374

2. at the same time:

error

Source: WAS, event ID 5009

A process for application pool "DefaultAppPool" was terminated unexpectedly.

The process ID is .... Process exit code 0xff.

We have reinstalled the whole webserver - same effect as above.

We are absolutely desparate - has anybody experienced this behaviour and

maybe some advice for us ? We'd be very grateful.

Today, and only today, we had another - third - event logged which is:

Application Error, Event ID 1000

Name of faulty application: fmswpc.exe,

name of faulty module: unknows

exception code: 0xc0000005

The FM website did not show, IIS restart had no effect.

After reboot of the machine the webserver was stripped of the

configurations made, i.e. binding for 443 was gone, virtual directories

not connected.

Kind regards

Marion

w3wp is associated with an IIS application pool. fmswpc is the filemaker server web publishing core.

I would suggest starting by running performance monitoring on the box and include the usual suspects: memory, disk and cpu. See if the CPU spikes around the time of the crashes or if virtual memory runs low.

Are the machines virtual or running on real hardware? How much RAM is installed?

w3wp is associated with an IIS application pool. fmswpc is the filemaker server web publishing core.

I would suggest starting by running performance monitoring on the box and include the usual suspects: memory, disk and cpu. See if the CPU spikes around the time of the crashes or if virtual memory runs low.

Are the machines virtual or running on real hardware? How much RAM is installed?

Hello Wim,

Thanks for your reply. Both the machines are virtual (VMware Environment) with 4 GB RAM. We will try to collect some performance

information but at the moment we have only a few web users and about 10 FM pro client connections at a time.

Regards

Marion

since most of the errors are the w2sp ones, I would concentrate on IIS. Not sure if the fmswpc error is a symptom of the other crashes or a contributing factor. Certainly do the performance monitoring.

In IIS: are there any other websites running or is it plain vanilla and configured just for FileMaker?