FIX: Error message in the Application event log when you use BizTalk Adapter for Oracle Database in BizTalk Server 2006: "Underlying connection was closed: Either there was a fatal error on the server or client authentication failed"

Article translations Article translations
Article ID: 973453 - View products that this article applies to.
Expand all | Collapse all

On This Page

SYMPTOMS

Consider the following scenario in Microsoft BizTalk Server 2006:
  • You use the BizTalk Adapter for Oracle Database to connect to Oracle 8, Oracle 9i, or Oracle 10g.
  • You have applied the following three hotfixes for BizTalk Server:
    934040 FIX: One of the Microsoft BizTalk Adapters for Enterprise Applications stops processing incoming messages until you restart the BizTalk Host instance
    942419 FIX: Event ID: 1723 occurs when you use Adapters for Enterprise Applications with BizTalk Server 2006 to process lots of messages
    959105 FIX: Multiple RunTimeAgent processes are created when you use the Microsoft BizTalk Adapter for Oracle database to connect to an Oracle server
In this scenario, you find that the Application log shows error messages that resemble the following.

Error 1


Runtime Error: Underlying connection was closed: Either there was a fatal error on the server or client authentication failed.

Error 2


Error transmitting message: An existing connection was forcibly closed by the remote host.

Error 3


The adapter failed to transmit message going to send port "<send port>" with URL "OracleDb://<URL>". It will be retransmitted after the retry interval specified for this Send Port. Details:"Error transmitting message: Underlying connection was closed: Either there was a fatal error on the server or client authentication failed".
When this problem occurs, some messages may be lost.

CAUSE

This problem occurs because of an error in how Microsoft BizTalk Adapters for Enterprise Applications handles transmission operations.

RESOLUTION

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:
http://support.microsoft.com/contactus/?ws=support
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 Microsoft BizTalk Adapters for Enterprise Applications (also known as Microsoft BizTalk LOB Adapters) 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.
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Microsoft.biztalk.adapters.coretransmitter.dll1.0.1175.041,36817-Jul-200900:00x86
Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.

STATUS

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

MORE INFORMATION

This hotfix also adds limited tracing capability to the BizTalk Adapter for Oracle Database. This hotfix can be used to troubleshoot issues mentioned in the 'Symptoms' section.
Note The information in this section should be applied only when you are troubleshooting these kinds of issues.
  1. Open the BizTalk installation folder. For example, open the following folder:
    C:\Program Files\Microsoft BizTalk Server 2006
  2. Open the BTSNTSvc.exe.config configuration file that is in the folder.
  3. Add the following node inside the <configuration> node.
    <system.diagnostics>
                                    <trace autoflush="true" indentsize="2">
                                                    <listeners>
                                                                    <remove name="Default"/>
                                                                    <add name="TextWriterTraceListener" type="System.Diagnostics.TextWriterTraceListener" initializeData="C:\\AdapterLog.txt"/>
                                                    </listeners>
                                    </trace>
                                    <switches>
                                                    <add name="LOBAdapterTraces" value="3" />
                                    </switches>
                    </system.diagnostics>
    
    Note You can specify a different path for the log file in the initializeData attribute. The LOBAdapterTraces log levels under the <switches> attribute can be specified by using the following values.
    Collapse this tableExpand this table
    ValueItemDescription
    0OffOutputs no messages to Trace Listeners
    1ErrorOutputs only error messages to Trace Listeners
    2WarningOutputs error and warning messages to Trace Listeners
    3InfoOutputs informational, warning and error messages to Trace Listeners
    4VerboseOutputs all messages to Trace Listeners
  4. Restart the BizTalk host instance.
  5. Start to send the message by using the send port in BizTalk Server 2006. Then you can collect traces from the path that is specified in the initializeData attribute.
For more information about Microsoft BizTalk Adapter for Oracle Database, visit the following Microsoft Developer Network (MSDN) Web sites:
http://msdn.microsoft.com/en-us/library/dd801410(BTS.10).aspx
http://msdn.microsoft.com/en-us/library/dd801977(BTS.10).aspx
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.

Properties

Article ID: 973453 - Last Review: August 14, 2009 - Revision: 1.1
APPLIES TO
  • Microsoft BizTalk Adapter for Oracle Database
  • Microsoft BizTalk Server 2006 Developer Edition
  • Microsoft BizTalk Server 2006 Enterprise Edition
  • Microsoft BizTalk Server 2006 Standard Edition
Keywords: 
kbbiztalk2006presp1fix kbsurveynew kbbtsadapters kbautohotfix kbexpertiseinter kbhotfixserver kbqfe KB973453

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com