Microsoft KB Archive/923650

= The BizTalk Adapters for Enterprise Applications adapter that you use in the BizTalk application may fail at run time when you use a domain group to configure BizTalk Server 2006 =

Article ID: 923650

Article Last Modified on 9/22/2006

-

APPLIES TO


 * Microsoft BizTalk Adapter for Oracle Database
 * Microsoft BizTalk Adapter for Oracle E-Business Suite
 * Microsoft BizTalk Adapter for PeopleSoft Enterprise
 * Microsoft BizTalk Adapter for Siebel eBusiness Applications
 * Microsoft BizTalk Adapter for J.D. Edwards EnterpriseOne
 * Microsoft BizTalk Adapter for J.D. Edwards OneWorld

-



Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows registry



SYMPTOMS
Consider the following scenario. You use a domain group to configure Microsoft BizTalk Server 2006. A domain user account that is a member of the domain group is configured as the BizTalk host instance. The domain user account is not a member of any group on the local computer. In a BizTalk application, you use one of the adapters that is included in Microsoft BizTalk Adapters for Enterprise Applications.

Note BizTalk Adapters for Enterprise Applications includes the adapters that are listed in the &quot;Applies to&quot; section.

In this scenario, the adapter that you use in the BizTalk application may fail at run time. When you run the BizTalk application, an Error event that resembles one of the following may be logged in the Application log:

Event 1

Event Type: Error

Event Source: Microsoft BizTalk Adapters for Enterprise Applications

Event Category: None

Event ID: 0

Description:

Runtime Error: Unable to load DLL (BAUtil.dll).

Event 2

Event Type: Error

Event Source: Microsoft BizTalk Adapters for Enterprise Applications

Event Category: None

Event ID: 0

Description:

&quot;RuntimeAgent: Error trapped in constructor: No connection could be made because the target machine actively refused it

Event 3

Event Type: Error

Event Source: BizTalk Server 2006

Event Category: BizTalk Server 2006

Event ID: 5754

Description:

A message sent to adapter &quot;PeopleSoft&quot; on send port &quot;PS_PORT&quot; with URI &quot;PeopleSoft:////xyxy:9200_abcdef01-0683-4103-8038-929220109528&quot; is suspended.



CAUSE
This issue occurs if the domain user account that is configured as the BizTalk host instance cannot read the following registry key:



RESOLUTION
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 your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

To resolve this issue, grant the Read permission on the following registry key to the domain group or to the domain user account that is configured as the BizTalk host instance:

To do this, follow these steps:  Click Start, click Run, type Regedit, and then click OK. Locate the following registry key:

 Right-click the registry key that you located in step 2, and then click Permissions. On the Security tab, click Add. Type the domain group or the domain user account that is configured as the BizTalk host instance, and then click OK. On the Security tab, click the domain group or the domain user account that you added in step 5, click to select the Read check box, and then click OK.</li> Exit Registry Editor.</li></ol>

<div class="moreinformation_section">

MORE INFORMATION
The adapters that are included in BizTalk Adapters for Enterprise Applications access the local registry at run time. If the domain user account that is configured as the BizTalk host instance does not have access to the local registry, the adapters fail. When BizTalk Server 2006 is configured to use a domain group for the BizTalk Application Users group, the domain group is not automatically granted access to the local registry.

<div class="references_section">