JSPM phase error after JSPM SP update

[Former Member]

Good day

I am experiencing the following problem.

We want to upgrade JAVA SP5 to 7.

1st step in JSPM is to update JSPM itself (ver 7.01.5.2 to 7.01.7.0). This happened without problem, and I restarted JSPM as instructed.

Now, every time I start JSPM in order to load the remaining patches, it reports an error:

******************************************************************************

An error occurred during the execution of the JSPM_MAIN phase.

Cannot initialise application data. Could not determine if instance 53 on host solapp01 is running. Cannot find instance with instance number 53 on host solapp01 in the cluster.

******************************************************************************

The log file contains:

Sep 24, 2010 4:26:22 PM [Info]: Checking status of instance 53 on host solapp01...

Sep 24, 2010 4:26:22 PM [Error]: Exception has occurred during the execution of the phase.

Sep 24, 2010 4:26:22 PM [Error]: Cannot find instance with instance number 53 on host solapp01 in the cluster.

Sep 24, 2010 4:26:22 PM [Error]: Could not determine if instance 53 on host solapp01 is running.

Sep 24, 2010 4:26:22 PM [Error]: Cannot initialize application data.

Sep 24, 2010 4:26:22 PM [Info]: Phase JSPM/JSPMPhases/JSPM_MAIN has been completed.

Sep 24, 2010 4:26:22 PM [Info]: Start time: 2010/09/24 16:24:56.

Sep 24, 2010 4:26:22 PM [Info]: End time: 2010/09/24 16:26:22.

Sep 24, 2010 4:26:22 PM [Info]: Duration: 0:01:26.569.

Sep 24, 2010 4:26:22 PM [Info]: Phase status is error.

JSPM_MAIN_1_01.LOG: END

*******************************************************************************

The Java stack is up and running. System has been restarted just in case.

Any ideas would be welcomed.

Regards

Derik

[former_member198270 · Accepted solution]

Dear All,

Please follow this procedure tosolve this problem and revert back with your feedback.

Cannot initialise application data. Could not determine if instance 53 on host solapp01 is running. Cannot find instance with instance number 53 on host solapp01 in the cluster

Actually this is happening because you production box is configured in cluster environment and inside your profile directory

you have profiles(instance, default and startup) for cluster instance as well which is located at some other host and JSPM is searching but could not find.

1. All you have to do to solve this is goto > cdpro > list all the files

now carefully create one folder and move all the profiles related to DR server in that folder.

Again start the JSPM and that prompt will not come.

2. One more solution to this problem is apply patch using SDM.

Hoipe it helps.

Regards, Amber S

[former_member198270 · Accepted solution]

Dear Russell, As to why you are finding this problem only in Production server(and didnot faced in development and quality server) because clustering is configured only in Production system.

hope it helps.

Regards,

Amber S | ITL

[Former Member · Accepted solution]

Thanks Amber

This worked!

[Former Member · Accepted solution]

Hi,

Could anyone Please let me know how you figure out cdpro and make changes?

[Former Member · Accepted solution]

As recommended by SAP, you should always delete all the unwanted profiles from SYS\Profiles before doing any upgrade.

Regards,

Rajneesh

[Former Member · Accepted solution]

Hello,

which are the "unwanted" profiles? We have the same problem ( from SP09 to SP24).

In our profile-directory are the following profiles: CEB_JC18_r3ucespr; CEB_SCS58_r3ucespr; DEFAULT.PFL; START_JC18_r3ucespr; START_SCS58_r3ucespr

Kind regards

Frank

[Former Member · Accepted solution]

Hello,

are there any solutions to the last post from Frank?

I have the same problem, and I do not have any unwanted profiles...

DEFAULT.PFL DEP_JC00_dedrs198 DEP_SCS01_dedrs198 START_JC00_dedrs198 START_SCS01_dedrs198

Any suggestions?

regards

Alex

[Former Member]

Hi ,

As per suggestion is repeat JSPM updated again with same version ..

Hope this help you.

Regards,

[Former Member]

Only bad news from me - I have the same problem. I have applied JSPM 7.01 SP 7 patch 2 and it makes no difference.

Naturally, the development and test systems worked perfectly. This problem is only affecting the production system which (a) not a VM server, and (b) on a different network.

[Former Member]

Hi

Login to confg tool and see you have that instance number

also check in your instance profile what is the instance number it is pointing to

[dao_ha]

Hi Derik,

There's a patch for JSPM NW 7.01 SP07 (7.01.7.2). Please apply the patch and see if it fixes your problem.

Hope it helps.

Regards,

Dao