Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. FIX: You receive a System.InvalidOperationException exception when you start a .NET Framework-based application that runs Extensible Object Markup Language workflows on a computer that has the FIPS algorithm enabled

FIX: You receive a System.InvalidOperationException exception when you start a .NET Framework-based application that runs Extensible Object Markup Language workflows on a computer that has the FIPS algorithm enabled

View products that this article applies to.

Symptoms

Consider the following scenario:
  • You enable the Federal Information Processing Standard (FIPS) algorithm on a computer.
  • You start a managed application that runs Extensible Object Markup Language (also known as XOML) workflows on the computer.
  • The application runs on the .NET Framework 2.0 or on later versions.
In this scenario, the application crashes. Additionally, a System.InvalidOperationException exception is thrown, and you receive the following error message:
This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.

↑ Back to the top

Cause

This problem occurs because Windows Workflow Foundation implements hash algorithms by using Message Digest 5 (MD5). However, MD5 is not compliant to the FIPS algorithm.

↑ Back to the top

Resolution

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

You must have the .NET Framework 3.5 Service Pack 1 (SP1) installed to apply this hotfix.

Restart requirement

You do not have to restart the computer after you apply this hotfix if no instance of the .NET Framework is being used.

Hotfix replacement information

This hotfix does not replace other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
For all supported x86-based versions of Windows Server 2000, of Windows Server 2003, and of Windows XP
File nameFile versionFile sizeDateTimePlatform
System.workflow.activities.dll3.0.4203.44431,142,78417-Nov-200922:17x86
System.workflow.componentmodel.dll3.0.4203.44431,630,20817-Nov-200922:17x86
System.workflow.runtime.dll3.0.4203.4443540,67217-Nov-200922:17x86
For all supported x64-based versions of Windows Server 2000, of Windows Server 2003, and of Windows XP
File nameFile versionFile sizeDateTimePlatform
System.workflow.activities.dll3.0.4203.44431,060,86417-Nov-200921:34x86
System.workflow.componentmodel.dll3.0.4203.44431,519,61617-Nov-200921:34x86
System.workflow.runtime.dll3.0.4203.4443454,65617-Nov-200921:34x86

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

Workaround

To work around this problem, disable the FIPS algorithm for the application. To do this, follow the steps that are described in the following Microsoft Developer Network (MSDN) Web site:
http://blogs.msdn.com/shawnfa/archive/2008/03/14/disabling-the-fips-algorithm-check.aspx
Note This method works only for applications that run on the .NET Framework 2.0 SP1 or on later versions.

↑ Back to the top

More Information

For more information about how to enable the FIPS algorithm on a computer, visit the following MSDN Web site:
http://blogs.msdn.com/shawnfa/archive/2005/05/16/417975.aspx

↑ Back to the top

Keywords: kb, kbexpertiseadvanced, kbnotautohotfix, kbhotfixdev, kbsurveynew, kbqfe, kbhotfixserver

↑ Back to the top

Article Info
Article ID : 977069
Revision : 4
Created on : 3/30/2017
Published on : 3/30/2017
Exists online : False
Views : 391