Export (0) Print
Expand All

How to Work Around Configuration Service Startup Issues

Updated: November 1, 2013

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

There are two workaround procedures that you can use to try to resolve the issue in which an upgrade to System Center 2012 – Service Manager fails as a result of Configuration service Startup timing out. You can:

  • Disable signature verification on the computer that is running Setup.

  • Increase the service time-out setting on the computer that is running Setup.

To disable signature verification

  1. On the computer that is running Setup, edit the Microsoft.Mom.ConfigServiceHost.exe.config file, which is located in the Program Files\Microsoft System Center\Service Manager 2010 folder.

  2. In the <runtime></runtime> section, add <generatePublisherEvidence enabled="false"/>.

  3. Save the changes to the file.

  4. Attempt the upgrade again.

To increase the service time-out setting

  1. On the computer that is running Setup, create the following registry value to increase the service time-out period:

    Incorrectly editing the registry may severely damage your system. Before making changes to the registry, you should back up any valued data on the computer.

    You may have to increase this value further if the service still fails to start. The value in this example is in milliseconds. For additional details about the registry key, see article 922918 in the Microsoft Knowledge Base.

  2. Start the computer again.

  3. Attempt the upgrade again.

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.
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
© 2015 Microsoft