Service Requests System Center Cloud Services Process Pack Failed #sysctr


The System Center Cloud Services Process Pack provides a service solution for automating the deployment of private and public cloud infrastructures. With the System Center Cloud Services Process Pack, enterprises can realize the benefits of infrastructure as a service while simultaneously leveraging their existing investments in System Center 2012 – Service Manager, System Center 2012 – Orchestrator, System Center 2012 – Virtual Machine Manager (VMM), and System Center 2012 – Operations Manager.

The System Center Cloud Services Process Pack offers a self-service experience to facilitate private cloud capacity requests from your business unit IT application owners and end users, including the flexibility to request additional capacity as business demands increase.

You can download System Center Cloud Services Process Pack at the Microsoft Download Center at

Service Requests System Center Cloud Services Process Pack Failed

In preparation of a Service Manager 2012 demo for the Pre-TechEd Europe 2012 event , organized by Microsoft, HP and Inovativ I was facing an issue. After submitting a cloud service request through the Service Manager 2012 Self-Service Portal all requests almost instantly failed.

The status of work items can also be viewed through the Service Manager console or by the Self-Service Portal.

When you drilldown to the workflows status section (Administration\Workflows\Status) and filter on cloud you’re able to find the faulting workflow which is related to the service request, in our case the Assign Virtual Machine Reviewer. (see also Troubleshooting Workflows in Service Manager for addtional throubleshooting tips)

When selecting the workflow we get clear where in the process the service request is failing, as you can see event 17 is faulting.

As sometimes error messages can be somewhat cryptically, a good next troubleshooting step is the Operations Manager eventlog. When searching the Operations Manager eventlog within the time range when the service request was failing Event 26319 got my attention. As you can see we found the root cause of our problem.

The user CONTOSO\svc-svcmgr-wf does not have sufficient permissions to perform the operation.

The CONTOSO\svc-scvmgr-wf is the Service Manager Workflow account. By simply adding the workflow account to the Activity Implementer user role the workflow account has the required permissions to successfully execute the workflow(s) which are part of the service request offerings.

After adding the Workflow account to the Activity Implementers user role and submitting a new request the service request wll succesfully processed.

Now the service request is ready to be approved…and provision the requested VM.

Many thanks to Raganathan Srikant (Program Manager at Microsoft) helping sorting this out.


Uninstalling SCSM 2012 – Error opening installation log file #sysctr

As part of the installation of SCSM 2012 Beta in my lab-environment I crossed an issue with uninstalling the previous installed version of SCSM 2012 (build CTP1).

Of course we don’t have the intention to make it a habit uninstalling SCSM J – but it is not always unavoidable in test-environments. Although the log files were not in place I was able to uninstall SCSM 2012 by simple click similar to “running elevated rights”. I’m local admin on the particular box without UAC enabled.


Open your control panel and shift-right-click
Programs and Features and select Open in new process

There you go…uninstallation process completed successfully! And now on with all the beauty SCSM 2012 Beta offers…

Service Manager 2012 CTP2 is Released (TAP Only) #sysctr

The Service Manager Product team by Travis Wright announced the Service Manager 2012 CTP2 release which is currenlty available only to TAP customers/partners.

Just wanted to let you know about another important milestone which has been reached in the SCSM 2012 development lifecycle. We have released the CTP2 build to TAP customers and partners on schedule. This will be the final non-public release before we get to the public beta towards the end of Q3 CY 2011. I’m sure you are all anxious to get your hands on SCSM 2012 bits, but unfortunately this is still a release that is limited to TAP customers and partners. I will be posting some new extensive demo videos in the next week or two so that you can all see what is coming and where we are at.

Official announcement:

We are proud to announce the release of System Center Service Manager 2012 CTP2, which is feature complete and higher quality than any previous release of Service Manager. This release will be available to TAP customers and partners via Microsoft Connect and delivers the ability to upgrade from SCSM 2010 SP1 with improved scale / performance and numerous enhancements that will benefit System Center customers and partners.
Continue reading “Service Manager 2012 CTP2 is Released (TAP Only) #sysctr”

System Center Service Manager – Exchange Connector 2.0 Released #sysctr

The System Center Service Manager – Exchange Connector connects Service Manager to Exchange for processing incoming emails related to incidents and change requests. The emails can update the incident action log or change the status of an incident to resolved or closed. Incoming emails with special keywords allow a change request reviewer to approve or reject a review activity and activity implementers can mark activities assigned to them as completed. The Send Email solution allows analysts to send messages to users via email from the console. Continue reading “System Center Service Manager – Exchange Connector 2.0 Released #sysctr”

Service Manager 2010 SP1 Cumulative Update 2 (CU2) is released

The Servce Manager product team announced this week a cumulative update which is a rollup of fixes for System Center Service Manager 2010 SP1. It can be applied to SP1 CU1 or directly to a Service Manager 2010 SP1 installation. This update contains a set of bug fixes to the Service Manager 2010 SP1 release. Continue reading “Service Manager 2010 SP1 Cumulative Update 2 (CU2) is released”

Getting Started with Service Manager Cmdlets for Windows PowerShell: Create $Profile #sysctr

Every time you start a Windows PowerShell session to run a Service Manager cmdlet, you must first add the Service Manager Windows PowerShell snap-in. As most of us are lazy admins I created a “service manager” profile having all Service Manager cmdlets by default available when starting PowerShell session.

Create a profile

  • Before we decide to create a profile, let’s check to see whether we already have one:

