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. Vague TCP/IP Socket Errors Are Returned for OLE DB2 Provider

Vague TCP/IP Socket Errors Are Returned for OLE DB2 Provider

View products that this article applies to.

This article was previously published under Q329818

↑ Back to the top

Symptoms

NOTE: This article also applies to Host Integration Server 2000

When you use Host Integration Server 2000 OLE DB Provider for DB2 in a TCP/IP environment, you may receive the following error message:
SQLSTATE: HY000, SQLCODE: -3
If you look at the Db2oledb.h header file, the "-3" indicates a DB2OLEDB_ERROR_RECEIVE for this error. This does not correctly indicate the TCP/IP socket error type.

NOTE: The Db2oledb.h header file is part of Host Integration Server 2000 software development kit (SDK).

↑ Back to the top

Cause

Host Integration Server 2000 OLE DB Provider for DB2 returns a generic SOCKET_ERROR when a TCP/IP send or receive fails.

↑ Back to the top

Resolution

Service pack information

To resolve this problem, obtain the latest service pack for Microsoft Host Integration Server 2000. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
328152� How to obtain the latest service pack for Host Integration Server 2000

Hotfix information

The English version of this fix has the file attributes (or later) 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 tool in Control Panel. 
   Date         Time   Version            Size    File name
   --------------------------------------------------------------
   17-Oct-2002  20:42  5.0.0.900         311,568  Crtpkg.dll       
   17-Oct-2002  20:42  5.0.0.900         663,824  Db2oledb.dll     
   17-Oct-2002  20:42  5.0.0.900          78,096  Mseidb2c.dll     
   17-Oct-2002  20:42  5.0.0.900         880,912  Mseidb2d.dll     
   17-Oct-2002  20:42  5.0.0.900          24,848  Mseidpm.dll      
   17-Oct-2002  20:42  5.0.0.900         262,416  Mseidrda.dll     
   17-Oct-2002  20:41  5.0.0.900         147,728  Mseidt.dll       
   17-Oct-2002  17:58  5.0.0.900          65,808  Crtpkg.exe

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in Microsoft Host Integration Server 2000 and Microsoft Host Integration Server 2000 Service Pack 1. This problem was corrected in Microsoft Host Integration Server 2000 Service Pack 2.

↑ Back to the top

More information

Microsoft has updated Host Integration Server 2000 OLE DB Provider for DB2 to provide the specific SOCKET_ERROR, which is displayed in internal tracing. To see the message, you must have Error Conditions turned on in DB2 Network Library. To do this, you can use the Systems Network Architecture (SNA) Trace utility (Snatrace.exe). You can potentially see a message when you connect, send, or receive over the Windows TCP socket. An example trace message is formatted as follows: 
Windows TCPIP Socket Connection (10061): No connection could
be made because the target machine actively refused it.

↑ Back to the top

Keywords: KB329818, kbhotfixserver, kbqfe, kbfix, kbbug

↑ Back to the top

Article Info
Article ID : 329818
Revision : 3
Created on : 9/27/2005
Published on : 9/27/2005
Exists online : False
Views : 441