Client browzers gets hanged

Hi,

I have an application developed in VB mainly with
controls embedded in ASP pages. It is a client server application and the
following error has occurred several times on production and affects both
clustered servers.


- Client Not Responding.

Symptons of this error

The client is running but when user clicks on any of the menus/controls in
the applicatin nothing happens. The database is up and running and jobs
continue to run successfully.
The IIS service has been checked this reports website is on-line. Restarting
IIS does not resolve the problem.

The following extracts taken from the HTTPERR1/W3SVC1 log files at the time
connections dropped. In all cases a hang occurs soon after a request to
print is made by the user. The business prints of confirmations every
morning but error only happens occassionally.

We've monitored the server performance during print runs but can see no
unusual activity on the server.

To Resolve this issue we have the following workaround :

Within component servcies select "Running Processes" and under here is the
"IIS Out-of-Process Pooled Applications".
Right Click and select shutdown. The process is removed from "Running
Processes". When the user attempts to connect to the application the process
automatically starts up and can be seen under "Running Processes". Sometimes
the process does not start and errors in the event viewer are logged as
follows. In this case a failover is performed to the other node.

The server failed to load application '/LM/W3SVC/1/Root/<Application Name>'. The error
was 'The RPC server is unavailable.

Is there a way in which we can fix this problem permanently?

The log:
2006-03-03 08:36:27 10.3.225.58 POST /msadc/msadcs.dll/RXBPrintQueueDC.Queue.
Enqueue - 80 UK\CR44779 161.12.206.120 ACTIVEDATA 200 0 0
2006-03-03 08:38:24 161.12.224.137 2961 10.3.225.58 80 HTTP/1.0 POST
/msadc/msadcs.dll/RXBDealCapture.Deal.InitialisationData - 1
Connection_Dropped DefaultAppPool


Can anyone help on this?

Thanks

When I've seen the error about "RPC Server is unavailable" it's always been from a server that is underpowered and can't allocate enough resources to IIS. Review your application code for any potential resource leaks, etc.