Hi - I have executed the command in order to see which workflows are running behind due to users identifying SCSM is running slow.

We seem to have some serious issues with workflows as you can see from the screenshot below. Can anyone recommend the next step to resolve this? we have restarted the servers but issue is ongoing. I can't identify the workflows that are causing the issues in order to disable them whilst it catches up.

Thanks in advance for your help.

Dear paulshab,

in which order did you restart the servers?

Try to restart the 3 SCSM Services on the SCSM Management Server.

Best Regards,

Georges Mouawad

I'd recommend you stop the services on the workflow server (usually the first management server you set up), and clear the Health and config Service States (in the service manager folder, rename the referenced folders) and restart the system center services. this should cause the workflow service to reevaluate it's position and start processing workflows from the start. 

however, this won't get you ahead. take a look at your Ops Manager log and see if you see any 33610 events. these "database subscription query is longer than expected" events is a clear indication that workflows are stuck or running log because of a database performance problem, which is the most freqeunt cause of performance issues in Service Manager. 

you might consider reducing the grooming timeouts on the Job status logs, which is a surprisingly large portion of the database that must be kept in ram to service workflow performance. 

I have tried all of the above but it hasn't resolved the issue.

Can anyone advise me how to disable the workflow 'Adjust Incident Priority and Resolution Time Rule Add' - I would just like to disable it on a temporary basis to see if it catches up

Yes you can make a new custom mp with overrides for that specific workflow:

http://blogs.technet.com/b/servicemanager/archive/2011/07/07/disabling-workflows-with-overrides.aspx

Edit:

For this specific workflow I'm pretty sure you can disable it in Incident Settings -> Resolution Time -> "Do not use legacy Target Resolution Time on Incident banner". 

If you have changed the priority calculation and/or Resolution Time recently, it re-calculates for all Incidents which can take quite some time if you have a lot :)

• Edited by Morten Meisler 18 hours 18 minutes ago

thanks morten - I am getting closer. This is the setting I have in resolution time, this looks ok to me, what do you think?

Plus below I have tried to write the xml to disable the workflow, but I have a few bits wrong, can you help with this?

<?xml version="1.0"?>

-<ManagementPack OriginalSchemaVersion="1.1" SchemaVersion="1.1" ContentReadable="true" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xsd="http://www.w3.org/2001/XMLSchema">

-<Manifest>

-<Identity>

<ID>Microsoft.Demo.Overrides</ID>

<Version>1.0.0.0</Version>

</Identity>

<Name>Override Demo</Name>

-<References>

-<Reference Alias="System">

<ID>System.Library</ID>

<Version>7.5.3079.0</Version>

<PublicKeyToken>31bf3856ad364e35</PublicKeyToken>

</Reference>

-<Reference Alias="IncidentLibrary">

<ID>ServiceManager.IncidentManagement.Library</ID>

<Version>7.5.3079.0</Version>

<PublicKeyToken>31bf3856ad364e35</PublicKeyToken>

</Reference>

</References>

</Manifest>

-<Monitoring>

-<Overrides>

-<RulePropertyOverride Property="Enabled" Rule="Incident_Adjust_PriorityAndResolutionTime_Custom_Rule.Update" Enforced="false" Context="System!System.Entity" ID="DisableIncident_Adjust_PriorityAndResolutionTime_Custom_Rule.Update">

<Value>false</Value>

</RulePropertyOverride>

-<RulePropertyOverride Property="Enabled" Rule="Incident_Adjust_PriorityAndResolutionTime_Custom_Rule.Update" Enforced="false" Context="System!System.Entity" ID="DisableIncident_Adjust_PriorityAndResolutionTime_Custom_Rule.Update">

<Value>false</Value>

</RulePropertyOverride>

</Overrides>

</Monitoring>

-<LanguagePacks>

-<LanguagePack ID="ENU" IsDefault="true">

-<DisplayStrings>

-<DisplayString ElementID="Microsoft.Demo.Overrides">

<Name>Override Demo</Name>

</DisplayString>

</DisplayStrings>

</LanguagePack>

</LanguagePacks>

</ManagementPack>

Yes you can make a new custom mp with overrides for that specific workflow:

http://blogs.technet.com/b/servicemanager/archive/2011/07/07/disabling-workflows-with-overrides.aspx

Edit:

