Archive

Archive for the ‘SCSM’ Category

System Center Service Manager :A Windows Workflow Foundation workflow failed during execution.

January 28, 2014 Leave a comment

Sometimes when you check the event viewer for Service Manager “Operations Manager” you get event ID 33880

 

A Windows Workflow Foundation workflow failed during execution.
 
Workflow Type: Microsoft.EnterpriseManagement.ServiceManager.SLA.Workflows.ApplySLAOnGroupInstance

Workflow Identifier: b3c0e6b3-b14e-345b-0cdc-cb6feaa9e3cd

Exception Type: Microsoft.EnterpriseManagement.Common.InconsistentDataException

Exception Message: Could not retrieve SLO information from the system. This can happen when SLO was either deleted or not created through console.

Exception Stack:    at Microsoft.EnterpriseManagement.ServiceManager.SLA.Workflows.ApplySLAOnGroupInstance.ApplySLA_ExecuteCode(Object sender, EventArgs e)
   at System.Workflow.ComponentModel.Activity.RaiseEvent(DependencyProperty dependencyEvent, Object sender, EventArgs e)
   at System.Workflow.Activities.CodeActivity.Execute(ActivityExecutionContext executionContext)
   at System.Workflow.ComponentModel.ActivityExecutor`1.Execute(T activity, ActivityExecutionContext executionContext)
   at System.Workflow.ComponentModel.ActivityExecutorOperation.Run(IWorkflowCoreRuntime workflowCoreRuntime)
   at System.Workflow.Runtime.Scheduler.Run()

This happens due to missing Workflow in one of the management packs, To correct that you have to get the workflow and remove it

to get the workflow using identifier you can open SM powershell and run

get-scsmworkflow -id <WorkflowID>

if the workflow does not exist in the SM console or if you would like to force deleting it then run:

get-scsmworkflow -id <WorkflowID> | remove-scsmworkflow

Powershell

Categories: SCSM Tags:

SCSM 2012 R2 PowerShell Tasks Created with the Authoring Tool Do Not Work Properly

October 2, 2013 2 comments

Since we are getting ready for System Center R2 release we start testing different upgrade scenarios for System Center. One of the problems we faced that some custom workflows that has PowerShell scripts is not running on SCSM R2. This a well known issue with System Center 2012 R2 and you have to edit MonitoringHost.exe.config to get over it.

Description: When you use the Authoring tool in Service Manager for System Center 2012 R2 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"?>
<configuration>
  <configSections>
    <section name="uri" type="System.Configuration.UriSection, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" />
  </configSections>
  <uri>
    <iriParsing enabled="true" />
  </uri> 
  <runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="Microsoft.Mom.Modules.DataTypes" publicKeyToken="31bf3856ad364e35" />
        <publisherPolicy apply="no" />
        <bindingRedirect oldVersion="6.0.4900.0" newVersion="7.0.5000.0" />
      </dependentAssembly>
      <dependentAssembly>
        <assemblyIdentity name="Microsoft.EnterpriseManagement.HealthService.Modules.WorkflowFoundation" publicKeyToken="31bf3856ad364e35" />
        <publisherPolicy apply="no" />
        <bindingRedirect oldVersion="6.0.4900.0" newVersion="7.0.5000.0" />
      </dependentAssembly>
  <dependentAssembly>
         <assemblyIdentity name="Microsoft.EnterpriseManagement.Modules.PowerShell" publicKeyToken="31bf3856ad364e35" />
        <bindingRedirect oldVersion="6.0.4900.0" newVersion="7.0.5000.0" />
     </dependentAssembly>
      <publisherPolicy apply="yes" />
      <probing privatePath="" />
    </assemblyBinding>
    <gcConcurrent enabled="true" />
  </runtime>
</configuration>

Categories: SCSM

Travis Wright Joins Cireson as Partner, and Director of Product

September 25, 2013 Leave a comment

Today, Cireson makes official the news that Travis Wright Microsoft Principal Program Manager will join Cireson. Anyone works with System Center already know Travis as SC Guru and Service Manager Hero.

I believe this a great step for Travis and Cireson, Travis will help Cireson to provide more amazing solutions , Congratulation Travis and Cireson wish you all the best.

Read more: http://www.digitaljournal.com/pr/1489289#ixzz2fvjWLN00

Categories: SCOM, SCSM

#SCSM: Set Service Request Title from Related Request Offering

One of request that I got through my SCSM project is to create custom workflow to Set Service Request Title from Related Request Offering

The script use SMLets commands that you can download from http://smlets.codeplex.com/

You can configure workflow using that script to trigger on new Service Request creation to copy title from related Request Offering

Import-Module SMLets  
$ServiceRequest = Get-SCSMObject -Class (Get-SCSMClass -Name System.WorkItem.ServiceRequest$) -Filter "ID -eq $ServiceRequestID"  
$GetRelatedRequestOffering = (Get-SCSMRelationshipObject -BySource $ServiceRequest | ?{$_.RelationshipID -eq "2730587f-3d88-a4e4-42d8-08cf94535a6e"}).TargetObject.DisplayName  
$GetServiceRequestTitle = $ServiceRequest.Title  $ServiceRequest | Set-SCSMObject -Property Title -Value "$GetRelatedRequestOffering"
Categories: PowerShell, SCSM Tags:

SCSM: Workflow to Assign Change Request Creator to Completed Needed Documentation

May 15, 2013 2 comments

All changes should be tracked in a change management system. The change is documented in the change tracking system when the change initiator has completed the required level of technical verification and completes a change request. The following status codes can be used to reflect the status of a change request:

  • Open: The change has been received and accepted but has not been assigned.
  • In-Progress: The change has been received, acknowledged, and assigned. Work is in progress to fulfill the change request.
  • Approved: The business and technical assessments have been completed and the change has been approved and committed to the change scheduler.
  • Rejected: The change has been rejected and will be routed back to the requester with an explanation and a recommended course of action.
  • Closed: The change request has been closed.
  • Canceled: The change request has been canceled.

The change initiator is the person who initially perceives the need for the change and develops, plans, and executes the steps necessary to meet the initial requirements for a Request for Change (RFC). A common task is when change request created by someone to assign first activity to him “Documentation” to be completed before proceeding with the change.

You can create different change request templates with different activities and identify “Documentation” as first manual activity task to be completed by change creator.

This Workflow will trigger on new Change Request creation and check  within the Change Request activities “Pre-defined template” for Manual activity with Name “Documentation”  and assign the Person who create the change to this manual activity to make sure that change initiator complete needed documentation before proceeding with the change request approvals

You can open the Workflow using Authoring tool and Change Manual Activity name  to fit with your organization requirements

You can download the workflow from there

 

 

 

SCSM 2012 Portal Knowledge Base “Web Based Solution”

One of the most common request from Microsoft System Center Service Manager customer’s is having Knowledge base as web based. In Service Manager Self Service Portal you have to open Knowledge base articles as .rtf files instead of just seeing a web page.

Microsoft did a great job with revamping the new Portal in SCSM 2012 but still same problem for Knowledge bases. We build a basic Web Part that could solve this problem.

After importing this web part you well see Top knowledge base as blow

001

When you press any knowledge base you will get your Knowledge base as blow

002

I will start uploading the Web part with implementation guide to Microsoft Gallery and Will send you guys the URLs, Enjoy Smile

Note: I will start working on the full solutions and keep this one for free, So if you can see any enhancements or feedback please feel free to do

Update: Solution URL http://gallery.technet.microsoft.com/Service-Manager-2012-Web-30655388

Categories: SCSM Tags:

SCSM 2012: Self Service Portal Redirection

March 1, 2013 3 comments

One of the most requirements that I found people asking about is Portal redirection. By default SCSM Portal exist at http://ServerName/SMPortal and this is difficult to end users to remember, In old days with SCSM 2010 redirection was easy using IIS Redirection.

With SCSM 2012 it is little bit hard since it is SharePoint. One way is to edit CSS file in SharePoint and this is not the best option for people that have limited knowledge with SharePoint, Another way is to use IIS Rewrite Tool 

IIS URL Rewrite enables Web administrators to create powerful rules to implement URLs that are easier for users to remember and easier for search engines to find. By using rule templates, rewrite maps, .NET providers, and other functionality integrated into IIS Manager, Web administrators can easily set up rules to define URL rewriting behavior based on HTTP headers, HTTP response or request headers, IIS server variables, and even complex programmatic rules. In addition, Web administrators can perform redirects, send custom responses, or stop HTTP requests based on the logic expressed in the rewrite rules.

After you install IIS Rewrite tool you will find new icon with name “URL Rewrite”. Double Click on it

Untitled

Then from the right pane press Add Rule

Untitled

 

 

 

 

Choose Rule with rewrite map

image

From Rule Action choose Redirect

image

 

 

In the rewrite map type ( SMPortal)

image

Ten open the new created Rule and check the pattern, Then try to open the Service Manager Portal directly by Typing  http://ServerName without adding SMPortal

image

 

 

Update: If these steps did not work try below

  • Choose Rule “ blank rule”
  • Use Regular Expressions to match ^$ (which means “empty”). Set Action Type to Redirect, and add the redirect URL (/SMPortal), set redirect type to Permanent (301).
Categories: SCSM Tags:
%d bloggers like this: