cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Shared memory error with jcmon

Former Member
0 Likes
4,613

When I attempt to launch jcmon.bat and access local administration, I get the following error:

ERROR => Can't attach to administration shared memory (rc=3) [jcmonxx.c 219]

Any ideas? I'm pretty sure that server0 is not running, but since I can't log into the Visual Administrator or jcmon I don't know for sure.

Thanks in advance!

View Entire Topic
Former Member
0 Likes

Hi Justin,

Can you post the dev_jcontrol log file for more details about the error.

Regards,

Siddhesh

Former Member
0 Likes

Justin and all,

I got this problem of mine resolved resolved working with a colleague and we have been at it for 3 days now.

do the below and the problem will dissapear

What we did was

1) We de-installed the JDK 1.4.2_10 and reinstalled 1.4.2_11. If you are installing on windows 32 bit, you need JDK 1.4.2_11

2) Check via java - version that the java version for JDK 1.4.2_11 is being used

If not edit your 'path' system environment variable. Also change the vm home parameter found in the ABAP instance profile and give it the correct path

3) If you already have the right JDK, then the most important step is next.

When you can see sapinst retrying saying trying to start j2ee, then it reports 'stopping', then again trying to start. When this is happening, go to your MMC and just stop the SCS (Central services Instance) and start it back up. DO NOT STOP the abap instance, only stop the SCS and start the SCS immediately. In our case when we did this, immediately to our delight we saw the sapinst progressed and the J2EE engine started and went on the post steps and finally the 'successful insallation' scree, Phew !!!. I guess the sapinst requires the SCS services to be down momentarily when the it tries to bring up the the J2EE engine (java server process).

regards, Vikram