It seems like murphy is laughing at me...

Not ntdll.dll this time though, but the error is similar in some ways I think.

New Post on OmniORB crash

This problem has also happened to me and caused me a lot of grief. Despite calls to FMP support, no help. Then I saw this stream and decided to try the installation of V3 then V2. This did not work as it said that the version was incorrect (i.e. didn't like to install down to V2). So I decided to uninstall and try again. It was then that I think I stumbled on the problem (at least for me). Before I tell you this, a bit of background and my thoughts:

1. The problem for me: The server initially was working well for 12 months flawlessly. Then I made some changes to a few of the database field validatations which meant that some of the data would have ordinarily failed validation. I had scripts running daily on the server and each time they would run, due to data validation failure, the server would go into melt down and become non-responsive with nothing in the log. I initially upgraded to V3 due to this problem and then later realised that it was the script crashing due to data validation failure. Anyway once this was sorted out the server started working well again, for about 1-2 weeks that is. Then it randomly started to just shut down with nothing in the logs. I disabled backups, scripts, everything I could think of but it continued to crash. That is when I found this stream.

2. The WPE Component not responding error is not the problem but more a symptom. This occurs when you try and contact the IIS server when the server is down

3. When I tried to install down to V2 as suggested in this forum and it failed, I uninstalled and also went into the FMP server directories. It was then in the LOG directory (C:Program FilesFileMakerFileMaker ServerLogs) that I saw a file pe_application_log.txt. This is a log of all script errors. I could not open it because it was 4.6 gig (likely as a result of my previous script error) !! So I figured, if I could not open this file in Word, Note pad or text editor then if FMP server tries to write to it it will also have problems. I deleted the log and hey presto, no more crashes (for now).

So FMP you need to:

1. Have better handling of scripts errors when run server side or through the IIS (i.e. stop them going into a loop and enable timeouts to be set)

2. Limit the size of all logs and not just the Event log.

I hope this helps some of you as it has been driving me nuts!!!

I will keep you posted if any more crashes occur

I am currently having this same issue, but with FMS 5.5 on W2K3 SP2. The FM services will run fine for a few weeks, then unexpectedly stop with an application error 1004.

I know this configuration is not supported, and I thought that was the issue. But if this is still happening with FM9, why upgrade?

Has anyone found a solution to this yet?

Thanks!

NOPE Still crashing!! I am going nuts with this problem. I have tried everything I can think of!!! Every 4-5 days, the Database Server gets a red light and stops responding in the admin console. Can't restart unless the system is rebooted!!! PLEASE anyone have suggestions??

Do you have SSL connections over FileMaker Network Sharing enabled? If so (and if possible) try turning them off and see if that helps.

- John

IWP + FMS10 +IIS+ win2003 SP2 = random unexpected exit sessions without warning.

Just wondering if anyone has experienced this while using the above and for some reason or another the iwp user is exited completely out of their session (as if someone has executed an exit application or the session has timed out - however there is no 'bad request - session timeout' msg and they had definitely not been within the session for the full extent of the timeout set value). This has started to appear ONLY this week after i realized that the web publishing log file was getting filled up with a lot of errors (saw your similar posts) on scripts that weren't valid during IWP e.g. adjust window, resize window, freeze window and other ones like go to record or go to field when there is no records so err 101 was occurring, so after installing the proper error capturing and disabling all of these non web compliant scripts i've found that for some reason its now randomly exiting on some say 1 out of every 10 (as a rough guide) users from their session after clicking a button that cycles through a lot of external DBs executing scripts/commits etc. Its as if the database isn't being found or for some reason its exiting, could one of the files be corrupted without it necessary telling me or without any issues during fmapp? or what specific scenarios could cause an IWP user to exit randomly like that? I thought it might be network based but it appears not to be. The weird thing is all of last year running the same scripts on FMS9 it worked like a treat AND it seemed to work fine before i started disabling these no compliant script steps, doesn't make sense though now as the log file is filling up at a much less rate (which i thought might have been cause of the original crashes we were having). To give you more of a background IWP/IIS has always crashed every 2 weeks (or so) and so i setup a schedule to restart it every week on the weekend which had been working well for a year or so, the start of this week it crashed a couple of times on Monday morning and i had to restart the server for IWP to work successfully then, so in attempting to resolve the server crashes it appears i've caused even bigger problems for our clients :