Microsoft KB Archive/922907

= BizTalk Server monitoring does not work as expected after you import the BizTalk Server 2004 Management Pack for MOM and the BizTalk Server 2006 Management Pack for MOM 2005 into the same MOM management group =

Article ID: 922907

Article Last Modified on 7/18/2006

-

APPLIES TO


 * Microsoft BizTalk Server 2006 Standard Edition
 * Microsoft BizTalk Server 2006 Enterprise Edition
 * Microsoft BizTalk Server 2006 Developer Edition
 * Microsoft BizTalk Server 2004 Standard Edition
 * Microsoft BizTalk Server 2004 Enterprise Edition
 * Microsoft BizTalk Server 2004 Developer Edition
 * Microsoft BizTalk Server 2004 Partner Edition

-





SYMPTOMS
Consider the following scenario. You import the Microsoft BizTalk Server 2004 Management Pack for MOM into Microsoft Operations Manager (MOM) 2005. You then import the Microsoft BizTalk Server 2006 Management Pack for MOM 2005 into the same MOM management group. In this scenario, BizTalk Server 2004 monitoring may not work as expected.

This issue can also occur if you import the BizTalk Server 2006 Management Pack for MOM 2005, and then you import the BizTalk Server 2004 Management Pack for MOM. In this scenario, BizTalk Server 2006 monitoring may not work as expected.



CAUSE
This issue occurs because the existing computer group is overwritten when you import the the BizTalk Server 2004 Management Pack for MOM and the BizTalk Server 2006 Management Pack for MOM 2005 into the same MOM management group.

For example, the BizTalk Server 2004 computer group is overwritten by a BizTalk Server 2006 computer group when you import the BizTalk Server 2004 Management Pack for MOM, and then you import the BizTalk Server 2006 Management Pack for MOM 2005.



RESOLUTION
To resolve this issue, delete the existing BizTalk Server computer group, and then re-create the BizTalk Server 2004 and BizTalk Server 2006 computer groups. To do this, follow these steps.

Note These steps assume that you imported the BizTalk Server 2004 Management Pack for MOM into the MOM 2005 Administrator Console, and then imported the BizTalk Server 2006 Management Pack for MOM 2005.  On a test server, import the BizTalk Server 2004 Management Pack for MOM. Note the properties of the BizTalk Server 2004 computer group. Then, import the BizTalk Server 2006 Management Pack for MOM 2005. Note the properties of the BizTalk Server 2006 computer group. Start the MOM 2005 Administrator Console, expand Management Packs, and then expand Computer Groups. Delete both the Biztalk Server 2004 MOM computer group and the BizTalk Server 2006 computer group if they are present. Right-click Management Packs, and then click Commit Configuration Change. In the MOM 2005 Administrator Console, expand Management Packs, and then click Computer Attributes. In the right pane, right-click BizTalk Server Root Key, and then click Properties.</li> On the Type tab, click Registry value.</li> On the Registry Path tab, type SOFTWARE\Microsoft\BizTalk Server\3.0\ProductVersion .</li> On the Value tab, click Retrieve registry value and convert to, click string, and then click OK.</li> Right-click Computer Groups, click Create Computer Group, and then click Next.</li> In the Name box, type BizTalk Server 2004, and then click Next.</li> Follow the steps on the screen to configure the computer group according to the properties that you noted in step 1.

Note Go to step 13 when the Formula window appears.</li> In the Formula window, click Specify a formula for the computer group. In the Formula for computer group box, create the following formula:

MatchWildcard(AttributeValue(BizTalk Server Root Key), &quot;3.0.*&quot;)

</li> Expand Rule Groups, right-click Microsoft BizTalk Server 2004, and then click Associate with Computer Group.</li> Click Add, click BizTalk Server 2004, and then click OK.</li> Right-click Management Packs, and then click Commit Configuration Change.</li> Right-click Computer Groups, click Create Computer Group, and then click Next.</li> In the Name box, type BizTalk Server 2006, and then click Next.</li> Follow the steps on the screen to configure the computer group according to the properties that you noted in step 1.</li> Expand Rule Groups, expand Microsoft BizTalk Server 2006, right-click BAM, click Associate with Computer Group, click Add, click BizTalk Server 2006, and then click OK.</li> Expand Rule Groups, expand Microsoft BizTalk Server 2006, right-click BAS, click Associate with Computer Group, click Add, click BizTalk Server 2006, and then click OK.</li> Expand Rule Groups, expand Microsoft BizTalk Server 2006, right-click BizTalk Server Core, click Associate with Computer Group, click Add, click BizTalk Server 2006, and then click OK.</li> <li>Expand Rule Groups, right-click Enterprise Single Sign-On, and then click Associate with Computer Group.</li> <li>Click Add, click BizTalk Server 2006, and then click OK.</li></ol>

