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.

BUG: OLE DB Simple Provider Crashes WJview.exe


View products that this article applies to.

This article was previously published under Q230761

↑ Back to the top


Symptoms

When using the OLE DB Simple Provider (OSP) from within Java, after a random amount of time the application will return an Application Error similar to:
The instruction at 0x7c00ba35 referenced memory at 0x00000004. The memory could not be 'read'"
This error is an Access Violation in the Java VM, and the VM will be terminated.

↑ Back to the top


Cause

A bug in the OSP provider (msdaosp.dll) has the DataSourceListener COM object hardwired to return 1 or 0 from the AddRef/Release methods and delete the object. Meanwhile, the Java VM holds a reference to the object, which it attempts to release when garbage collection occurs. By this time, however, the object is no longer in memory, and an Access Violation (AV) occurs.

↑ Back to the top


Resolution

A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Microsoft Data Access Components 2.1 SP2 that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix should have the following file attributes or later:

Collapse this tableExpand this table
DateVersionSizeFile name
4/29/99 2.10.402972.2KBmsdaosp.dll

Workaround

None.

↑ Back to the top


Status

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

↑ Back to the top


More information

To reproduce the error, use code similar to the following in a Java application:
Recordset rs;
rs = new Recordset();
rs.setCursorLocation( AdoEnums.CursorLocation.CLIENT );
Connection conn = new Connection();
conn.open( "Provider=MSDAOSP.1;Data Source=TestOSP.MyDataSource;");
for ( int i = 0; i < 100; i++ )
	{
		Debug.println( "Iteration: " + Integer.toString(i+1) );
		rs.open( "customer.txt", conn );
		rs.close();
	}
				

↑ Back to the top


Keywords: KB230761, kbhotfixserver, kbado210fix, kbqfe, kboledb210fix, kbfix, kbbug

↑ Back to the top

Article Info
Article ID : 230761
Revision : 6
Created on : 10/7/2005
Published on : 10/7/2005
Exists online : False
Views : 357