Monday, July 4, 2011

Error: "The operation has timed out", "Request timed out."


Moving the original post

All of a sudden the messages start getting suspended and 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.
Resolution
After fixing the problem with the BizTalk jobs in SQL agent and shrinking the databases issue get resolved.
Cheers
Rohit Sharma

3 comments:

Anonymous said...

Hi,

What is actual resolution? What did you do with BizTalk jobs and what procedure (steps) is involved in shrinking the database?

Cheers,

BizTalk beginner

Rohit Sharma said...

In this case the person who configured BizTalk has used his own user name as the owner of jobs and his account was removed from AD after he left the job. I asked my DBA to change the job owner and he in addition that executed the DBCC SHRINKFILE command to free some of the space. But shrinking is not required if you have sufficient free disk space.

Anonymous said...

In this case the user who configured BizTalk has used his own user name as the owner of jobs and his account was removed from AD after he left the job. I told to DBA to change the job owner to service account.

Post a Comment