Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. FIX: Errors occur after you change the Connect Timeout property to a value greater than 15 seconds in a Host Integration Server 2010 or 2013 environment

FIX: Errors occur after you change the Connect Timeout property to a value greater than 15 seconds in a Host Integration Server 2010 or 2013 environment

View products that this article applies to.

Symptoms

Consider the following scenario:
  • You use one of the following Microsoft Host Integration Server 2010 data providers to connect to an IBM DB2 system:
    • Microsoft BizTalk Adapter for DB2
    • Microsoft ADO.NET Data Provider for DB2
  • You enable connection pooling by adding the Connection Pooling=True property to the connection string that is used to connect to the IBM DB2 system.
  • You change the Connect Timeout property in the DB2 connection string to have a value greater than 15 seconds.
  • You save the changes to the DB2 connection string.

In this scenario, when you use the BizTalk Adapter for DB2 or when you run an application that uses the ADO.NET Data Provider for DB2, you receive one of the following error messages:

Error message 1

The connection string is not defined or contains invalid properties

Error message 2

Value is out of range

↑ Back to the top

Cause

This problem occurs because the BizTalk Adapter for DB2 and the ADO.NET Data Provider for DB2 data providers use a Connect Timeout property that has a maximum value of 15 seconds.

↑ Back to the top

Resolution

Cumulative update information

The fix that resolves this issue is included in cumulative update package 1 for Host Integration Server 2013. For more information about how to obtain the cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2908834  Cumulative Update Package 1 for Host Integration Server 2013
The fix that resolves this problem is included in cumulative update package 8 for Host Integration Server 2010. For more information about how to obtain the cumulative update package, see Cumulative Update Package 8 for Host Integration Server 2010 .

↑ Back to the top

Status

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

↑ Back to the top

More Information

The Connect Timeout property specifies how long a new connection request waits when all the connections in the connection pool are being used. If a connection does not become available before the value of the Connect Timeout property expires, the new connection request fails, and a "connection not available" exception occurs.

After you apply this update, the Connect Timeout property does not have an upper limit. Additionally, an infinite Connect Timeout value is specified by using a value of -1.

This updated behavior for the BizTalk Adapter for DB2 and the Microsoft ADO.NET Data Provider for DB2 matches the behavior that is already present when you use the OLE DB Provider for DB2 that is included in Host Integration Server 2010 and the stand-alone OLE DB Provider for DB2 providers that are included with the Microsoft SQL Server feature packs.

↑ Back to the top

Keywords: kbqfe, kbfix, kbnotautohotfix, kbexpertiseinter, kbbug, kbsurveynew, kb

↑ Back to the top

Article Info
Article ID : 2878946
Revision : 1
Created on : 1/7/2017
Published on : 3/31/2014
Exists online : False
Views : 311