disp+work.exe. Memory could not be read

[Former Member]

Hello SAP Experts!!!

We are trying to install SAP PI component. We are encountering an error at instace start up stage, which is popping up with a window that says :

disp+work.exe:

The instruction at "0x0043f3a9" referenced memory at "0x0000003c". The memory could not be read.

Click ok to terminate the program.

Click Cancel to debug the program.

Please i invite and wait for your valuable inputs.

thanks & Regards

Vanitha

Edited by: Vanitha badampudi on Feb 26, 2009 11:32 AM

[Former Member]

As i said before, try replacing the dispwork.exe file under the Kernel directory with the other one having the same Kernel level or you can try replacing the whole Kernel. Not sure but seems like dispwork.exe is corrupt

Thanks,

Varun

[Former Member]

Hi all,

The Java Instance is not being created in MMC. We are using 1 GB RAM. We know the performance will be too slow after installation. But it is not allowing us to complete the installation. Is this because of the RAM?

Thanks & Regards

Vanitha

[Former Member]

Hi all,

thank you for your inputs. We are going ahead with new installation.

thanks & Regards

Vanitha

[markus_doehr2]

Just to add:

1 GB is WAY WAY too few memory for the system. Keep in mind that the Java heap needs to be kept in real memory.

Markus

[Former Member]

Instruction cannot be read errors can be caused by bad memory, faulty CPU, bad drivers and even hardware conflicts. So it could not be necessarily SAP that is faulty. And as the workprocess log files are not even getting generated so I believe dispwork is not getting started and and not able to comunicate with the message server. May be you can find something relevant in the event viewer application and system logs. Also you can try replacing the dispwork.exe file under the Kernel directory with the other one in the same Kernel level.

Thanks,

Varun

[markus_doehr2]

> Instruction cannot be read errors can be caused by bad memory, faulty CPU, bad drivers and even hardware conflicts. So it could not be necessarily SAP that is faulty.

I agree - but that error messages can be a bit misleading.

If you develop software on Windows and you have pointer pointing to nowhere or trying to free() memory twice a likewise error will come.

Turn AV-software off, check, that your installed the R3DLLs as latest software package (yes, the DLL hell is still there) and configure Dr.Watson (Note 33772 - Correct configuration of Dr. Watson). Maybe the logfile can give more information about what's wrong.

Markus

[Former Member]

Hello,

Follwing is the error information from the event veiwer error log.

Faulting application disp+work.EXE, version 7000.75.13.373, faulting

module disp+work.EXE, version 7000.75.13.373, fault address 0x0003f3a9.

any suggestions please

Regards

Vanitha

[markus_doehr2]

> any suggestions please

There are already quite a few suggestions in this thread (kernel update, reinstallation of R3DLLINS etc.) - did you go through all those?

Markus

[markus_doehr2]

What OS are you using? Which kernel DVD?

Markus

[Former Member]

Hello Markus,

OS is Windows 2003 server and Kernel DVD, 51032266.

Please suggest .

thankyou

Vanitha

[Former Member]

Hello Markus,

OS is Windows 2003 server and Kernel DVD, 51032266.

Please suggest .

thankyou

Vanitha

[markus_doehr2]

Can't find this DVD...

Please post the developer trace (dev_w*) of the workprcess that was dying.

Markus

[Former Member]

hi markus,

In OS level, there are no dev_w* log files found.

Thanks

Vanitha

[markus_doehr2]

Without logfiles it's impossible to suggest something

I'd open an OSS call and let the support have a look on the system, everything else would just be "wild guess".

Markus

[former_member204746]

also check stderr* files.

I would also recommend a kernel upgrade and see if this helps.

[Former Member]

What is your virtual memory...

[Former Member]

Hello,

Virtual Memory is 4500.

Thank you

Vanitha