[OpsMgr 2012] SP1 upgrade fails with error "Failed to set DW upgrade scenario"

When performing an upgrade to OpsMgr 2012 SP1, the upgrade process fails with the following error:

Failed to set DW upgrade scenario: Threw Exception.Type: System.Data.SqlClient.SqlException, Exception Error Code: 0x80131904, Exception.Message: Cannot open database "OperationsManagerDW" requested by the login. The login failed.

In order to be able to relaunch the upgrade, verify that the correct Data Warehouse server name and SRS database instance name exist in the registry on the Management Server:

Data Warehouse server name:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Setup\DatawarehouseDBServerName

NOTE: This is a DWORD value and is the NetBIOS name or FQDN of the server.

SRS database instance name:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Reporting\SRSInstance

NOTE: The default SQL instance name is MSSQLSERVER but may be different in your environment if using a named instance.

Please read the original post on This page

This posting is provided "AS IS" with no warranties.

[OpsMgr 2007 R2][OpsMgr 2012] Running Operations Manager reports fail with "System.ArgumentOutOfRangeException" error

Article ID: 2836388 - View products that this article applies to.

Article ID: 2836388

Symptoms

When running reports using the Operations Manager console, the report fails with the error message below:

Date: <date-time>
Application: Operations Manager
Application Version: 7.0.9538.0
Severity: Error
Message: Cannot execute report.
System.ArgumentOutOfRangeException: Value of '0001-01-01 12:00:00 AM' is not valid for 'Value'. 'Value' should be between 'MinDate' and 'MaxDate'.
Parameter name: Value
   at System.Windows.Forms.DateTimePicker.set_Value(DateTime value)
   at Microsoft.EnterpriseManagement.Mom.Internal.UI.Reporting.Parameters.Controls.RelativeDateTimePicker.LoadRelativeDateValues(ComboBox dateEditor, DateTimePicker timeEditor, ReportParameterInfo dateBaseTypeParameter, ReportParameterInfo dateBaseValueParameter, ReportParameterInfo dateOffsetTypeParameter, ReportParameterInfo dateOffsetValueParameter)
   at Microsoft.EnterpriseManagement.Mom.Internal.UI.Reporting.Parameters.Controls.RelativeDateTimePicker.LoadValues(ReportParameterInfoCollection reportParameters)
   at Microsoft.EnterpriseManagement.Mom.Internal.UI.Reporting.Parameters.Controls.RelativeDateTimeBusinessPicker.LoadValues(ReportParameterInfoCollection reportParameters)
   at Microsoft.EnterpriseManagement.Mom.Internal.UI.Reporting.Parameters.ReportParameterBlock.LoadValues()
at Microsoft.EnterpriseManagement.Mom.Internal.UI.Console.ReportForm.OnRenderingCompleteJob(Object sender, ConsoleJobEventArgs args)

Cause

This issue can occur if there is a custom Short DateTime format being used on the console server.

For example, say the system locale on the Operations console server is ENC and the default short DateTime format for ENC locale is dd/MM/yyyy. If this short DateTime format is changed from dd/MM/yyyy to a different format such as yyyy-MM-dd, the error above may occur.

Resolution

To resolve this issue, set the short DateTime format to the system locale's default value.

More information

Custom DateTime formats are not supported with System Center Operations Manager reporting.

Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.

Properties

Article ID: 2836388 - Last Review: April 18, 2013 - Revision: 1.0
Applies to
Microsoft System Center 2012 Operations Manager Service Pack 1
Microsoft System Center 2012 Operations Manager
Microsoft System Center Operations Manager 2007 R2
Microsoft System Center Operations Manager 2007 Service Pack 1
Microsoft System Center Operations Manager 2007

This posting is provided "AS IS" with no warranties.

[OpsMgr 2007 R2][OpsMgr 2012] System Center Data Access or Management Configuration services fail to start after applying KB2677070

Summary

After applying KB2677070 (http://support.microsoft.com/kb/2677070), the System Center Data Access service or System Center Management Configuration service may fail to start with a TimeOut error.

Direct link to Microsoft article

More Information

This issue occurs because the update changes the URLs used to contact Windows Update to download the trusted and untrusted CTLs. If the old URLs were hardcoded as exceptions in the firewall or proxy, the server running the Data Access service or the Management Configuration service will fail to download the new CTLs because it can't reach the updated web address.

The workaround for this is to unblock the updated URLs in the firewall or proxy or disable CRL checking for the Data Access service and Management Configuration service.

The updated URLs are:

http://ctldl.windowsupdate.com/msdownload/update/v3/static/trustedr/en/disallowedcertstl.cab

(http://ctldl.windowsupdate.com/msdownload/update/v3/static/trustedr/en/disallowedcertstl.cab)

http://ctldl.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cab

(http://ctldl.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cab)

Open the following file in a text editor:
- for the Data Access service: Microsoft.Mom.Sdk.ServiceHost.exe.config
- for the Management Configuration service: Microsoft.Mom.ConfigServiceHost.exe.config (in SM) or cshost.exe.config (in OM)

To disable CRL checking add the following line in the <runtime> section:

<generatePublisherEvidence enabled="false"/>

Below is an example of this tag being added for System Center 2012 Operations Manager:

 <runtime>
<generatePublisherEvidence enabled="false"/>
      <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
        <dependentAssembly>
          <assemblyIdentity name="Microsoft.EnterpriseManagement.HealthService" publicKeyToken="31bf3856ad364e35" />
          <publisherPolicy apply="no" />
          <bindingRedirect oldVersion="6.0.4900.0" newVersion="7.0.5000.0" />
        </dependentAssembly>
        <publisherPolicy apply="no" />
        <probing privatePath="" />
      </assemblyBinding>
      <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
        <dependentAssembly>
          <assemblyIdentity name="Microsoft.Mom.Common" publicKeyToken="31bf3856ad364e35" />
          <publisherPolicy apply="no" />
          <bindingRedirect oldVersion="6.0.4900.0" newVersion="7.0.5000.0" />
        </dependentAssembly>
        <publisherPolicy apply="no" />
        <probing privatePath="" />
      </assemblyBinding>
      <gcServer enabled="true"/>
    </runtime>


The next example shows the same parameter added in the configuration file for System Center Operations Manager 2007 R2:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
    <runtime>
<generatePublisherEvidence enabled="false"/>
        <gcServer enabled="true"/>
    </runtime>


The two*.config files can be found in the following directories:

-System Center Operations Manager 2007 R2: %ProgramFiles%\System Center Operations Manager 2007
-System Center Service Manager 2010: %ProgramFiles%\System Center Service Manager 2010
-System Center 2012 - Operations Manager: %ProgramFiles%\System Center 2012\Operations Manager\Server
-System Center 2012 - Service Manager: %ProgramFiles%\System Center 2012\Service Manager

Properties

Article ID: 2730040 - Last Review: October 2, 2012 - Revision: 3.0

Applies to

• Microsoft System Center 2012 Operations Manager
• Microsoft System Center Operations Manager 2007 R2
• Microsoft System Center 2012 Service Manager
• Microsoft System Center Service Manager 2010

Keywords:

kbtshoot KB2730040

This posting is provided "AS IS" with no warranties.