Microsoft Knowledge Base Email Alertz

(225047) - An OLE DB Provider created using the Visual J++ 6.0 and the OLE DB Simple Provider Toolkit does not work reliably. When attempting to use such a provider from ActiveX Data Object (ADO) via the Recordset.Open() method, the following error occurs:...

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 225047 - Last Review: May 17, 2007 - Revision: 4.2

FIX: Java OLE DB Simple Provider Does Not Work Reliably

This article was previously published under Q225047

SYMPTOMS

An OLE DB Provider created using the Visual J++ 6.0 and the OLE DB Simple Provider Toolkit does not work reliably. When attempting to use such a provider from ActiveX Data Object (ADO) via the Recordset.Open() method, the following error occurs:
-2147217865 (0x80040E37) Description unavailable.
The following application error may occur when using the provider from a Visual J++ or Visual Basic client:
The instruction at '0x7c00ba36' referenced memory at '0x00000004'. The memory could not be 'read'.
The following application error may occur when using the provider from a Visual C++ client:
Unhandled exception in <program.exe> (MSJAVA.DLL): 0xC000005: Access Violation

CAUSE

The Microsoft OLE DB Simple Provider component (Msdaosp.dll) does not properly implement COM reference counting. This causes erratic results with any client of the provider, because the provider may release itself when its real reference count is greater than zero.

RESOLUTION

This problem has been fixed with Microsoft Data Access Components (MDAC) 2.1 Service Pack 2 (SP2). You can download the latest MDAC from the following Microsoft Universal Data Access Web site:
http://msdn2.microsoft.com/en-us/data/aa937695.aspx (http://msdn2.microsoft.com/en-us/data/aa937695.aspx)

STATUS

Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.

MORE INFORMATION

The new release of MDAC also fixes a problem in the Java OLE DB Simple Provider, which causes access violation errors when using the Recordset.Delete() method.

REFERENCES

For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
236044  (http://kbalertz.com/Feedback.aspx?kbNumber=236044/EN-US/ ) Java OLE DB Simple Provider Crashes in Recordset.Delete() Method

APPLIES TO
  • Microsoft Visual J++ 6.0 Standard Edition
  • OLE DB Simple Provider Toolkit 2.0
  • Microsoft Data Access Components Software Development Kit 2.0
  • Microsoft Data Access Components Software Development Kit 2.0
  • Microsoft Data Access Components Software Development Kit 2.1
  • Microsoft Data Access Components 2.1 Service Pack 2
  • Microsoft Data Access Components 2.5
Keywords: 
kbbug kbdatabase kbfix kbmdac210sp2fix KB225047
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate