Summary

When a user creates a project in Bizagi Studio and it is deployed to the IIS, the project loads correctly the first time. Nevertheless when the project tries to invoke a Web Service from an Automatic task, the Web Application displays an error. Then, when the IIS is restarted, the Work Portal does not start and the event viewer displays the detail of the error above.

Applies to

Bizagi Engine 10.x .NET or higher

Symptoms

This error has two symptoms:

1. When trying to execute automatic tasks or any process activity, the following error is displayed:

Unable to process the case: "Automatic Task Failed: Id Task = X, Id Case = Y. This implementation is not part of the Windows Plataform FIPS validate cryptographic algorithms".

2. The Web Application does not start and the Event Viewer displays errors like: 

Cause

This is an error generated on .Net Framework, and according to Microsoft “Windows Workflow Foundation implements hash algorithms by using Message Digest 5 (MD5). However, MD5 is not compliant to the FIPS algorithm.”
Refer to https://support.microsoft.com/en-us/kb/977069 for more information.

Solution

In the link mentioned above, Microsoft explains a solution to this problem and give a workaround.
The workaround is to include the following key in Bizagi’s web.config (located in the root folder, C:\Bizagi\Projects\[ProjectName]\WebApplicaton\web.config)
 Within the <runtime> section:

<enforceFIPSPolicy enabled=”false” />