You are viewing limited content. For full access, please sign in.

Question

Question

Forms App Pool Keeps Stopping

asked on February 10, 2016

We are having a problem with our Forms app pool stopping lately. There have not been any Windows updates applied to the server in question and none of the other app pools on the server are affected. In the Event Viewer we are seeing the following error message precede the stop.

Log Name:      Application
Source:        Application Error
Date:          2/10/2016 1:41:22 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Web2.d91.k12.id.us
Description:
Faulting application name: w3wp.exe, version: 7.5.7601.17514, time stamp: 0x4ce7afa2
Faulting module name: clr.dll, version: 4.0.30319.34209, time stamp: 0x5348a1ef
Exception code: 0xc00000fd
Fault offset: 0x0000000000009d5c
Faulting process id: 0x1d34
Faulting application start time: 0x01d1644360627895
Faulting application path: c:\windows\system32\inetsrv\w3wp.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
Report Id: a47c2069-d036-11e5-adcd-005056a41094
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2016-02-10T20:41:22.000000000Z" />
    <EventRecordID>3025379</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Web2.d91.k12.id.us</Computer>
    <Security />
  </System>
  <EventData>
    <Data>w3wp.exe</Data>
    <Data>7.5.7601.17514</Data>
    <Data>4ce7afa2</Data>
    <Data>clr.dll</Data>
    <Data>4.0.30319.34209</Data>
    <Data>5348a1ef</Data>
    <Data>c00000fd</Data>
    <Data>0000000000009d5c</Data>
    <Data>1d34</Data>
    <Data>01d1644360627895</Data>
    <Data>c:\windows\system32\inetsrv\w3wp.exe</Data>
    <Data>C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll</Data>
    <Data>a47c2069-d036-11e5-adcd-005056a41094</Data>
  </EventData>
</Event>

There is a hotfix that is referenced, but when I try to install it, it says it does not apply to our server. Does anyone have any other ideas of how to troubleshoot this issue?

Replies

replied on February 16, 2016

Hi Blake,

Please open a support case with your VAR so we can further investigate this issue. 

replied on February 16, 2016

The default setting for app pool turns on a feature called "rapid-fail protection" where IIS will disable the app pool if it crashes more than the specified number of times within the given interval. You can turn that off for now (in IIS' app pool advanced settings). It's not a fix, but if it crashes IIS will just restart it. So at least users won't get the 503 error, but rather just see the site slightly more sluggish as the app pool restarts.

replied on February 16, 2016

I made some changes to settings with the application pool as you suggested from the other post I made. So the application pool doesn't stop anymore, but now it logs the users out and if someone is in the middle of filling out a form and the error above happens it tells them that "Invalid form data was sent to the server. This can occur if the form is out of date. Please refresh and try again. [LFF2106-InvalidDataSent]"

replied on February 16, 2016

Does the crash generate a dump file? You might be able to find it in C:\Users\USERNAME\AppData\Local\Microsoft\Windows\WER\ReportQueue, where the username would be the Windows user the app pool is running as. There should be folders in the containing the process name in their name. If you find a .dmp file in any of the w3wp.exe ones, zip it and attach it to your support case. We might be able to get more information on what causes the crash.

replied on February 16, 2016 Show version history

I found it and sent a ticket into our VAR with a link to the dump file. It was too large to attach to an email.

replied on February 17, 2016

As a heads up, I believe it is related to a specific Forms Process. We believe we have narrowed it down to when a process admin is working on a specific process that it takes it down. I can provide the exported XML of the process and have our VAR attach it to the case if you think it would be useful.

replied on February 19, 2016 Show version history

Hi, I looked at the dump file and it looks like the crash was caused by a call to a process with a variable with a parent\child relationship like a collection or table  in which the child refers to the parent.  This creates a endless loop in our code and I eventually the memory is used up.   I will look into adding some code for the next release which will prevent the loop.  Please look at the xml generated or you can send us the xml for the process if its not clear which table\collection has become corrupted.

 

replied on February 21, 2016

I know which process is having the problem, but I do not know whether to look in the process modeler or a field rule for the issue? I have tried to export the process, but it errors out before it finishes.

replied on February 22, 2016 Show version history

Yeah, sorry I assume the export function runs into the endless loop as well.  Are there a lot of forms?  The problem is probably in a collection or table on one of those forms.  Maybe you can delete your table or collections variables one at a time and locate the cause that way.  Make sure you just don't just remove the field from the form but the variable itself.  

replied on February 22, 2016

I tried to get to the variables, but it kicks me out before it ever pulls them up. Any other ideas?

replied on February 24, 2016

A support case has being submitted to resolve the issue, Laserfiche has sent out a sql script that should resolve the issue. Waiting for a response in case.

You are not allowed to follow up in this post.