BI EHP1 ONLINE_DEPLOY JSPM Error

Hi Gurus,
We are in the process of upgrading our BI JAVA Production system (HA Cluster Mode) to EHP1 SPS 04 for NW 7. We have BI ABAP + DB running on hsap1 and BI JAVA running on hsap2 with common DB for BI ABAP and BI JAVA (MCOD Installation). We have failed over hsap1 onto hsap2, and started the EHP upgrade.
In the ONLINE_DEPLOY_DEPL phase we too are facing the problem where the JSPM is giving the following error.
Jul 13, 2009 12:46:29 AM [Info]: Checking status of instance 10 on host hsap1.
Jul 13, 2009 12:46:29 AM [Error]: Cannot find instance with instance number 10 o
n host hllsap1 in the cluster.
Jul 13, 2009 12:46:29 AM [Error]: Restarting JP1 10 instance failed.
Jul 13, 2009 12:46:29 AM [Error]: Cannot check the state(running/stoped) of the
CI.
We have manually modified the file Jspm.JSPM.DataModel.xml and Jspm.xml under /usr/sap/<SID>/<instance>/j2ee/JSPM/data/variables to adapt the current working host(hsap2). Still JSPM is not able to pick up the current working hostname(hsap2). Instead it is trying to check the status of the instance 10 on the other hostname (hsap1).
The upgrade has struck up because of this as we are unable to make JSPM to pick up hsap2.
Your suggestion is needed on this and your help is greatly appreciated.
Regards,
Venky.

Hi,
Yes the table space is full at this point. However after you add the space the SAPehpi process can't continue as the j2ee engine files are half deployed and at this stage the SAPEHpi tries to start the j2ee instance for an online deployment.
Possible bug that this tablespace doen't appear in the checks phase.
Have you experienced this?
Regards Dave

Similar Messages

JSPM Error while applying As Java Patch to PI 7.1

Dear All
I am facing an issue when trying to patch new Pi 7.1 Ehp1 Java patch through JSPM
steps i did
. since the download manger is not working for us i click on the link and down load all the patches to windows machine ( Installed machine is AIX)
all the patches were downloded in SCA.zip " LMNWATOOLS04_0-20003137.SCA.zip" format which is not recognizable through JSPM
i rename all the file taking off zip extension "LMNWATOOLS04_0-20003137.SCA" , but now the initiating is working but it throws an error saying to revise all the selected patches?
" Error occured, while reading refactoring configuration from SDU file /usr/sap/trans/EPS/in/ESREGBASIC04_0-20003135.SCA. java.io.IOException: java.io.IOException: "
how can i deploy these patches comes with SCA.zip format ? i know only SCA can be deployed , but since i have downloaded them directly it converted to SCA.zip
please advice me how to resoleve this urgently
appreciate your coperation with regard to this
Buddhike

> how can i deploy these patches comes with SCA.zip format ? i know only SCA can be deployed , but since i have downloaded them directly it converted to SCA.zip
It is fine just to delete the .zip at the end. The issue has another reason.
Have you patched the JSPM before you applied the patches?

JSPM: Error while detecting start profile for instance with ID _c.

