Chat with us, powered by LiveChat

When installing Microsoft System Center Service Manager (SCSM) 2010, 90% of the time the independent installations of Service Manager or the Data Warehouse are successful. Microsoft has done a great job in managing all the pre-requisites of an installation prior to an Administrator actually selecting the “install” button. Even with all these fail safes in place, there are a few occasions where the installation does encounter an issue and errors out. Now if an Administrator has not snapshot their VM prior to installation (shame on you), you may find yourself in a precarious situation and will most likely start from scratch as to have the “cleanest” install possible.

Problem
In this remaining 10% of installation errors, our team runs into the below screenshot the most. It states “an error occurred while executing custom action:RollbackCleanup”.

If you were to take a look at Event Viewer, within the System event log you will see the following error:

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 .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. Additionally, 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 the Microsoft Support Web site article (http://go.microsoft.com/fwlink/?LinkId=207190).

Solution
In order to solve this issue, you must increase the Service timeout settings within the registry in order to allow for Service Manager adequate time to restart its services. Beware that this workaround is a global setting, and it will affect timeouts for every service. The following steps outline how to make these changes:

To work around this problem, modify the registry to increase the default time-out value for the service control manager. To increase this value to 600 seconds, follow these steps:

  1. Click Start, click Run, type regedit, and then click OK.
  2. Locate and then click the following registry subkey:
    1. HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControl
  3. In the right pane, locate the ServicesPipeTimeout entry
    Note: If the ServicesPipeTimeout entry does not exist, you must create it. To do this, follow these steps:
    1. On the Edit menu, point to New, and then click DWORD Value.
    2. Type ServicesPipeTimeout, and then press ENTER.
  4. Right-click ServicesPipeTimeout, and then click Modify.
  5. Click Decimal, type 600000, and then click OK
This value represents the time in milliseconds before a service times out.
  6. Restart the computer.

For additional details about the registry key, see the Microsoft Support Web site article. After these changes are made, your Server instance will allow adequate time for Service Manager to restart its services and perform a successful installation.

 

Recommendations
The Cireson team recommends making these modifications prior to every Service Manager and Data Warehouse installation.