Data Access Worldwide Knowledge Base
Article Text
PROBLEM:
We are using a Visual DataFlex WebApplication for years. Sometimes my users get an HTTP 500 error. When I look in the Windows Event Log I see:
/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-
Event Type: Error
Event Source: Visual DataFlex 10.1 Web Application Server
Event Category: None
Event ID: 214
Date: 31-8-2005
Time: 16:26:30
User: N/A
Computer: SOMENAME
Description:
Application: Y2Y.Web.Work
Session: ASP:2DE31213
From: XXX.XXX.254.145
A communication error occured. Remote end of the connection has been closed.
Session aborted and all pending i/o cancelled.
/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-
What does this mean?
EXPLANATION:
The 214 error above is not a VDF error. It's not an error about the VDF process. It's an error about the communication link between Web Application Server and IIS. The keyword here is "Endpoint connection". The "Endpoint connection" in WebApp Server terminology is the connection between the WebApp Server service and the Endpoint module (which is either the ASP endpoint module or the webservice endpoint module) residing in the IIS process. If WebApp Server determines that this connection is broken, it usually indicates that IIS crashed.
To illustrate, a WebApp Server model looks like this:
IIS
ASP Endpoint Module / Web Service Endpoint Module
|
|<-- This link is the Endpoint Module communication link
|
WebApp Server Service
|
|<-- This link is the VDF process communication link
|
VDF Program
Based on the information supplied in the error log, WebApp Server determined that the endpoint connection was unexpectedly terminated, which would indicate that the communication with IIS was broken, probably due to IIS crashing.
You need to find why IIS crashed. This could be a lot of things, from anything in ASP, other ASP components used, or it could be a bug in wasasp.dll or waswsvc.dll.
SOLUTION:
The developer reported that the problem was caused by Crystal Reports WebServer 9. When the user had a preview window open and requested for another report to start, the errors occured. When they first close the preview window and ask for the next report all is fine. The developer will now try to find a way to avoid the user to attempt to run two reports.
Email this Article
Email this Article to a Colleague
Send Feedback on this Article to Data Access Worldwide
Copyright ©2010 Data Access Corporation. All rights reserved.
| The information provided in the Data Access Technical Knowledge Base is provided "as is" without warranty of any kind. Data Access Corporation disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Data Access Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Data Access Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply. |