jcontrol startup errors [semi-urgent]

[Former Member]

Hi,

New to the forum (and SAP) so hope i'm posting to the correct category. Evaluating the Netweaver preview and i am encountering problems with the jcontrol startup, specifically:

[Thr 4724] JsfCreateShm: ShmCreate(79, 4096, ATTACH) failed (rc = 3 SHM segment doesn't exist)...

[Thr 4724] INFO: Invalid property value [vm.ClassPath=./bootstrap/sap.com_tcbl_{offline_launcher}impl.jar:$[DIR_EXECUTABLE]/jstartupapi.jar:$[DIR_EXECUTABLE]/jstartupimpl.jar]

[Thr 4724] INFO: Invalid property value [homeDir=$[jstartup/DIR_CLUSTER]]

[Thr 4724] INFO: Invalid property value [runLevel=1]

[Thr 4724] [Node: Deploy_offline] java home is set by profile parameter

[Thr 4724] Java Home: C:\SAP
JP1\SYS\exe\run\sapjvm_5

[Thr 4724] [Node: Deploy_offline] java vm type is set by profile parameter

[Thr 4724] Java VM Type: server

and then just before exit:

[Thr 4724] Sun Sep 24 12:00:00 2006

[Thr 4724] JControlMSConnect: attached to message server (laredo-zafinlabs/3601)

[Thr 4724] *** ERROR => can't retrieve client list (rc=24) [jcntrms.c 749]

[Thr 4724] JControlCloseProgram: started (exitcode = 24)

[Thr 4724] JControlCloseProgram: good bye... (exitcode = 24)

An explanation would be very helpful.

Thanks,

Jeff Larstone

[Former Member]

Hi Jeff/Varda

The problem is that JC cannot connect to SCS MS.

Explanation of your problem:

1) communictation with the message server

- it sends asynchronously requests to the message server and doesn't

wait synchronously for the answers.

- Laterly it wait for ms response. But now it might get the answer of

any previous request

2) There seems to be request (change ip address ..) with an ms

ip address which is not valid on the host the message server runs on.

Therefore this request cannot be performed successfully.

Alternative Solution :disable the Microsoft Loopback Adapter

Pls award suitable points:

Message was edited by:

Rajat Anand

[vincentlim826]

Maybe a misconfiguration in the network name.

the Message Server seems cannot resolve the host name of the instance host.

Check the name resolution of the instance host name on the machine where the Message Server runs.

Hope this helps.

[Former Member]

I had the same problem, and Vincent's suggestion was spot on... too bad I cannot award him points.

Cheers

G