Wednesday, February 2, 2011

The time out errors

All of a sudden on production environment of client the messages start getting suspended and I got a call in early morning to look into this. The event log was full of these warning and error messages.
Event Type:       Error
Description:
A message sent to adapter "SOAP" on send port "<PortName>" with URI "<WebServiceURL>" is suspended.
 Error details: WebException: The operation has timed out
In this case the above WebServiceURL is pointing to an orchestration exposed as web service.
Event Type:       Warning
Event Source:   ASP.NET 2.0.50727.0
Description:
Event code: 3001
Event message: The request has been aborted.
Exception information:
    Exception type: HttpException
    Exception message: Request timed out.

 Event Type:      Error
Description:
A response message sent to adapter "SOAP" on receive port "<ReceivePortName>" with URI “” is suspended.
 Error details: Safe handle has been closed
Event Type:       Error
Description:
A response message sent to adapter "SOAP" on receive port ""<ReceivePortName>" with URI “" is suspended.
 Error details: The original request has timed out. The response arrived after the timeout interval and it cannot be delivered to the client.
Cause:
The above details were pointing that something is wrong with BizTalk and it starts taking lot of time to receive the message. After investigating it further it was found that the account used for running the SQL Server agent was disabled resulting in the size of the MessageBox increased to 1.7 GB as the jobs for maintaining the message box were not running.

Cheers
Rohit Sharma