Hi Experts,
we have an error when we start JSPM with message "cannot initialize application data. Error while detecting start profile for instance with ID _c." . Until now nothing has been updated yet. The system can be started up and shut down without any problem. The profiles are found in /usr/sap/PMA/SYS/profile
Our BI system is currently Netweaver 7.0 with SPS14. We plan to update it to SPS20. But when we start JSPM, we have abover error.
could somebody give a help? Thank you very much.
Rongfeng
P.S. the log file DETECT_SYSTEM_PARAMETERS_01.LOG:
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7185 - 630]/>
<!NAME[/usr/sap/PMA/DVEBMGS10/j2ee/JSPM/log/log_2009_11_18_10_28_50/DETECT_SYSTEM_PARAMETERS_01.LOG]/>
<!PATTERN[DETECT_SYSTEM_PARAMETERS_01.LOG]/>
<!FORMATTER[com.sap.tc.logging.ListFormatter]/>
<!ENCODING[UTF8]/>
<!LOGHEADER[END]/>
#1.5^H#C000995FC0200000000000207BD47BD40004789C01294DB0#1258511336558#/System/Server/Upgrade/JSPM##com.sap.sdt.jspm.gui.InitialParametersDetector.initializeJspmDataModel(InitialParametersDetector.java:397)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.InitialParametersDetector.initializeJspmDataModel(InitialParametersDetector.java:397)#Java###Initializing JSPM data model...##
#1.5^H#C000995FC0200000000000217BD47BD40004789C01295968#1258511336561#/System/Server/Upgrade/JSPM##com.sap.sdt.jspm.gui.InitialParametersDetector.detectProfileDirectory(InitialParametersDetector.java:1468)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.InitialParametersDetector.detectProfileDirectory(InitialParametersDetector.java:1468)#Java###Detected profile directory .#1#/usr/sap/PMA/SYS/profile#
#1.5^H#C000995FC0200000000000227BD47BD40004789C0141AFE0#1258511338156#/System/Server/Upgrade/JSPM##com.sap.sdt.jspm.gui.InitialParametersDetector.detectDb(InitialParametersDetector.java:936)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.InitialParametersDetector.detectDb(InitialParametersDetector.java:936)#Java###Detecting the parameters of the database...##
#1.5^H#C000995FC0200000000000237BD47BD40004789C014205D0#1258511338178#/System/Server/Upgrade/JSPM##com.sap.sdt.db.dmtif.AbstractDMTController.execute(AbstractDMTController.java:261)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.db.dmtif.AbstractDMTController.execute(AbstractDMTController.java:261)#Java###Executing command with arguments .#2#dbinfo#/usr/sap/PMA/DVEBMGS10/j2ee/JSPM/config/DBINFO.XML#
#1.5^H#C000995FC0200000000000247BD47BD40004789C01421570#1258511338182#/System/Server/Upgrade/JSPM##com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:41)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:41)#Java###Java process ID , name has been started.#2#5#com.sap.sdt.dmt.main.DMT#
#1.5^H#C000995FC0200000000000257BD47BD40004789C01421958#1258511338183#/System/Server/Upgrade/JSPM##com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:54)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:54)#Java###Command line: #2# #/opt/IBMJava2-amd64-142/jre/bin/java -cp .:/usr/sap/PMA/DVEBMGS10/j2ee/JSPM/lib/sdt_dmt.jar:/oracle/client/10x_64/instantclient/ojdbc14.jar:/usr/sap/PMA/DVEBMGS10/j2ee/JSPM/lib/jddi.jar:/usr/sap/PMA/DVEBMGS10/j2ee/JSPM/lib/opensqlsta.jar:/usr/sap/PMA/DVEBMGS10/j2ee/JSPM/lib/tc_sec_secstorefs.jar:/usr/sap/PMA/DVEBMGS10/j2ee/JSPM/lib/frame.jar:/usr/sap/PMA/DVEBMGS10/j2ee/JSPM/lib/exception.jar:/usr/sap/PMA/DVEBMGS10/j2ee/JSPM/lib/logging.jar:/usr/sap/PMA/DVEBMGS10/j2ee/JSPM/lib/jperflib.jar:/usr/sap/PMA/DVEBMGS10/j2ee/JSPM/lib/util.jar:/usr/sap/PMA/DVEBMGS10/j2ee/JSPM/./lib/tc_sec_secstorefs.jar:/usr/sap/PMA/DVEBMGS10/j2ee/JSPM/./lib/exception.jar:/usr/sap/PMA/DVEBMGS10/j2ee/JSPM/./lib/logging.jar:/usr/sap/PMA/DVEBMGS10/j2ee/JSPM/./lib/opensqlsta.jar:/sapmnt/PMA/global/security/lib/tools/info/IAIKSecurityFS.list:/sapmnt/PMA/global/security/lib/tools/iaik_jce.jar:/sapmnt/PMA/global/security/lib/tools/iaik_smime.jar:/sapmnt/PMA/global/security/lib/tools/iaik_jsse.jar:/sapmnt/PMA/global/security/lib/tools/w3c_http.jar:/sapmnt/PMA/global/security/lib/tools/iaik_ssl.jar:/sapmnt/PMA/global/security/lib/engine/info/IAIKSecurityFS.list:/sapmnt/PMA/global/security/lib/engine/iaik_jce.jar com.sap.sdt.dmt.main.DMT -rootdir=/usr/sap/PMA/DVEBMGS10/j2ee/JSPM -descriptor=csrt29_PMA -logfile=/usr/sap/PMA/DVEBMGS10/j2ee/JSPM/log/log_2009_11_18_10_28_50/DMT_01.LOG dbinfo /usr/sap/PMA/DVEBMGS10/j2ee/JSPM/config/DBINFO.XML#
#1.5^H#C000995FC0200000000000267BD47BD40004789C01422128#1258511338185#/System/Server/Upgrade/JSPM##com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:55)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:55)#Java###Standard out: #2# #/usr/sap/PMA/DVEBMGS10/j2ee/JSPM/log/log_2009_11_18_10_28_50/DMT_01_01.OUT#
#1.5^H#C000995FC0200000000000277BD47BD40004789C01424838#1258511338195#/System/Server/Upgrade/JSPM##com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:126)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:126)#Java###Process ID has been started.#1#5#
#1.5^H#C000995FC0200000000000287BD47BD40004789C014253F0#1258511338198#/System/Server/Upgrade/JSPM##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:182)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:182)#Java###Waiting for process ID , name to finish.#2#5#java#
#1.5^H#C000995FC0200000000000297BD47BD40004789C017402B0#1258511341454#/System/Server/Upgrade/JSPM##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:215)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:215)#Java###Process ID , name has been finished, exit code .#3#5#java#0#
#1.5^H#C000995FC02000000000002A7BD47BD40004789C01741638#1258511341459#/System/Server/Upgrade/JSPM##com.sap.sdt.db.dmtif.AbstractDMTController.execute(AbstractDMTController.java:273)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.db.dmtif.AbstractDMTController.execute(AbstractDMTController.java:273)#Java###Command has been executed.#1#dbinfo#
#1.5^H#C000995FC02000000000002B7BD47BD40004789C017421F0#1258511341462#/System/Server/Upgrade/JSPM##com.sap.sdt.jspm.gui.InitialParametersDetector.detectDb(InitialParametersDetector.java:984)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.InitialParametersDetector.detectDb(InitialParametersDetector.java:984)#Java###Detection of the parameters of the database has finished. Database type is , database name is and database version is .#3#ORA#Oracle#10.2.0.2.0#
#1.5^H#C000995FC02000000000002C7BD47BD40004789C01744CE8#1258511341473#/System/Server/Upgrade/JSPM##com.sap.sdt.j2ee.tools.sysinfo.AbstractInfoController.updateProfileVariable(AbstractInfoController.java:284)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j2ee.tools.sysinfo.AbstractInfoController.updateProfileVariable(AbstractInfoController.java:284)#Java###Parameter has been detected. Parameter value is .#2#/J2EE/StandardSystem/DefaultProfilePath#/usr/sap/PMA/SYS/profile/DEFAULT.PFL#
Sorry, I don't know how to format post
Edited by: Rongfeng Shi on Nov 18, 2009 4:20 AM

Hi Rongfeng,
There is not much information about the error in the log file you have pasted above.
Please repeat the issue and catch the log files once again.
Are you able to open SDM ?
Best Regards
Raghu

JSPM error while updating solution Manager

Hi All,
I am getting following error in JSPM while updating SP14 solution manager to SP17 .
Jan 10, 2010 1:03:35 AM [Info]: Dialog type InfoText with dialog name step displays dialog text <html>Could not obtain MBean server connection with host: hostname, p4Port: 50000 and username: J2EE_ADMIN.
com.sap.engine.services.jmx.exception.JmxConnectorException: Unable to connect to connector server.
com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is com.sap.engine.interface
s.cross.DestinationException: cannot establish connection with any of the available instances
        Nested exceptions are:
        com.sap.engine.services.rmi_p4.P4IOException: Cannot open connection on host: x.x.x.x and port: 50000
