Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

JSPM_MAIN error upgrading from 700 sp17 to EHP1 sp04

Hello experts,

I am an EP consultant, this problem have been encountered by our BASIS team, can you just tell me what may be the problem, as some of them are saying its related to some NWDI locking ??

these are the screenshots of the errors....

http://rapidshare.com/files/299558537/basis.7z(can be opened by any zip program)

if you cant download, I will try to explain.

We are trying to upgrade from 700 sp17 to EHP1sp04, in the "check queue" screen we get error as

An error has occurred in the execution of JSPM_MAIN phase.

Here is the log file: http://rapidshare.com/files/299561607/JSPM_MAIN_1_01.LOG

Oct 27, 2009 8:53:37 AM [Error]: com.sap.sdm.util.sduread.IllFormattedSduFileException: The information about the development component found in the manifest is either missing or incomplete!

Manifest attributes are missing or have badly formatted value:

attribute keylocation is missing

attribute keyname is missing

attribute keyvendor is missing

attribute keycounter is missing

(/usr/sap/trans/EPS/in/CSR0120031469_0036994.ATT)

Oct 27, 2009 8:53:37 AM [Error]: File /usr/sap/trans/EPS/in/CSR0120031469_0036994.ATT is not a valid SDA or SCA file.

Oct 27, 2009 8:53:37 AM [Warning]: File /usr/sap/trans/EPS/in/CSR0120031469_0036994.ATT is not a valid SDA or SCA file.

Oct 27, 2009 8:53:37 AM [Error]: com.sap.sdm.util.sduread.IllFormattedSduFileException: The information about the development component found in the manifest is either missing or incomplete!

Manifest attributes are missing or have badly formatted value:

attribute keylocation is missing

attribute keyname is missing

attribute keyvendor is missing

attribute keycounter is missing

(/usr/sap/trans/EPS/in/CSR0120031469_0036994.PAT)

Oct 27, 2009 8:53:37 AM [Error]: File /usr/sap/trans/EPS/in/CSR0120031469_0036994.PAT is not a valid SDA or SCA file.

Oct 27, 2009 8:53:37 AM [Warning]: File /usr/sap/trans/EPS/in/CSR0120031469_0036994.PAT is not a valid SDA or SCA file.

Oct 27, 2009 8:53:37 AM [Error]: com.sap.sdm.util.sduread.IllFormattedSduFileException: The information about the development component found in the manifest is either missing or incomplete!

Manifest attributes are missing or have badly formatted value:

attribute keylocation is missing

attribute keyname is missing

attribute keyvendor is missing

attribute keycounter is missing

(/usr/sap/trans/EPS/in/CSN0120061532_0034496.ATT)

Oct 27, 2009 8:53:37 AM [Error]: File /usr/sap/trans/EPS/in/CSN0120061532_0034496.ATT is not a valid SDA or SCA file.

Oct 27, 2009 8:53:37 AM [Warning]: File /usr/sap/trans/EPS/in/CSN0120061532_0034496.ATT is not a valid SDA or SCA file.

Oct 27, 2009 8:53:37 AM [Error]: com.sap.sdm.util.sduread.IllFormattedSduFileException: The information about the development component found in the manifest is either missing or incomplete!

Manifest attributes are missing or have badly formatted value:

attribute keylocation is missing

attribute keyname is missing

attribute keyvendor is missing

attribute keycounter is missing

(/usr/sap/trans/EPS/in/CSN0120061532_0034496.PAT)

Oct 27, 2009 8:53:37 AM [Error]: File /usr/sap/trans/EPS/in/CSN0120061532_0034496.PAT is not a valid SDA or SCA file.

Oct 27, 2009 8:53:37 AM [Warning]: File /usr/sap/trans/EPS/in/CSN0120061532_0034496.PAT is not a valid SDA or SCA file.

Oct 27, 2009 8:53:37 AM [Error]: com.sap.sdm.util.sduread.IllFormattedSduFileException: The information about the development component found in the manifest is either missing or incomplete!

Manifest attributes are missing or have badly formatted value:

attribute keylocation is missing

attribute keyname is missing

attribute keyvendor is missing

attribute keycounter is missing

(/usr/sap/trans/EPS/in/CSN0120061532_0034436.ATT)

Oct 27, 2009 8:53:37 AM [Error]: File /usr/sap/trans/EPS/in/CSN0120061532_0034436.ATT is not a valid SDA or SCA file.

Oct 27, 2009 8:53:37 AM [Warning]: File /usr/sap/trans/EPS/in/CSN0120061532_0034436.ATT is not a valid SDA or SCA file.

Oct 27, 2009 8:53:37 AM [Error]: com.sap.sdm.util.sduread.IllFormattedSduFileException: The information about the development component found in the manifest is either missing or incomplete!

Manifest attributes are missing or have badly formatted value:

attribute keylocation is missing

attribute keyname is missing

attribute keyvendor is missing

attribute keycounter is missing

(/usr/sap/trans/EPS/in/CSN0120061532_0034436.PAT)

-


i have to delete many lines which were NOT error due to restriction of words----


Oct 27, 2009 8:53:40 AM [Warning]: No deployed component found with name SAPPCUI_GP and vendor sap.com.

Oct 27, 2009 8:54:40 AM [Error]: You are trying to update software component sap.com/SAP_ESS from release 603 SP level 4.12 and provider SAP AG to release 600 SP level 11.0 and provider ZIP.

