https://www.betaarchive.com/wiki/index.php?title=Microsoft_KB_Archive/246038&feed=atom&action=history
Microsoft KB Archive/246038 - Revision history
2024-03-29T00:06:12Z
Revision history for this page on the wiki
MediaWiki 1.39.3
https://www.betaarchive.com/wiki/index.php?title=Microsoft_KB_Archive/246038&diff=135081&oldid=prev
3155ffGd: importing KB archive
2020-07-18T16:12:51Z
<p>importing KB archive</p>
<p><b>New page</b></p><div><div id="nsbanner"><br />
<br />
<div id="bannerrow1"><br />
<br />
{|<br />
| Knowledge Base<br />
|<br />
|}<br />
<br />
<br />
</div><br />
<div id="TitleRow"><br />
<br />
= <span id="KB246038"></span>How To Avoid COM/MTS Object Activation Delay on MSCS =<br />
<br />
<br />
</div><br />
<br />
</div><br />
<div id="nstext" valign="BOTTOM"><br />
<br />
Article ID: 246038<br />
<br />
Article Last Modified on 1/5/2006<br />
<br />
<br />
-----<br />
<br />
APPLIES TO<br /><br />
<br /><br />
<br />
* Microsoft COM+ 1.0<br />
* Microsoft Transaction Services 2.0<br />
<br />
<br />
-----<br />
<br />
<div class="notice_section"><br />
<br />
This article was previously published under Q246038<br />
<br />
</div><br />
<div class="summary_section"><br />
<br />
== SUMMARY ==<br />
<br />
If you follow the default Microsoft Cluster Server (MSCS) installation settings, you will get a 32-second delay the first time you try to access the COM+/MTS object.<br />
<br />
</div><br />
<div class="moreinformation_section"><br />
<br />
== MORE INFORMATION ==<br />
<br />
The nature of this problem is described in the following Microsoft Knowledge Base article:<br />
<div class="indent"><br />
<br />
[[../288886|288886]] PRB: Delayed DCOM Activation on Multihomed Computers<br />
<br />
<br />
</div><br />
However, the solution that is provided in Q288886 does not apply to MSCS and may cause Microsoft Distributed Transaction Coordinator (MS DTC) access violations.<br /><br />
<br /><br />
Two possible solutions are available (note that changes should be made on both nodes).<br />
==== Method 1: Disable WINS on the Private Network Interface ====<br />
<br />
Disable the Microsoft Windows Internet Naming Service (WINS) for the private network interface cards (NICs) for node communication. This will prevent private NICs' IP addresses from being broadcast over network. Hence, the client can only access the client NIC's IP. For additional information on WINS configuration, click the article number below to view the article in the Microsoft Knowledge Base:<br />
<div class="indent"><br />
<br />
[[../193890|193890]] Recommend WINS Configuration for Microsoft Cluster Server<br />
<br />
<br />
</div><br />
==== Method 2: Change the Binding Order of the Network Adapters ====<br />
<br />
Change the order of network cards: On the '''Binding''' tab available from the '''Network''' application in Control Panel, select '''Choosing Protocol''' and change the order in which NICs are listed. Then restart the computer.<br /><br />
<br /><br />
'''NOTE:''' The order should be the same for both nodes. Also note that method 2 is not as good as the first approach because the performance for node-to node communication will be affected.<br />
<br />
</div><br />
<div class="references_section"><br />
<br />
== REFERENCES ==<br />
<br />
For additional information, click the article numbers below to view the articles in the Microsoft Knowledge Base:<br />
<div class="indent"><br />
<br />
[[../193890|193890]] Recommend WINS Configuration for Microsoft Cluster Server<br />
<br />
<br />
</div><br />
<div class="indent"><br />
<br />
[[../258750|258750]] Recommended Private 'Heartbeat' Configuration on a Cluster Server<br />
<br />
<br />
</div><br />
<div class="indent"><br />
<br />
[[../288886|288886]] PRB: Delayed DCOM Activation on Multihomed Computers<br />
<br />
<br />
</div><br />
<br />
</div><br />
<br /><br />
<br />
Additional query words: server cluster<br />
<br />
Keywords: kbhowto kbdtc KB246038<br />
<br />
<div class="footer"><br />
<br />
<br /><br />
<br />
<br />
-----<br />
<br />
[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]<br />
<br />
<span>© Microsoft Corporation. All rights reserved.</span><br />
<br />
<br />
</div><br />
<br />
</div></div>
3155ffGd