com.sap.engine.interfaces.cross.DestinationException: cannot establish connection with any of the available instances
        Nested exceptions are:
        com.sap.engine.services.rmi_p4.P4IOException: Cannot open connection on host: x.x.x.x and port: 50000
Anyidea how I can fix it ?
Thanks,
Suman

Hi Suman,
Usually the p4port should be 5<xx>04 where xx is the instance number. But the error says p4port is 50000.
Login to Visual Admin and check the p4provider service under dispatcher node. If the port is 50000 then change it to 50004.
Then try again.
Cheers.....,
Raghu

JSPM Error with SAP-JEE component SP16

Hi
I am depolying a queue in JSPM SP16.1 for an ECC6 700 SR3 installed ABAP/Java system and it errors with the component SAP-JEE SP16 (installed level is SP14 as delivered in the SR3 kit)
The log has the messages:
Oct 8, 2008 1:49:57 PM Warning: Caught CVersProxyAccessException while saving repository: CVersAccessException: Cannot access CVers due to missing or incorrect configuration.
Additional error message is:
com.sap.sdm.apiint.serverext.servertype.TargetServiceException: Cannot provide connect data for database target system "CONFIG_DB".
Additional error message is:
com.sap.sdm.serverext.servertype.dbsc.DatabaseConnectException: Creation of DataSource for database "WFQ" failed. (com.sap.sql.log.OpenSQLException: Error while accessing secure store: Encryption or decryption is not possible because the full version of the SAP Java Crypto Toolkit was not found (iaik_jce.jar is required, iaik_jce_export.jar is not sufficient) or the JCE Jurisdiction Policy Files don't allow the use of the "PbeWithSHAAnd3_KeyTripleDES_CBC" algorithm..)
regards
Michael

Hi Philipp
My version is 700 and the database is DB2/400 for IBM System i.
The sapcrypto is treated differently on this platform, so I havent done anything with it as yet.
I logged a message with SAP which has gone to the BC-JAS-SEC queue and the reply I received is below. Please let me know if this has helped you as I have not had the chance to get back to the system to try these steps :
regards
Michael.
To do the further investigation, may I check info below with you:
- are you able to read the content of the
/sapbwtest/global/security/lib/tools/iaik_jce.jar file with jar
- do you have the full strength JCE files installed for this JDK?
See note: 739043
- What user is used to connect to the Database from the java side in
the secure store? check if the password is correct or the user
is unlocked.
Make sure the connection details in Secure Store are the correct ones
you can check it in the config tool:
the jdbc/pool/<SID>/Password and jdbc/pool/<SID>/User
Edited by: Michael Power on Oct 15, 2008 8:52 PM

32 bit EHp1 system export error on Oracle 10.2.0.2 & windows

Hi All,
I am performing export of solman EHp1 system base on Oracle 10.2.0.2 & windows 2003(32 bit) bot database & OS).
Database size is 100 gig.during export it stope at error.
I checked sapinst.log which shows below error
INFO[E] 2010-09-16 21:03:20.328
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) export_monitor.java.log, export_monitor.log.
ERROR 2010-09-16 21:03:20.343
FCO-00011 The step runMigrationMonitor with step key |NW_Export|ind|ind|ind|ind|0|0|NW_ABAP_Export_Dialog|ind|ind|ind|ind|4|0|NW_ABAP_Export|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR.
Then I checked export_monitor.java.log
java version "1.4.2_13"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_13-b06)
Java HotSpot(TM) Client VM (build 1.4.2_13-b06, mixed mode)
Export Monitor jobs: running 0, waiting 18, completed 1, failed 0, total 19.
Export Monitor jobs: running 1, waiting 17, completed 1, failed 0, total 19.
Export Monitor jobs: running 2, waiting 16, completed 1, failed 0, total 19.
Export Monitor jobs: running 3, waiting 15, completed 1, failed 0, total 19.
Export Monitor jobs: running 3, waiting 14, completed 2, failed 0, total 19.
Unloading of 'SAPAPPL1' export package: ERROR
Export Monitor jobs: running 2, waiting 14, completed 2, failed 1, total 19.
Then I again chked SAPAPPL1 log file
DbSl Trace: Error 1652 in stmt_fetch() from oci_execute_stmt(), orpc=0
DbSl Trace: ORA-1652 occurred when executing SQL stmt (parse error offset=538)
(EXP) ERROR: DbSlExeRead failed
rc = 99, table "ALALERTDB"
(SQL error 1652)
error message returned by DbSl:
ORA-01652: unable to extend temp segment by 128 in tablespace PSAPTEMP
(DB) INFO: disconnected from DB
E:\usr\sap\X11\SYS\exe\nuc\NTI386\R3load.exe: job finished with 1 error(s)
Regards
Sarth

Hi,
ORA-01652: unable to extend temp segment by 128 in tablespace PSAPTEMP
Try to extend the temp tablespace (PSAPTEMP) using BRTools and then continue the export process.
Hope this will resolve ur isse.
Regards,
Varadharajan M

JSPM ERROR- cannot add JAVA patches to deploy queue via JSPM

Hi Experts! Last two days I have deployed java patches(SP13 to SP18).......almost finished......i have to deploy 2 more components only but suddenly i got error.now i cannot add java patches to JSPM deployment queue. am getting error '/usr/sap/BWP/DVEBMGS10/j2ee/JSPM/log/log_2009_07_22_23_41_20/JSPM_MAIN_1_01.LOG.' I have checked trouble ticket log and i have followed Snote-1329945 and changed instace.properties files as instance.runmode=normal and just restarted java via SMICM only (server reboot is not possible in my environment)
Trouble Ticket Report----
Java Support Package Manager for SAP NetWeaver'04s
SID................: BWP
Hostname...........: abcbwp02
Install directory..: /usr/sap/BWP
Database...........: DB2/AIX64
Operating System...: $(/J2EE/StandardSystem/CentralInstance/J2EEEngineInstanceHost/OpSysType)
JDK version........: 1.4.2 IBM Corporation
JSPM version.......: 7.00.18.1.01
System release.....: 700
ABAP stack present.: true
The execution ended in error.
Cannot initialize application data.
Error while detecting start profile for instance with ID _s.
More information can be found in the log file /usr/sap/BWP/DVEBMGS10/j2ee/JSPM/log/log_2009_07_22_23_41_20/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/Java Support Package Manager
log_2009_07_22_23_41_20 exception:
#1.5 #C000C0A8D28F0000000000366BD46BD400046F4D35AF2008#1248277310677#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:795)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:795)#Java###Duration: .#1#0:00:10.915#
#1.5 #C000C0A8D28F0000000000376BD46BD400046F4D35AF2008#1248277310677#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:796)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:796)#Java###Phase status is .#1#error#
Thanks.

