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: -
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 BizTalk Server 2006 R2 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 |
---|
Btswmiprovider.dll | 3.6.1482.2 | 606,736 | 11-Aug-2008 | 17:51 | x86 |
After you apply this hotfix, the
problem does not occur when you create the new MessageBox databases in BizTalk
Server 2006 R2.
Note This hotfix does not recover the problematic MessageBox database
that is created before you apply this hotfix. You have to delete
the problematic MessageBox. To do this, refer to
the "More
information"
section. You should be aware that deleting the MessageBox may cause a
loss of data.