Application Server: The Workflow Management service should be started

Updated: September 23, 2010

Applies To: Windows Server 2008 R2, Windows Server 2012

This topic is intended to address a specific issue identified by a Best Practices Analyzer scan. You should apply the information in this topic only to computers that have had the Application Server Best Practices Analyzer run against them and are experiencing the issue addressed by this topic. For more information about best practices and scans, see Best Practices Analyzer.

 

Operating System

Windows Server 2012

Windows Server 2008 R2

Product/Feature

Application Server role

Severity

Error

Category

Operations

The AppFabric Workflow Management service has not been started.

This server will not be able to resume persisted WF instances, and you will not be able to control (resume, suspend, cancel, terminate, or delete) your WF service instances.

The AppFabric role service of the Application Server role uses the Workflow Management service to provide management services for workflow service instances, including activation of workflow service instances and the execution of user control commands. The steps performed when the Workflow Management service is installed and configured are described in Installing and Configuring the Workflow Management Service (http://go.microsoft.com/fwlink/?LinkId=200784).

Start the AppFabric Workflow Management service.

  1. Open a command line running as an administrator, and then execute Net Start “AppFabric Workflow Management Service”; or open a PowerShell console, and then execute Start-Service “AppFabric Workflow Management Service”.

Workflow Management Service (http://go.microsoft.com/fwlink/?LinkId=200929)

Community Additions

ADD
Show: