Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 929796 - Last Review: January 2, 2007 - Revision: 1.3
MOM 2005 request sequences are not imported successfully when you follow the steps in the "Microsoft Operations Manager Web Sites and Services Management Pack Guide"
When you follow the steps in the
Microsoft Operations Manager Web Sites and Services Management Pack Guide
to import request sequences into Microsoft Operations Manager (MOM) 2005, the request sequences are not imported successfully.
Note To obtain this guide, visit the following Microsoft Web site:
You may experience this problem if you have configured a managed code response for an event rule that you import.
The following procedure appears in the "Importing Individual Request Sequences" section of the
Microsoft Operations Manager Web Sites and Services Management Pack Guide:
To import the Request Sequences and their data files:
- Make sure a local copy or shared folder of the exported files is accessible.
- Open the MOM Administrator console. Right-click Management Packs, and then select Import/Export Management Pack. Import the .akm file from your backup folder.
- Copy and paste the rules from the newly-imported rule group to the destination rule group under the Request Sequence Groups rule group.
- Note the new Rule GUID value assigned to each imported rule.
- Open the MP Configuration Wizard. Connect to the Management Server and select the Manage Request Sequence Groups configuration task. Proceed through the rest of the Wizard without making any changes. This step refreshes the local cache of Request Sequence data files.
- Open Windows Explorer, and browse to the C:\Documents and Settings\[logged on user’s account]\Application Data\ folder. Copy the Request Sequence XML data files from your backup folder to this Application Data folder.
- Rename the .xml files, using the new Rule ID values you noted in step 4.
- Open the MP Configuration Wizard again. Connect to the Management Server and select the Manage Request Sequence Groups configuration task. The imported Request Sequence Groups and Request Sequences should be displayed. Proceed through the rest of the Wizard and save your changes to the Management Server. This step updates the Request Sequence data files stored in the Web Sites and Services MP BITS virtual directory on the Management Server.
This procedure is not correct if you have configured a managed code response for an event rule that you import. In this case, you must modify the value of the
System.UInt32 method parameter in the imported rule to match that of the source rule.
To resolve this issue, follow these steps:
- Follow steps 1 through 6 in the "Importing Individual Request Sequences" section of the Microsoft Operations Manager Web Sites and Services Management Pack Guide. These steps appear in the "Cause" section.
- On the site to which you import the request sequences, start the MOM 2005 Administrator Console program.
- Locate the imported rule, right-click that rule, and then click Properties.
- In the RuleType Properties (ManagementGroupName) - RuleName dialog box, click the Responses tab.
- Click the managed code response, and then click Edit.
- In the Method parameters (in order) list, click System.UInt32, and then click Edit.
- In the Edit Method Parameter dialog box, click the option in the Value list that matches the value from the same rule in the source site from which you exported the rule.
- Click OK three times.
- Follow steps 7 through 8 in the "Importing Individual Request Sequences" section of the Microsoft Operations Manager Web Sites and Services Management Pack Guide.
To obtain the Microsoft Web Sites and Services Management Pack for MOM 2005 package, visit the following Microsoft Web site:
APPLIES TO
- Microsoft Operations Manager (MOM) 2005
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate