FIX: You receive a time-out error message when you try to send a message to the target service of a Service Broker application that you create in SQL Server 2005

Consider the following scenario:

• In Microsoft SQL Server 2005, you create a Service Broker application.
• The Service Broker application has message forwarding enabled.
• You try to send a message to the target service of the Service Broker application.

In this scenario, the message is not sent to the target service. Additionally, you may receive one of the following time-out error messages:

This issue occurs because SQL Server has timed out. In the forwarding instance, there is a limit on the time that can elapse between when a message is sent and when the message is received. If the forwarding instance does not receive the message within the time limit, the message is dropped.

The time counter should start when the last byte of a new message is received. However, the time counter starts when the first byte of a new message is received. Therefore, you always receive a time-out error message if SQL Server takes a long time to receive a message.

The fix for this issue was first released in Cumulative Update 4. For more information about how to obtain this cumulative update package for SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 2 hotfix to an installation of SQL Server 2005 Service Pack 2. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

For more information about what files are changed, and for information about any prerequisites to apply the cumulative update package that contains the hotfix that is described in this Microsoft Knowledge Base article, click the following article number to view the article in the Microsoft Knowledge Base:

For more information about the list of builds that are available after SQL Server Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base: For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:For more information about how to obtain SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base: For more information about the new features and the improvements in SQL Server 2005 Service Pack 2, visit the following Microsoft Web site: For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: