Article ID: 928833
Article Last Modified on 12/8/2006
APPLIES TO
- Windows Workflow Foundation
SYMPTOMS
When you develop or run a Microsoft Windows Workflow Foundation-based application on a computer that has Federal Information Processing Standard (FIPS) compliant algorithms enabled, you may experience any of the following symptoms:
- The application crashes, and you receive the following error message:
- When you debug the application, Microsoft Visual Studio crashes.
- You receive the following build error message when you try to compile a project that contains an Extensible Object Markup Language (XOML) workflow object:
CAUSE
This issue occurs because Windows Workflow Foundation uses the MD5CryptoServiceProvider class to provide non-secure hashing of a string to a unique key. The MD5CryptoServiceProvider class does not support FIPS compliance.
WORKAROUND
To work around this issue, disable the FIPS encryption level. You can use the Group Policy Object. To do this, follow these steps:
- Click Start, click Run, type gpedit.msc, and then click OK.
- Expand Computer Configuration, expand Windows Settings, expand Security Settings, expand Local Policies, and then click Security Options.
- In the right pane, double-click System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing, click Disable, and then click OK.
STATUS
This behavior is by design.
MORE INFORMATION
For more information about the GPO setting for System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing, click the following article number to view the article in the Microsoft Knowledge Base:
811833 The effects of enabling the "System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing" security setting in Windows XP and later versions
Keywords: kbtshoot kbprb KB928833
