Page 1 of 1

Issue with app on some machines

Posted: Thu 26 Mar 2009 02:52
by jdredd
I have a simple app that brings up this error while using a toraquery. This is using delphi 2007 and latest odac software.

















































NET: Access violation at address 0050FE4D in module VICreate.exe. Read of address 00000008

It works fine on 3 other systems, but not on 2 others. Is there something that must be installed, some kind of windows update or something thats required to be installed that im missing?

Posted: Thu 26 Mar 2009 18:45
by jdredd
Ok im pretty sure its something "missing" or "messed" up with windows, but not sure yet on what.

As soon as anything with ODAC gets initilized it crashes on this 1 system. But I can't find anything in the help/documents on what if anything is required of windows to be isntalled/updated.

This is also in direct mode.

Posted: Fri 27 Mar 2009 14:07
by jdredd
ok, i using the example programs included with ODAC same issues.

I created a small program that all it does is try to connect to a server.

as soon as a i press the button to run odac.connect; it throws out the same exact errors as above, on this 1 machine.

So does anyone know if there is a certain set of files/updates that need to be done to windows?

Posted: Mon 30 Mar 2009 07:24
by Plash
Please specify whether you connect in the Direct mode or using Oracle client.

Posted: Mon 30 Mar 2009 17:37
by jdredd
2nd post, mentioned Direct mode.

This doesnt work with the demo applications either on this problem machine.
As soon as a connection is tried, it crashes out with same exact errors.

Not really sure cause he uses the system all day long for like 10 other tasks using all kinds of stuff, and no problems yet with anything else.

Posted: Thu 02 Apr 2009 14:34
by jdredd
bump, any ideas? :cry:

don't really want to reload the guys system, if its a simple fix.

Posted: Thu 09 Apr 2009 01:39
by jdredd
bump :(

Posted: Thu 16 Apr 2009 07:14
by Plash
Does the same problem occur on this machine for both Direct and OCI modes?

Posted: Sun 19 Apr 2009 20:10
by jdredd
Yes.. it happened basically once any kind of connection command was ran..

we ended up just reloading the system, because we couldn't wait any longer to figure it out what the issue was with odac and that instance of windows install was the issue..