Was this page helpful?
Additional feedback?
1500 characters remaining
Export (0) Print
Expand All

Release Notes for Service Manager in System Center 2012 R2


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

Before you install and use Service Manager in System Center 2012 R2, read these release notes.

Description: If the Service Manager console is installed on the same server as VMM, then you cannot use that Service Manager console to create a VMM connector to that VMM server.

Workaround: None, however you can use a different Service Manager console to create the VMM connector.

Description: The Data Warehouse stops working after upgrading Service Manager in System Center 2012 SP1 to System Center 2012 R2 due to a Data Warehouse fact entity upgrade.

Workaround: To prevent this issue from occurring again, run the following SQL script for each of the following data warehouse databases: DW Repository, DW DataMart, CM DataMart, and OM DataMart. If this workaround is applied after data warehouse upgrade, resume the failed management pack upgrade process deploy captured in the list of Data Warehouse Management Packs from the Service Manager console.

IF OBJECT_ID('tempdb..#PKFixQueries') IS NOT NULL
    DROP TABLE #PKFixQueries

;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
    FROM    etl.TablePartition p
    JOIN    FactName f ON p.WarehouseEntityName = f.WarehouseEntityName
, FactWithPK
AS (
    SELECT  f.WarehouseEntityName, f.PartitionName, b.CONSTRAINT_NAME, a.COLUMN_NAME
    FROM    FactList f
, FactWithDefaultOrNoPK
AS (
    SELECT  DISTINCT f.WarehouseEntityName, f.PartitionName
            , 'PK_' + f.WarehouseEntityName AS DefaultPKConstraint
            , 'PK_' + f.PartitionName AS NewPKConstraint
    FROM    FactList f
    LEFT JOIN    FactWithPK pkf ON pkf.WarehouseEntityName = f.WarehouseEntityName AND pkf.PartitionName = f.PartitionName
    WHERE   pkf.WarehouseEntityName IS NULL OR pkf.CONSTRAINT_NAME = 'PK_' + f.WarehouseEntityName
, FactPKList
AS (
    SELECT  DISTINCT f.WarehouseEntityName, f.COLUMN_NAME
    FROM    FactWithPK f
, FactPKListStr
AS (
    SELECT  DISTINCT f1.WarehouseEntityName, F.COLUMN_NAME AS PKList
    FROM    FactPKList f1
                    SELECT  '[' + COLUMN_NAME + '],'
                    FROM    FactPKList f2
                    WHERE   f2.WarehouseEntityName = f1.WarehouseEntityName
                    ORDER BY COLUMN_NAME
                    FOR XML PATH('')
                ) AS F (COLUMN_NAME)
SELECT  f.PartitionName,
        '----------------------------- [' + f.PartitionName + '] -----------------------------' + CHAR(13) +
        'IF OBJECT_ID(''[' + f.DefaultPKConstraint + ']'') IS NOT NULL' + CHAR(13) +
        'BEGIN' + CHAR(13) +
        '  ALTER TABLE [dbo].[' + f.PartitionName + '] DROP CONSTRAINT [' + f.DefaultPKConstraint + ']' + CHAR(13) +
        'END' + CHAR(13) + CHAR(13) +
        'IF OBJECT_ID(''[' + f.NewPKConstraint + ']'') IS NULL' + CHAR(13) +
        'BEGIN' + CHAR(13) +
        '  ALTER TABLE [dbo].[' + f.PartitionName + '] ADD CONSTRAINT [' + f.NewPKConstraint + '] PRIMARY KEY NONCLUSTERED (' + SUBSTRING(pk.PKList, 1, LEN(pk.PKList) -1) + ')' + CHAR(13) +
        'END' AS Query
INTO    #PKFixQueries
FROM    FactWithDefaultOrNoPK f
JOIN    FactPKListStr pk ON pk.WarehouseEntityName = f.WarehouseEntityName

            @PartitionName = PartitionName,
            @Query = Query
    FROM    #PKFixQueries

    PRINT   @Query

    DELETE  #PKFixQueries
    WHERE   PartitionName = @PartitionName

Description: When installing chargeback report files on the Service Manager management server after upgrading Service Manager in System Center 2012 SP1 to System Center 2012 R2, you may receive an error message. This occurs because files are not able to be imported from Operations Manager.

Workaround: If this issue affects you, complete the following procedure and try to use chargeback again:

To prepare for chargeback

  1. On the server running System Center 2012 R2 Virtual Machine Manager, copy the following management packs from their installed location, by default InstallationDrive:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\ManagementPacks to a folder on the server running the Service Manager management server.

    • Microsoft.SystemCenter.VirtualMachineManager.PRO.Library

    • Microsoft.SystemCenter.VirtualMachineManager.PRO.V2.Library

    • Microsoft.SystemCenter.VirtualMachineManager.Pro.2008.Library

    • Microsoft.SystemCenter.VirtualMachineManager.Library

    • Microsoft.SystemCenter.VirtualMachineManager.2012.Discovery

  2. Start the Service Manager console and navigate to Administration, Management Packs.

  3. Import the management packs that you copied to the Service Manager management server. Make sure to click Yes on the Online Data Connection dialog box.

Description: Service Manager might stop unexpectedly unless you apply a Hotfix which is available at Microsoft Support.

Workaround: Apply Hotfix 2600907.

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

Workaround: None.

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 R2.

Workaround: None.

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.

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.

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.

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.

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.

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 R2.

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.

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:

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.

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.

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.

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.

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.

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.

Description: This problem can occur after upgrading from System Center Service Manager 2010 to Service Manager in System Center 2012 R2 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

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.

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.

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.

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.

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.

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.

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

Workaround: None.

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 R2\PowerShell'
Import-Module .\System.Center.Service.Manager.psd1
Import-SCSMManagementPack ..\AlertCube.mpb
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
© 2015 Microsoft