The MS Windows Script Control and/or Adobe FDF Toolkit are missing or not registering properly on the Windows server


#1

This article applies to WorkflowGen version 5.x.

Errors

  • MS Windows Script Control: Retrieving the COM class factory for component with CLSID {0E59F1D5-1FBE-11D0-8FF2-00A0D10038BC} failed due to the following error: 80040154.

  • Adobe FDF Toolkit: Retrieving the COM class factory for component with CLSID {CB830891-2E18-11D1-B8CF-00A0C9259304} failed due to the following error: 80040154.

Cause

These exception errors could be raised after completing an action or by the WorkflowGenEngineServiceservice because the Windows Script Control (msscript.ocx) and/or Adobe FDF Toolkit (FDFACX.DLL) are either missing, not registered properly or requires the COM+ applications on the Windows server that is hosting WorkflowGen.

Solution

The solution can be found in the Server-side COM Components and Additional configurations for Windows in 64-bit sections in the WorkflowGen Technical Reference Guide.

Note: You must create the WorkflowGen COM+ Applications if your Windows server is in 64 bit because the WorkflowGenEngineService service will running natively in 64 bit mode unless you force it to run in 32 bit mode using the CorFlags Conversion Tool (CorFlags.exe).

Workaround

To avoid the creation of the COM+ applications, you have to setup IIS application pool and WorkflowGenEngineService in 32-bit mode.