Hi,
ABAP stack present.: true
The execution ended in error.
Cannot initialize application data.
Error while detecting start profile for instance with ID _s.
Looks like the problem is above 1
Do the following. This should resolve the issues.
1. If your dialog instance are also having the Java stack then do one thing move your profile folder to some other name and create a new profile folder with the name "profile".
Copy only the central instance profiles Default, Instance and start profile.
Then give a try.
2. If you do not have the java instance in Dialog instance still do the same thing what I have described. move the current profile folder and create the new folder with the name "profile" and copy the profiles Default, Instance and start profile.
Chances are the JSPM is reading some other profile while starting the JSPM.
Regards,
Ravi

JSPM error when we are updating core-tools component.

Hi Gurus,
We are updating Service Pack on Java (GRC) System. In JSPM when we are updating core-tools component we are getting the below error message. Could any one let me know whats going wrong.
Let me know if you have any questions.
Jan 31, 2011 10:46:50... Info: Error handling strategy: OnErrorStop
Jan 31, 2011 10:46:50... Info: Prerequisite error handling strategy: OnPrerequisiteErrorSkipDepending
Jan 31, 2011 10:46:50... Info: Update strategy: UpdateLowerOrChangedVersions
Jan 31, 2011 10:46:50... Info: Starting deployment prerequisites:
Jan 31, 2011 10:46:50... Info: Loading selected archives...
Jan 31, 2011 10:46:50... Info: Loading archive '/usr/sap/trans/EPS/in/CORETOOLS07P_2-20002784.SCA'
Jan 31, 2011 10:46:53... Info: Selected archives successfully loaded.
Jan 31, 2011 10:46:54... Info: Actions per selected component:
Jan 31, 2011 10:46:54... Info: Update: Selected development component 'com.sap.engine.visualadmin'/'sap.com'/'SAP AG'/'7.0107.20100816112037.0000'/'0' updates currently deployed development component 'com.sap.engine.visualadmin'/'sap.com'/'SAP AG'/'7.0103.20081111105857.0000'/'0'.
Jan 31, 2011 10:46:54... Info: Update: Selected development component 'tc/template_config_tool'/'sap.com'/'SAP AG'/'7.0107.20100428095633.0000'/'0' updates currently deployed development component 'tc/template_config_tool'/'sap.com'/'SAP AG'/'7.0103.20081105084616.0000'/'0'.
Jan 31, 2011 10:46:54... Info: Update: Selected development component 'IAIKSecurityFS'/'sap.com'/'SAP AG'/'7.0106.20091119090313.0000'/'0' updates currently deployed development component 'IAIKSecurityFS'/'sap.com'/'SAP AG'/'7.0103.20081105085706.0000'/'0'.
Jan 31, 2011 10:46:54... Info: Update: Selected development component 'tc/sapinst/fs'/'sap.com'/'SAP AG'/'7.0107.20100817122315.0000'/'0' updates currently deployed development component 'tc/sapinst/fs'/'sap.com'/'SAP AG'/'7.0103.20081111152535.0000'/'0'.
Jan 31, 2011 10:46:54... Info: Update: Selected software component 'CORE-TOOLS'/'sap.com'/'SAP AG'/'1000.7.01.7.2.20100818104542''/'0' updates currently deployed software component 'CORE-TOOLS'/'sap.com'/'SAP AG'/'1000.7.01.3.0.20081208163400''/'0'.
Jan 31, 2011 10:46:54... Info: Update: Selected development component 'com.sap.engine.client'/'sap.com'/'SAP AG'/'7.0107.20100816112037.0000'/'0' updates currently deployed development component 'com.sap.engine.client'/'sap.com'/'SAP AG'/'7.0103.20081111105857.0000'/'0'.
Jan 31, 2011 10:46:54... Info: Update: Selected development component 'com.sap.engine.configtool'/'sap.com'/'SAP AG'/'7.0107.20100816112037.0000'/'0' updates currently deployed development component 'com.sap.engine.configtool'/'sap.com'/'SAP AG'/'7.0103.20081111105857.0000'/'0'.
Jan 31, 2011 10:46:54... Info: Update: Selected development component 'com.sap.engine.deploytool'/'sap.com'/'SAP AG'/'7.0107.20100816112037.0000'/'0' updates currently deployed development component 'com.sap.engine.deploytool'/'sap.com'/'SAP AG'/'7.0103.20081111105857.0000'/'0'.
Jan 31, 2011 10:46:54... Info: No action: Selected development component 'com.sapportals.supportplatformSDA'/'sap.com'/'SAP AG'/'7.0103.20081105090112.0000'/'1' will not be redeployed. Only the previous development component 'com.sapportals.supportplatformSDA'/'sap.com'/'SAP AG'/'7.0103.20081105090112.0000'/'0' will be updated in the SDM repository.
Jan 31, 2011 10:46:55... Info: Ending deployment prerequisites. All items are correct.
Jan 31, 2011 10:46:55... Info: Starting: Update: Selected development component 'IAIKSecurityFS'/'sap.com'/'SAP AG'/'7.0106.20091119090313.0000'/'0' updates currently deployed development component 'IAIKSecurityFS'/'sap.com'/'SAP AG'/'7.0103.20081105085706.0000'/'0'.
Jan 31, 2011 10:46:55... Info: ***** Begin of File-System Deployment IAIKSecurityFS *****
Jan 31, 2011 10:46:55... Info: Deploy Action is UPDATE
Jan 31, 2011 10:46:55... Info: Update - no information about previously deployed files available. Deploy new files only.
Jan 31, 2011 10:46:55... Info: Deploying Fileset SAP Java Cryptography Toolkit / SAPJavaCryptographyToolkit to /usr/sap/D19/SYS/global/security/lib
Jan 31, 2011 10:46:55... Error: Error: Could not extract file engine/info/IAIKSecurityFS.list from archive /usr/sap/D19/JC19/SDM/root/origin/sap.com/IAIKSecurityFS/SAP AG/0/7.0106.20091119090313.0000/tc_sec_java_crypto_fs_lib.sda
Jan 31, 2011 10:46:55... Error: Additional error message is:
Jan 31, 2011 10:46:55... Error: /usr/sap/D19/SYS/global/security/lib/engine/info/IAIKSecurityFS.list (Permission denied)
Jan 31, 2011 10:46:55... Error: Error deploying Fileset SAP Java Cryptography Toolkit to /usr/sap/D19/SYS/global/security/lib
Thanks,
Shankam

