FIX: A CPU usage spike occurs on all the BizTalk hosts after you install security bulletin MS07-040 on a server that is running Microsoft BizTalk Server 2006 or Microsoft BizTalk Server 2006 R2

Consider the following scenarios.

Scenario 1

• You have the Microsoft .NET Framework 2.0 RTM installed on a server that also has Microsoft BizTalk Server 2006 or Microsoft BizTalk Server 2006 R2 installed.
• The server is running a 64-bit operating system.
• You install security bulletin MS07-040 on the server. This updates the .NET Framework 2.0 RTM to a later RTM branch version.

Scenario 2

• You have the .NET Framework 2.0 SP1 or a later version installed�on a server that also has BizTalk Server 2006 or BizTalk Server 2006 R2 installed.
  
  Note The .NET Framework 2.0 SP1 and later versions include the changes in security bulletin MS07-040.
• The server is running a 64-bit operating system.

In these scenarios, an increase in CPU usage occurs on all the BizTalk hosts.

Notes

• This issue does not occur on a 32-bit operating system.
• On a 64-bit version of BizTalk Server 2006 or BizTalk Server 2006 R2, when you shut down a 64-bit BizTalk Server host instance, the shutdown process may take 60 seconds to finish.

Service pack information

To resolve this issue for BizTalk 2006 R2, obtain the latest service pack. For more information about BizTalk Server 2006 R2 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:

Hotfix information

There are two versions of this hotfix:

• BizTalk Server 2006
• BizTalk Server 2006 R2

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. 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 the following software products installed to apply this hotfix:

• Microsoft BizTalk Server 2006
• Microsoft BizTalk Server 2006 R2

Restart requirement

You do not have to restart your 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.

Microsoft BizTalk Server 2006

Microsoft BizTalk Server 2006 R2

Note Only a 32-bit version of the Microsoft.biztalk.msgboxperfcounters.dll file is available.

Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.

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

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