Hotfix information
There are two versions of this hotfix:
- Microsoft BizTalk Server 2006
- Microsoft 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.
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
This hotfix applies Microsoft BizTalk Adapters for Enterprise Applications installed on BizTalk Server 2006�BizTalk Server 2006 R2.
and
BizTalk Adapters for LOB applications installed. Or, you must have BizTalk Server 2006 R2 and BizTalk Adapters for LOB applications installed.
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.
BizTalk Server 2006
File name | File version | File
size | Date | Time | Platform |
---|
Microsoft.biztalk.adapters.bizutil.dll | 1.0.1168.0 | 164,224 | 05-Nov-2008 | 17:40 | x86 |
BizTalk Server 2006 R2
File name | File version | File
size | Date | Time | Platform |
---|
Microsoft.biztalk.adapters.bizutil.dll | 1.0.5020.0 | 162,680 | 24-Mar-2009 | 20:54 | x86 |
Note Because of file dependencies, the most recent hotfix that
contains these files may also contain additional files.
How to use this hotfix
This hotfix updates the same DLL on BizTalk Server 2006 and on BizTalk Server 2006 R2. Please note the file version in these tables to confirm that you installed the correct version.
After you apply this hotfix, you must do the following:
- Manually register the Microsoft.BizTalk.Adapters.BizUtil.dll file in the global assembly cache (GAC). To do this, use one of the following methods.
Method 1: If you have Microsoft Visual Studio 2005 installed- Click Start, point to All Programs, point to Microsoft Visual Studio 2005, point to Visual Studio Tools, and then click Visual Studio 2005 Command Prompt.
- At the Visual Studio command prompt, locate the following folder:
%ProgramFiles%\Common Files\Microsoft BizTalk Adapters for Enterprise Applications\Bin
- At the Visual Studio command prompt, run the following command:
gacutil /i Microsoft.BizTalk.Adapters.BizUtil.dll
Method 2: If you do not have Microsoft Visual Studio 2005 installed- Click Start, click Run, type cmd, and then click OK.
- At the command prompt, locate the following folder:
%WINDIR%\Microsoft.NET\Framework\v1.1.4322
- At the command prompt, run the following command:
gacutil /i "<Drive>:\Program Files\Common Files\Microsoft BizTalk Adapters for Enterprise Applications\Bin\ Microsoft.BizTalk.Adapters.BizUtil.dll"
Note These BizTalk adapters use the Microsoft .NET Framework 1.1. - In the registry, follow these steps and then quit Registry Editor:
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
- Click Start, click Run, type regedit, and then click OK.
- Locate and then select the following key in the registry:
32-bit: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\BizTalkAdapters
64-bit: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\BizTalkAdapters
- On the Edit menu, point to New, and then click DWORD Value.
- Type AgentOutboundTimeout, and then press ENTER.
- On the Edit menu, click Modify.
- Select Decimal, type 60000, and then click OK.
The AgentOutboundTimeout value is used to recycle the RunTimeAgent processes after a certain time of inactivity. The value should be set so it is more than the time it takes for the operation to complete on the Oracle server. The default value is 60000 milliseconds (1 minute).