Export (0) Print
Expand All

Appendix A: Known RTM to SP1 Upgrade Issues

Updated: May 22, 2009

Applies To: Operations Manager 2007 SP1

The following items are known issues with the Microsoft System Center Operations Manager 2007 SP1 release.

An "Audit Collection Services update failed" Error Might Occur When Upgrading to Audit Collection Services SP1

An "Audit Collection Services update failed" error might be displayed after performing an upgrade of the ACS Collector. The error ID that will be displayed is 0x00000BC2. This error incorrectly states that the upgrade failed.

Workaround: Restart the computer. The error code of 0x00000BC2 means that changes have been made but will not be effective until the computer has been restarted.

Additional Upgrade Steps Must Be Performed When Installing or Reinstalling Reporting in an Environment Where the RMS Was Upgraded from SP1 RC to SP1

If your environment contains a root management server that was at one time at the SP1 RC level, and was later upgraded to SP1, you must follow the steps below after Reporting has been installed.

Workaround: Add the credentials you specified for the Data Reader account to the Operations Manager Report Operators User Role. See the topic "How to Add Users or Groups to the Report Operator User Role in Operations Manager 2007" in the Operations Manager Help.

Agents That Are Not Upgraded Can Consume Excessive System Resources

Agents that are not upgraded in an environment where the management server has been upgraded can cause the computer hosting the agent to consume excessive system resources.

Workaround: Upgrade the agent, or if this is not possible, install hotfix Q941811. This hotfix is available on the Operations Manager 2007 SP1 installation media.

Cluster May Failover to Another Node While Performing the Upgrade

If an upgrade on a clustered node fails, examine the Operations Manager Event log for the following event:

Event Type: Error

Event Source: OpsMgr SDK Service

Event Category: None

Event ID: 23680

Description:

The System Center Operations Manager SDK Service failed due to an unhandled exception.

The service will attempt to restart.

Exception:

System.TypeLoadException: Method 'SetupEventsByManagedEntityIdAndCriteriaAndClassReader' in type 'Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.SdkDataAccess' from assembly 'Microsoft.Mom.Sdk.ServiceDataLayer, Version=6.0.4900.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' does not have an implementation.

at Microsoft.EnterpriseManagement.Mom.Sdk.Service.SdkSubService.AsyncStartCallback(Object notUsed)

at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)

at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(Object state)

This issue might occur when a service is stopped during the upgrade. The cluster interprets this as a failure and then performs a failover to another node.

Workaround: To prevent this issue, use the following procedure to limit the nodes that a service can run on to the specific node you are upgrading.

To limit nodes that a service can run on

  1. In the Cluster Administrator pane, right-click the service you want to change (for example, OpsMgr Health Service), and then click Properties.

  2. In the OpsMgr Health Service Properties dialog box, click Modify.

  3. In the Modify Preferred Owner dialog box, under Available nodes, select the node you are performing the upgrade on, ensure it is the only node listed under Preferred owners, and then click OK.

Health Service State Directory Error

An error regarding the deletion of the Health Service State directory during upgrade of the root management server, management server, gateway server, or agent might occur during the upgrade.

The error contains the following information:

Event Type: Error

Event Source: Service Control Manager

Event Category: None

Event ID: 7023

Description:

The OpsMgr Health Service service terminated with the following error:

%%2164195332

Workaround: Use the following procedure to manually delete the directory and then restart the OpsMgr Health Service.

To delete the Health Service State directory and restart the Health Service

  1. Click Start, point to Programs, point to Administrative Tools, and then click Services (on a client operating system, the Services application is accessed through Control Panel).

  2. In the Name column, right-click OpsMgr Health Service, and then click Stop.

  3. Start Windows Explorer and navigate to %Program Files%\System Center Operations Manager 2007.

  4. Right-click the Health Service State folder, and then click Delete.

  5. Exit Windows Explorer.

  6. Click Start, point to Programs, point to Administrative Tools, and then click Services (on a client operating system, the Services application is accessed through Control Panel).

  7. In the Name column, right-click OpsMgr Health Service, and then click Start.

To delete the Health Service State directory on a cluster and restart the Health Service

  1. Log on to the active node of the cluster.

  2. Using the Cluster Administrator, set the OpsMgr Health Service to offline.

  3. Start Windows Explorer, navigate to the Health Service State folder on the shared drive, and then click Delete.

  4. Exit Windows Explorer.

  5. Using the Cluster Administrator, set the OpsMgr Health Service to online.

Unable to Start the Operations Console After Upgrading from Operations Manager 2007 SP1 RC to Operations Manager 2007 SP1 When Hotfixes Q945313 or Q946528 Have Been Installed

If you are upgrading from Operations Manager 2007 SP1 RC to Operations Manager 2007 SP1 and you had hotfixes Q945313 or Q946528 installed, you might be unable to start the Operations console. Moreover, the Operations Manager database version number in the dbo__MOMManagementGroupInfo__ table will not have been updated.

Workaround: Using SQL Server Management Studio, open the OperationsManager database, locate the dbo__MOMManagementGroupInfo__ table, and change the DBVersion entry from 6.0.6246.0 to 6.0.627x.0, where X is the last digit of the version number for Operations Manager 2007 SP1.

A Multihomed Agent Stops Sending Events to Management Groups That Are Not Updated

If an agent is multihomed to two management groups where one management group has been upgraded to SP1 and the other management group has not, the agent will stop sending events to the non upgraded management group.

