[ABAP: ACTIVE, Java: UNKNOWN] did not reach state STARTING after 20:10 minutes. Giving up.)

[Former Member]

I am installing a secondary application server for a SAP PI 7.1 system, but the installation is stuck on phase 10 of 10 (Start Dialog instance) with the error:

[ABAP: ACTIVE, Java: UNKNOWN] did not reach state STARTING after 20:10 minutes. Giving up.)

This is strange because the MMC shows that everything is running, I can see the system in transaction SM51 (and I can log onto it and run transactions), plus I can access the Java system on http://myserver:50000/

Running this:

C:\>sapcontrol -nr 00 -function GetProcessList

Returns this:

26.04.2012 16:33:27

GetProcessList

OK

name, description, dispstatus, textstatus, starttime, elapsedtime, pid

disp+work.EXE, Dispatcher, GREEN, Running, Message Server connection ok, Dialog

Queue time: 0.00 sec, AS Java: All processes running, 2012 04 26 16:12:28, 0:20:

59, 204

igswd.EXE, IGS Watchdog, GREEN, Running, 2012 04 26 16:12:28, 0:20:59, 4972

which indicates that everything is okay and started correctly.

Please can you tell me why the installation cannot see that the JAVA stack is started?

Thanks.

[DavidLY · Accepted solution]

Hello,

As a workaround, you can stop sapinst and restart it with SAPINST_SKIP_ERRORSTEP=TRUE.

Check if this workaround could help to finish the installation action or not.

Regards,

David

[Former Member · Accepted solution]

Hi David,

Your workaround would probably have worked, but I went with this reply from SAP OSS which is similar:

instance 00 seems to be up and running.

We can also see that from the output of sapcontrol. However, for some
reason, sapinst is not being able to interpret that output. In this caseplease, do the following:

1. Stop sapinst
2. Make a backup of the file keydb.xml from the installation directory
3. Edit the keydb.xml file and search for 'CDATA[ERROR]'
4. Replace it for 'CDATA[OK]'
5. Repeat the installation choosing 'continue with old option'

Please, note the workaround above must never be used unless advised by
SAP Support, as it is not supported, otherwise.

I did this and it resolved/bypassed the issue.

Thanks.