cscript.exe - Application Error 'The instruction at 0x7c82f583' referenced memory at 0xffffffff'. The memory could not be read.

[Tim Frawley]

Windows 2003 Server Standard Edition SP1
IIS6
Oracle ODBC Driver version: 10.01.00.31
WSH version (from the cscript.exe file): 5.6.0.8825

In ASP I execute:
----------------------------------------------
DIM objShell
Set objShell = CreateObject("WScript.Shell")
objShell.Run "cscript c:\inetpub\scripts\test.vbs"
Set objShell = Nothing
----------------------------------------------

The test.vbs file contains:
----------------------------------------------
DIM objConn,vDBResult,strSQL

strSQL = "select * from dual"

Set objConn = CreateObject("ADODB.Connection")
objConn.Open "DSN=xxx;UID=xxx;PWD=xxx"
Set vDBResult = objConn.Execute(strSQL)
----------------------------------------------

Every single execution causes the following error:

cscript.exe - Application Error
'The instruction at 0x7c82f583' referenced memory at 0xffffffff'.
The memory could not be read.

This test works fine on our old server:

Windows 2000 Server SP4
IIS5
Oracle ODBC Driver verison 10.01.00.31
WSH version (from the cscript.exe file): 5.6.0.6626

The test is running in a virtual directory setup with an application
pool running under Local System (the only way I could figure out how to
run the VBS script without permission issues).

Does anyone have any suggestions?

[[MSFT]]

Hello,

If you execute the VBS file in a Command prompt window, will this error
also occur? If so, I suggest you may need to reinstall MDAC and Oracle
driver on this server.

Luke

[Tim Frawley]

I did get the error from the command prompt. For some reason I thought
I wouldn't.

The server is Windows 2003 SP1, I can't believe the MDAC would be out
of date so quickly.

I patched the Oracle Client yesterday and installed their latest ODBC
drivers: 10.01.00.4 and still had some issues last night with the
w3wp.exe process as well as this cscript error, both from ASP and
command prompt.

The exciting part is that I changed the connection string from:

objConn.Open "DSN=xxx;UID=xxx;PWD=xxx"

to

objConn.Open "Provider=OraOLEDB.Oracle;Data Source=xxx;" & _
"User ID=xxx;Password=xxx;"

and guess what, no error!

Looks like an ODBC issue to me. I will report this to Oracle. In the
meantime I have converted our entire Intranet and Public site from ODBC
to OraOLEDB. I am keeping my fingers crossed and will post success or
failure on Monday.

Thanks for your help Luke!

Tim Frawley

Tim

[[MSFT]]

Hello Tim,

Thank you for the update. I am very glad the problem was resolved!

Regards,

Luke