In Federal Information Processing Standard (FIPS)-compliant systems, you receive the following error message when you use Microsoft Windows Communication Foundation (WCF) to serialize generic types:

Back to the top

This problem occurs because the MD5 algorithm is not FIPS compliant. The MD5 algorithm uses Windows Communication Foundation to obtain a hash value. The hash value generates a unique name for a data contract.

Back to the top

Download information

The following file is available for download from the Microsoft Download Center:
Download the 307137_intl_i386_zip.exe package or the 307138_intl_x64_zip.exe package now. (https://connect.microsoft.com/VisualStudio/Downloads/DownloadDetails.aspx?DownloadID=7248)

Release Date: 6/20/2007

For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base: Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.

Back to the top

Hotfix information

A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft .NET Framework 3.0 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

You must have the .NET Framework 3.0 installed to apply this hotfix.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any 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.

File name	File version	File size	Date	Time	Platform
System.runtime.serialization.dll	3.0.4506.44	884,736	21-Mar-2007	20:49	x86

Back to the top

To work around this problem, use one of the following methods.

Back to the top

Method 1

Provide unique names for the data contracts.

You can use this method when the generic types that you must serialize must be used as the generic parameters.

Back to the top

Method 2

Create a subclass of the ReadOnlyCollection<T> class. When you use instances of the subclass, use the CollectionDataContract attribute to handle the namespace hash value issues. For example, use the following code.

[CollectionDataContract(Name=”ReadOnlyCollectionOf{0}{1}”)]

class MomReadOnlyCollection<T> : ReadOnlyCollection<T> { }

Back to the top

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

Back to the top

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top