Here’s another good KB article we published today that shows you how to import AVIcode 5.7 templates after upgrading to the 2012 version of OpsMgr:
After upgrading a System Center Operations Manager 2007 R2 management group that was integrated with AVIcode 5.7 to System Center 2012 - Operations Manager, when trying to edit new or existing AVIcode 5.7 templates in the Operations Console, one of these errors occurs: The page [AVIcode.SystemCenter.UIPages.LobASPNETChooseName] in the assembly [AVIcode.SystemCenter.UIPages, Version=5.7.491.0, Culture=Neutral, PublicKeyToken=5e9f8bbdb7409eb4] could not be loaded. Please make sure that the account you are running under has sufficient privileges to load the given assembly, or the Management Pack that defines this page is installed or the assembly containing the page is in the path of the executable or that the page derives from known Operations Manager page type. Microsoft.EnterpriseManagement.Internal.UI.Authoring.Extensibility.UISDKException: The page could not be loaded. Please review the errors and try again. ---> Microsoft.EnterpriseManagement.Internal.UI.Authoring.Extensibility.UISDKException: The page could not be loaded. Please review the errors and try again. ---> System.MissingMethodException: Method not found: 'Microsoft.EnterpriseManagement.ManagementGroup Microsoft.EnterpriseManagement.UI.UIPage.get_ManagementGroup()'.
After upgrading to the newer version of Operations Manager, the console cannot load the correct Wizard Pages for the AVIcode template and for the .NET Events view because it must reference binaries from the SDK for Operations Manager 2007. To allow monitoring configuration changes, this solution redirects the binding assemblies of the UI SDK for Operations Manager 2007 to the UI SDK for the newer version of Operations Manager. The Template need updating too, but this doesn’t happen automatically during setup.
When AVIcode .NET Enterprise Management Pack for Operations Manager 2007 is present in the management group, and the system gets upgraded, some management packs will need to be manually upgraded after setup has finished, in order to fix incompatibilities with the 2012 release of Operations Manager. The Management Pack files will be copied to the server under the directory where Operations Manager is installed, but not imported automatically. The MP files that need to be imported are: 1. AVIcode.DotNet.SystemCenter.Enterprise.Monitoring.mpb 2. AVIcode.DotNet.SystemCenter.Client.Monitoring.mp
To restore management pack templates functionality, the used should import the fix for the AVIcode Management Packs which will be copied by setup to the server under the directory where Operations Manager is installed.
For the most current version of this article please see the following:
2606375: Steps to import AVIcode 5.7 templates after upgrading to System Center 2012 - Operations Manager
J.C. Hornbeck | System Center Knowledge Engineer
App-V Team blog: http://blogs.technet.com/appv/ AVIcode Team blog: http://blogs.technet.com/b/avicode ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/ DPM Team blog: http://blogs.technet.com/dpm/ MED-V Team blog: http://blogs.technet.com/medv/ OOB Support Team blog: http://blogs.technet.com/oob/ Opalis Team blog: http://blogs.technet.com/opalis Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/ OpsMgr Support Team blog: http://blogs.technet.com/operationsmgr/ SCMDM Support Team blog: http://blogs.technet.com/mdm/ SCVMM Team blog: http://blogs.technet.com/scvmm Server App-V Team blog: http://blogs.technet.com/b/serverappv Service Manager Team blog: http://blogs.technet.com/b/servicemanager System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials WSUS Support Team blog: http://blogs.technet.com/sus/