I'm experiencing the following exception after running my application for a few hours. Unfortunately, this has been difficult to reproduce with a sample app. Could you shed any light as to what this assertion failure means?
Assertion failure (C:\Program Files\CoreLab\SDAC\Source\OLEDBAccess.pas, line 7481)
What starts it off is the following error:
Access violation at address 74A5846D in module 'MSDART.DLL'. Read of address 0000007D
This is under: MDAC 2.8 SP2 on Windows Server 2003 SP1
I've used the component checker to verify MDAC, and it reports no problems.
On another note, I've emailed the following question twice, with no response (this happens on two different machines, one being the same as above):
We are seeing this error in Delphi 7 after executing a stored proc a number of times (varies from several hundred to several thousand calls). This is occurring in a single thread and CoInitialize has been called correctly within the context of the Thread.Execute method before the main loop.
EOLEDBError 'Object was open.'
What does the error message 'Object was open.' mean and do you know under what conditions this error could be caused?
We are using the latest version of SQL Server Data Access Components (SDAC) 3.70.1.25
ANY clues as to the nature of this error would be GREATLY appreciated.
Assertion failure (OLEDBAccess.pas, line 7481)
We answered you 23.03.2006. Please check your spam filter.
As for 'Object was open' error message.
Most possible reason of this error is that several components from different
threads use same connection.
Assertion failure can occur when a lot of options are set to non-default value.
We couldn't reproduce the problem.
Please send us a complete small test project to reproduce the problem; it is
desirable to use Northwind or Master schema objects, otherwise include
definition of your own database objects; don't use third party components.
Also supply us following information
- Exact version of Microsoft SQL Server and OLE DB provider that you use.
You can see it in Info sheet of TMSConnection Editor.
As for 'Object was open' error message.
Most possible reason of this error is that several components from different
threads use same connection.
Assertion failure can occur when a lot of options are set to non-default value.
We couldn't reproduce the problem.
Please send us a complete small test project to reproduce the problem; it is
desirable to use Northwind or Master schema objects, otherwise include
definition of your own database objects; don't use third party components.
Also supply us following information
- Exact version of Microsoft SQL Server and OLE DB provider that you use.
You can see it in Info sheet of TMSConnection Editor.