Article ID: 322054
Article Last Modified on 11/15/2007
APPLIES TO
- Microsoft BizTalk Server 2002 Standard Edition
This article was previously published under Q322054
SYMPTOMS
BizTalk Server 2002 uses the root node of the body of a BizTalk Framework (BTF) message to determine the message type. However, when several different message types have the same root node name, you may want to specify the message type in the SOAP envelope.
RESOLUTION
Service Pack Information
To resolve this problem, obtain the latest service pack for Microsoft BizTalk Server 2002. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
815781 How to Obtain the Latest BizTalk Server 2002 Service Pack
Hotfix Information
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:
The English version of this fix should have the following file attributes or later:
Date Time Version Size File name
-----------------------------------------------------------------
11-Apr-2002 9:41 13,680 BTM_PriorityUpgrade.sql
11-Apr-2002 9:41 19,632 SQ_PriorityUpgrade.sql
30-Apr-2002 14:59 3.0.1514.0 172,304 BizTalkHTTPReceive.dll
30-Apr-2002 14:56 3.0.1514.0 24,848 BTStrace.dll
30-Apr-2002 14:59 3.0.1514.0 131,344 CisAPI.dll
30-Apr-2002 14:59 3.0.1514.0 524,560 CisCore.dll
30-Apr-2002 14:56 3.0.1514.0 86,288 CisDAV.dll
30-Apr-2002 14:59 3.0.1514.0 250,128 CisDTA.dll
30-Apr-2002 14:59 3.0.1514.0 405,776 CisEngine.dll
30-Apr-2002 14:56 3.0.1514.0 61,712 CisErrLog.dll
30-Apr-2002 14:59 3.0.1514.0 172,304 CisMsg.dll
30-Apr-2002 14:59 3.0.1514.0 712,976 CisParser.dll
30-Apr-2002 14:59 3.0.1514.0 20,752 CisPerf.dll
30-Apr-2002 14:59 3.0.1514.0 471,312 CisSerializer.dll
30-Apr-2002 14:56 3.0.1514.0 53,520 DbAccessor.dll
30-Apr-2002 14:59 3.0.1514.0 348,432 Mscis.exe
30-Apr-2002 14:59 3.0.1514.0 188,688 SerializeDoc.dll
30-Apr-2002 14:59 3.0.1514.0 487,696 ValidateDoc.dll
To install this fix, follow these steps:
- Stop the Biztalk Messaging Service.
- Copy Biztalkhttpreceive.dll to the \Biztalk server\Httpreceive directory and any other locations that this file has been copied to.
- Copy all of the other files to the \Biztalk server\ directory.
- Use the SQL Query Analyzer to apply BTM_PriorityUpgrade.sql to the InterchangeBTM database.
- Use the SQL Query Analyzer to apply SQ_PriorityUpgrade.sql to the InterchangeSQ database.
- Add the following two registry values:
- BTFInboundGetDocType
- BTFOutboundGetDocType
- Start the BizTalk Messaging Service.
NOTE: All servers that share the database must be upgraded. Any servers with the old files fail to start after InterchangeBTM and InterchangeSQ have been updated.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
This problem was first corrected in Microsoft BizTalk Server 2002 Service Pack 1.
MORE INFORMATION
With this fix, the messageType element is added to the BTF Services tag. Note that the namespace for messageType is new:
<services xmlns="http://schemas.biztalk.org/btf-2-0/services">
<messageType xmlns="http://schemas.biztalk.org/bts/messageType">CommonPO2</messageType>
</services>
You need two registry values to turn on the new behavior:
BTF Inbound:
BizTalk Server looks for messageType under the Services tag for the message type. If messageType does not exist, BizTalk Server uses the root node of the body to determine the message type. This BTF inbound behavior can be turned on with a registry setting under the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BTSSvc
Create a DWORD value named BTFInboundGetDocType, and then assign it a value of 1.
BTF Outbound:
BizTalk Server will serialize ServicesmessageType document specification name/messageType/Services. This BTF outbound behavior can be turned on with a registry setting under the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BTSSvc
Create a DWORD value named BTFOutboundGetDocType, and then assign it a value of 1.
Keywords: kbhotfixserver kbqfe kbbiztalk2002sp1fix kbbug kbfix KB322054