Notes
 * When you re-create the BizTalk Server 2004 group, you must update the BizTalk Server Root Key computer attribute. This attribute is used to identify the BizTalk Server 2004 computer.
 * If you have not already imported the BizTalk Server 2006 Management Pack for MOM 2005 and the BizTalk Server 2004 Management Pack for MOM into the same MOM management group, you can create the appropriate computer group. You do not have to delete the existing computer group.

<div class="status_section">

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.

<div class="moreinformation_section">

MORE INFORMATION
The BizTalk Server 2004 Management Pack for MOM and the BizTalk Server 2006 Management Pack for MOM 2005 share many common MOM providers for performance measuring rules. You can set different sampling rates for the BizTalk Server 2004 Management Pack for MOM and the BizTalk Server 2006 Management Pack for MOM 2005. To do this, make a copy of the provider that you want in the MOM 2005 Administrator Console, and then create a performance rule to generate an event, an alert, or a response that is based on the data that is collected.

The following are the common providers:
 * BizTalk:Messaging-Documents processed/Sec-<All>-15.0-minutes
 * BizTalk:Messaging-Documents processed-<All>-15.0-seconds
 * BizTalk:Messaging-Documents received/Sec-<All>-5.0-minutes
 * BizTalk:Messaging-Documents received-<All>-15.0-minutes
 * BizTalk:Messaging-Documents suspended/Sec-<All>-5.0-minutes
 * BizTalk:Messaging-Documents suspended-<All>-15.0-minutes
 * BizTalk:Messaging-ID Process-<All>-15.0-minutes
 * XLANG/s Orchestrations-% used physical memory-<All>-15.0-minutes
 * XLANG/s Orchestrations-Database transactions/sec-<All>-15.0-minutes
 * XLANG/s Orchestrations-Database transactions-<All>-15.0-minutes
 * XLANG/s Orchestrations-Dehydratable orchestrations-<All>-15.0-minutes
 * XLANG/s Orchestrations-Dehydrating orchestrations-<All>-15.0-minutes
 * XLANG/s Orchestrations-Idle orchestrations-<All>-15.0-minutes
 * XLANG/s Orchestrations-Megabytes allocated private memory-<All>-15.0-minutes
 * XLANG/s Orchestrations-Megabytes allocated virtual memory-<All>-15.0-minutes
 * XLANG/s Orchestrations-MessageBox databases connection failures-<All>-15.0-minutes
 * XLANG/s Orchestrations-Orchestrations completed/sec-<All>-15.0-minutes
 * XLANG/s Orchestrations-Orchestrations completed-<All>-15.0-minutes
 * XLANG/s Orchestrations-Orchestrations dehydrated/sec-<All>-15.0-minutes
 * XLANG/s Orchestrations-Orchestrations dehydrated-<All>-15.0-minutes
 * XLANG/s Orchestrations-Orchestrations discarded/sec-<All>-15.0-minutes
 * XLANG/s Orchestrations-Orchestrations discarded-<All>-15.0-minutes
 * XLANG/s Orchestrations-Orchestrations rehydrated/sec-<All>-15.0-minutes
 * XLANG/s Orchestrations-Orchestrations rehydrated-<All>-15.0-minutes
 * XLANG/s Orchestrations-Orchestrations resident in-memory-<All>-15.0-minutes
 * XLANG/s Orchestrations-Orchestrations suspended/sec-<All>-15.0-minutes
 * XLANG/s Orchestrations-Orchestrations suspended-<All>-15.0-minutes
 * XLANG/s Orchestrations-Pending messages-<All>-15.0-minutes
 * XLANG/s Orchestrations-Pending work items-<All>-15.0-minutes
 * XLANG/s Orchestrations-Runnable orchestrations-<All>-15.0-minutes
 * XLANG/s Orchestrations-Running orchestrations-<All>-15.0-minutes

<div class="references_section">