SPStab.xml 0kb !?
Hello,
At my work we are patching a solman 4 and ran in to a problem:
The xml-file "SPStab.xml" we download when we download Support Packs is always empty!?
Has this happened to anyone here?
I am rather new to this but need your input, can't figure out what I am doing wrong.
regards
Patrik
Please go through if you have not checked this thread....?
[Re: SOLMAN EhP1 xml file problem;
Similar Messages
-
EhP1 - Unable to create XML file in Solman
Hi all,
I need some assistance
I am trying to upgrade our XI system to EhP1 - SP04. I use Maintenance Optimizer in our Solution Manager (SAP EHP 1 for SAP Solution Manager 7.0) to select the necessary files for my upgrade. The XI system has been set up in SMSY an given a Logical Component. Also, added to the Solution Landscape. I use the SAPehpi-installer to upgrade XI.
However, when I get to section three, I am supposed to provide the SMSDXML.xml file. This file is not created by our Solution Manager for some reason. The file, as I understand it, is supposed to be generated automatically during Maintenance Optimizer. But when I check the EPS and EPS/in folder of our solman, the file is not to be found. I have also checked the parameter DIR_EPS_ROOT in RZ11. It is correct. The authorization has been set to full on group Everyone, just to check if that could be the problem, but with no luck.
When I use transaction /n/tmwflow/mopz_stack i am able to view the XML file (I assume that it is the correct file), but any attempt to copy the text displayed, and to save it as an XML-file has not resulted in any success.
The only thing I have to go on, is a warning displayed in Maintenance Optimizer, stating: "Warning - No SLM configured in system - <SID>. Every document etc, Iu2019ve read sais that one can use Software Lifecycle Manager as an alternative to Download Basket. I havenu2019t seen SLM listed as a prereq, so I donu2019t believe that this could be the reason why the XML-file is not generated.
Is there some setup/configuration Iu2019ve missed?
Any help will be much appreciated!
Best Regards,
Stian
Notes checked:
1134872 FAQ for stack Delta Files
1022704 Upgrade phase EHP_INCLUSION and SPSTACK_REQUEST
1277035 Solution Manager: EHP4 product data missingI downloaded the SPSTab.xml from SMP, but it didnt work. It gave an error: "The selected configuration file ("C:EHP1SPSTab.xml") is not usable. Reason: "Stackfile not found""
I have used the dockument in the link you provided as a basis for my upgrade. So I still need this to work in order to upgrade my XI Netweaver 7.0 to Enhancement Package 1...
In the document you provided:
Section 3 SAP Solution Manager
3.1 Support Package Level of SAP Solution Manager (Check - Mine is EHP1)
3.2 System Landscape (SMSY) of SAP Solution Manager (Check - as stated above in opening post)
3.3 SAP Solution Manager Maintenance Optimizer (Check)
3.4 SAP Solution Manager Troubleshooting: (Check)
3.4.4 No Stack Configuration File is generated: This is the core of my problem... I have read the notes listed, and run the IMG activity under Maintenance Optimizer, as per note 1134872. I get an warning stating "SAP ChaRM auto-configuration warnings" This could be the source of the problem, but in the thread Re: Message no. IMG_FASTCONF028 in Charm SolManiac says that it is nothing to worry about.
So to summarise:
I an still unable to generate XML file in Solman, and I am uable to get the XML downloaded from SMP to work with SAPehpi.
BR
Stian
(EDIT: I am however not shure if the settings under SMSY etc are 100% correct, but in my mind, that should prevent Maintenance Optimizer from generating the XML file)
Edited by: Stian Eiken on Jul 13, 2009 1:18 PM -
Couldnt upgrade the java stack after upgrading the abap to ehp1
Hi
I have upgarded the system to ehp1 but i couldnt continue to upgarde the java stack to 18th patch.The reason is it coudlnt find the file JSPM02P-2-20002796.SCA. I couldnt find this file . i couldnt find only this file JSPM02P_4-20002796.SCA . I tried to put this file in inbox and tried to run the jspm but it is not recognizing this as a valid file and its expecting JSPM02P-2-20002796.SCA. I couldnt find this file can anyone suggest me where i could find this file.
Thanks and Regards
MA.SreenivasanWhen you download the files, be sure to select "Save As File", which next to the "Add to Download Basket" button. Copy that SPStab.xml file to your EPS/in directory. Without that, it won't recognize the files even if they are there.
-
When starting the JSPM i get an error saying software component SAP_BUILDT
software component SAP_BUILDT is missing from the system and will be generated using data from active usage AS.
The next messege in the log tells me its been created successfully and I can see it the list of deployed components with an SP level of 0.0. I've got the correct SP level(11) for our system but can't specify it in the queue as a single SP. I already updated the rest but it missed BUILDT off.
Any ideas?
Its Netweaver 7.00 ABAP & JavaHello,
Make sure you have the JSPM first updated to SP11
and you have all the sP11 archives / SCAs in EPS/in directory
Also, you must have the SPSTab.xml file generated for SP11 in the EPS/in directory.
If jspm still fails, please paste the latest exception from jspm.trc file. and also check if the sdmlogs are getting updated under SDM\program\log directory.
If they are, please paste the error/exception from the latest SDM log.
Regards,
Snehal -
Hello Gurus,
Need a help,
I am in the process of upgrading the SolMan to EHP1.
I have read all the Docs available in SMP and also refered the Blogs.
Can any 1 please give the Brief steps that we need to follow to upgrade SolMan as i need to submit the request i need to specify the what all actions am going to perform. So i need the brief steps in order, that would of great help.
Our Kernel release is 700 SOlMan7. i know that we need to take SP to 17 before upgradation. But what abt Kernel level.
Here SP17 means is it only ABAP. Basis and Java or it it all the SP availabe in the system should be take to 17.
Please help.
Regards,
SrHi Anjali,
Upgrade all components which are not upgraded by stack upgrade to highest level.
Does this mean i need to upgrade all the SP levels of all SP available in my system.
Upgrade Java to SP17 using JSPM
can you please let me know the path where i can download the Java SP17.
Download SPS tab file in XML from Marketplace for EhP1 and upload in /usr/sap/trans/EPS/in
As per the note sapnote_0001169247, there are 2 XML files SAP_SOLUTION_MANAGER_70_EHP1.xml and SPSTab.xml.
whats the main use of these files, whats the mai purpose, what they contain. How they are useful in upgrading SolMan to EHP1.
Please let me know.
Regards,
Sr -
Hi All
Iam planning to upgrade my solution manger system to SP16 present level is SP12,i have applied latest SPAM level 34 and downloaded relevant SP stack 16 through MO and also SPSTab.xml file and solman.csv and pasted all downloaded fileS in EPS/in directory including the xml file, when i try to load the pathces from application level in tcode SPAM its saying error as "No OCS files were found for uploading"
My question
1:Do i need to uncar all the car files and then paste it in EPS/in directory ?then what is use of xml file?
2:Is there any method to uncar all the files at one shot rather then single patch?
3:Can any one provide me related document how to do it ?
Regards
Uday> 1:Do i need to uncar all the car files and then paste it in EPS/in directory ?then what is use of xml file?
Yes.
cd /usr/sap/trans
SAPCAR <file>
This will place them directly to EPS/in
> 2:Is there any method to uncar all the files at one shot rather then single patch?
On Unix:
copy all files to a directory, then
cd /usr/sap/trans
for i in `ls <directory`; do SAPCAR -xvf <directory>/$i; done
Markus -
Unable to update CE EHP1.
I just installed NW CE EHP1 and now I would like to update it to SP Stack 2.
According to the Update Guide, I first upgraded the ceupdatemanager.exe as explained in SAP Note 1224927.
Then I downloaded the stack to a local directory. In that directory I also saved the SPSTab.xml.
When I execute the ceupdatemanager, it gets to phase 4 (Update Java Support Package Manager) where it fails with an ExecuteException saying:
The execution of .sca archive-deployment and binary exchange with JSPM failed. Deployment queue RSD-1245227173093 should be validated successfully before it can be deployed. JSPM version is 7.11.2.0.33. Current JSPM log directory is C:\usr\sap\CE1\J00\j2ee\JSPM\log\log_2009_06_17_10_25_40
I checked the UpdateSystem.log file and several other log and trace file, but I couldn't understand the cause of this exception. This error can be reproduced any time I re-run the ceupdatemanager.
Any help would be appreciated.
Thanks in advance.
Livio.Hi Livio!
Currently, we are performing an update from CE 7.1 SP 5 to CE 7.1 EhP1 SP 2.
You have to put the files you downloaded for your update stack in the /usr/sap/trans/EPS/in directory (remark: this path will be slightly different on a Windows server!). Make sure that these are the only files in that directory. The file SPSTab.xml is not required. You should omit it. You will get a warning that this file is missing but the update should work anyway.
However, we have trouble performing our update as we had to update the kernel manually beforehand. This issue currently is not coverd by the SAP notes.
Best regards and good luck
Alexander
Edited by: Alexander Königs on Jun 19, 2009 10:16 AM -
Update java server from 7.00 SP17 to 7.05 SP05 with EHPI
hi all
i' m upgrading a java server from version 7.00 SP17 to version 7.01 SP05 (ehp1) with the
EHPI installer
during the phase PREPARE_JSPM_QUEUE i get the error that the jspm has already been started
any ideas
regards tom
file: TroubleTicket_01.txt
SID................: JWC
Hostname...........: aapbwc
Install directory..: /usr/sap/JWC
Upgrade directory..: /usr/sap/JWC/EHPI/java
Database...........: Oracle
Operating System...: UNIX
JDK version........: 1.5.0_12 SAP AG
SAPJup version.....: 3.2.2
Source release.....: 700
Target release.....: 700
Start release SP...: $(/J2EE/StandardSystem/SPLevel)
Target release SP..: $(/J2EE/ShadowSystem/SPLevel)
Current usages.....:
ABAP stack present.: false
The execution of PREPARE/INIT/PREPARE_JSPM_QUEUE ended in error.
Could not connect JSPM tool.
JSPM has already been started.
file: PREPARE_JSPM_QUEUE_CSZ_01.LOG
Nov 9, 2009 11:11:51 AM [Warning]: com.
sap.sdt.j700.deploymentmgr.DeploymentManagerImpl [Thread[main,5,main]]: Deployment of a
rchive /usr/sap/trans/EPS/in/JSPM05_0-20002796.SCA has been rejected because it is alre
ady deployed.
Nov 9, 2009 11:11:51 AM [Info]: com.sap.sdt.j2ee.phases.jspm.JSPMSpStackQueuePreparator
.createAndValidateQueue(JSPMSpStackQueuePreparator.java:184) [Thread[main,5,main]]: Cre
ating jspm queue sapjup-queue from sp stack file /usr/sap/trans/EPS/in/SPSTab.xml.
Nov 9, 2009 11:11:51 AM [Error]: com.sap.sdt.ucp.phases.AbstractP
haseType.doExecute(AbstractPhaseType.java:863) [Thread[main,5,main]]: Exception has occ
urred during the execution of the phase.
Nov 9, 2009 11:11:51 AM [Error]: com.sap.sdt.sltool.rapi.connector.AbstractToolConn
ector.startTool(AbstractToolConnector.java:98) [Thread[main,5,main]]: JSPM has already
been started.hi ventsi
the port 6240 is not in use until the ehpi comes to the failing phase
PREPARE_JSPM_QUEUE phase
bash-3.00$ netstat -an | grep -i 6240
tcp4 0 0 *.6240 . LISTEN
tcp4 0 0 10.128.72.179.6240 10.128.72.179.49942 ESTABLISHED
tcp4 0 0 10.128.72.179.49942 10.128.72.179.6240 ESTABLISHED
and then it fails with the above error
regards tom -
UPGRADE/DEPLOYMENT_BASED_UPGRADE/DEPLOY_ONLINE_DEPL
hi Friends An error has occurred during the execution of the DEPLOY_ONLINE_DEPL phase. Error while executing DeploymentManager phase with action deploySlot. Check the log files for the specified action. Could not execute deployment of stack file D:/SP09/SPSTab.xml. The deployment of the queue failed. Deployment of queue sapjup-queue completed with error Archive with all relevant logs and traces is created in D:\usr\sap\PP4\DVEBMGS00\j2ee\JSPM\log\errorReport.zip JSPM version is 7.11.4.0.12. Current JSPM log directory is D:\usr\sap\PP4\DVEBMGS00\j2ee\JSPM\log\log_2010_06_07_21_33_11 DEPLOY_ONLINE_DEPL_DDB_04.LOG; Jun 8, 2010 9:50:42 AM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:754) [Thread[main,5,main]]: Phase UPGRADE/DEPLOYMENT_BASED_UPGRADE/DEPLOY_ONLINE_DEPL has been started. Jun 8, 2010 9:50:42 AM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:755) [Thread[main,5,main]]: Phase type is com.sap.sdt.j2ee.phases.PhaseTypeDeploymentManager. Jun 8, 2010 9:50:42 AM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:409) [Thread[main,5,main]]: Parameter action=deploySlot Jun 8, 2010 9:50:42 AM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:409) [Thread[main,5,main]]: Parameter connect=standard Jun 8, 2010 9:50:42 AM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:409) [Thread[main,5,main]]: Parameter errorStrategy=skipDepending Jun 8, 2010 9:50:42 AM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:409) [Thread[main,5,main]]: Parameter rule=all Jun 8, 2010 9:50:42 AM [Info]: com.sap.sdt.j2ee.phases.PhaseTypeDeploymentManager.checkParameters(PhaseTypeDeploymentManager.java:558) [Thread[main,5,main]]: Checking phase parameters action, connect. Jun 8, 2010 9:50:42 AM [Info]: com.sap.sdt.j2ee.phases.PhaseTypeDeploymentManager.checkParameters(PhaseTypeDeploymentManager.java:570) [Thread[main,5,main]]: Phase parameters have been checked. All required 1 phase parameters have been set. Jun 8, 2010 9:50:42 AM [Info]: com.sap.sdt.sapjup.tools.sapjupjspm.SAPJupJSPMRapiAdapter.connect(SAPJupJSPMRapiAdapter.java:152) [Thread[main,5,main]]: Trying to connect JSPM. Jun 8, 2010 9:50:42 AM [Info]: com.sap.sdt.sapjup.tools.sapjupjspm.SAPJupJSPMRapiAdapter.connect(SAPJupJSPMRapiAdapter.java:168) [Thread[main,5,main]]: JSPM was connected successfully. Jun 8, 2010 9:50:42 AM [Info]: com.sap.sdt.sapjup.tools.sapjupjspm.SAPJupJSPMRapiAdapter.deploy(SAPJupJSPMRapiAdapter.java:496) [Thread[main,5,main]]: Starting deployment. Jun 8, 2010 9:52:10 AM [Error]: com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:863) [Thread[main,5,main]]: Exception has occurred during the execution of the phase. Jun 8, 2010 9:52:10 AM [Error]: com.sap.sdt.jspm.unattended.processors.ExecuteRequestProcessor.process(ExecuteRequestProcessor.java:193) [Thread[main,5,main]]: Deployment of queue sapjup-queue completed with error Archive with all relevant logs and traces is created in D:\usr\sap\PP4\DVEBMGS00\j2ee\JSPM\log\errorReport.zip JSPM version is 7.11.4.0.12. Current JSPM log directory is D:\usr\sap\PP4\DVEBMGS00\j2ee\JSPM\log\log_2010_06_07_21_33_11. Jun 8, 2010 9:52:10 AM [Error]: com.sap.sdt.sapjup.tools.sapjupjspm.SAPJupJSPMRapiAdapter.createAndLogRapiException(SAPJupJSPMRapiAdapter.java:714) [Thread[main,5,main]]: The following SAP Note 1399846 may contain solution for the problem. Jun 8, 2010 9:52:10 AM [Error]: com.sap.sdt.sapjup.tools.sapjupjspm.SAPJupJSPMRapiAdapter.createAndLogRapiException(SAPJupJSPMRapiAdapter.java:706) [Thread[main,5,main]]: The deployment of the queue failed. Jun 8, 2010 9:52:10 AM [Error]: com.sap.sdt.sapjup.tools.sapjupjspm.deploy.SAPJupJSPMDeployer.deployList(SAPJupJSPMDeployer.java:68) [Thread[main,5,main]]: Could not execute deployment of stack file D:/SP09/SPSTab.xml. Jun 8, 2010 9:52:10 AM [Error]: com.sap.sdt.j2ee.phases.PhaseTypeDeploymentManager.execute(PhaseTypeDeploymentManager.java:519) [Thread[main,5,main]]: Error while executing DeploymentManager phase with action deploySlot. Check the log files for the specified action. Jun 8, 2010 9:52:10 AM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:906) [Thread[main,5,main]]: Phase UPGRADE/DEPLOYMENT_BASED_UPGRADE/DEPLOY_ONLINE_DEPL has been completed. Jun 8, 2010 9:52:10 AM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:907) [Thread[main,5,main]]: Start time: 2010/06/08 09:50:42. Jun 8, 2010 9:52:10 AM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:909) [Thread[main,5,main]]: End time: 2010/06/08 09:52:10. Jun 8, 2010 9:52:10 AM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:910) [Thread[main,5,main]]: Duration: 0:01:28.065. Jun 8, 2010 9:52:10 AM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:911) [Thread[main,5,main]]: Phase status is error. I have searched blogs and followed SAP Note 1371424,1284402, 1251735. Nothing relevent and fruitful. PI 7.01 SP09----> PI 7.11 SP04 Please advice. Pooja
Hi Experts
My main instance is down.
I followed some notes to amke it up.
But server 0 is yellow from more then 40 mins,
SAP Note 710663 - AS Java Bootstrap Synchronization
Follow the steps as per the note SAP Note 1025085 - How to manually patch the SAPJVM
SAP Note 1133020 - How to import a SAP JVM patch into an AS Java
JSPM Log info.
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[2.0.7.1006]/>
<!NAME[D:\usr\sap\PP4\DVEBMGS00\j2ee\JSPM\log\log_2010_06_07_21_33_11\deploy_2010-06-08_09-51-27.log]/>
<!PATTERN[deploy_2010-06-08_09-51-27.log]/>
<!FORMATTER[com.sap.tc.logging.TraceFormatter(%25d[%6s]:%m)]/>
<!ENCODING[UTF8]/>
<!LOGHEADER[END]/>
Jun 8, 2010 9:51:27 AM [Info ]:DC API is trying to connect to 'HOSTEST:50004'
Jun 8, 2010 9:51:27 AM [Error ]:[ Exception ]::SessionImpl::getContext():[get ctx. NamingException],cause=Exception during getInitialContext operation. Cannot establish connection to the remote server. -
UPGRADE/DEPLOYMENT_BASED_UPGRADE/DEPLOY_ONLINE_DEPL failed
hi Friends
An error has occurred during the execution of the DEPLOY_ONLINE_DEPL phase.
Error while executing DeploymentManager phase with action deploySlot. Check the log files for the specified action. Could not execute deployment of stack file D:/SP09/SPSTab.xml. The deployment of the queue failed. Deployment of queue sapjup-queue completed with error Archive with all relevant logs and traces is created in D:\usr\sap\PP4\DVEBMGS00\j2ee\JSPM\log\errorReport.zip JSPM version is 7.11.4.0.12. Current JSPM log directory is D:\usr\sap\PP4\DVEBMGS00\j2ee\JSPM\log\log_2010_06_07_21_33_11
DEPLOY_ONLINE_DEPL_DDB_04.LOG;
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[2.0.7.1006]/>
<!NAME[D:\NW7\EHPI\java\log\DEPLOY_ONLINE_DEPL_DDB_04.LOG]/>
<!PATTERN[DEPLOY_ONLINE_DEPL_DDB_04.LOG]/>
<!FORMATTER[com.sap.tc.logging.TraceFormatter(%d [%s]: %-100l [%t]: %m)]/>
<!ENCODING[UTF8]/>
<!LOGHEADER[END]/>
Jun 8, 2010 9:50:42 AM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:754) [Thread[main,5,main]]: Phase UPGRADE/DEPLOYMENT_BASED_UPGRADE/DEPLOY_ONLINE_DEPL has been started.
Jun 8, 2010 9:50:42 AM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:755) [Thread[main,5,main]]: Phase type is com.sap.sdt.j2ee.phases.PhaseTypeDeploymentManager.
Jun 8, 2010 9:50:42 AM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:409) [Thread[main,5,main]]: Parameter action=deploySlot
Jun 8, 2010 9:50:42 AM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:409) [Thread[main,5,main]]: Parameter connect=standard
Jun 8, 2010 9:50:42 AM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:409) [Thread[main,5,main]]: Parameter errorStrategy=skipDepending
Jun 8, 2010 9:50:42 AM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:409) [Thread[main,5,main]]: Parameter rule=all
Jun 8, 2010 9:50:42 AM [Info]: com.sap.sdt.j2ee.phases.PhaseTypeDeploymentManager.checkParameters(PhaseTypeDeploymentManager.java:558) [Thread[main,5,main]]: Checking phase parameters action, connect.
Jun 8, 2010 9:50:42 AM [Info]: com.sap.sdt.j2ee.phases.PhaseTypeDeploymentManager.checkParameters(PhaseTypeDeploymentManager.java:570) [Thread[main,5,main]]: Phase parameters have been checked. All required 1 phase parameters have been set.
Jun 8, 2010 9:50:42 AM [Info]: com.sap.sdt.sapjup.tools.sapjupjspm.SAPJupJSPMRapiAdapter.connect(SAPJupJSPMRapiAdapter.java:152) [Thread[main,5,main]]: Trying to connect JSPM.
Jun 8, 2010 9:50:42 AM [Info]: com.sap.sdt.sapjup.tools.sapjupjspm.SAPJupJSPMRapiAdapter.connect(SAPJupJSPMRapiAdapter.java:168) [Thread[main,5,main]]: JSPM was connected successfully.
Jun 8, 2010 9:50:42 AM [Info]: com.sap.sdt.sapjup.tools.sapjupjspm.SAPJupJSPMRapiAdapter.deploy(SAPJupJSPMRapiAdapter.java:496) [Thread[main,5,main]]: Starting deployment.
Jun 8, 2010 9:52:10 AM [Error]: com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:863) [Thread[main,5,main]]: Exception has occurred during the execution of the phase.
Jun 8, 2010 9:52:10 AM [Error]: com.sap.sdt.jspm.unattended.processors.ExecuteRequestProcessor.process(ExecuteRequestProcessor.java:193) [Thread[main,5,main]]: Deployment of queue sapjup-queue completed with error Archive with all relevant logs and traces is created in D:\usr\sap\PP4\DVEBMGS00\j2ee\JSPM\log\errorReport.zip
JSPM version is 7.11.4.0.12. Current JSPM log directory is D:\usr\sap\PP4\DVEBMGS00\j2ee\JSPM\log\log_2010_06_07_21_33_11.
Jun 8, 2010 9:52:10 AM [Error]: com.sap.sdt.sapjup.tools.sapjupjspm.SAPJupJSPMRapiAdapter.createAndLogRapiException(SAPJupJSPMRapiAdapter.java:714) [Thread[main,5,main]]: <html>The following <b><a href="http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=DISPL_TXT&_NNUM=1399846">SAP Note 1399846</a></b> may contain solution for the problem.
Jun 8, 2010 9:52:10 AM [Error]: com.sap.sdt.sapjup.tools.sapjupjspm.SAPJupJSPMRapiAdapter.createAndLogRapiException(SAPJupJSPMRapiAdapter.java:706) [Thread[main,5,main]]: The deployment of the queue failed.
Jun 8, 2010 9:52:10 AM [Error]: com.sap.sdt.sapjup.tools.sapjupjspm.deploy.SAPJupJSPMDeployer.deployList(SAPJupJSPMDeployer.java:68) [Thread[main,5,main]]: Could not execute deployment of stack file D:/SP09/SPSTab.xml.
Jun 8, 2010 9:52:10 AM [Error]: com.sap.sdt.j2ee.phases.PhaseTypeDeploymentManager.execute(PhaseTypeDeploymentManager.java:519) [Thread[main,5,main]]: Error while executing DeploymentManager phase with action deploySlot. Check the log files for the specified action.
Jun 8, 2010 9:52:10 AM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:906) [Thread[main,5,main]]: Phase UPGRADE/DEPLOYMENT_BASED_UPGRADE/DEPLOY_ONLINE_DEPL has been completed.
Jun 8, 2010 9:52:10 AM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:907) [Thread[main,5,main]]: Start time: 2010/06/08 09:50:42.
Jun 8, 2010 9:52:10 AM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:909) [Thread[main,5,main]]: End time: 2010/06/08 09:52:10.
Jun 8, 2010 9:52:10 AM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:910) [Thread[main,5,main]]: Duration: 0:01:28.065.
Jun 8, 2010 9:52:10 AM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:911) [Thread[main,5,main]]: Phase status is error.
I have searched blogs and followed SAP Note 1371424,1284402, 1251735.
Nothing relevent and fruitful.
PI 7.01 SP09----> PI 7.11 SP04
Please advice.
PoojaHi,
Could you please paste latest logs of JSPM ?
Thanks
Sunny -
EHPI failed in DEPLOY_ONLINE_DEPL
I am upgrading my PI system from NW700 SPS14 to NW7.01 SPS3 with EHPI.
In the DEPLOY_ONLINE_DEPL it fails because SDM server is being shutdown
while the JSPM is trying to update the SDM repository. My full problem
analysis is below.
Thank you.
Dave
Error...
Error while executing DeploymentManager phase with action deploySlot.
Check the log files for the specified action.
Could not execute deployment of stack file D:\usr\sap\trans\EPS\Sept2009\SPSTab.xml.
JSPM could not log in to the Java server with user SAP*.
Probably the server is not running or the provided credentials are not correct.
JSPM is unable to logon to SDM. Check that SDM password is correct and the system is up and running.
JSPM version is 7.01.3.0.15.
Current JSPM log directory is D:\usr\sap\DPI\DVEBMGS01\j2ee\JSPM\log\log_2009_10_12_13_41_52.
[Thread[JSPM,5,main]]: Discarding message $com.sap.sdt.sltool.rapi.connector.MsgData@5738ec91
[Thread[main,5,main]]: JSPM was started successfully.
[Thread[main,5,main]]: Trying to log in with user SAP*.
[Thread[main,5,main]]: JSPM successfully logged in with user SAP*.
[Thread[CharacterCommLink,5,main]]: Socket closed
[Thread[JSPM,5,main]]: Reporting failed commlink.
Oct 12, 2009 1:42:11 PM [Info]: java.lang.Thread.dumpThreads(Thread.java:-2) [Thread[ProcessReader,5,main]]: >> Closed input stream
Oct 12, 2009 1:42:11 PM [Info]: java.lang.Thread.dumpThreads(Thread.java:-2) [Thread[ProcessReader,5,main]]: >> Closed input stream
Oct 12, 2009 1:42:11 PM [Info]: com.sap.sdt.jspm.rapi.connector.JSPMConnector.waitForJSPMTermination(JSPMConnector.java:457) [Thread[main,5,main]]: JSPM stopped.
Oct 12, 2009 1:42:11 PM [Error]: com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:863) [Thread[main,5,main]]: Exception has occurred during the execution of the phase.
Oct 12, 2009 1:42:11 PM [Error]: com.sap.sdt.jspm.unattended.RequestController.addContextInfo(RequestController.java:178) [Thread[main,5,main]]: JSPM is unable to logon to SDM. Check that SDM password is correct and the system is up and running.
JSPM version is 7.01.3.0.15. Current JSPM log directory is D:\usr\sap\DPI\DVEBMGS01\j2ee\JSPM\log\log_2009_10_12_13_41_52.
Oct 12, 2009 1:42:11 PM [Error]: com.sap.sdt.sapjup.tools.sapjupjspm.SAPJupJSPMRapiAdapter.createAndLogRapiException(SAPJupJSPMRapiAdapter.java:702) [Thread[main,5,main]]: JSPM could not log in to the Java server with user SAP*. Probably the server is not running or the provided credentials are not correct.
[Thread[main,5,main]]: Could not execute deployment of stack file D:\usr\sap\trans\EPS\Sept2009\SPSTab.xml.
[Thread[main,5,main]]: Error while executing DeploymentManager phase with action deploySlot. Check the log files for com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:906) [Thread[main,5,main]]: Phase UPGRADE/DEPLOYMENT_BASED_UPGRADE/DEPLOY_ONLINE_DEPL has been completed.
Start CMD
cd D:\usr\sap\DPI\DVEBMGS01\SDM\program
.\stopserver.bat
This should end with return code =104-no server running.
sdm.bat jstartup u201Cmode=standaloneu201D
sdm.bat changepassword u201Cnewpassword={enter password here as per password file}u201D
sdm.bat jstartup u201Cmode=integratedu201D
u2026no luck
Also tested the password by logging into SDM Guiu2026
sdm.bat remotegui (need to start the SDM server for this)
u2026no luck
Tried increasing java heap memory used by SDM from 256M to 512M as per OSS Note 1264514 and OSS Note 879377.
u2026no luck
When I look at jcontrol in SAPMMC I can seeu2026that the status of the jcontrol was "Some processes running [Safe Mode]
Follow Note 1267123 - System remains in SAFE mode after update.pdf u2026
Start CMD
cd D:\usr\sap\DPI\DVEBMGS01\j2ee\configtool
.\configtool.bat
The J2EE Engine Config Tool starts.
Menu File -> Safe Mode
Choose Safe Mode Enabled = NO then OK
Exit
Apply changes? = Yes
Logs Message appears, OK
OK
Restart SAP System 01 ONLY in SAPMMC then totally get out of SAPMMC before proceeding.
u2026no luck
OK the SDM server is failing to start so Iu2019ll look into thatu2026
Try to start manually in standalone modeu2026as per commands above.
u2026no luck
Follow the EHPI_Java Troubleshooting Guide.
Only suggestion is to stop the EHPI Java processes after setting the SDM server to normal mode.
u2026no luck
Look at JSPM logu2026
Oct 12, 2009 1:42:04 PM [Info]: Phase JSPM/JSPMPhases/JSPM_MAIN has been started.
Oct 12, 2009 1:42:04 PM [Info]: Phase type is com.sap.sdt.jspm.phases.PhaseTypeLupJSPM.
Oct 12, 2009 1:42:04 PM [Info]: Message type received login.
Oct 12, 2009 1:42:04 PM [Info]: Processing login request for user SAP*.
Oct 12, 2009 1:42:04 PM [Info]: Detecting system parameters...
Oct 12, 2009 1:42:04 PM [Info]: You can find additional information in log file D:\usr\sap\DPI\DVEBMGS01\j2ee\JSPM\log\log_2009_10_12_13_41_52\DETECT_SYSTEM_PARAMETERS_01.LOG.
Oct 12, 2009 1:42:08 PM [Info]: Detection of system parameters has finished.
Oct 12, 2009 1:42:09 PM [Info]: Checking connectivity for SDM server on host DVW3SAPPI01, port 50118...
Oct 12, 2009 1:42:10 PM [Error]: com.sap.sdm.apiimpl.remote.client.APIRemoteExceptionImpl: Server DVW3SAPPI01 did not accept login request as admin on port 50118. Details: ERROR: Could not establish connection to server DVW3SAPPI01 at port 50118: Connection refused: connect
Oct 12, 2009 1:42:10 PM [Error]: JSPM is unable to logon to SDM. Check that SDM password is correct and the system is up and running.
Oct 12, 2009 1:42:10 PM [Info]: Could not process login request for user SAP*.
Oct 12, 2009 1:42:10 PM [Error]: JSPM is unable to logon to SDM. Check that SDM password is correct and the system is up and running.
JSPM version is 7.01.3.0.15. Current JSPM log directory is D:\usr\sap\DPI\DVEBMGS01\j2ee\JSPM\log\log_2009_10_12_13_41_52.
Oct 12, 2009 1:42:10 PM [Info]: Message type received disconnect.
Oct 12, 2009 1:42:10 PM [Info]: Remote connection is closed.
Oct 12, 2009 1:42:10 PM [Info]: Phase JSPM/JSPMPhases/JSPM_MAIN has been completed.
Oct 12, 2009 1:42:10 PM [Info]: Start time: 2009/10/12 13:42:04.
Oct 12, 2009 1:42:10 PM [Info]: End time: 2009/10/12 13:42:10.
Oct 12, 2009 1:42:10 PM [Info]: Duration: 0:00:06.172.
Oct 12, 2009 1:42:10 PM [Info]: Phase status is initial.
OK definitely looks like we need to get that SDM server running!
Look at the SDM logsu2026
Maybe itu2019s just because the SDM is set to standalone? I set it to integrated!
Restart SAP System 01 ONLY in SAPMMC then totally get out of SAPMMC before proceeding.
u2026no luck
Iu2019m going back to the VM Clone to double check the SDM and SAP* and j2ee_admin passwords.
u2026no lucku2026because we are not rolling back the database when we do this.
Found new erroru2026some error about localhost so added changes to host file.
u2026no luck
OK now we up the logging on the SDM Server and find out why it is not runningu2026
Canu2019t find why? I am sure that in fact the EHPI is shutting it down.
Updated the kernel as per OSS Note 1274006 and 1122058 and per Kreasanu2019s suggestion.
Shutdown all SAP processes, unpacked kernel into SYS directory, restarted SAP, restarted EHPI (not from the start though).
u2026no luckThank you Sunny and Supriya,
In fact because the UME has been set to ABAP, and the j2ee_admin is on the ABAP, it is not used because the ABAP has been moved to the shadow and is locked for upgrade.
What SAPjup does then is create a SAP* on the java and changes the secure store to use the SAP* user. I have double checked the secure store and I am able to log into the NWA as the SAP*(java) user (although the screen is blank like there is no user context).
The log file also shows that the SAP* user is being used.
The problem seams to be more that the SDM server is not running, and in fact it's not. Even if I change it to mode=integrated and start it, the upgrade stops teh server then changes it back to mode=standalone for some reason? The sdmlog###.log shos this but there are no errors.
Kind regards,
Dave -
NW 7.00 SP20 to 7.01 SP5 stops at PREPARE_JSPM_QUEUE phase
Hello,
I have problem with upgrade NW 7.00 SP20 to EHP1 with SP5 using EHPI installer.
During PREPARE_JSPM_QUEUE phase I receive message: The validation of the Deploy queue was not successful.
''sap.com/SAP_JTECHF: You are trying to update software component sap.com/SAP_JTECHF from release 7.00 SP level 20.0 and provider SAP AG to release 7.01 SP level 5.0 and provider SAP AG. This update is not possible since the target SP level is older than the source SP level''
Same message for SAP_JTECHS.
In Note 1248905 NW 7.00 SP20 is equivalent to NW 7.05 SP5.
From SAP Support I also receive answer, that this upgrade should go smoothly.
I have extracted both JTECHF and JTECHS SCA files and I can see that 2 components have older date as already implemented.
These 2 components are
SAP_JTECHF
tc/wd/webdynpro (Installed version 7.0020.20090723111631.0000 new version 7.0105.20090710120949.0000)
SAP_JTECHS
tc/wd/dispwda (Installed version 7.0020.20090723111631.0000 new version 7.0105.20090710120949.0000).
I assume, that date inside version means date of component these 2 components in fact have older date, than already implemented.
On marketplace there are already hotfixes for both SAP_HTECHF and SAP_JTECHS (SAPJTECHS05P_2-10005886 and SAPJTECHF05P_3-10005909), and inside those 2 hotfixes, components are newer, but I can't include these 2 SCA files into Stack XML file (SPSTab.xml).
In JSPM_MAIN_1_01.LOG I can see that also UWLJWF component has older date, than already implemented, but this component has been admitted for deployment.
ABAP Configuration phase was finished OK.
Is it possible somehow to include latest SCA files with hotfixes into SPSTab.xml?
Regards
StaneHi Stan,
Both patchs are equivalent , you can't update the patch 7.0.20 to 7.1.5
You can check note 1248905 which says
Installed release Target Release
SAP NetWeaver 7.0 SAP EHP1 for Netweaver 7.0
SPS 20 SPS 5
You can update 7.0.20 to 7.1.6 , but yet patch 6 has not been relase by SAP
Thanks,
Anil -
Error in CHECK_START_RELEASE_COMPONENTS Phase
I'm working in upgrading my landscape with EHP4 on a ECC server. I've done this before on other servers but now I'm getting an error on the Java side stating "The retrieval of the source release software components failed. There is no active product on the system. Probably no usage type is activated on the system. JSPM version is 7.01.2.3.2." I don't know what the problem is but I need to have this taken care of right away. I recreated the SPSTAB.XML file and made sure all the components match. If anyone can provide me with a solution on what the issue is or provide me with a password to skip this phase, I would greatly appreciate it!
I am currently running ECC 6.0 SPS9 with SQL Server 2005, Java SPS13. Seems that using note 883948 may fix my issue but I'm getting the an error when running the script. Here is what the UTL.LOG file indicates:
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7185 - 630]/>
<!NAME[utl.log]/>
<!PATTERN[utl.log]/>
<!FORMATTER[com.sap.tc.logging.TraceFormatter(%24d %7s: %m)]/>
<!ENCODING[UTF8]/>
<!LOGHEADER[END]/>
Dec 6, 2009 5:50:11 PM Info : Successfully parsed!
Dec 6, 2009 5:50:11 PM Info : Executing command Activate...
Dec 6, 2009 5:50:11 PM Info : Establishing DB connection...
Dec 6, 2009 5:50:11 PM Path : Exception : The DataBase is down or the connection parameters are wrong: -sid=ECL -dsn=jdbc/pool/ECL -ssprops=E:\usr\sap\ECL\SYS\global/security/data/SecStore.properties -ssk=E:\usr\sap\ECL\SYS\global/security/data/SecStore.key -keyphrase=null
java.lang.Exception
at com.sap.exception.BaseExceptionInfo.traceAutomatically(BaseExceptionInfo.java:1141)
at com.sap.exception.BaseExceptionInfo.<init>(BaseExceptionInfo.java:413)
at com.sap.exception.BaseException.<init>(BaseException.java:302)
at com.sap.sl.ut.infoprovider.exceptions.UTInfoException.<init>(UTInfoException.java:96)
at com.sap.sl.ut.manager.persistence.db.DataBaseInfoFactory.connect(DataBaseInfoFactory.java:215)
at com.sap.sl.ut.manager.persistence.db.InfoManager.activateUsageType(InfoManager.java:124)
at com.sap.sl.ut.manager.persistence.db.DataBaseInfoFactory.activateUsageType(DataBaseInfoFactory.java:1063)
at com.sap.sl.ut.manager.command.Activate.execute(Activate.java:44)
at com.sap.sl.ut.manager.command.Command.exec(Command.java:88)
at com.sap.sl.ut.manager.UtlMain.exec(UtlMain.java:60)
at com.sap.sl.ut.manager.UtlMain.main(UtlMain.java:56)
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.offline.OfflineToolStart.main(OfflineToolStart.java:81)
Caused by: com.sap.sql.log.OpenSQLException: Could not load class com.sap.nwmss.jdbc.sqlserver.SQLServerDriver.
at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:106)
at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:143)
at com.sap.sql.connect.OpenSQLDataSourceImpl.createConnection(OpenSQLDataSourceImpl.java:522)
at com.sap.sql.connect.OpenSQLDataSourceImpl.getConnection(OpenSQLDataSourceImpl.java:276)
at com.sap.sl.ut.manager.persistence.db.DBConnection.connectViaSecureStore(DBConnection.java:159)
at com.sap.sl.ut.manager.persistence.db.DBConnection.connect(DBConnection.java:171)
at com.sap.sl.ut.manager.persistence.db.DataBaseInfoFactory.connect(DataBaseInfoFactory.java:213)
at com.sap.sl.ut.manager.persistence.db.InfoManager.activateUsageType(InfoManager.java:124)
at com.sap.sl.ut.manager.persistence.db.DataBaseInfoFactory.activateUsageType(DataBaseInfoFactory.java:1063)
at com.sap.sl.ut.manager.command.Activate.execute(Activate.java:44)
at com.sap.sl.ut.manager.command.Command.exec(Command.java:88)
at com.sap.sl.ut.manager.UtlMain.exec(UtlMain.java:60)
at com.sap.sl.ut.manager.UtlMain.main(UtlMain.java:56)
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.offline.OfflineToolStart.main(OfflineToolStart.java:81)
Caused by: java.lang.ClassNotFoundException: com.sap.nwmss.jdbc.sqlserver.SQLServerDriver
at com.sap.engine.offline.FileClassLoader.findClass(FileClassLoader.java:691)
at com.sap.engine.offline.FileClassLoader.loadClass(FileClassLoader.java:600)
at com.sap.engine.offline.FileClassLoader.loadClass(FileClassLoader.java:578)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:141)
at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:134)
... 16 more
caused by
java.lang.ClassNotFoundException: com.sap.nwmss.jdbc.sqlserver.SQLServerDriver
at com.sap.engine.offline.FileClassLoader.findClass(FileClassLoader.java:691)
at com.sap.engine.offline.FileClassLoader.loadClass(FileClassLoader.java:600)
at com.sap.engine.offline.FileClassLoader.loadClass(FileClassLoader.java:578)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:141)
at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:134)
at com.sap.sql.connect.OpenSQLDataSourceImpl.createConnection(OpenSQLDataSourceImpl.java:522)
at com.sap.sql.connect.OpenSQLDataSourceImpl.getConnection(OpenSQLDataSourceImpl.java:276)
at com.sap.sl.ut.manager.persistence.db.DBConnection.connectViaSecureStore(DBConnection.java:159)
at com.sap.sl.ut.manager.persistence.db.DBConnection.connect(DBConnection.java:171)
at com.sap.sl.ut.manager.persistence.db.DataBaseInfoFactory.connect(DataBaseInfoFactory.java:213)
at com.sap.sl.ut.manager.persistence.db.InfoManager.activateUsageType(InfoManager.java:124)
at com.sap.sl.ut.manager.persistence.db.DataBaseInfoFactory.activateUsageType(DataBaseInfoFactory.java:1063)
at com.sap.sl.ut.manager.command.Activate.execute(Activate.java:44)
at com.sap.sl.ut.manager.command.Command.exec(Command.java:88)
at com.sap.sl.ut.manager.UtlMain.exec(UtlMain.java:60)
at com.sap.sl.ut.manager.UtlMain.main(UtlMain.java:56)
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.offline.OfflineToolStart.main(OfflineToolStart.java:81)
Dec 7, 2009 2:11:50 PM Info : Severe (database) error. Return code: 64
Dec 7, 2009 4:51:37 PM Info : Successfully parsed!
Dec 7, 2009 4:51:37 PM Info : Executing command Activate...
Dec 7, 2009 4:51:37 PM Info : Establishing DB connection...
Dec 7, 2009 4:51:37 PM Path : Exception : The DataBase is down or the connection parameters are wrong: -sid=ECL -dsn=jdbc/pool/ECL -ssprops=e:\usr\sap\ECL\SYS\global/security/data/SecStore.properties -ssk=e:\usr\sap\ECL\SYS\global/security/data/SecStore.key -keyphrase=null
java.lang.Exception
at com.sap.exception.BaseExceptionInfo.traceAutomatically(BaseExceptionInfo.java:1141)
at com.sap.exception.BaseExceptionInfo.<init>(BaseExceptionInfo.java:413)
at com.sap.exception.BaseException.<init>(BaseException.java:302)
at com.sap.sl.ut.infoprovider.exceptions.UTInfoException.<init>(UTInfoException.java:96)
at com.sap.sl.ut.manager.persistence.db.DataBaseInfoFactory.connect(DataBaseInfoFactory.java:215)
at com.sap.sl.ut.manager.persistence.db.InfoManager.activateUsageType(InfoManager.java:124)
at com.sap.sl.ut.manager.persistence.db.DataBaseInfoFactory.activateUsageType(DataBaseInfoFactory.java:1063)
at com.sap.sl.ut.manager.command.Activate.execute(Activate.java:44)
at com.sap.sl.ut.manager.command.Command.exec(Command.java:88)
at com.sap.sl.ut.manager.UtlMain.exec(UtlMain.java:60)
at com.sap.sl.ut.manager.UtlMain.main(UtlMain.java:56)
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.offline.OfflineToolStart.main(OfflineToolStart.java:81)
Caused by: com.sap.sql.log.OpenSQLException: Could not load class com.sap.nwmss.jdbc.sqlserver.SQLServerDriver.
at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:106)
at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:143)
at com.sap.sql.connect.OpenSQLDataSourceImpl.createConnection(OpenSQLDataSourceImpl.java:522)
at com.sap.sql.connect.OpenSQLDataSourceImpl.getConnection(OpenSQLDataSourceImpl.java:276)
at com.sap.sl.ut.manager.persistence.db.DBConnection.connectViaSecureStore(DBConnection.java:159)
at com.sap.sl.ut.manager.persistence.db.DBConnection.connect(DBConnection.java:171)
at com.sap.sl.ut.manager.persistence.db.DataBaseInfoFactory.connect(DataBaseInfoFactory.java:213)
at com.sap.sl.ut.manager.persistence.db.InfoManager.activateUsageType(InfoManager.java:124)
at com.sap.sl.ut.manager.persistence.db.DataBaseInfoFactory.activateUsageType(DataBaseInfoFactory.java:1063)
at com.sap.sl.ut.manager.command.Activate.execute(Activate.java:44)
at com.sap.sl.ut.manager.command.Command.exec(Command.java:88)
at com.sap.sl.ut.manager.UtlMain.exec(UtlMain.java:60)
at com.sap.sl.ut.manager.UtlMain.main(UtlMain.java:56)
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.offline.OfflineToolStart.main(OfflineToolStart.java:81)
Caused by: java.lang.ClassNotFoundException: com.sap.nwmss.jdbc.sqlserver.SQLServerDriver
at com.sap.engine.offline.FileClassLoader.findClass(FileClassLoader.java:691)
at com.sap.engine.offline.FileClassLoader.loadClass(FileClassLoader.java:600)
at com.sap.engine.offline.FileClassLoader.loadClass(FileClassLoader.java:578)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:141)
at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:134)
... 16 more
caused by
java.lang.ClassNotFoundException: com.sap.nwmss.jdbc.sqlserver.SQLServerDriver
at com.sap.engine.offline.FileClassLoader.findClass(FileClassLoader.java:691)
at com.sap.engine.offline.FileClassLoader.loadClass(FileClassLoader.java:600)
at com.sap.engine.offline.FileClassLoader.loadClass(FileClassLoader.java:578)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:141)
at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:134)
at com.sap.sql.connect.OpenSQLDataSourceImpl.createConnection(OpenSQLDataSourceImpl.java:522)
at com.sap.sql.connect.OpenSQLDataSourceImpl.getConnection(OpenSQLDataSourceImpl.java:276)
at com.sap.sl.ut.manager.persistence.db.DBConnection.connectViaSecureStore(DBConnection.java:159)
at com.sap.sl.ut.manager.persistence.db.DBConnection.connect(DBConnection.java:171)
at com.sap.sl.ut.manager.persistence.db.DataBaseInfoFactory.connect(DataBaseInfoFactory.java:213)
at com.sap.sl.ut.manager.persistence.db.InfoManager.activateUsageType(InfoManager.java:124)
at com.sap.sl.ut.manager.persistence.db.DataBaseInfoFactory.activateUsageType(DataBaseInfoFactory.java:1063)
at com.sap.sl.ut.manager.command.Activate.execute(Activate.java:44)
at com.sap.sl.ut.manager.command.Command.exec(Command.java:88)
at com.sap.sl.ut.manager.UtlMain.exec(UtlMain.java:60)
at com.sap.sl.ut.manager.UtlMain.main(UtlMain.java:56)
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.offline.OfflineToolStart.main(OfflineToolStart.java:81)
Dec 7, 2009 4:51:37 PM Info : Severe (database) error. Return code: 64 -
Apply service pack to upgrade from SP12 to SP14 - am I done?
I run a local instance of SAP portal for development and testing. I manage my jCo's, maintain a local UME for myself and my fellow WDP Java developers, and regularly manually transport and apply changes from our production system to keep my content and presentation synched.
Our development, testing and production environments have been updated from SP12 to SP14, and my goal is to keep my local instance aligned by updating it to SP14 too.
I have downloaded the necessary SP12 to SP14 support package files from the support portal, and generated the XML for the SPSTab.xml file. I have successfully deployed these files using JSPM/SDM.
I have downloaded the NWDS SP14 stack, extracted the files using SAPCAR, and executed the upgrade by launching the IDE70setup.exe application.
My update does not seem complete. Did I miss a step?Hello Jennifer,
You can find the component SP level by using the following URL:
http://<host>:<port>/sap/monitoring/ComponentInfo
Note: Login to the portal first and then paste the above appropriate URL.
Thanks,
Mani.
Edited by: Manikantan Velayuthan on Sep 17, 2008 2:57 PM -
Hi all,
I want to update NetWeaver 7.0 Application Server Java SP9 to SPS11. How is it done?
I have not found an exact guide yet.
I have a .SCA file which includes SAP-JEE, verison SPS11.
Thanks,
PeterHi,
I have all necessary .sca-s, SPSTab.xml and SDMKIT.jar as well. But when I start upgrade using JSPM choosing <b>Support Pack Stack / No NWDI Control</b> I got the following error message:
"<i>No applicable support package stack(s) found for deployment in inbox directory C:\ usr\sap\trans\EPS\in.
Either you do not have a stack definition XML file, download it from SAP Service Marketplace. For more information, see SAP note 884537.
If you have downloaded the stack definition XML file, on the Logs tab page, check the SCAN_INBOX_xx.LOG files for errors. </i>"
I checked the log tab, it contains the following errors:
"<i> - Stack definition file C:\usr\sap\trans\EPS\in\SPSTab.xml is rejected. Download a new version on SAP Marketplace.
- java.lang.StringIndexOutOfBoundsException: String index out of range: -9</i>"
I also tried to upgrade choosing <b>Single Support Packages (advanced use)</b> some parts were upgraded, but many of them not:
<u>Deployed:</u>
SAP_JAVASL
BASETABLES
SAP-JEE
SAP-JEECOR
SAP_JTECHF
<u>Not deployed:</u>
ADSSAP
BI_MMR
KM-KW_JIKS
CAF-UM
SAP_JTECHS
BI_UDI
CAF
LM-TOOLS
UMEADMIN
After this I tried a "<b>New Deployment</b>" then only the following parts were in the queue:
BI_UDI
CAF
LM-TOOLS
SAP_JTECHS
UMEADM
The error was: Connection between SDM and J2E engine is broken, but I could connect to SDM using RemoteGui...
Then I tried to "<b>Resume</b>" the upgrade, but I got the following error:
"<i>Phase Error Report
An error has occured during the execution of the JSPM_MAIN phase.
java.lang.reflect.UndeclaredThrowableException: null
More information can be found in the log file C:\usr\sap\J2E\JC01\j2ee\JSPM\log\log_2007_10_09_17_01_36\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.util.diag.JavaException
java.lang.reflect.UndeclaredThrowableException: null
JSPM_MAIN
JSPMPhases
NetWeaver Upgrade
SAPJup
Java Upgrade
</i>"
Have you any ideas for the problem?
Thanks,
Peter
Maybe you are looking for
-
Ipod nano is detected but not identified
I have an ipod nano 3rd generation that works fine on my Macbook Pro laptop, but when I plug it in to my Dual 800MHz PowerPC G4, (it's an early classic stack), the computer tells me an ipod has been detected but can not identify it, and tells me to u
-
Move a query to from one user group to another user group
Hi, it's possible to move a query (SQ01) from one user group to another user group ?? Thank you.
-
Mail not showing up in Mac mail and iphone (Sky email UK)
Hi, This relates to a post from yesterday which I thought was solved, if only- ! If I check my mail on iphone it doesn't show up later in Mac mail. I have 5 accounts set up. 3 work fine, 2 don't. My Sky email account and a domain account that is set
-
Quantity Withdrawn field in production order
Hi all, I have a doubt there is a component A in production order Required quantity is 10 Initially i issue 15 qty's then the same qty gets updated in "Quantity withdrawn" field (component overview screesn) Then i reverse 3 qty's of component A,which
-
How can I get itunes to work on my laptop
itunes use to be on my laptop...for some reason i get an error message. how can i reinstall?