Can't install Java ADD-IN for NTW04s

[Former Member]

We are installing the Java Add-in for an existent SAP BI (stack13) environment.

The installation fails because during the deploy of the EPBC09_2.SCA we recive this error:

"Error: An error occured while storing the cluster instances.

Error: There is no control instance running in the cluster returned by MessageServer [MS host: myhost ; MS port: 3901].

The instances are:

Name:JM_T1195569190860_1_myhost Host:myhost State:5 HostAddress:xxx.xxx.xxx.xxx

Please check if there are running cluster instances "

So the J2EE was down at that time.

But if we try to star it the MMC snap-in remains yellow and into the dev_disp we see the J2EE goes tfrom STARTING to SHUTDOWN .

No other logs (std_server.out, std_dispatcher.out, dev_jcontrol*,....) are present into the DVEBMGS00\work directory, so it's not very clear what's the error.

The platform in use is IA64, Win 2003. The JSDK installed is the 1.4.2_16 for IA64.

Any idea ?

Regards

[Former Member · Accepted solution]

Could you check the <b>j2ee_start</b> parameter to see if it's true(1)? After 3 attempts to start J2EE this parameter becomes false. Make sure it's true.

regards,

tamilboy

[Former Member · Accepted solution]

thanks for the feedback.

We applied note 741289 for the missing J2EE parameters and double checked the status of the parameters as for note 821875.

We are now at the latest step of module 'Installation CI instance' of the Java Add-in installation.

All the MMC is green and the J2EE is yet up and running.

We restart sapinst to terminate the installation.

It arrives to the latest step 'Prepare to install minimal configuration' and start to run the RFC_ABAP_INSTALL_AND_RUN. After a while we recive the msg 'done successfully !'

Into the MMC the J2EE become yellow and the J2EE process disappear (bu the item for the SCS instace remain green).

After that we recive the message :

'INSTANCE SID/DVEBMGS00 [JAVA UNKNOWN] did not stop after xx minutes. Givig up'.

And the sapinst aborted.

We try to stop-start the SCS instance after the termination of the RFC_ABAP_INSTALL_AND_RUN but the error continue to occurs.

What it's trying to do the sapinst ?

Can we skip this latest phase ?

Regards