Release Notes for Service Manager in System Center 2012 SP1


Updated: May 13, 2016

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

These release notes contain information that is required to successfully install Service Manager in System Center 2012 Service Pack 1 (SP1). They contain information that is not available in the product documentation.

Before you install and use Service Manager, read these release notes.

Known Issues

Service Manager Requires a Hotfix

Description: Service Manager might stop unexpectedly unless you apply hotfix 2600907, which is available at Microsoft Support.

Workaround: None.

Self-Service Portal Installation

Description: For Service Manager in System Center 2012 Service Pack 1 (SP1), you must install the Self-Service Portal on a server that does not host a Service Manager role.

Workaround: None.

Service Manager Requires SQL Server 2008 R2 SP1 or Later

Description: The Service Manager prerequisite checker included in Setup does not check for SQL Server 2008 R2 SP1, however it is required. If you are running the RTM version of SQL Server 2008 R2, then you must upgrade it to SQL Server 2008 R2 SP1 or later before you can install System Center 2012 Service Pack 1 (SP1).

Workaround: None.

Data Warehouse Setup Might Fail if the Database or Log Path Includes a Single Quotation Mark Character

Description: During Setup, if you specify a database or log path that includes a single quotation mark character ('), Setup might fail.

Workaround: None. The path that you specify cannot include a single quotation mark character.

Setup Might Fail if the Service Manager 2010 Authoring Tool Has Been Installed

Description: Setup might fail if you have previously installed any version of the Service Manager 2010 Authoring Tool.

Workaround: Remove the Service Manager 2010 Authoring Tool, and then retry Setup.

Setup Does Not Install the Report Viewer Language Pack

Description: Setup includes a prerequisite checker that checks for and—if necessary, installs—the Microsoft Report Viewer. However, Setup does not install the Report Viewer Language Pack, which makes the Microsoft Report Viewer compatible with Windows operating systems that are configured to use languages other than English.

Workaround: If your system is configured to use a language other than English, you should manually install the Report Viewer Language Pack for that language. You can download the Microsoft Report Viewer Redistributable 2008 SP1 Language Pack from the Microsoft Download Center.

Service Manager Setup Fails if a SQL Server Instance Contains a $ Character

Description: If you attempt to install Service Manager using a named Structured Query Language (SQL) instance that contains a dollar sign ($) character, Setup fails.

Workaround: Use a SQL instance that does not contain the $ character in its name.

MPSync Jobs Might Fail After Upgrading the Service Manager 2012 SP1 Data Warehouse

Before Upgrade

Description: After you upgrade the data warehouse to Service Manager 2012 SP1 and if your data warehouse has been running for more than 3 months, MPsynch jobs will fail. Additionally, transform and load jobs might also fail. This error can occur because of erroneous database grooming.

If you have not upgraded the data warehouse to Service Manager 2012 SP1 and this problem does not yet affect you, then you have to run the following query on the DWRepository database to get the actual SQL scripts that drop and add a constraint on the primary key in fact tables in the DWRepository database. Execute the following SQL script on your DWRepository database to prevent the problem from occurring in the future.

;WITH FactName
AS (
       select w.WarehouseEntityName from etl.WarehouseEntity w
       join etl.WarehouseEntityType t on w.WarehouseEntityTypeId = t.WarehouseEntityTypeId
       where t.WarehouseEntityTypeName = 'Fact'
AS (
    SELECT  PartitionName, p.WarehouseEntityName,
            RANK() OVER ( PARTITION BY p.WarehouseEntityName ORDER BY PartitionName ASC ) AS RK
    FROM    etl.TablePartition p
       join FactName f on p.WarehouseEntityName = f.WarehouseEntityName
, FactPKList
AS (
    SELECT  f.WarehouseEntityName, a.TABLE_NAME, a.COLUMN_NAME, b.CONSTRAINT_NAME, f.RK,
            CASE WHEN b.CONSTRAINT_NAME = 'PK_' + f.WarehouseEntityName THEN 1 ELSE 0 END AS DefaultConstraints
    FROM    FactList f
, FactWithoutDefaultConstraints
AS (
    SELECT  a.*
    FROM    FactPKList a
    LEFT JOIN FactPKList b ON b.WarehouseEntityName = a.WarehouseEntityName AND b.DefaultConstraints = 1
    WHERE   b.WarehouseEntityName IS NULL AND a.RK = 1
, FactPKListStr
AS (
    FROM    FactWithoutDefaultConstraints f1
                    SELECT  '[' + COLUMN_NAME + '],'
                    FROM    FactWithoutDefaultConstraints f2
                    WHERE   f2.TABLE_NAME = f1.TABLE_NAME
                    ORDER BY COLUMN_NAME
                   XML PATH('')
                ) AS F (COLUMN_NAME)
        'ALTER TABLE [dbo].[' + f.TABLE_NAME + '] ADD CONSTRAINT [PK_' + f.WarehouseEntityName + '] PRIMARY KEY NONCLUSTERED (' + SUBSTRING(f.PKList, 1, LEN(f.PKList) -1) + ')' + CHAR(13) + CHAR(10)
FROM    FactPKListStr f

Workaround 1: If you have already upgraded and you do not have problems with transform or load job failures but do have a management pack deployment failure, then follow the steps in the Before Upgrade section. In addition, after the default primary keys have been restored, restart the failed management pack deployment in the Service Manager console by navigating to the Data Warehouse workspace and then select Management Pack.

Workaround 2: If you have upgraded and you have problems with transform or load job failures, then determine if the SystemDerivedMp.Microsoft.SystemCenter.Datawarehouse.Base management pack exists in the DWStagingAndConfig database by running the following query.

select * from ManagementPack where mpname like '%SystemDerivedMp.Microsoft.SystemCenter.Datawarehouse.Base%'

If the management pack does not exist, you need to restore your database to a state prior to upgrade. To restore your database, perform the following steps.

  1. Perform disaster recovery steps for the database backups.

  2. Disable the MPSyncJob schedule.

  3. Restore all the missing primary keys in the DWRepository manually. You can drop and recreate the primary key using the SQL script from the Before Upgrade section.

  4. Restart the failed base management pack deployment using the Service Manager console.

Orchestrator Connector Account Password Cannot Contain $ Characters

Description: If the Orchestrator connector account password contains a $ character, the sync job completes, however runbooks are not updated in the Service Manager database.

Workaround: If your Orchestrator connector account password contains a $ character, change the password to one that does not include the $ character.

Registering an Operations Manager 2007 R2 Data Source Fails

Description: When you attempt to register an Operations Manager 2007 R2 data source in the Data Warehouse workspace, registration fails and an error appears stating that The Data Access service is either not running or not yet initialized. Check the event log for more information.

Workaround: None. This is a known problem when you try to register an Operations Manager 2007 R2 data source with Service Manager in System Center 2012 Service Pack 1 (SP1).

PowerShell Tasks Created with the Authoring Tool Do Not Work Properly

Description: When you use the Service Manager SP1 version of the Authoring tool to create a workflow, then custom scripts called by the workflow fail. This is due to a problem in the Service Manager MonitoringHost.exe.config file.

Workaround: To work around this problem, update the MonitoringHost.exe.config XML file using the following steps.

  1. Navigate to %ProgramFiles%\Microsoft System Center 2012\Service Manager\ or the location where you installed Service Manager.

  2. Edit the MonitoringHost.exe.config file and add the section in italic type from the example below in the corresponding section of your file. You must insert the section before <publisherPolicy apply="yes" />.

  3. Save your changes to the file.

  4. Restart the System Center Management service on the Service Manager management server.

<?xml version="1.0"?>
    <section name="uri" type="System.Configuration.UriSection, System, Version=, Culture=neutral, PublicKeyToken=b77a5c561934e089" />
    <iriParsing enabled="true" />
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
        <assemblyIdentity name="Microsoft.Mom.Modules.DataTypes" publicKeyToken="31bf3856ad364e35" />
        <publisherPolicy apply="no" />
        <bindingRedirect oldVersion="6.0.4900.0" newVersion="7.0.5000.0" />
        <assemblyIdentity name="Microsoft.EnterpriseManagement.HealthService.Modules.WorkflowFoundation" publicKeyToken="31bf3856ad364e35" />
        <publisherPolicy apply="no" />
        <bindingRedirect oldVersion="6.0.4900.0" newVersion="7.0.5000.0" />
         <assemblyIdentity name="Microsoft.EnterpriseManagement.Modules.PowerShell" publicKeyToken="31bf3856ad364e35" />
        <bindingRedirect oldVersion="6.0.4900.0" newVersion="7.0.5000.0" />
      <publisherPolicy apply="yes" />
      <probing privatePath="" />
    <gcConcurrent enabled="true" />

Information Linked from Setup Might Not Display Localized Content

Description: Information that is linked from Setup to the Setup log and to technical documentation might not display localized content. Setup logs in Service Manager are available in English only. Technical documentation is available in a variety of localized languages. Where available, localized technical documentation is displayed on TechNet; however, not all languages are available.

Workaround: None.

Full Text Search Does Not Work for Some Turkish Language Characters

Description: Full text search in the Self-Service Portal works only if you have a licensed non-Microsoft word breaker installed. However, full text search does not work for some characters of the Turkish language even if you have a licensed non-Microsoft Turkish word breaker installed.

Workaround: Load a licensed non-Microsoft word breaker that enables full-text search to function. For more information, see the following links for the version of SQL Server that you are using:

Unassigned Virtual Machines Appear in Reporting Information

Description: All virtual machines appear in Microsoft Online Analytical Processing (OLAP) cube data and the sample Microsoft Excel report, regardless of whether a virtual machine is assigned to a cloud. Reporting information is designed to show unassigned virtual machines as rows without price sheet data.

Workaround: None.

Virtual Machine Component Aggregation Is Misleading

Description: The SystemCenterVmmCloudChargebackCube OLAP cube contains aggregated values for virtual machine components. However, values for the components should not be expressed in the cube using any manner other than a daily count.

Workaround: None. However, you should ignore any aggregated time values for virtual machine components other than daily values.

Reassigned Virtual Machine Values Might Be Erroneously Calculated

Description: When you remove and then reassign a virtual machine from one cloud object to another, erroneous calculated values might appear for both clouds where the virtual machine was assigned. This condition might occur only for the same date when values for the virtual machine are not removed from the cloud that the virtual machine was initially assigned to. Data for the next day is accurate.

Workaround: None.

Values in Price Sheets Are Effective Starting on the Next Day

Description: When you type a value in a price sheet, the value becomes effective on the following day. For example, if you modify a calculated price today, the updated price will not immediately appear in OLAP cube data or the sample chargeback Excel report. Instead, the old price continues to appear in OLAP cube data and the sample chargeback Excel report. This behavior is expected; you can use it to update prices throughout your business day without the prices going into effect until the next business day.

Workaround: None.

After the Display Language Is Changed, the Wizard Text Might Display an Incorrect Language

Description: After you change the display language using the Language menu in the Service Manager console, wizard text might be displayed in your previously selected language.

Workaround: If this problem affects you, do the following:

  1. Close the Service Manager console.

  2. On the Start menu, click Run, type %temp%, and then click OK.

  3. Navigate up to the parent LOCAL folder.

  4. Open \Microsoft\System Center Service Manager 2010\<ServerName>\<VersionNumber>\, and then delete the contents of the folder.

  5. Open the Service Manager console. The wizard text should appear in the language that you selected previously.

Errors Might Occur When You Modify or Delete Service Request Template Items

Description: When you create a service request using a request offering template and you modify or delete activities that are contained in the template, various errors might occur that prevent you from saving the service request.

Workaround: When you create service requests, avoid modifying or deleting activities that are contained in a request offering template. If necessary, you can create a new request offering template with only the activities that are necessary and configured properly for your intended use.

The Service Manager Console Stops When You Attempt to Open a Change Request if the SelectedDate Value Is Not Valid

Description: This problem can occur after upgrading from System Center Service Manager 2010 to System Center 2012 – Service Manager if a change request’s scheduled end is set before the scheduled start date. The error message might resemble System.ArgumentOutOfRangeException: SelectedDate value is not valid.

Workaround: To display the change request containing a ScheduledStartDate value that is greater than the ScheduledEndDate value, you can use the following sets of commands in a Service Manager module for Windows PowerShell window:

$class=get-scclass -Name System.WorkItem.ChangeRequest

$instances= get-scclassinstance $class | where {$_.ScheduledStartDate -gt


$instances | Select DisplayName, ScheduledStartDate, ScheduledEndDate

To correct the situation, run the following set of cmdlets. These cmdlets set the ScheduledEndDate value to the same value as ScheduledStartDate.

$class=get-scclass -Name System.WorkItem.ChangeRequest

$instances= get-scclassinstance $class | where {$_.ScheduledStartDate -gt


$instances | Select DisplayName, ScheduledStartDate, ScheduledEndDate

$instances | %{ $_.ScheduledEndDate = $_.ScheduledStartDate ; $_ } | update-scclassinstance

Double-Byte Characters Might Not Display Correctly if a Knowledge Article Is Created from a TXT File

Description: If you create a knowledge article using a TXT file that contains double-byte characters, the characters might not display correctly.

Workaround: If this problem affects you, do not use TXT files to create knowledge articles. Instead, use RTF files.

Shortcut Keys Have Limited Functionality

Description: Most shortcut keys do not work properly.

Workaround: If a particular shortcut key does not work, on the Tasks menu, click Tasks, and then try the shortcut key.

Analyze Cube in Excel Does Not Work with Excel Viewer

Description: If you attempt to analyze an OLAP data cube in the Data Warehouse workspace using Microsoft Office Excel Viewer, a dialog box appears, stating erroneously that you can install Microsoft Excel viewer and try again.

Workaround: Close the Service Manager console, install Microsoft Excel, and then try again.

Configuring the Reporting Server Might Take a Long Time

Description: When you install the data warehouse, validation of the default web server URL might take as long as 25 seconds to complete.

Workaround: None.

Double-Byte Characters Are Sent Incorrectly to Search Provider

Description: When you perform a knowledge search and you type double-byte characters in the Search Provider box, they are not sent correctly to the search website. Instead, erroneous characters are sent.

Workaround: None.

Data Binding Does Not Work for Class Extension Properties

Description: The value for an extended property is not saved when a form control is bound to an extended property on a class.

Workaround: Restart the Service Manager console after binding to a property.

Sorting Knowledge Articles by Date Does Not Work

Description: When you try to sort knowledge articles by date, sorting does not work.

Workaround: None.

The System Center Alert Management Cube Management Pack Is Not Imported During Operations Manager Registration

Description: When you register Operations Manager as a data source, the System Center Alert Management Cube management pack will not be imported.

Workaround: First, create a data source for Operations Manager. For more information, see How to Register the System Center Data Warehouse to Operations Manager in the Service Manager Administrator's Guide.

Next, make sure that the System Center Data Warehouse Operations Manager management pack has been imported. In the Service Manager console, click Data Warehouse, click Management Packs, and confirm that System Center Datawarehouse Operations Manager Library is listed.

Finally, on the Data Warehouse Management Server, type the following Windows PowerShell commands to manually import the management pack. (This example assumes that Service Manager is on drive C and that you installed Service Manager using the default path).

cd 'C:\Program Files\Microsoft System Center\Service Manager 2012' 
Import-Module .\System.Center.Service.Manager.psd1 
Import-SCSMManagementPack ..\AlertCube.mpb