IIS7 Application pool is being shut down
Crystal Reports is bringing down the application pool, however the problem is with how sessions are handled in the our web application interface that uses Crystal Reports. The basic problem definition is:
1) A user runs a Crystal Report. This instantiates a new browser window.
2) The user returns to work in the web application leaving the Crystal Report browser window open.
3) The user does something like goes to a meeting, lunch, or works in another application.
4) The web application session sits long enough to time out or the user logs out manually.
5) The user tries to use the web application, however has to log on because of the session timeout/or logged out. This creates a new session and/or the old session is null and void.
6) The user goes to the now expired Crystal Report browser windows and attempt to page forward, refresh or interact with it in some other way.
7) The Crystal Report server refuses the connection and throws errors like the below and then crashes the Application Pool.
Application log error:
Faulting application name: w3wp.exe, version: 7.5.7600.16385, time stamp: 0x4a5bcd2b
Faulting module name: Emfgen.dll, version: 9.2.0.528, time stamp: 0x3d253fc7
Exception code: 0xc0000005
Fault offset: 0x00001470
Faulting process id: 0x1108
Faulting application start time: 0x01cfb09ca344bb9f
Faulting application path: C:\Windows\SysWOW64\inetsr
Faulting module path: C:\Program Files (x86)\Common Files\Crystal Decisions\2.0\bin\Emfgen.d
Report Id: 796b282f-1cac-11e4-8c19-00
Followed by system log warnings between 10:26:30 AM – 10:26:31 AM
A process serving application pool 'AppPool_Foo' suffered a fatal communication error with the Windows Process Activation Service. The process id was '4360'. The data field contains the error number.
A process serving application pool 'AppPool_Foo' suffered a fatal communication error with the Windows Process Activation Service. The process id was '3196'. The data field contains the error number.
A process serving application pool 'AppPool_Foo' suffered a fatal communication error with the Windows Process Activation Service. The process id was '872'. The data field contains the error number.
A process serving application pool 'AppPool_Foo' suffered a fatal communication error with the Windows Process Activation Service. The process id was '1800'. The data field contains the error number.
A process serving application pool 'AppPool_Foo' suffered a fatal communication error with the Windows Process Activation Service. The process id was '2996'. The data field contains the error number.
Our web application is written in classic ASP. Server is MS Server 2008 R2, IIS 7
1) A user runs a Crystal Report. This instantiates a new browser window.
2) The user returns to work in the web application leaving the Crystal Report browser window open.
3) The user does something like goes to a meeting, lunch, or works in another application.
4) The web application session sits long enough to time out or the user logs out manually.
5) The user tries to use the web application, however has to log on because of the session timeout/or logged out. This creates a new session and/or the old session is null and void.
6) The user goes to the now expired Crystal Report browser windows and attempt to page forward, refresh or interact with it in some other way.
7) The Crystal Report server refuses the connection and throws errors like the below and then crashes the Application Pool.
Application log error:
Faulting application name: w3wp.exe, version: 7.5.7600.16385, time stamp: 0x4a5bcd2b
Faulting module name: Emfgen.dll, version: 9.2.0.528, time stamp: 0x3d253fc7
Exception code: 0xc0000005
Fault offset: 0x00001470
Faulting process id: 0x1108
Faulting application start time: 0x01cfb09ca344bb9f
Faulting application path: C:\Windows\SysWOW64\inetsr
Faulting module path: C:\Program Files (x86)\Common Files\Crystal Decisions\2.0\bin\Emfgen.d
Report Id: 796b282f-1cac-11e4-8c19-00
Followed by system log warnings between 10:26:30 AM – 10:26:31 AM
A process serving application pool 'AppPool_Foo' suffered a fatal communication error with the Windows Process Activation Service. The process id was '4360'. The data field contains the error number.
A process serving application pool 'AppPool_Foo' suffered a fatal communication error with the Windows Process Activation Service. The process id was '3196'. The data field contains the error number.
A process serving application pool 'AppPool_Foo' suffered a fatal communication error with the Windows Process Activation Service. The process id was '872'. The data field contains the error number.
A process serving application pool 'AppPool_Foo' suffered a fatal communication error with the Windows Process Activation Service. The process id was '1800'. The data field contains the error number.
A process serving application pool 'AppPool_Foo' suffered a fatal communication error with the Windows Process Activation Service. The process id was '2996'. The data field contains the error number.
Our web application is written in classic ASP. Server is MS Server 2008 R2, IIS 7
ASKER
They access our web application via the browser, so the web application session closes either when they log out within the web app, or the session sits idle for so long and times out. As stated above, Crystal is linked to the web app, so when they run a report through the the web app another browser window is instantiated for the report.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
danmcfadden, thanks for the info. Yes, this is an older version of Crystal Report Viewer. With the info from the link you provided, I will mess around in the test system and see if I can get any positive results.
IN our viewer when you timeout it either blanks the window at that point or when you next try to interact with it. Also our viewer doesn't have any of the browser menus available.
mlmcc