ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

After Workflow Server install SymWebInclude and SymWorkflowPages are configured to work in ProcessManagerPool without that pool existing.

book

Article ID: 161296

calendar_today

Updated On:

Products

Workflow Solution

Issue/Introduction

After Workflow Server install SymWebInclude and SymWorkflowPages are configured to work in ProcessManagerPool without that pool existing.

This affects components on form that use scripts from these, for example date picker dropdown.

Cause

Workflow installer will set SymWebInclude and SymWorkflowPages to work in ProcessManagerPool without actually creating the pool or checking if that pool exists. That application pool is created by installer as part of Process Manager role installation but installing Process Manager role is not a requirement.

Resolution

Symantec Engineering is working on the issue.

WORKAROUND/FIX:

Create an Application Pool called ProcessManagerPool with suitable configuration (.NET Framework version: v2.0 and Managed Pipeline Mode: Classic).

  1. Open IIS Manager
  2. Navigate to Application Pools
  3. Add Application Pool:
    Name: ProcessManagerPool
    .Net Framework version: .NET Framework v2.0.50727
    Managed pipeline mode: Classic

Alternatively, SymWebinclude and SymWorkflowPages can be configured to use a different Application Pool with the same configuration.

On SMP Server, it is safe to remove these two applications from IIS.


Applies To

Workflow Server 7.5 installed without Process Manager role (including Workflow Server installed on SMP/CMS/ITMS 7.5)