For this specific workflow I'm pretty sure you can disable it in Incident Settings -> Resolution Time -> "Do not use legacy Target Resolution Time on Incident banner". 

If you have changed the priority calculation and/or Resolution Time recently, it re-calculates for all Incidents which can take quite some time if you have a lot :)

• Edited by Morten Meisler Thursday, May 28, 2015 12:57 PM

Yes you can make a new custom mp with overrides for that specific workflow:

http://blogs.technet.com/b/servicemanager/archive/2011/07/07/disabling-workflows-with-overrides.aspx

Edit:

For this specific workflow I'm pretty sure you can disable it in Incident Settings -> Resolution Time -> "Do not use legacy Target Resolution Time on Incident banner". 

If you have changed the priority calculation and/or Resolution Time recently, it re-calculates for all Incidents which can take quite some time if you have a lot :)

• Edited by Morten Meisler Thursday, May 28, 2015 12:57 PM

Yes you can make a new custom mp with overrides for that specific workflow:

http://blogs.technet.com/b/servicemanager/archive/2011/07/07/disabling-workflows-with-overrides.aspx

Edit:

For this specific workflow I'm pretty sure you can disable it in Incident Settings -> Resolution Time -> "Do not use legacy Target Resolution Time on Incident banner". 

If you have changed the priority calculation and/or Resolution Time recently, it re-calculates for all Incidents which can take quite some time if you have a lot :)

• Edited by Morten Meisler Thursday, May 28, 2015 12:57 PM
• Marked as answer by paulshab 17 hours 51 minutes ago

Yes you can make a new custom mp with overrides for that specific workflow:

http://blogs.technet.com/b/servicemanager/archive/2011/07/07/disabling-workflows-with-overrides.aspx

Edit:

For this specific workflow I'm pretty sure you can disable it in Incident Settings -> Resolution Time -> "Do not use legacy Target Resolution Time on Incident banner". 

If you have changed the priority calculation and/or Resolution Time recently, it re-calculates for all Incidents which can take quite some time if you have a lot :)

• Edited by Morten Meisler Thursday, May 28, 2015 12:57 PM
• Marked as answer by paulshab Tuesday, June 02, 2015 1:23 PM

Yes you can make a new custom mp with overrides for that specific workflow:

http://blogs.technet.com/b/servicemanager/archive/2011/07/07/disabling-workflows-with-overrides.aspx

Edit:

For this specific workflow I'm pretty sure you can disable it in Incident Settings -> Resolution Time -> "Do not use legacy Target Resolution Time on Incident banner". 

If you have changed the priority calculation and/or Resolution Time recently, it re-calculates for all Incidents which can take quite some time if you have a lot :)

• Edited by Morten Meisler Thursday, May 28, 2015 12:57 PM
• Marked as answer by paulshab Tuesday, June 02, 2015 1:23 PM

Yes you can make a new custom mp with overrides for that specific workflow:

http://blogs.technet.com/b/servicemanager/archive/2011/07/07/disabling-workflows-with-overrides.aspx

Edit:

For this specific workflow I'm pretty sure you can disable it in Incident Settings -> Resolution Time -> "Do not use legacy Target Resolution Time on Incident banner". 

If you have changed the priority calculation and/or Resolution Time recently, it re-calculates for all Incidents which can take quite some time if you have a lot :)

• Edited by Morten Meisler Thursday, May 28, 2015 12:57 PM
• Marked as answer by paulshab Tuesday, June 02, 2015 1:23 PM

You missed the reference and alias to the workflow in the override rule, as well as some typo stuff with dash etc.

The filename needs to have the same name as the ID also: Microsoft.Demo.Override or whatever you wanna call it.

Here's the version:

<ManagementPack OriginalSchemaVersion="1.1" SchemaVersion="2.0" ContentReadable="true" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xsd="http://www.w3.org/2001/XMLSchema">

<Manifest>

<Identity>
<ID>Microsoft.Demo.Overrides</ID>
<Version>1.0.0.0</Version>
</Identity>
<Name>Override Demo</Name>

 <References>
      <Reference Alias="System">
        <ID>System.Library</ID>
        <Version>7.5.8501.0</Version>
        <PublicKeyToken>31bf3856ad364e35</PublicKeyToken>
      </Reference>
     <Reference Alias="IncidentLibrary">
<ID>ServiceManager.IncidentManagement.Library</ID>
<Version>7.5.3079.0</Version>
<PublicKeyToken>31bf3856ad364e35</PublicKeyToken>
</Reference>
</References>
     
   
</Manifest>

<Monitoring>

<Overrides>
<RulePropertyOverride Property="Enabled" Rule="IncidentLibrary!Incident_Adjust_PriorityAndResolutionTime_Custom_Rule.Update" Enforced="false" Context="System!System.Entity" ID="DisableIncident_Adjust_PriorityAndResolutionTime_Custom_Rule.Update">
<Value>false</Value>
</RulePropertyOverride>

</Overrides>
</Monitoring>

<LanguagePacks>

<LanguagePack ID="ENU" IsDefault="true">

<DisplayStrings>

<DisplayString ElementID="Microsoft.Demo.Overrides">
<Name>Override Demo</Name>
</DisplayString>
</DisplayStrings>
</LanguagePack>
</LanguagePacks>
</ManagementPack>

You missed the reference and alias to the workflow in the override rule, as well as some typo stuff with dash etc.

The filename needs to have the same name as the ID also: Microsoft.Demo.Override or whatever you wanna call it.

Here's the version:

<ManagementPack OriginalSchemaVersion="1.1" SchemaVersion="2.0" ContentReadable="true" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xsd="http://www.w3.org/2001/XMLSchema">

<Manifest>

<Identity>
<ID>Microsoft.Demo.Overrides</ID>
<Version>1.0.0.0</Version>
</Identity>
<Name>Override Demo</Name>

 <References>
      <Reference Alias="System">
        <ID>System.Library</ID>
        <Version>7.5.8501.0</Version>
        <PublicKeyToken>31bf3856ad364e35</PublicKeyToken>
      </Reference>
     <Reference Alias="IncidentLibrary">
<ID>ServiceManager.IncidentManagement.Library</ID>
<Version>7.5.3079.0</Version>
<PublicKeyToken>31bf3856ad364e35</PublicKeyToken>
</Reference>
</References>
     
   
</Manifest>

<Monitoring>

<Overrides>
<RulePropertyOverride Property="Enabled" Rule="IncidentLibrary!Incident_Adjust_PriorityAndResolutionTime_Custom_Rule.Update" Enforced="false" Context="System!System.Entity" ID="DisableIncident_Adjust_PriorityAndResolutionTime_Custom_Rule.Update">
<Value>false</Value>
</RulePropertyOverride>

</Overrides>
</Monitoring>

<LanguagePacks>

<LanguagePack ID="ENU" IsDefault="true">

<DisplayStrings>

<DisplayString ElementID="Microsoft.Demo.Overrides">
<Name>Override Demo</Name>
</DisplayString>
</DisplayStrings>
</LanguagePack>
</LanguagePacks>
</ManagementPack>

• Marked as answer by paulshab 17 hours 51 minutes ago

You missed the reference and alias to the workflow in the override rule, as well as some typo stuff with dash etc.

The filename needs to have the same name as the ID also: Microsoft.Demo.Override or whatever you wanna call it.

Here's the version:

<ManagementPack OriginalSchemaVersion="1.1" SchemaVersion="2.0" ContentReadable="true" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xsd="http://www.w3.org/2001/XMLSchema">

<Manifest>

<Identity>
<ID>Microsoft.Demo.Overrides</ID>
<Version>1.0.0.0</Version>
</Identity>
<Name>Override Demo</Name>

 <References>
      <Reference Alias="System">
        <ID>System.Library</ID>
        <Version>7.5.8501.0</Version>
        <PublicKeyToken>31bf3856ad364e35</PublicKeyToken>
      </Reference>
     <Reference Alias="IncidentLibrary">
<ID>ServiceManager.IncidentManagement.Library</ID>
<Version>7.5.3079.0</Version>
<PublicKeyToken>31bf3856ad364e35</PublicKeyToken>
</Reference>
</References>
     
   
</Manifest>

<Monitoring>

<Overrides>
<RulePropertyOverride Property="Enabled" Rule="IncidentLibrary!Incident_Adjust_PriorityAndResolutionTime_Custom_Rule.Update" Enforced="false" Context="System!System.Entity" ID="DisableIncident_Adjust_PriorityAndResolutionTime_Custom_Rule.Update">
<Value>false</Value>
</RulePropertyOverride>