Hi Sowjanya,
I gave full access to the file but still no luck.
Here is the log error message:
Starting Deployment of CORE-TOOLS
Aborted: software component 'CORE-TOOLS'/'sap.com'/'SAP AG'/'1000.7.01.4.0.20090417021948''/'0':Failed deployment of SDAs:development component 'IAIKSecurityFS'/'sap.com'/'SAP AG'/'7.0104.20090220131743.0000'/'0' : abortedPlease, look at error logs above for more information!
Deployment of CORE-TOOLS finished with Error (Duration 1031 ms
Starting Deployment of CORE-TOOLS
Aborted: software component 'CORE-TOOLS'/'sap.com'/'SAP AG'/'1000.7.01.4.0.20090417021948''/'0':Failed deployment of SDAs:development component 'IAIKSecurityFS'/'sap.com'/'SAP AG'/'7.0104.20090220131743.0000'/'0' : abortedPlease, look at error logs above for more information!
Deployment of CORE-TOOLS finished with Error (Duration 1031 ms
Help plzzz..
Thanks,
Shankam

JSPM error with Patch application

Hi all,
i am getting Error when trying to apply patch on Prdouction server which is in cluster.
i am presently working on ECC 6.0 version using JSPM trying to update patch which gives me error
Error occured when execution of JSPM_MAIN phase
Configuration error of Secure store:Library directory k:/usr/sap/sys/global/security/lib/tools" does not exist . which when i checked the folder exist in the directory .
I would like to update that 2 week before we had aserver crash and system was restored with help of backups .can ther be any effect of Server crash .
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7185 - 630]/>
<!NAME[E:\usr\sap\E6P\DVEBMGS02\j2ee\JSPM\log\log_2008_08_21_07_37_09\JSPM_MAIN_1_01.LOG]/>
<!PATTERN[JSPM_MAIN_1_01.LOG]/>
<!FORMATTER[com.sap.tc.logging.ListFormatter]/>
<!ENCODING[Cp1252]/>
<!LOGHEADER[END]/>
#1.5#C0000A00001E00000000001645B9CE4B000454F0E01F8568#1219293435889#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:720)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:720)#Java###Phase has been started.#1#JSPM/JSPMPhases/JSPM_MAIN#
#1.5#C0000A00001E00000000001745B9CE4B000454F0E01F8568#1219293435889#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:721)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:721)#Java###Phase type is .#1#com.sap.sdt.jspm.phases.PhaseTypeJSPM#
#1.5#C0000A00001E00000000001845B9CE4B000454F0E0203918#1219293435935#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.jspm.gui.DialogController.showInitDialog(DialogController.java:547)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.DialogController.showInitDialog(DialogController.java:547)#Java###Starting Initialize dialog...##
#1.5#C0000A00001E00000000001E45B9CE4B000454F0E0225FE0#1219293436076#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.jspm.gui.SystemInitializer.initializeDataModelAndLogging(SystemInitializer.java:418)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.SystemInitializer.initializeDataModelAndLogging(SystemInitializer.java:418)#Java###Detecting system parameters...##
#1.5#C0000A00001E00000000001F45B9CE4B000454F0E0225FE0#1219293436076#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.jspm.trace.JspmExtLoggingManager.logReferenceToExtLog(JspmExtLoggingManager.java:167)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.trace.JspmExtLoggingManager.logReferenceToExtLog(JspmExtLoggingManager.java:167)#Java###You can find additional information in log file .#1#E:
usr
sap
E6P
DVEBMGS02
j2ee
JSPM
log
log_2008_08_21_07_37_09
DETECT_SYSTEM_PARAMETERS_01.LOG#
#1.5#C0000A00001E00000000002D45B9CE4B000454F0E03EFC18#1219293437951#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.jspm.gui.SystemInitializer.initializeDataModelAndLogging(SystemInitializer.java:439)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.SystemInitializer.initializeDataModelAndLogging(SystemInitializer.java:439)#Java###Detection of system parameters has finished.##
#1.5#C0000A00001E00000000002E45B9CE4B000454F0E03EFC18#1219293437951#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.jspm.gui.DialogController.execute(DialogController.java:459)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.DialogController.execute(DialogController.java:459)#Java###Initialize dialog has been processed.##
#1.5#C0000A00001E00000000002F45B9CE4B000454F0E03EFC18#1219293437951#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.jspm.gui.DialogController.loginDialog(DialogController.java:1031)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.DialogController.loginDialog(DialogController.java:1031)#Java###Starting dialog...#1#LogIn#
#1.5#C0000A00001E00000000003945B9CE4B000454F0E1DE4C68#1219293465169#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.jspm.gui.DialogController.loginDialog(DialogController.java:1036)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.DialogController.loginDialog(DialogController.java:1036)#Java###Dialog has been confirmed by the user.#1#LogIn#
#1.5#C0000A00001E00000000003A45B9CE4B000454F0E1DEC968#1219293465201#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl#Java###Checking connectivity for SDM server on host , port ...#2#aperpp1#50218#
#1.5#C0000A00001E00000000003B45B9CE4B000454F0E1E31310#1219293465482#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl#Java###Connection to SDM server on host , port is valid.#2#aperpp1#50218#
#1.5#C0000A00001E00000000003C45B9CE4B000454F0E1E6E3A0#1219293465732#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.jspm.deployedsdu.DeployedComponentsProvider.refresh(DeployedComponentsProvider.java:183)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.deployedsdu.DeployedComponentsProvider.refresh(DeployedComponentsProvider.java:183)#Java###Detecting components of the J2EE engine...##
#1.5#C0000A00001E00000000003D45B9CE4B000454F0E1E72220#1219293465748#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.jspm.trace.JspmExtLoggingManager.logReferenceToExtLog(JspmExtLoggingManager.java:167)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.trace.JspmExtLoggingManager.logReferenceToExtLog(JspmExtLoggingManager.java:167)#Java###You can find additional information in log file .#1#E:
usr
sap
E6P
DVEBMGS02
j2ee
JSPM
log
log_2008_08_21_07_37_09
DETECT_SYSTEM_COMPONENTS_01.LOG#
#1.5#C0000A00001E00000000004445B9CE4B000454F0E1FEB930#1219293467294#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:756)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:756)#Java###Exception has occurred during the execution of the phase.##
#1.5#C0000A00001E00000000004545B9CE4B000454F0E1FEB930#1219293467294#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:755)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:755)#Java###java.lang.IllegalStateException: Cannot access SecureStore.
Additional error message is:
com.sap.sdm.util.classloaders.SDMClassLoaderException: Cannot register class loader for SecureStore.
Additional error message is:
com.sap.sdm.util.classloaders.SDMClassLoaderException: Configuration error of SecureStore: Library directory "K:/usr/sap/E6P/SYS/global/security/lib/tools" does not exist.##
#1.5#C0000A00001E00000000004645B9CE4B000454F0E1FEB930#1219293467294#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:792)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:792)#Java###Phase has been completed.#1#JSPM/JSPMPhases/JSPM_MAIN#
#1.5#C0000A00001E00000000004745B9CE4B000454F0E1FEB930#1219293467294#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:793)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:793)#Java###Start time: .#1#2008/08/21 07:37:15#
#1.5#C0000A00001E00000000004845B9CE4B000454F0E1FEB930#1219293467294#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:794)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:794)#Java###End time: .#1#2008/08/21 07:37:47#
#1.5#C0000A00001E00000000004945B9CE4B000454F0E1FEB930#1219293467294#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:795)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:795)#Java###Duration: .#1#0:00:31.405#
#1.5#C0000A00001E00000000004A45B9CE4B000454F0E1FEB930#1219293467294#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:796)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:796)#Java###Phase status is .#1#aborted#
apreciate your help on this
regards
Roop

Hi Biswaroop
The main problem i see here is Cannot access SecureStore, maybe the path is not defined properly. Please check the JAVA_HOME variable or there is no authorization for SDIADM user to execute on this folder.
You can download the seculib for java , Copy the files "US_export_policy.jar" and "local_policy.jar" into the folder "$JAVA_HOME/jre/lib/security".
Please also check the Whether or not they can be accessed by sidadm user at OS level.
Regards
Kaleem

JSPM Error unable to update SP16

Hi all
this is the error i am getting when i start JSPM to update SP16
Please any help will be appreciated
The execution ended in error.
Cannot initialize application data.
Could not extract value with key SAPSYSTEM from file /usr/sap/NW1/SYS/profile/NW1_JC01_epsanbox. 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: java.io.IOException: sappfpar: not found
More information can be found in the log file /usr/sap/NW1/JC01/j2ee/JSPM/log/log_2008_12_30_17_26_31/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
thanks and regards
Melvin

This is the error i get when i start JSPM with SIDadm usr
Please check with this sir...
epsanbox:nw1adm 3> ./go
java version "1.4.2_12"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_12-b03)
Java HotSpot(TM) Client VM (build 1.4.2_12-b03, mixed mode)
12/31/08 5:49 PM com.sap.engine.tools.launcher.Launcher Error : console error stream will not be logged into a file; there was an error opening the log file
java.io.FileNotFoundException: /usr/sap/NW1/JC01/j2ee/admin/log/console_logs/error.log (Permission denied)
        at java.io.FileOutputStream.open(Native Method)
        at java.io.FileOutputStream.<init>(FileOutputStream.java:179)
        at java.io.FileOutputStream.<init>(FileOutputStream.java:131)
        at com.sap.engine.tools.launcher.Launcher.initLogs(Launcher.java:621)
        at com.sap.engine.tools.launcher.Launcher.init(Launcher.java:198)
        at com.sap.engine.tools.launcher.Launcher.main(Launcher.java:113)
