FIX: You cannot use Message Queuing 3.0 to send messages over HTTPS if the Federal Information Processing Standard (FIPS) is enabled in Windows Server 2003

On a computer that is running Windows Server 2003, if you have enabled Federal Information Processing Standard (FIPS)-compliant algorithms, you cannot send messages by using Message Queuing (also known as MSMQ) 3.0 over HTTPS.

By default, when you use Message Queuing 3.0 to send messages over HTTPS, a Secure Sockets Layer (SSL) 3.0 connection is established. However SSL 3.0 is not FIPS-compliant. Therefore, if FIPS is enabled on the computer, you cannot send messages over HTTPS by using Message Queuing.

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 the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

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, contact 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: 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 Windows Server 2003 Service Pack 1 (SP1) or Windows Server 2003 SP2 installed to apply this hotfix.

Restart requirement

You must restart your computer after 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.

Windows Server 2003 with Service Pack 1, x86-based versions

Windows Server 2003 with Service Pack 2, x86-based versions

Windows Server 2003 with Service Pack 1, x64-based versions

Windows Server 2003 with Service Pack 2, x64-based versions

Windows Server 2003 with Service Pack 1, IA64-based versions

Windows Server 2003 with Service Pack 2, IA64-based versions

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

Note The Federal Information Processing Standard 140-1 (FIPS 140-1) and its successor,the FIPS 140-2, are United States Government standards that provide a benchmark for implementing cryptographic software.

To enable FIPS-compliant algorithms, follow these steps:

1. In Control Panel, double-click Administrative Tools.
2. In Administrative Tools, double-click Local Security Policy.
3. In Local Security Policy, expand Local Policies, expand Security Options, and then double-click System cryptography: Use FIPS compliant algorithms for encryption, hashing and signing.
4. In the System cryptography: Use FIPS compliant algorithms for encryption, hashing and signing Properties dialog box, click the Local Security Setting tab.
5. On the Local Security Setting tab, click Enabled, and then click OK.
6. Close Local Security Policy.

For more information about how to configure Message Queuing 3.0 for messaging by using HTTPS, download the document from the following link: