Data Access Worldwide Knowledge Base
Article Text
PROBLEM:
We are using Web Application Server 9.1 and we run several applications on this server. We do not use Process Pooling -- we use WBO persistence.
Constantly the Windows Application Log shows the error:
Event ID: 201
A child process does not respond, unconditionally terminating the process (C:\...\Webapp.exe).
When this error occurs, it is necessary to re-start the server or re-start the Visual DataFlex Web Application Server. We already configured the server as indicated in article http://www.dataaccess.com/KBPrint.asp?ArticleID=1158, but it did not solve the problem.
What else could be causing this error?
There is a big and slow process being called by the ASP. Is there any configuration to increase the ASP timeout?
SOLUTION:
Here are the full descriptions for the error message you are seeing:
>From the 9.1 help (Web Application Development | Troubleshooting Web Applications | Understanding Errors | Warning Messages):
MessageId: EVMSG_W_TERMPROCESS 0x800000C9L
Indicates a warning. Occurs when the DataFlex process is hung. Usually indicates that the DataFlex program doesn't respond. The service will force a process terminate and any unsaved data will be lost. If possible, setup "Allow service to interact with desktop", or some other means of debugging the DataFlex process. Could indicate errors such as infinite loops in the DataFlex program and so on.
>From the 10.0 help (General Reference | Error Codes | Runtime Error Messages | Web Application Errors | Web Application Warning Messages):
201 - EVMSG_W_TERMPROCESS
A child process does not respond, unconditionally terminating the process ProcessName. Occurs when the Visual DataFlex process is hung. Usually indicates that the Visual DataFlex program doesn't respond. The service will force a process terminate and any unsaved data will be lost. If possible, setup "Allow service to interact with desktop", or some other means of debugging the Visual DataFlex process. Could indicate errors such as infinite loops in the Visual DataFlex program and so on.
You should use the debugger to see what is going on with the application. The problem could be because you are relying on persistence. From the information on persistence in the VDF help, persistence is not recommended anyway: "We advise you not to use session (and therefore WBO) persistence."
If the process being run is always the same and the problem doesn't always happen, the timeout value might not be the cause... You can try configuring the timeouts in Web Application Admnistrator to see if that helps, but reviewing the application would be the best to do.
The problem in this case was being caused by an obsolete message: Destroy_Object message (obsolete) was being used in the application. Once the message was changed to Destroy, the error stopped occurring.
Contributed By:
Ivan Kaupa
Company: Data Access Brazil
Web Site: http://www.dataaccess.com.br
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. |