Failed Upgrade in System Center 2012 R2 - Service Manager

  • Article

Applies To: System Center 2012 R2 Service Manager, System Center 2012 SP1 - Service Manager

An upgrade to Service Manager in System Center 2012 R2 might not finish successfully. The steps that you take to recover from a failed upgrade depend on the phase of the upgrade in which the failure occurs:

  • Failure occurs during the prerequisite check.

  • Failure occurs during predicted checks.

  • Failure occurs in an unpredictable manner before permanent changes are made to a management server.

  • Failure occurs in an unpredictable manner after permanent changes are made to a management server.

  • Failure occurs in an unpredictable manner after permanent changes are made to a database.

The upgrade might also fail because startup of the System Center Management Configuration service times out.

Failure occurs during the prerequisite check

Before the installation of Service Manager in System Center 2012 R2 begins, the system conducts a prerequisite check for certain requirements. If the system finds a condition in which Service Manager in System Center 2012 R2 will continue to function, you receive a warning. Warnings are identified with an exclamation point (!) in a yellow triangle. Conditions that the system has identified as a warning will not prevent you from installing Service Manager.

If the system finds a condition that is an absolute requirement, a failure indication appears. Failure indications are identified with an X in a red circle.

If either a warning or a failure indication appears, you can either cancel the installation and make the necessary changes, or make the appropriate changes and then click Check prerequisites again and continue with the installation. You must correct all failure conditions before the installation or upgrade can proceed.

Failure occurs during predicted checks

After you correct any failures that the system identified during the prerequisite check, you can click Next on the Prerequisites page of the wizard to start the upgrade or installation of Service Manager. The system checks for the following conditions during the installation or upgrade process:

  • The data warehouse database that you specified exists.

  • The computer running Microsoft SQL Server that you specified is not running Microsoft SQL Server 2008 Service Pack 1 (SP1), SQL Server 2008 Service Pack 2 (SP2), or SQL Server 2008 R2.

  • The hard disk drive that you specified for a database has at least 1 gigabyte (GB) of free space.

  • The System Center Data Access Service service can log on with the set of credentials that you supplied.

  • The System Center Management Configuration service can log on with the set of credentials that you supplied.

  • There is enough free disk space to install the upgraded files.

  • Setup can access the file location for the Service Manager installation.

If failures occur during these types of checks, you can make the appropriate changes. For example, you can specify a hard disk location that has sufficient space, and then on the Warning page, click Retry to continue the installation.

Failure occurs in an unpredictable manner before permanent changes are made to a management server

If an error occurs before permanent changes are made to the Service Manager management server or data warehouse management server—for example, before changes are made to the Structured Query Language (SQL) database or before management packs are imported—the error message that appears includes a Retry button. In this situation, you can correct the issue and then retry the installation or upgrade.

Failure occurs in an unpredictable manner after permanent changes are made to a management server

If an error occurs after permanent changes are made to the Service Manager management server or data warehouse management server—for example, after changes are made to the SQL database or after management packs are imported—the error message that appears does not include a Retry button. In this situation, you must reinstall the original version of the affected management server.

In any case, you need the backup of the encryption key. For the Service Manager management server, the encryption key is available only if you made a backup before you started the upgrade. For more information, see How to Back Up the Encryption Key in Service Manager.

Failure occurs in an unpredictable manner after permanent changes are made to a database

If an error occurs after permanent changes have been made to a database—for example, after management packs are imported or any other time that data is written into the database—the error message that appears does not include a Retry button.

At this point, your only option is to click Close and begin a disaster recovery process to restore the database. This recovery is possible only if you backed up the database before you started the upgrade process. For more information, see Backing Up Service Manager Databases.

Upgrade fails because Management Configuration service startup times out

On some computers, Service Manager Setup fails and rolls back if it cannot start the System Center Management Configuration service in a timely fashion. If this problem occurs, you might see the following entries in the installation log.

CAStartServices: Attempting to start service. OMCFG

CAStartServices: StartService failed. Error Code: 0x8007041D. 
 
ConfigureSDKConfigService: CAStartServices failed. Error Code: 0x8007041D. OMCFG

Error 0x8007041D indicates that the service did not respond to the start or control request in a timely fashion. In addition, the following event may be logged in the System Event log.

Log Name:      System
Source:        Service Control Manager
Event ID:      7009
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Description:
A timeout was reached (30000 milliseconds) while waiting for the System Center Management Configuration service to connect.

This problem occurs because a Microsoft .NET Framework 2.0 managed assembly that has an Authenticode signature takes longer than usual to load. The signature is always verified when the .NET Framework 2.0 managed assembly that has an Authenticode signature is loaded. In addition, the .NET Framework 2.0 managed assembly may take longer than usual to load because of various other settings. For example, the .NET Framework 2.0 managed assembly may take longer than usual to load because of the network configuration.

For additional information about the cause of this problem, see FIX: A .NET Framework 2.0 managed application that has an Authenticode signature takes longer than usual to start.

For information about possible workaround procedures, see How to Work Around Configuration Service Startup Issues.

-----
For additional resources, see Information and Support for System Center 2012.

Tip: Use this query to find online documentation in the TechNet Library for System Center 2012. For instructions and examples, see Search the System Center 2012 Documentation Library.
-----