When you upgrade Microsoft System Center Operations Manager 2007
to Operations Manager 2007 Service Pack 1, and then you try to modify a Web application that was created before the upgrade, the modifications are not saved. Additionally, you receive the following
error message:
Date:
Date
Application: System Center Operations
Manager 2007
Application Version: 6.0.6278.0
Severity:
Error
Message: There was an error while applying the
changes.
Stack_Information
This
issue occurs because the
Web application that was created in the original version of Operations Manager
2007 is incompatible with the new
features that are included
in Operations Manager 2007 Service Pack 1.
Update Information
This fix is contained within the Microsoft System Center Operations Manager 2007 Service Pack 1 update. To see a list of issues are fixed and how to obtain the cumulative rollup, refer to this article in the Microsoft Knowledge Base:
971541Â
(http://kbalertz.com/Feedback.aspx?kbNumber=971541/
)
Description of System Center Operations Manager 2007 Service Pack 1
Hotfix information
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
Prerequisites
To apply this hotfix, you must have System Center Operations
Manager 2007 Service Pack 1 installed on the computer.
Restart requirement
You do not have to restart the computer after you apply this
hotfix.
Hotfix replacement information
This hotfix does not replace any other hotfixes.
Hotfix installation instructions
You must apply this hotfix on each computer that hosts an
Operations Manager 2007 Operations Console. Before you apply the hotfix, we
recommend that you back up any
management packs that contain
Web applications that were created by using
the original version of Operations Manager 2007. To apply this hotfix, follow
these steps:
- On the computer on which you want to apply this hotfix,
close all instances of Operations Console.
- Copy the
SystemCenterOperationsManager2007-SP1-KB951527-X86-X64-ENU.MSI file to a local
folder or to a shared folder, and then run the file.
- Restart Operations Console.
After you apply this hotfix, we recommend that you
open and then resave all Web applications in Operations Manager 2007.
After you do this, Web applications
can use the new features in Operations Manager 2007 Service Pack 1.
If a Web application has not migrated
correctly,
you will see an asterisk (*) in the title bar
when you open the Web application in Web Application Editor.
Some
Web application monitors may be in an unhealthy state. Or, some alerts that are
triggered by Web application monitors may be unresolved.
After you resave the Web applications, the monitor states are
reset, and the unresolved
alerts are resolved.
File information
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the
Time Zone tab in the
Date and Time item in Control Panel.
System Center Operations Manager 2007 with Service Pack 1, x86-based version
Collapse this tableExpand this table
| File name | File version | File
size | Date | Time | Platform |
|---|
| Microsoft.enterprisemanagement.ui.authoring.dll | 6.0.6278.28 | 5,832,704 | 30-May-2008 | 22:45 | x86 |
System Center Operations Manager 2007 with Service Pack 1, x64-based version
Collapse this tableExpand this table
| File name | File version | File
size | Date | Time | Platform |
|---|
| Microsoft.enterprisemanagement.ui.authoring.dll | 6.0.6278.28 | 5,832,704 | 30-May-2008 | 19:21 | x64 |
Microsoft
has confirmed that this is a problem in the Microsoft products that are listed
in the "Applies to" section.This problem was first corrected in Microsoft System Center Operations Manager 2007 R2.
For a list of issues that are fixed in Microsoft System Center Operations Manager 2007 R2, refer to the following article in the Microsoft Knowledge base:
971410Â
(http://kbalertz.com/Feedback.aspx?kbNumber=971410/
)
List of issues that are fixed in System Center Operations Manager 2007 R2
For more information about
software update terminology, click the following article number to view the
article in the Microsoft Knowledge Base:
824684Â
(http://kbalertz.com/Feedback.aspx?kbNumber=824684/
)
Description of the standard terminology that is used to describe Microsoft software updates
Stack output
The error message that is mentioned
in the "Symptoms" section includes the following stack output:
Microsoft.EnterpriseManagement.Common.ObjectNotFoundException: An object of
type UnitMonitorType with Id 2d5d403a-b1e3-e6cf-ec4e-7cde81890488 was not found.
at
Microsoft.EnterpriseManagement.Configuration.TypeSpaceCache.GetType[T](Guid
managementPackObjectId, Dictionary`2 objectIdMap)
at
Microsoft.EnterpriseManagement.Configuration.TypeSpaceCache.GetUnitMonitorType(Guid
unitMonitorTypeId)
at Microsoft.EnterpriseManagement.ManagementGroup.GetUnitMonitorType(Guid
id)
at
Microsoft.EnterpriseManagement.Configuration.ManagementPackDatabaseReader.GetUnitMonitorType(ManagementPackElementReference`1
reference)
at
Microsoft.EnterpriseManagement.Configuration.ManagementPack.Microsoft.EnterpriseManagement.Configuration.IO.IManagementPackSearch.GetUnitMonitorType(ManagementPackElementReference`1
reference)
at
Microsoft.EnterpriseManagement.Configuration.ManagementPack.GetUnitMonitorType(String
name)
at
Microsoft.EnterpriseManagement.WebApplicationMonitoring.RequestType.UpdateUnitMonitor(ManagementPack
mp, MonitoringClass targetClass, UnitMonitorConfiguration
unitMonitorConfiguration, UpdateMode mode)
at
Microsoft.EnterpriseManagement.WebApplicationMonitoring.RequestType.UpdateDefaultMonitors(ManagementPack
mp, MonitoringClass targetClass)
at
Microsoft.EnterpriseManagement.WebApplicationMonitoring.RequestType.UpdateMonitors(ManagementGroup
mg, ManagementPack mp, MonitoringClass targetClass)
at
Microsoft.EnterpriseManagement.WebApplicationMonitoring.WebApplication.UpdateMonitoringConfiguration(ManagementGroup
mg, ManagementPack mp, MonitoringClass monitoringClass)
at
Microsoft.EnterpriseManagement.WebApplicationMonitoring.WebApplication.UpdateTypes(ManagementGroup
mg, ManagementPack mp, MonitoringClass monitoringClass)
at
Microsoft.EnterpriseManagement.WebApplicationMonitoring.WebApplication.AcceptChanges(ManagementGroup
mg, ManagementPack mp)
at
Microsoft.EnterpriseManagement.Internal.UI.Authoring.WebApp.WebApplicationEditorForm.<Worker_DoWork_Apply>b__3(Object
, ConsoleJobEventArgs )
at
Microsoft.EnterpriseManagement.Mom.Internal.UI.Console.ConsoleJobExceptionHandler.ExecuteJob(IComponent
component, EventHandler`1 job, Object sender, ConsoleJobEventArgs args)