The instruction at xxxxxxx referenced memory at yyyyyyy
The memory could not be read.

OK to terminate
CANCEL to Debug

Any pointers on what I should be looking for to resolve this shared memory issue. ???

What's the application - most likely a dodgy version of a DLL in memory.

It's a VB app. pulls data from essbase cubes and exports to flat files.

Is there a utility for checking the status of dll files or is it a case of checking properties of each file individually ??

Jods,

Well all you can get from a DLL are imported and exported functions, they do have addresses but I *think* these are just offsets from wherever the DLL gets loaded into memory. Is this an automation server dll? If its is perhaps you use something else (word/excel) as an automation controller. Can you generate memory maps from VB? If so you could then see what modules were loaded at what addresses, your best bet is to check out www.turbopower.com and look for memory sleuth, Im sure theres a VB version.

good luck!

Gary