Article ID: 307564
Article Last Modified on 5/15/2006
APPLIES TO
- Microsoft BizTalk Server 2000 Service Pack 1a
- Microsoft BizTalk Server 2000 Standard Edition
This article was previously published under Q307564
SYMPTOMS
If you configure the advanced properties for multiple channels that are bound to the same port with a transport of an Application Integration Compononent (AIC) that implements the IPipelineComponentAdmin interface, properties that are changed in one channel may overwrite advanced properties in other channels that are bound to the same port.
RESOLUTION
To resolve this problem, obtain the latest service pack for Microsoft BizTalk Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
299664 INFO: How to Obtain the Latest BizTalk Server 2000 Service Pack
NOTE: After you apply SP2 on all computers, you will need to apply BTS_Configuration_Logic.SQL to the BizTalk Messaging Management database.
- On the Start menu, point to Programs, point to Microsoft SQL Server, and then click Query Analyzer.
- In the SQL Server list, click the name of the SQL Server instance that hosts the BizTalk Messaging Management database, enter the appropriate log in information, and then click OK.
- If you have Microsoft SQL Server 7.0 installed, in the DB list, click the name of the BizTalk Messaging Management database (for example, InterchangeBTM) and continue to step 5.
-or-
If you have Microsoft SQL Server 2000 installed, on the Query menu, click Change Database, and then continue to step 4.
- Click the name of the BizTalk Messaging Management database (for example, InterchangeBTM), and then click OK.
- On the File menu, click Open.
- In the Open Query File dialog box, in the Look in list, browse to \Program Files\Microsoft BizTalk Server\Setup.
- Click BTS_Configuration_Logic.SQL, and then click Open.
- On the Query menu, click Execute.
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 2000 Service Pack 2.
Keywords: kbbug kbfix kbbiztalk2000sp2fix kbhotfixserver KB307564
