Skip to Content
0
Former Member
Jan 07, 2008 at 03:03 PM

INSTALLING SOLUTION MANAGER 4.0 (sr3/windows 32bits and oracle)

48 Views

Hello!:

Now we are installing a new Solution Manager 4.0 SR3, and executing

sapints in phase 35 of 44 (Start java engine) appears the next error:

"Java process dispatcher of instance SMG/DVEBMGS00 [ABAP: ACTIVE, Java:

(dispatcher: UNKNOWN, server0: RUNNING) did not start......"

In the file "sapinst.log" we can see:

INFO 2008-01-02 16:48:18.156

State of instance SMG/DVEBMGS00 changed from ABAP: ACTIVE, Java:

(dispatcher: STARTING, server0: STARTING_APPS) to ABAP: ACTIVE, Java:

(dispatcher: STARTING, server0: STARTING_APPS).

ERROR 2008-01-02 16:48:18.187

CJS-30153 Java process dispatcher of instance SMG/DVEBMGS00 reached

state UNKNOWN after having state STARTING. Giving up.

ERROR 2008-01-02 16:48:18.187

FCO-00011 The step startJava with step key

|NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_CI_Instance_StartJava|ind|ind|ind|ind|5|0|startJava was executed with status ERROR .

So, I've tried two options to solve the problem:

option 1) S:\usr\sap\SMG\DVEBMGS00\exe>

jcmon p pf="S:\usr\sap\SMG\SYS\profile\DEFAULT.PFL"

select 20 and stop/start

option2 ) login to ABAP layer (if you can), TCODE SMICM, from the

adminitration menu, stop and restart java..

The problem continue in PHASE 35 of START JAVA ENGINE, ABAP active, but

the JAVA has problems: SDM OK, server0 OK, but dispatcher STOPPED.

Our SERVER is a Intel, the installation i386, so we have used the next

java exe:

j2re-1_4_2_16-windows-i586-p

j2sdk-1_4_2_16-windows-i586-p

Can you help us?.

Best regards,

BC Team.