This update is not possible since the target SP level is older than the source SP level.

Therefore the target SP level does not provide all error corrections which are already contained in the source SP level.

As a result, there is danger that after the update you will experience errors which have already been corrected in the source release.

Include the newest support package stack of the target release into your update.

Oct 27, 2009 8:54:40 AM [Info]: Validation message for component SAP_ESS : You are trying to update software component sap.com/SAP_ESS from release 603 SP level 4.12 and provider SAP AG to release 600 SP level 11.0 and provider ZIP.

This update is not possible since the target SP level is older than the source SP level.

Therefore the target SP level does not provide all error corrections which are already contained in the source SP level.

As a result, there is danger that after the update you will experience errors which have already been corrected in the source release.

Include the newest support package stack of the target release into your update..

Oct 27, 2009 8:54:40 AM [Info]: Validation message for component SAPPCUI_GP : Archive /usr/sap/trans/EPS/in/SAPPCUIGP04_1-20002356.SCA has been admitted for deployment..

Oct 27, 2009 8:54:40 AM [Info]: File /usr/sap/EPD/JC00/j2ee/JSPM/config/templates/AppSnapshotExport.xml has been copied to /usr/sap/EPD/JC00/j2ee/JSPM/tmp/AppSnapshotExport.xml.

Oct 27, 2009 8:54:40 AM [Info]: Java process ID 4, name com.sap.engine.offline.OfflineToolStart has been started.

Oct 27, 2009 8:54:40 AM [Info]: Command line: /usr/java14_64/jre/bin/java -cp /usr/sap/EPD/JC00/j2ee/configtool/lib/launcher.jar com.sap.engine.offline.OfflineToolStart com.sap.engine.configtool.batch.BatchConfig /usr/sap/EPD/JC00/j2ee/configtool/lib /usr/sap/EPD/JC00/j2ee/JSPM/tmp/AppSnapshotExport.xml

Oct 27, 2009 9:03:39 AM [Info]: Standard out: /usr/sap/EPD/JC00/j2ee/JSPM/log/log_2009_10_27_08_51_20/JCMON_START_00_01.OUT

Oct 27, 2009 9:03:39 AM [Info]: Process ID 20 has been started.

Oct 27, 2009 9:03:39 AM [Info]: Waiting for process ID 20, name jcmon to finish.

Oct 27, 2009 9:03:40 AM [Info]: Process ID 20, name jcmon has been finished, exit code 0.

Oct 27, 2009 9:03:40 AM [Info]: Generated log file position: 4.

Oct 27, 2009 9:03:40 AM [Info]: Appending the content of the file JCMON_START_00_01.OUT to file JCMON_START_00.OUT.

Oct 27, 2009 9:03:40 AM [Info]: Deleting file JCMON_START_00_01.OUT.

Oct 27, 2009 9:03:40 AM [Info]: Generated log file position: 4.

Oct 27, 2009 9:03:40 AM [Info]: Appending the content of the file JCMON_START_00_01.ERR to file JCMON_START_00.ERR.

Oct 27, 2009 9:03:40 AM [Info]: Deleting file JCMON_START_00_01.ERR.

Oct 27, 2009 9:03:40 AM [Info]: System 01 is running.

Oct 27, 2009 9:03:40 AM [Info]: Ping the SDM server.

Oct 27, 2009 9:03:40 AM [Info]: You can find additional information in log file /usr/sap/EPD/JC00/j2ee/JSPM/log/log_2009_10_27_08_51_20/SDM_OPERATION_08.LOG.

Oct 27, 2009 9:03:41 AM [Info]: Starting Finish dialog...

Oct 27, 2009 9:04:13 AM [Info]: Dialog Finish: you have chosen to close JSPM.

Oct 27, 2009 9:04:13 AM [Info]: Finish dialog has been processed.

Oct 27, 2009 9:04:13 AM [Info]: Adding system configuration.

Oct 27, 2009 9:04:13 AM [Info]: Generating phase and total run times.

Oct 27, 2009 9:04:13 AM [Info]: Adding version information.

Oct 27, 2009 9:04:13 AM [Info]: Adding phase run times.

Oct 27, 2009 9:04:13 AM [Info]: Adding deploy run times.

Oct 27, 2009 9:04:13 AM [Info]: Phase JSPM/JSPMPhases/JSPM_MAIN has been completed.

Oct 27, 2009 9:04:13 AM [Info]: Start time: 2009/10/27 08:51:43.

Oct 27, 2009 9:04:13 AM [Info]: End time: 2009/10/27 09:04:13.

Oct 27, 2009 9:04:13 AM [Info]: Duration: 0:12:30.009.

Oct 27, 2009 9:04:13 AM [Info]: Phase status is initial.

In the second screen in the above attachment it says.

you are trying to update software component sap.com/SAP_ESS from release 603 SP Level 4.12 and provider SAP AG to release 600 SP Level 11.0 and provider ZIP. This update is not possible since the target SP is older than the source SP level..........

But, our basis team is sure that the version they are upgrading to is higher then the already applied version. as you may see in the second screenshot which i have pasted in attachment.

Can someone please help, what is happening over here ???

regards,

Rajat

Former Member
Not what you were looking for? View more on this topic or Ask a question