You have a computer that is running Microsoft BizTalk Server 2006 R2 or Microsoft BizTalk Server 2009.
You use one of the following adapters to exchange Business Function messages between BizTalk Server and a JD Edwards EnterpriseOne system:
Microsoft BizTalk Adapter for JD Edwards EnterpriseOne
Microsoft BizTalk Adapter for JD Edwards OneWorld XE
In this scenario, one or more of the following issues may occur.
After you try to send a message by using the adapter, the adapter is idle for a while and then you try to send another message. In this scenario, the adapter does not send the first message. However, the adapter sends the second message. Additionally, an event that resembles the following is logged in the Application log:
Event Type: Error Event Source: Microsoft Biztalk Adapters for Enterprise Applications Event Category: None Event ID: 0 Description: Runtime Error: No connection could be made because the target machine actively refused it 127.0.0.1:15000
When you set the Max Concurrent Calls transport property to a value that is greater than 1 for the adapter, many message instances dehydrate and are not processed.
Periodically messages are suspended. Additionally, some event entries that resemble the following are logged in the Application log:
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.
To apply this hotfix, you must have BizTalk Adapters for Enterprise Applications (also known as BizTalk LOB Adapters) installed. Additionally, the computer should be running BizTalk Server 2006 R2 Service Pack 1 (SP1) or BizTalk Server 2009.
You do not have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace any other hotfixes.
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.
For BizTalk Server 2006 R2 SP1
For BizTalk Server 2009
How to apply this hotfix
To apply this hotfix after you install it, do the following:
Manually register the Microsoft.BizTalk.Adapters.BizUtil.dll file in the global assembly cache (GAC). To do this, follow these steps.
Open a Visual Studio Command Prompt or SDK Command Prompt window. Change the current directory to the following:
%ProgramFiles%\Common Files\Microsoft BizTalk Adapters for Enterprise Applications\Bin
Important To open a Visual Studio Command Prompt window, you must have Microsoft Visual Studio 2008 or Microsoft Visual Studio 2005 installed. To open a SDK Command Prompt window, you must have the Microsoft .NET Framework 2.0 SDK installed.
At the Visual Studio Command Prompt or SDK Command Prompt window, type the following command, and then press Enter:
gacutil /i Microsoft.BizTalk.Adapters.BizUtil.dll
Create a new subkey in the registry. To do this, follow these steps:
Warning Serious problems might occur if you change the registry incorrectly by using Registry Editor or by using another method. These problems might require you to reinstall the operating system. Microsoft cannot guarantee that these problems can be resolved. Change the registry at your own risk.
Click Start, click Run, type regedit, and then click OK.
Locate and then select the following registry key:
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 period of inactivity. We recommend that you set the value so that it is more than the time that is required for the operation to complete on the Oracle server. By default, the value is 60000 milliseconds (1 minute).
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about BizTalk Adapter for JD Edwards EnterpriseOne, visit the following Microsoft Developer Network (MSDN) website:
Microsoft BizTalk Server 2009 Branch, Microsoft BizTalk Server 2009 Developer, Microsoft BizTalk Server 2009 Enterprise, Microsoft BizTalk Server 2009 Standard, Microsoft BizTalk Server 2006 R2 Service Pack 1