JSPM throws error on start

[bhaskar_ghandikota]

I have to apply SP11 for my PI7 instance on Windows Oracle.

I applied the Kernel and ABAP patces using SPAM.

Now to apply the Java patches, I started JSPM and it throws error :

SID................: PI7

Hostname...........: skzw26x

Install directory..: E:/usr/sap/PI7

Database...........: Oracle

Operating System...: $(/J2EE/StandardSystem/CentralInstance/J2EEEngineInstanceHost/OpSysType)

JDK version........: 1.4.2_15 Sun Microsystems Inc.

JSPM version.......: 7.00.9.2.1.4.35

System release.....: 700

ABAP stack present.: true

The execution ended in error.

Cannot initialize application data.

Could not extract value with key SAPSYSTEM from file E:/usr/sap/PI7/SYS/profile/PI7_DVEBMGS10_skzw26x. A possible reason could be that the path to the directory containing the sappfpar executable is not included in the PATH environment variable.

Could not start process sappfpar.

Error while executing process sappfpar.

java.io.IOException: CreateProcess: sappfpar pf=E:/usr/sap/PI7/SYS/profile/PI7_DVEBMGS10_skzw26x SAPSYSTEM error=2

More information can be found in the log file E:\usr\sap\PI7\DVEBMGS10\j2ee\JSPM\log\log_2007_10_12_11_58_40\JSPM_MAIN_1_01.LOG.

Use the information provided to trouble-shoot the problem. There might be an OSS note providing a solution to this problem. Search for OSS notes with the following search terms:

com.sap.sdt.jspm.phases.PhaseTypeJSPM

com.sap.sdt.jspm.gui.JspmUiException

Cannot initialize application data.

JSPM_MAIN

JSPMPhases

NetWeaver Upgrade

SAPJup

Java Upgrade

Please advise.

I followed several threads here but the issue still exist.

Thanks and regards,

Bhaskar

[Former Member · Accepted solution]

Did you check this?

<i>A possible reason could be that the path to the directory containing the sappfpar executable is not included in the PATH environment variable.</i>

[bhaskar_ghandikota · Accepted solution]

Barry,

You are the man. I ignroed this error as I was reading thorigh the big log file that came out of it.

The error is gone.

Thanks,

Bhaskar