Microsoft KB Archive/925102
Article ID: 925102
Article Last Modified on 11/15/2007
- Microsoft BizTalk Server 2006 Developer Edition
- Microsoft BizTalk Server 2006 Enterprise Edition
- Microsoft BizTalk Server 2006 Standard Edition
Consider the following scenario:
- A Web service contains two Web service methods in Microsoft BizTalk Server 2006. One method is a two-way Web service method. The other method is a one-way Web service method.
Note A two-way Web service method includes a request method and a response method. A one-way Web service method only includes a request method.
- A BizTalk orchestration uses both Web service methods in the same SOAP send port.
In this scenario, when an orchestration port uses the two Web service methods, the one-way method returns an unexpected response exception. The exception causes routing failures and suspended messages.
To work around this problem, use one of the following methods:
Make sure that the Web service contains either the one-way Web service method or the two-way Web service method.
Make sure that the Web service exposes either the one-way Web service method or the two-way Web service method.
Follow these steps:
- Manually define the one-way port type and the two-way port type instead of using a Web port type.
- Create the corresponding one-way Web service method and the solicit-response port in the BizTalk Explorer.
- In the SOAP transport properties dialog box, configure the proxy and the methods of the SOAP send port.
- Set the SOAP.MethodName property before you send the message out.
After you apply this hotfix, BizTalk Server queries the attributes that are compiled with the Web service method. Therefore, BizTalk Server can determine at runtime whether the Web service method is a one-way method or a two-way method. If the Web service method has the One-way property set to true, the unexpected responses are no longer generated.
A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.
To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:
Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:
No prerequisites are required
You do not have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace any other hotfixes
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
|File name||File version||File size||Date||Time||Platform|
Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Additional query words: messagebox soap orchestration one-way web method solicit response
Keywords: kbbug kbfix kbpubtypekc kbhotfixserver kbqfe KB925102