12/31/08 5:49 PM com.sap.engine.tools.launcher.Launcher Error : console output stream will not be logged into a file; there was an error opening the log file
java.io.FileNotFoundException: /usr/sap/NW1/JC01/j2ee/admin/log/console_logs/output.log (Permission denied)
        at java.io.FileOutputStream.open(Native Method)
        at java.io.FileOutputStream.<init>(FileOutputStream.java:179)
        at java.io.FileOutputStream.<init>(FileOutputStream.java:131)
        at com.sap.engine.tools.launcher.Launcher.initLogs(Launcher.java:636)
        at com.sap.engine.tools.launcher.Launcher.init(Launcher.java:198)
        at com.sap.engine.tools.launcher.Launcher.main(Launcher.java:113)
12/31/08 5:49 PM com.sap.engine.tools.launcher.Launcher Error : unable to invoke main class com.sap.engine.services.adminadapter.gui.AdminFrameView
Exception in thread "main" com.sap.engine.tools.launcher.LauncherException
        at com.sap.engine.tools.launcher.Launcher.launch(Launcher.java:340)
        at com.sap.engine.tools.launcher.Launcher.main(Launcher.java:114)
caused by -
java.lang.reflect.InvocationTargetException
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:324)
        at com.sap.engine.tools.launcher.Launcher.launch(Launcher.java:336)
        at com.sap.engine.tools.launcher.Launcher.main(Launcher.java:114)
