One workstation gets AV at 0, read of address 0

MarcS · Post by **MarcS** » Tue 21 Oct 2008 19:53

I emailed this to support on 10/15, but haven't heard back. Maybe somebody here has experienced the same problem.

Our application is compiled with Delphi 2007 (Win32). We generally use either dbexpoda40.dll to connect to Oracle or dbexpsda40.dll to connect to MS SQL.

Specific versions we're using are dbexpoda40.dll 4.20.0.8 and dbexpsda40.dll 4.25.0.8.

Our application works fine on many different inhouse and customer workstations.

One of our employees, not a developer, with our client-server app on his desktop is getting Access Violation at address 0, read of address 0. This happens regardless of what Oracle database we configure him to connect to. If we set him to connect to an MS SQL database, it works fine.

As a test, I also compiled the demo app "Query.exe" from my "C:\Program Files\CoreLab\DbxOda\Demos\Win32\Query". (I don’t remember whether I took default location for CoreLab install.) On my workstation this works fine, but on his we get the same Access Violation at address 0, read of address 0.

He has Oracle 10g client installed, I don't know the specific version.

He is able to use TOAD to connect to the same databases where our dbExpress code gets the Access Violation.

It seems like this is a configuration problem not a Devart code problem specifically, but do you have any suggestions for resolving or further diagnosing it?

Thanks.

Plash · Post by **Plash** » Fri 24 Oct 2008 07:45

Does this access violation occur with the Oracle driver only or with the SQL Server driver, too?
If it is possible, please check if the standard Borland driver for Oracle works without errors on this workstation.

MarcS · Post by **MarcS** » Thu 30 Oct 2008 14:34

SQL Server driver doesn't get the access violation. I had mentioned that in my original post, but it was buried in there.

I recompiled the Devart query.exe demo to use the standard Borland driver dbxora30.dll. That does NOT give the access violation either.

Thanks.

MarcS · Post by **MarcS** » Thu 30 Oct 2008 20:33

Just to clarify, using the CodeGear / Borland driver is not a feasible "solution" for us - that's why we bought devart's.

Hoping you have more suggestions about how we might diagnose or work-around?

Thanks.

MarcS · Post by **MarcS** » Mon 10 Nov 2008 22:05

Any further suggestions?

Thanks.

Plash · Post by **Plash** » Tue 02 Dec 2008 09:06

Please contact us by e-mail dbxoda*devart*com. We'll send you the driver compiled with EurekaLog. It will create a log file with the call stack for the access violation.