Workaround: If possible, upgrade the remaining management group to SP1. If that is not possible, install hotfix Q941557 on the computer hosting the management server that the agent is connecting to in the non-upgraded management group. This hotfix is available on the Operations Manager 2007 SP1 installation media.

An Error Event with an ID of 4511 Might Occur When Upgrading to SP1

An event of type error with an Event ID of 4511 might occur after upgrading a management server when the associated agents are monitoring cluster-aware applications; for example, Microsoft SQL Server or Microsoft Exchange. This issue will occur only when upgrading from Operations Manager 2007 to Operations Manager 2007 SP1. This issue will not occur when upgrading from an RC version of Operations Manager 2007 SP1 to Operations Manager 2007 SP1. This issue might occur after the management server is updated and before the agent is updated.

Workaround: This issue will be resolved after the agent has been updated to Operations Manager 2007 SP1. We recommend that agents are updated as soon as possible.

Uninstalling the Operations Console Permanently Removes the Command Shell

Removing the Operations console from a computer that is also hosting either a root management server or management server will result in the permanent loss of the Command Shell on that computer. This issue does not occur if the Operations console is on a stand-alone computer.

After the Operations console is removed, you can reinstall the Operations console, but not the Command Shell.

Upgrading Microsoft System Center Desktop Error Monitoring 2007 Might Fail to Upgrade if Hotfixes Have Been Installed

Attempting to upgrade System Center Desktop Error Monitoring 2007 to System Center Desktop Error Monitoring 2007 SP1 or attempting to upgrade System Center Desktop Error Monitoring 2007, which has been licensed (Select version) to Select SP1, might fail if hotfixes have been installed.

Workaround: Customers using System Center Desktop Error Monitoring 2007 should not use the Operations Manager 2007 SP1 upgrade and instead wait for the System Center Desktop Error Monitoring 2007 SP1 Upgrade to be released. Customers who have licensed their copy of System Center Desktop Error Monitoring 2007 to the Select version should contact Microsoft for upgrade instructions before attempting an upgrade.

Error Messages

When you use Add or Remove Programs to remove the Operations console, the following issues might occur.

  • Warning 25453. Setup failed to cleanup the service stat folder at <path to Operations Manager>\Health Service State. Please remove it manually.

  • Error 1334. The file F_Microsoft.Mom.Sdk.OperationsManager.ClientShell.Startup.ps1.E1C3A829_C8F3_443F_B5FEE_0CE01DB47829 cannot be installed because the file cannot be found in cabinet file Data.Cab.

Click OK on any error message that displays. These errors can be ignored.

Dialog Boxes Indicate an Upgrade When Uninstalling the Operations Console

When you use Add or Remove Programs to remove the Operations console, dialog boxes might display indicating that you are upgrading Operations Manager. Make the same choices you made when you performed the upgrade. The Operations console is removed during this process.

Workaround: Install the Operations console and Command Shell on a stand-alone computer from the Operations Manager 2007 installation media, and then upgrade to SP1.

Attempting to Add Additional Components Might Fail

Attempting to add additional components to a computer that has been upgraded to Operations Manager 2007 SP1 might fail when double-clicking SetupOM.exe from the SP1 media.

Workaround: Use Add or Remove Programs and select Modify to add additional components after upgrading to SP1.

In the following example, an Operations console will be installed on a computer that hosts a management server. The management server was previously upgraded to SP1.

To Add Additional Components to Operations Manager 2007 SP1

  1. Click Start, point to Settings, and then click Control Panel.

  2. In Control Panel, double-click Add or Remove Programs.

  3. In Add or Remove Programs, click Change or Remove Programs.

  4. In the list of Currently installed programs, click System Center Operations Manager 2007, and then click Change.

  5. On the Welcome to the System Center Operations Manager 2007 Setup Wizard page, click Upgrade to Ops Mgr 2007, and then click Next.

  6. On the End-User License Agreement page, read the licensing terms, click I accept the terms in the license agreement, and then click Next.

  7. On the Ready to Install the Program page, click Install.

    noteNote
    No changes to your installation will take place at this time.

  8. On the Welcome to the System Center Operations Manager 2007 Setup Wizard page, click Next.

  9. On the System Center Operations Manager 2007 Maintenance page, click Modify, and then click Next.

  10. On the Custom Setup page, select the components you want to add. For example, click User Interfaces, click This component will be installed on local hard drive, and then click Next.

  11. On the Customer Experience Improvement Program page, do one of the following:

    • If you do not want your organization to participate in the program, leave the default option I don't want to join the program selected, and then click Next.

    • If you want your organization to participate in the program, select Join the Customer Experience Improvement Program, and then click Next.

  12. On the Ready to Modify the Program page, click Install.

    noteNote
    Errors messages might be displayed. Press OK on any error dialog boxes that display.

  13. On the Completing the System Center Operations Manager 2007 Setup Wizard page, click Finish.

  14. Close the Add or Remove Programs dialog box.

  15. Close the Control Panel dialog box.

The SP1 Release Includes OpsMgr VSS Writer Service

A new OpsMgr VSS Writer Service has been added to computers that host either a root management server or a management server. The Volume Shadow Copy Service provides the means for creating consistent point-in-time copies of data known as shadow copies. Disabling this service will not impact any other Operations Manager 2007 functionality.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft