The memory could not be read

[pliva]

MSACCESS.EXE Application error

The instruction at "" referenced memory at"". The memory could not be read.

This message results when I try to run MS access runtime to access a MYSQL database. Dr Watson log file shows the following:

Application exception occurred:
App: (pid=180) This is MSACCESS.EXE
When: 1/3/2002 @ 12:49:25.997
Exception number: c0000005 (access violation)

function: CreateIExprSrvObj
3003f9cb 8b5c2410 mov ebx,[esp+0x10] ss:013be74f=????????
3003f9cf 83662000 and dword ptr [esi+0x20],0x0 ds:013be772=????????
3003f9d3 895e24 mov [esi+0x24],ebx ds:013be772=????????
3003f9d6 897e70 mov [esi+0x70],edi ds:013be772=????????
3003f9d9 a15ca43f30 mov eax,[303fa45c] ds:303fa45c=303fa468
3003f9de 80780401 cmp byte ptr [eax+0x4],0x1 ds:796beb3e=??
3003f9e2 7413 jz CreateIExprSrvObj+0x1361f (3003f9f7)
3003f9e4 85ff test edi,edi
3003f9e6 7430 jz CreateIExprSrvObj+0x13640 (3003fa18)
3003f9e8 8b07 mov eax,[edi] ds:30037400=78430138
FAULT ->3003f9ea 8b10 mov edx,[eax] ds:78430138=????????

My OS is NT4 workstation.
I've tried many fixes for this including MS security rollup, install new MDAC, reinstall office, reinstall msaccess runtime, reinstall MySQL drivers. This program runs fine on another NT4.0 PC, but not mine. I've read that similar "memory could not be read" errors require an OS reload. Please tell me this isn't true.

Thanks!

Phil

 

[Ed2020]

I'm afraid I don't have an answer to the problem but I can tell you it is definitely not an MS Access problem or an installation problem.

I have experienced the same thing and it is something to do with your OS. The problem *appears* to be completely random, not associated with any particular task. In fact I have had it when Access is open, no database is open, and MS Access isn't even the current application!

Do you use Novell as your client?

Ed Metcalfe.
ed_metcalfe@hotmail.com

 

[pliva]

Ed,

Thanks for response. We don't use Novell. The error is not random. It only happens with this one database, and happens every single time I try to open it. Microsoft's knowledgebase does not have many references to this error message (memory could not be read). It seems to be a flaw in the OS perhaps. Something they don't want to own up to.

Phil

 

[Ed2020]

Phil,

Yep. Definitely an OS problem. I've had NT4 network administrators looking into it for me and they are still none the wiser.

If I ever find an answer, I'll let you know.......

Ed.