Caused by: java.lang.InternalError: Can't connect to X11 window server using ':0.0' as the value of the DISPLAY variable.
        at sun.awt.X11GraphicsEnvironment.initDisplay(Native Method)
        at sun.awt.X11GraphicsEnvironment.<clinit>(X11GraphicsEnvironment.java:134)
        at java.lang.Class.forName0(Native Method)
        at java.lang.Class.forName(Class.java:141)
        at java.awt.GraphicsEnvironment.getLocalGraphicsEnvironment(GraphicsEnvironment.java:62)
        at java.awt.Window.init(Window.java:231)
        at java.awt.Window.<init>(Window.java:275)
        at java.awt.Frame.<init>(Frame.java:401)
        at java.awt.Frame.<init>(Frame.java:366)
        at javax.swing.SwingUtilities$1.<init>(SwingUtilities.java:1641)
        at javax.swing.SwingUtilities.getSharedOwnerFrame(SwingUtilities.java:1637)
        at javax.swing.JWindow.<init>(JWindow.java:160)
        at javax.swing.JWindow.<init>(JWindow.java:112)
        at com.sap.engine.services.adminadapter.gui.AboutWindow.<init>(AboutWindow.java:12)
        at com.sap.engine.services.adminadapter.gui.AdminFrameView.main(AdminFrameView.java:234)
        ... 6 more
caused by -
java.lang.reflect.InvocationTargetException
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
        at java.lang.reflect.Method.invoke(Method.java:324)
        at com.sap.engine.tools.launcher.Launcher.launch(Launcher.java:336)
        at com.sap.engine.tools.launcher.Launcher.main(Launcher.java:114)
