BUG: OLE DB Simple Provider Crashes WJview.exe

ID: Q230761

The information in this article applies to:

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.


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.


RESOLUTION

A supported fix that corrects this problem is now available from Microsoft, but it has not been fully regression tested and should be applied only to systems experiencing this specific problem. If you are not severely affected by this specific problem, Microsoft recommends that you wait for the next Microsoft Data Access Components 2.1 SP2 that contains this fix.

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 on support costs, please go to the following address on the World Wide Web:

http://www.microsoft.com/support/supportnet/overview/overview.asp
The English version of this fix should have the following file attributes or later:

Date Version Size File name
4/29/99 2.10.4029 72.2KB msdaosp.dll

NOTE: If this product was already installed on your computer when you purchased it from the Original Equipment Manufacturer (OEM) and you need this fix, please call the Pay Per Incident number listed on the above Web site. If you contact Microsoft to obtain this fix, and if it is determined that you only require the fix you requested, no fee will be charged. However, if you request additional technical support, and if your no-charge technical support period has expired, or if you are not eligible for standard no-charge technical support, you may be charged a non-refundable fee.

For more information about eligibility for no-charge technical support, see the following article in the Microsoft Knowledge Base:
Q154871 Determining If You Are Eligible for No-Charge Technical Support

Workaround

None.


STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article.


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();
	}

Additional query words: wjview java osp ole db simple provider av crash random garbage collection 


Keywords          : kbADO210fix kbOLEDB210fix kbOSP kbMDAC210 
Version           : WINDOWS:2.1 SP1
Platform          : WINDOWS 
Issue type        : kbbug

Last Reviewed: July 2, 1999