I get similar when I try to invoke a .net command from autolisp.
it may be that the .net command was written poorly, or there is some other issue with lisp and .net commands that I don't understand.
Or you are starting two commands somehow and both are trying to access the same database (OLEDB_SELECT sounds like a database/spreadsheet access command)?
I have seen similar but not in normal operation. only when doing custom lisp stuff.
I think I get that same error or at least very close to it when I use
wd_oledb_select
I have determined that this command was poorly written as it opens the database but never closes it. I was originally using this command to read the project scratch database. It cut off autocad electrical 2018.1.2 from being able to rebuild it. I would like to know how you are using the command (what ever that is) you are using, because I found a work around to not using wd_oledb_select.
i do not use this command directly
For example, when i want editing component. I choose Edit component command then it gives the fault.
Usually if I get many unhandled exception codes in Autocad and it is really impeding my work. I back up my customizations. Then run the 'reset settings to default autocad electrical' utility in windows. However, this is typically a last resort option.
Is this problem drawing specific? Have you been able to replicate it on another computer with the same drawings or projects? Or is it only your computer?
It is only my computer.Usually when I want edit component or insert catalog data , give the same failure.
I get this error when trying to edit the Termination Builder in AutoCAD Electrical 2019.
If I close AutoCAD Electrical and delete the project.mdb file then the termination builder will work a few more times before this error renders it unusable and I have to delete the project.mdb file again.
Not sure if this is a bug introduced in AutoCAD Electrical 2019 but we have dealt with similar sized projects in the past without this problem.
does wd_oledb_select work on another computer?
This command may not need to close the database because it is accessing the scratch database that ACADE already has opened.
Also try wd_oledb_command, and just type any query you want... maybe that one works?
i tried almost everything what you said . my problem is still not solved . I think, i need reload but now my project very busy therefore i can't reload
I know this is not a permanent solution, but I find if I go uninstall the latest MS Access windows update all my errors go away. It is February 202 and I never had these issues until thanksgiving of 2019 up to now. I must keep going in and uninstalling the updates once or twice a week. Once I do Acad-e works like a charm again.
This thread is not affected by that update. That update was released on November 12th 2019. His post was posted on "08-09-2018." Long before that update was released. To fix your problem of uninstalling that update twice a week is to run the update after that one. Located here:
https://support.microsoft.com/en-us/help/4484193/security-update-for-office-2010-december-10-2019