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 :
