cancel
Showing results for 
Search instead for 
Did you mean: 

During installation of solution manager 4.0 java engine is not active

0 Kudos

Dear all,

i am installing sap solution manager 4.0 on windowns 2003 server with 3 Gm RAM and used java j2re-1_4_2_13

during the installation "START JAVA ENGINE" phase error occure

ERROR 2008-04-22 14:42:38.218

CJS-30150 Java processes of instance SOL/DVEBMGS00 [ABAP: ACTIVE, Java: UNKNOWN] did not reach state PARTRUNNING after 20:00 minutes. Giving up.

and sapmmc shows Dispatcher yallow and Runnig, message server connection OK,Dialog Queue time 0:00 sec,j2ee status infounavailable.

and developer trace

DpSysAdmExtInit: ABAP is active

DpSysAdmExtInit: VMC (JAVA VM in WP) is not active

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

anyone have sollution for this problem?

I have the same one, and have no sollution for it.

Thanks,

Dren

markus_doehr2
Active Contributor
0 Kudos

> DpSysAdmExtInit: ABAP is active

> DpSysAdmExtInit: VMC (JAVA VM in WP) is not active

This is VMC (VM Container) as does not relate to the J2EE engine.

check the traces

dev_bootstrap

dev_server0

std_server0.out

Markus

Former Member
0 Kudos

Hi markus

I am also facing similar kind of problem in MSCS enviorment while performing dialog installtion

for system copy(last step in Installation of SAP in mscs mode) .

Below is the enviorment:

Homogenous system copy (SAP PI 7.0) from win 2003 32 bit x64 (standalone with MSSQL 2000) to win

2003 64 bit x64 (MSCS with MSSQL 2005)

Source system export completed

MSCS installtion done (by OS team)

MSSQL 2005 software successfully clustered with failover

ASCS installtion successfully done (instnace number 11)

SCS installtion successfully done (instnace number 61)

Configure first MSCS node installtion successfully done

Install Database Instance successfully done

Configure additional MSCS Node successfully done

Installed Enque replication server on both nodes (instnace number 21)

Installed Central instance on first MSCS node (instnace number 01)

Installing DI-Dialog Instance on add. MSCS node (error in the last step "start dialog instance")

Problem 1

The dialog instance doesnt started shows status ABAP active, J2EE status unknown (elapsed time

21:30) giving up.

When i check the SAPMMC, the dispatcher of Dialog instance is showing yellow J2EE status info

unavailable....

Problem 2

For troubleshooting the above problem, i tried looging into the ABAP instance.... but the SAP

instance doesnt connects through the virtual groups. It successfully connects throught the

physical hostname of the server.... which is wrong. in MSCS enviorment end users will connect to

the SAP instance via the virtual name (ASCS instance number).

I am able to successfully telnet to that ASCS virtual hostname port 3611 & 3911 but cant connect through SAPGUI

Waiting for ur reply asap.

former_member190272
Active Contributor
0 Kudos

Hi,

Try java version 09 ( j2sdk-1_4_2_09-windows)

Thanks

Pankaj Kalsayan