</Overrides>
</Monitoring>

<LanguagePacks>

<LanguagePack ID="ENU" IsDefault="true">

<DisplayStrings>

<DisplayString ElementID="Microsoft.Demo.Overrides">
<Name>Override Demo</Name>
</DisplayString>
</DisplayStrings>
</LanguagePack>
</LanguagePacks>
</ManagementPack>

• Marked as answer by paulshab Tuesday, June 02, 2015 1:24 PM

You missed the reference and alias to the workflow in the override rule, as well as some typo stuff with dash etc.

The filename needs to have the same name as the ID also: Microsoft.Demo.Override or whatever you wanna call it.

Here's the version:

<ManagementPack OriginalSchemaVersion="1.1" SchemaVersion="2.0" ContentReadable="true" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xsd="http://www.w3.org/2001/XMLSchema">

<Manifest>

<Identity>
<ID>Microsoft.Demo.Overrides</ID>
<Version>1.0.0.0</Version>
</Identity>
<Name>Override Demo</Name>

 <References>
      <Reference Alias="System">
        <ID>System.Library</ID>
        <Version>7.5.8501.0</Version>
        <PublicKeyToken>31bf3856ad364e35</PublicKeyToken>
      </Reference>
     <Reference Alias="IncidentLibrary">
<ID>ServiceManager.IncidentManagement.Library</ID>
<Version>7.5.3079.0</Version>
<PublicKeyToken>31bf3856ad364e35</PublicKeyToken>
</Reference>
</References>
     
   
</Manifest>

<Monitoring>

<Overrides>
<RulePropertyOverride Property="Enabled" Rule="IncidentLibrary!Incident_Adjust_PriorityAndResolutionTime_Custom_Rule.Update" Enforced="false" Context="System!System.Entity" ID="DisableIncident_Adjust_PriorityAndResolutionTime_Custom_Rule.Update">
<Value>false</Value>
</RulePropertyOverride>

</Overrides>
</Monitoring>

<LanguagePacks>

<LanguagePack ID="ENU" IsDefault="true">

<DisplayStrings>

<DisplayString ElementID="Microsoft.Demo.Overrides">
<Name>Override Demo</Name>
</DisplayString>
</DisplayStrings>
</LanguagePack>
</LanguagePacks>
</ManagementPack>

• Marked as answer by paulshab Tuesday, June 02, 2015 1:24 PM

You missed the reference and alias to the workflow in the override rule, as well as some typo stuff with dash etc.

The filename needs to have the same name as the ID also: Microsoft.Demo.Override or whatever you wanna call it.

Here's the version:

<ManagementPack OriginalSchemaVersion="1.1" SchemaVersion="2.0" ContentReadable="true" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xsd="http://www.w3.org/2001/XMLSchema">

<Manifest>

<Identity>
<ID>Microsoft.Demo.Overrides</ID>
<Version>1.0.0.0</Version>
</Identity>
<Name>Override Demo</Name>

 <References>
      <Reference Alias="System">
        <ID>System.Library</ID>
        <Version>7.5.8501.0</Version>
        <PublicKeyToken>31bf3856ad364e35</PublicKeyToken>
      </Reference>
     <Reference Alias="IncidentLibrary">
<ID>ServiceManager.IncidentManagement.Library</ID>
<Version>7.5.3079.0</Version>
<PublicKeyToken>31bf3856ad364e35</PublicKeyToken>
</Reference>
</References>
     
   
</Manifest>

<Monitoring>

<Overrides>
<RulePropertyOverride Property="Enabled" Rule="IncidentLibrary!Incident_Adjust_PriorityAndResolutionTime_Custom_Rule.Update" Enforced="false" Context="System!System.Entity" ID="DisableIncident_Adjust_PriorityAndResolutionTime_Custom_Rule.Update">
<Value>false</Value>
</RulePropertyOverride>

</Overrides>
</Monitoring>

<LanguagePacks>

<LanguagePack ID="ENU" IsDefault="true">

<DisplayStrings>

<DisplayString ElementID="Microsoft.Demo.Overrides">
<Name>Override Demo</Name>
</DisplayString>
</DisplayStrings>
</LanguagePack>
</LanguagePacks>
</ManagementPack>

• Marked as answer by paulshab Tuesday, June 02, 2015 1:24 PM