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. DB2OLEDB May Return Empty Recordsets Under Load

DB2OLEDB May Return Empty Recordsets Under Load

View products that this article applies to.

Symptoms

When you use OLE DB Provider for DB2 (DB2OLEDB) from an ASP page that uses ActiveX Data Objects (ADO) and the client cursor engine, the ASP client code may receive an empty Recordset object when under load. When the client cursor engine is not used, the ASP client code may receive the following error message:

"Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done."

↑ Back to the top

Cause

In multithreaded situations, the DB2OLEDB provider may incorrectly set a column length to zero. This causes a data conversion error to occur. This error, in turn, causes ADO to throw an exception and then return an empty Recordset to the client application.

↑ 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
   --------------------------------------------------------------
   09-Dec-2002  12:01  5.0.0.900       311,568    Crtpkg.dll
   09-Dec-2002  12:01  5.0.0.900       667,920    Db2oledb.dll
   09-Dec-2002  12:01  5.0.0.900        53,552    Ddmstr.dll
   09-Dec-2002  12:01  5.0.0.900        78,096    Mseidb2c.dll
   09-Dec-2002  12:01  5.0.0.900       880,912    Mseidb2d.dll
   09-Dec-2002  12:01  5.0.0.900        24,848    Mseidpm.dll
   09-Dec-2002  12:01  5.0.0.900       262,416    Mseidrda.dll
   09-Dec-2002  12:01  5.0.0.900       147,728    Mseidt.dll
   09-Dec-2002  12:01  5.0.0.900        65,808    Crtpkg.exe
   01-Oct-2002  12:17  5.0.0.900        82,192    Ddmserv.exe

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

↑ Back to the top

Workaround

You can work around this problem if you force the application to run as single threaded by enabling ASP script debugging. However, this workaround greatly affects performance.

↑ Back to the top

Status

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

↑ Back to the top

Keywords: KB810330, kbhotfixserver, kbprb, kbhis2000fix, kbqfe, kbfix, kbbug

↑ Back to the top

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