In this article

Release Notes for Service Manager in System Center 2012

Read these release notes before you install and use the System Center 2012 – Service Manager software.

Service Manager Requires a Hotfix

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

Workaround: None.

Upgrade from Service Manager 2010 SP1 Requires Cumulative Update 3

Description: Upgrading from Service Manager 2010 SP1 to System Center 2012 – Service Manager Release Candidate (RC) or later requires Cumulative Update 3. You can download System Center Service Manager 2010 Cumulative Update 3 from the Microsoft Download Center.

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

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.

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:

Close the Service Manager console.

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

Navigate up to the parent LOCAL folder.

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

Open the Service Manager console, and the wizard text should appear in the correct language.

Localized Generic Incident Request Offerings Are Not Updated When You Upgrade

Description: Management packs in System Center 2012 – Service Manager Beta do not contain localized generic incident request offerings. When you upgrade from Beta to RC, the management packs that are present in the Beta version are carried forward during the upgrade process to the RC version. If you want to use localized generic incident request offerings included in the RC version of the management packs, you can import the upgraded management packs after upgrading.

This situation does not affect upgrades from the RC to final (RTM) versions.

Workaround: Import the management pack that contains localized request offerings after you upgrade to System Center 2012 – Service Manager by performing one of the following actions:

Manually merge the pre-upgrade management pack with the RC management pack that has the localized information.

Import the RC management pack with the localized information and then perform the edits again.

Upgrade to System Center 2012 – Orchestrator After All Service Manager Activities Are Completed

Description: Various settings are replaced when you upgrade System Center 2012 – Orchestrator from Beta to RC and those settings might not be preserved during the upgrade. For example, a connector’s URL or runbook IDs might change.

Workaround: None. However, you should wait to upgrade System Center 2012 – Orchestrator to RC until all Service Manager activities are completed. Afterward, you should create a new Orchestrator connector.

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

Workaround: When creating service requests, avoid modifying or deleting activities contained in a request offering template. If necessary, you can create a new request offering template with only the activities necessary and properly configured 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 the Service Manager module for Windows PowerShell:

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.

The System Center 2012 Configuration Manager Connector Fails to Synchronize After an Upgrade from Service Manager CTP2 to System Center 2012 – Service Manager Beta

Description: An existing System Center 2012 Configuration Manager connector does not synchronize if you upgrade from Service Manager CTP2 to System Center 2012 – Service Manager Beta.

Workaround: You can work around this problem by completing the following steps:

Delete your System Center 2012 Configuration Manager connector.

Recreate the connector.

Synchronize the new connector.

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

Software Required for the Service Manager console

Description: The Service Manager console requires Microsoft Analysis Management Objects (AMOs) so that it can work with SQL Server Analysis Services (SSAS). Choose one of the following three setup files to install Microsoft AMOs, based on the microprocessor architecture that you are using:

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

Release Notes Copyright Information

This document is provided "as-is". Information and views expressed in this document, including URL and other Internet website references, may change without notice.

Some examples depicted herein are provided for illustration only and are fictitious. No real association or connection is intended or should be inferred.

This document does not provide you with any legal rights to any intellectual property in any Microsoft product. You may copy and use this document for your internal, reference purposes. You may modify this document for your internal, reference purposes.