Caused by: java.lang.InternalError: Can't connect to X11 window server using ':0
        at sun.awt.X11GraphicsEnvironment.initDisplay(Native Method)
        at sun.awt.X11GraphicsEnvironment.<clinit>(X11GraphicsEnvironment.java:1
        at java.lang.Class.forName0(Native Method)
        at java.lang.Class.forName(Class.java:141)
        at java.awt.GraphicsEnvironment.getLocalGraphicsEnvironment(GraphicsEnvi
        at java.awt.Window.init(Window.java:231)
        at java.awt.Window.<init>(Window.java:275)
        at java.awt.Frame.<init>(Frame.java:401)
        at java.awt.Frame.<init>(Frame.java:366)
        at javax.swing.SwingUtilities$1.<init>(SwingUtilities.java:1641)
        at javax.swing.SwingUtilities.getSharedOwnerFrame(SwingUtilities.java:16
        at javax.swing.JWindow.<init>(JWindow.java:160)
        at javax.swing.JWindow.<init>(JWindow.java:112)
        at com.sap.engine.services.adminadapter.gui.AboutWindow.<init>(AboutWind
        at com.sap.engine.services.adminadapter.gui.AdminFrameView.main(AdminFra
        ... 6 more
epsanbox:nw1adm 4>

JSPM error in NW2004s SR1 installation

Hi,
I have just freshly installed NW2004s Application Server SR1. Then I tried to run JSPM to patch it up. When logging onto SDM as the first screen in JSPM, I got the following error:
The execution ended in error.
com.sap.sdt.util.diag.DevelopmentSupportRequiredException: Assertion failed for (Could not parse version string content. For input string: "${SP-Patchlevel}") at com.sap.sdt.util.diag.SDT.check(SDT.java:36).
More information can be found in the log file C:\usr\sap\JAV\JC01\j2ee\JSPM\log\log_20060727155309\JSPM_PROCESS_1_01.LOG.
When I looked at the JSPM_PROCESS_1_01.log, I found the followings at the bottom of the log:
#1.5#C000C0A801650000000000AE0037FB1E000419908952E9A0#1154008476740#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:796)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:796)#Java###Phase status is .#1#aborted#
I've already had my JAVA_HOME and PATH set already, and they both point to the same JDK (which is the only JDK I have in the machine). SDM doesn't seem to have problems as I can logon with the remoteGUI in SDM. Does anyone have any idea what's wrong or what I'm missing?
Thanks,
Marc

Hello Marc,
I ran into the same issue. After a lot of trial and error I eventuelly found out, was the problem was...
I had to do two things to resolve this:
1. Download the XML file containing the SP stack definition:
-You'll find the instructions for downloading this file on the Support Package Stacks Download Page for NW2004s in the box 'Additional information'.
-Put the XML file in the JSPM inbox (Folder '/usr/sap/trans/EPS/in' on a standard installation).
2. Update the SDM:
-Download the file with the description 'SP07 for SAP SOFTW. DELIV. MANAGER 7.00' from the Support Package Stacks Download Page
-SAP Note 860939 explains how to update the SDM
Hope this helps...
Regards,
Bjoern

JSPM Error

Dear All,
1. I am trying to patch enterprise portal 7 . I have downloaded the sp-stack and xml file . At the time of sp-statck I have choosen the target -
SAP NETWEAVER 7.0-19(06/2009 ) and in the source system---- 14(01/2008)
Q.1 - What is 14 (01/2008 ) ? I got this info from system information tab
Software Components all components...
Name Version Applied
sap.com/SAP-JEECOR 7.00 SP14 (1000.7.00.14.0.20071210172300) 20080125132852
sap.com/SAP-JEE 7.00 SP14 (1000.7.00.14.0.20071210172039) 20080125132853
Q2- Is this info is right for my system ?
2. In usage selection I have choosed 1. enterprise portal 2. ep core 3. application server java . Because I have choosed only these component at the time of installation of Enterprise portal 7 .
Q.3 - Am i right here ?
3. In second step of sp-stack I have selected only SAP IGS , SAP KERNEL 64Bit (os dependent , os independent) , TREX 7.0 , TREX 7.1
Q.4 -Is the TREX already installed with ep6 . Am I right here to choose TREX 7 and 7.0 ?
4. sp-stack 3rd step selected all the patches which came in to the box and added to download basket .
I have downloaded the save-as xml file .
Q.5 Am I right here ?
5. .when finishing the step 3 it was asking for - Total 21 no. of object added to download basket and available for download .Total no. of object added to approval list and require approval 21 .
We don't solution manger installed . I have not confirmed these patches with solution manger and download all 21 patches through download manager . Is it ok or confirmation is must ?
5. I have copied all the download patches adn xml file to EPS\in windows directory and started JSPM
Here i have selected support pack type - support pack stack
select support pack stack to apply - sap.com/SAP NETWEAVER 7.0
Error during validation of the dependencies of the selected support package stacks
some patch status is OK and
some patch status is REVISE
In show detail =
detailed message(s):-
archive
sapep1\sapmnt\trans\EPS\in\SAPJTECHF19_0-10003468.SCA not found in inbox directory
Pl. advice where I am wrong .
Thanks is advance .

Hi
Answers to your Questions
Also refer my [Blog|Applying SAP Netweaver 7 SP18] on this.
1. I am trying to patch enterprise portal 7 . I have downloaded the sp-stack and xml file . At the time of sp-statck I have choosen the target -
SAP NETWEAVER 7.0-19(06/2009 ) and in the source system---- 14(01/2008)
Q.1 - What is 14 (01/2008 ) ? I got this info from system information tab
14 (01/2008 ) Means SP14 and its relese date.
Software Components all components...
Name Version Applied
sap.com/SAP-JEECOR 7.00 SP14 (1000.7.00.14.0.20071210172300) 20080125132852
sap.com/SAP-JEE 7.00 SP14 (1000.7.00.14.0.20071210172039) 20080125132853
Q2- Is this info is right for my system ?
Yes
2. In usage selection I have choosed 1. enterprise portal 2. ep core 3. application server java . Because I have choosed only these component at the time of installation of Enterprise portal 7 .
Q.3 - Am i right here ?
Yes
3. In second step of sp-stack I have selected only SAP IGS , SAP KERNEL 64Bit (os dependent , os independent) , TREX 7.0 , TREX 7.1
Q.4 -Is the TREX already installed with ep6 . Am I right here to choose TREX 7 and 7.0 ?
Yes
4. sp-stack 3rd step selected all the patches which came in to the box and added to download basket .
I have downloaded the save-as xml file .
Q.5 Am I right here ?
Yes
5. .when finishing the step 3 it was asking for - Total 21 no. of object added to download basket and available for download .Total no. of object added to approval list and require approval 21 .
We don't solution manger installed . I have not confirmed these patches with solution manger and download all 21 patches through download manager . Is it ok or confirmation is must ?
You need all the Patches. so you need to Approve the download through solution nmanager.
without that the Patches wont be applied.
5. I have copied all the download patches adn xml file to EPSin windows directory and started JSPM
Here i have selected support pack type - support pack stack
select support pack stack to apply - sap.com/SAP NETWEAVER 7.0
Error during validation of the dependencies of the selected support package stacks
This is because the required Components are not present in the EPSIn Directory.
Regards
Rajendra

JSPM: Error during validation of the dependencies of the selected hot fixes

Hi,
We have a strange problem, recently we have upgraded our server from XI 3.0 to PI 7.1 and after the upgrade
as part of post upgrade steps I had to deploy few SDA/SCA files, while I am trying to deploy these files
I am getting the error "Error during validation of the dependencies of the selected hot fixes" during the check queue phase and I am not able to go ahead..
As I am facing the same error for three different kinds of SDA files, I was trying to apply SP03 for my
JSPM version 7.11.0.0.119 but even here I am facing the same error.
I am sure that what ever the files I am trying to deploy are correct because these are instructed by SAP.
I guess I have some problem with my JSPM.
Please help me.
Thanking you in advance.
Sonali

Just updated your other post -
Java deployment tools on NW 7.1
Error during validation of the dependencies of the selected hot fixes
Btw, could you check the documents of these SDA files in case there is soem common dependency?

JSPM Error : DocumentServicesLicenseManager not deployed b/c login failed

hello all,
I want to update NW2004s SPS09 to SPS10
After having had troubles with the Kernel which is finally replaced succesfully, I now seem to have problems with the login:
"Cannot login to the SAP J2EE Engine using user and password as provided in the Filesystem J2EE Engine Config Tool. [..]
com.sap.sdm.serverext.servertype.inqmy.extern.DeployManagerAuthExceptionWrapper: Wrong security credentials detected while trying to obtain connection to the J2EE Engine. [..]"
I took a look at the corresponding SAP Note and re-entered the password in the secure store of the config tool - no change - I don't know what could be the problem. Everything worked fine before.
Could it be a problem with Adobe and Licensing!?!? As part of it is Adobe Document Services - ADS is the package where it has this problem.
thanks in advance

To test whether my portal is still working and what parts have been updated I entered http://[host]:50100 and then clicked on "system information"
I had to enter an username and a password and nothing worked. When I tried to enter the portal as an Administrator it said, this account has been locked.
Thank god I had an user from my LDAP with User Admin rights so I re-activated my administrator with the old password, that also is stored in the secure store from the config tool.
How come that this account has been locked? is this normal?

JSPM_MAIN error in upgrading netweaver- NWDI related error, please check !

Here is the proper step by step explanation
1.)Before any patching the portal
The SP level of EP was SP17 and the ESS/MSS and the SAPPCUI_GP was at 600 .11
2.)The we patched the EP to EHP1 using EHPI installer. Which was done without errors.
3.) Then we patched the MSS to 600.15 and the SAPPCUI_GP to 603.4.1.
4.) The ESS Needs to be patched to 603.4.1, but while patching we got the following errors attached.
The first screen shot is the error we had received first. we resolved it by creating that directory.we donu2019t know why this directory it asked for.
Please refer to this link
JSPM error for applying ESS patch
The second screenshot is the error where I am stuck.
The 3 rd screen shots shows that the ESS is modified by NWDI.
Can someone please explain as to what is the way out, or what it needs to be done in NWDI.
for all the trace files and the screenshots... please download below file.
http://rapidshare.com/files/300025619/ESSIssue.7z

Hi,
The problem has been solved,
The prerequisite to the patching of the portal were not met initially.
REgards,
Rajat

BI EHP1 ONLINE_DEPLOY JSPM Error

Similar Messages

Maybe you are looking for