Skip to main content
Language Selector

  1. Other Languages

    (machine translation)

Planview Customer Success Center

Workflow Management job never finishes and is always in "Running" status

  1. Last updated
  2. Save as PDF

Question
Why the workflow management job never finishes and is always in "Running" status?


Answer
Check if "Windows FIPS encryption" is enabled on the server. "Windows FIPS encryption" can conflict with WorkflowManagement.exe. 

Symptoms and Error/warning messages:
Workflow Management job never finishes and is always in "running" status in SQL Server Management Studio although the WorkflowManagement.exe does not appear in Task Manager/Processes.

The following error appears when running the WorkflowManagement executable using a command line :

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.InvalidOperationException: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.
at System.Security.Cryptography.RijndaelManaged..ctor()
at WorkflowEscalation.Escalation.StepEscalation..ctor()
at WorkflowEscalation.Form1.Form1_Load(Object sender, EventArgs e)
at System.Windows.Forms.Form.OnLoad(EventArgs e)
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)