Error: " The underlying connection was closed: An unexpected error occurred on a receive."

Moving the original post

Event Type:   Error

Event Source: BizTalk Server 2006

Event ID:       5754

Description:

A message sent to adapter "HTTP" on send port "<SendPortName>" with URI "<URL>" is suspended.

 Error details: The underlying connection was closed: An unexpected error occurred on a receive.

You can get the similar error for SOAP adapter too.

Cause

On production environment this error was occurring randomly once or twice in a month. After lot of investigation I came to know that the AppPool was getting recycled before Web Page can respond to the request.

Though there are no of reasons for AppPool recycle but in this case the IIS was hosted on a machine having sufficient resources(memory,CPU). I figured out that the app pool used for web application was configured to get recycled after 1740 minutes (which is default setting when you create new App Pool).

Resolution

Open the Internet Information Services (IIS) Manager go to Application Pool  and open the properties of the required application pool. Uncheck the "Recycle worker processes (in minutes):" check box.

Cheers
Rohit Sharma

Error: "The HTTP send adapter cannot complete the transmission within the specified time"

Moving the original post

Event Type:   Error

Event ID:       5754

Description:

A message sent to adapter "HTTP" on send port "<SendPortName>" with URI "<URL>" is suspended.

Error details: The HTTP send adapter cannot complete the transmission within the specified time.

Cause

This error occurred for Solicit-response send port when the HTTP adapter does not receive the response within the time specified for Request timeout. The default value for Request timeout is 0 and in this condition the BizTalk Messaging Engine calculates the time-out based on the request message size.

Resolution

Set the value of Request timeout for send handler created for HTTP adapter then this change will affect all the send ports. or

You also have the option to set the value of Request timeout for a particular send port in HTTP Transport Properties.

Cheers
Rohit Sharma

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