Test-Path $profile
  • If the profile exists this command will return True; if it doesn’t exist, the command will return False. If this command returns False, you need to create the profile.
  • Creating a profile is really easy. Simply type this at the command prompt:

    New-Item -path $profile -type file -force

      Continue reading “Getting Started with Service Manager Cmdlets for Windows PowerShell: Create $Profile #sysctr”

    Customize your Service Manager 2010 Portal #sysctr

    The feedback on the self-service portal has consistently been that it needs to be more customizable. That is by far the #1 feedback item on SCSM 2010. The types of desired customizations typically fall into these categories:

    • change the text shown in a label
    • hide buttons or web parts
    • change the style (colors, fonts, etc.)
    • change the layout
    • show more or less information
    • add additional capabilities
    • add languages or allow users to choose which language the portal is displayed in

    Most of these things ideally would be configurable options on the web parts and there would be some sort of administrative UI which allowed you to change these things. Making things like that configurable via an admin experience requires significant development and test time which unfortunately we didn’t have in the 2010 product development cycle. That is what we are shooting for in the vNext version (currently code named “R2”) of the SCSM portal that we are super excited to show you at the Microsoft Management Summit for the first time. The vNext portal will be based on SharePoint 2010 (any version including Foundation). It will be made up of web parts. You can change the text shown on labels, change fonts, change the style, change the layout, etc. using standard SharePoint administrative experiences and tools. It will be relatively easy to add new content to the portal by creating web parts that use the SDK and plugging them into the SharePoint site. You will also be able to add languages or change display strings by modifying the string resource files. We will let the user choose which language they want to display the console in. The portal will be a single SharePoint site instead of an analyst portal and an end user portal, but the user experience will be role based so people only see what they need to see. In short, it will be what we all wished the SCSM 2010 portal could have been.

    Continue reading “Customize your Service Manager 2010 Portal #sysctr”

    Service Manager Exchange Connector in different domains #sysctr

    Early this year, the Exchange connector for Service Manager was released. The Exchange Connector provides the following capabilities:

    • Create incident from email (replaces out of the box functionality; just turn it off)
    • The sending user is looked up in the CMDB and related to the incident as the affected user
    • The email subject becomes the incident title
    • The email body becomes the incident description
    • Update incident action log from email
    • Resolve or close incidents from email
    • Approve/reject change requests from email
    • Update change request “action log” from email
    • Mark manual activities completed from email
    • Add email file attachment to work items as attachments
    • Emails can be sent in from outside the organization
    • Emails can be sent from users which do not exist in the CMDB yet and a new user record will be created for them and related to the incident

    Implementing Service Manager Exchange connector for a customer last week brings me to the following challange; the Service Manager setup is installed in domain X but the Exchange environment was installed in domain Y without any chains or trusts. Service Manager workflow Account (domain X) requires permissions to domain Y accessing the mailbox defined.

    Continue reading “Service Manager Exchange Connector in different domains #sysctr”

    Troubleshooting Service Manager 2010 Reporting #sysctr

    Last week I had some challenges getting Service Manager Reporting working properly in a scenario with a remote SQL Server Reporting Services (SSRS) as shown below.

    During deployment of the Service Manager data warehouse management server, you can specify the server to which Microsoft SQL Server Reporting Services (SSRS) will be deployed. By default, the computer that is hosting the data warehouse management server is selected during setup. If you specify a different computer, you are prompted to follow this procedure to configure the remote SSRS server. Before you follow this procedure, you must perform the following actions:

    • Copy Microsoft.EnterpriseManagement.Reporting.Code.dll from the Service Manager installation media to the computer that is hosting SSRS.
    • Add a code segment to a configuration file on the computer that is hosting SSRS.
    Manual Steps to Configure the Remote SQL Server Reporting Services

    Upgrade Service Manager 2010 SP1 “System Center Service Manager is not in a valid state”

    Make sure when you’re upgrading SCSM 2010 RTM (7.0.5826.0) to SP1 (7.0.6555.0) the account you’re using has te required permisions on both ‘ServiceManager’ and ‘DWStagingAndConfig’ database. Otherwise the upgrade wizard will fail. See message below:

    Upgrade wizard SCSM SP1 - System Center Service Manager is not in a valid state.

    The logfiles of the upgrade path are located at ‘c:\users\%currentusers%\appdata\local\temp\’. As stated in the SCSMSetupWizard.log I’m running the setup without the necessary rights as you can see in the logfile:

    02:07:33:CheckPrerequisites: Return Value 1
    02:07:34:Getting Management Group information from SERVER\SCSM:DWStagingAndConfig
    02:07:34:[GetManagementGroupPropertiesFromDB]:  Opened the DB connection using Data Source=SERVER\SCSM;Initial Catalog=DWStagingAndConfig;Integrated Security=True;Persist Security Info=False.
    02:07:34:[GetManagementGroupPropertiesFromDB]:  Error: We hit exception type System.Data.SqlClient.SqlException. Message:The EXECUTE permission was denied on the object ‘p_MOMManagementGroupInfoSelect’, database ‘DWStagingAndConfig’, schema ‘dbo’.
    02:07:34:Error:ERROR: Failed to get installed product details, Exception Type: System.Exception, Exception Message: System Center Service Manager is not in a valid state.
    02:07:34:StackTrace:   at Microsoft.SystemCenter.Essentials.SetupFramework.InstallationSummaryPage.workerThread_DoWork(Object sender, DoWorkEventArgs e)
    02:16:56:Application Ended

    When running the upgrade with proper permissions the installation wizard will pass. This applies to upgrading both service manager management- and data warehouse server.

    SCSM SP1 upgrade wizard - passed.