DB_E_BADTYPENAME Error with ADO and OLEDB2 Provider

View products that this article applies to.

This article was previously published under Q330834

NOTE: This article also applies to Microsoft Host Integration Server 2000

Symptoms

If you call a Stored Procedure from ADO while using the Microsoft Host Integration Server OLE DB2 Provider for DB2, you may receive a DB_E_BADTYPENAME (0x80040E30) error for the OleDbDataAdapter:Fill method.

↑ 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
   --------------------------------------------------------------
   30-Oct-2002  17:14  5.0.0.900         311,568  Crtpkg.dll       
   30-Oct-2002  17:13  5.0.0.900         667,920  Db2oledb.dll     
   30-Oct-2002  17:14  5.0.0.900          78,096  Mseidb2c.dll     
   30-Oct-2002  17:14  5.0.0.900         880,912  Mseidb2d.dll     
   30-Oct-2002  17:14  5.0.0.900          24,848  Mseidpm.dll      
   30-Oct-2002  17:14  5.0.0.900         262,416  Mseidrda.dll     
   30-Oct-2002  17:13  5.0.0.900         147,728  Mseidt.dll       
   30-Oct-2002  17:14  5.0.0.900          65,808  Crtpkg.exe

NOTE: Because of file dependencies, the most recent fix that contains the preceding files may also contain additional files.

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in Microsoft Host Integration Server 2000, 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