Stack error in PREPARE_JSPM_QUEUE phase

Hi all,
We are upgrading our Enterprise Portal system SAP NW 7.0 EHP1 to EHP2. We generated the stack XML file through MOPZ whereby we did select EHP2 Stack 9 and started the EHPI. However, it failed in the configuration step in the PREPARE_JSPM_QUEUE phase. For example, the error log says:
Software component sap.com/SAPJTECHF with version 7.01.5.4 is found on the system but in the stack it is listed with version 7.01.0.0.
For several components, it gives error as above.
Note our Portal system comprises of EP, EP CORE, AS JAVA, BI JAVA and industry package like Tax Officer. As of now we have not included the SCA file for Tax Officer (We intend to upgrade this later).
Please provide us your feedback what may be causing this error.
Thanks & regards.

Hi,
We removed the tags and repeated the phase; it ran successfully but this time the JSPM is confused about the Kernel files because we have placed both the Kernel 7.20 and Kernel 7.20 EXT files. Can both be used?
We removed the EXT files. But it is asking for these files now because I guess they are present in the XML file. Any suggestion regarding this?
--> you only need Kernel 7.20. Is either you generate the mopz or remove all entries with 7.20 EXT
As regards to the software components being correctly entered in SOLMAN (SMSY), we have only one concern - the products are displayed correctly but the SP level are not displayed at all in the Instances tab. Our Solman is on EHP1 stack 25.
--> Have you check the data in SLD? and have apply  Note 1485385 - MOpz: Collective corrections 25
Thanks,
Nicholas Chang

Similar Messages

  • Error in PREPARE_JSPM_QUEUE phase

    While attempting to install EHP4 for ECC6/EHP1 for Netweaver I am failing during the PREPARE_JSPM_QUEUE phase
    I am getting the following error and looking for suggestions.
    The parsing of SP stack file e:\download\SMSDXML_CROSSSYS_20090610175030.663.xml resulted with null value.
    My log shows the following
    Manifest attributes are missing or have badly formatted value:
    attribute keylocation is missing
    attribute keyname is missing
    attribute keyvendor is missing
    attribute keycounter is missing
    (e:\download\SAPSHRAPP13_5-20001151.SCA)
    Stack definition file e:\download\SMSDXML_CROSSSYS_20090610175030.663.xml is rejected. Download a new version on SAP Service Marketplace and try again.
    Exception has occurred during the execution of the phase.
    The parsing of SP stack file e:\download\SMSDXML_CROSSSYS_20090610175030.663.xml resulted with null value.
    Any suggestions would most appreciated.
    I could reset and start all over but have no reason to believe the resulting xml file would be any different.

    We are attempting to install EHP4 for ERP.
    This morning we discovered a new symptom:  The xml and txt files generated by MOPZ have different technical usages listed than those selected during our MOPZ transaction.
    Although I selected Financials the files generated list "Leasing/Contract A/R & A/P"   We are certain we selected the right technical usages.
    I also see no reference to JAVA in the text file but I do see Java files in the form of SCAs in the xml file.
    I am pasting the SMSDXML_DEV_20090612172403.292.txt file below
    Thanks for all the help
    [stack xml data: version=1.0]
    [SPAM_CVERS]
    SAP_APPL                      604       0003
    EA-APPL                       604       0003
    SAP_BS_FND                    701       0003
    FI-CA                         604       0003
    FI-CAX                        604       0003
    SAP_BASIS                     701       0003
    SAP_ABA                       701       0003
    SAP_BW                        701       0003
    PI_BASIS                      701       0003
    WEBCUIF                       700       0003
    ECC-DIMP                      604       0003
    EA-IPPE                       400       0015
    SAP_HR                        600       0038
    EA-DFPS                       600       0015
    EA-PS                         600       0015
    EA-GLTRADE                    600       0015
    EA-FINSERV                    600       0015
    EA-HR                         600       0038
    EA-RETAIL                     600       0015
    SEM-BW                        600       0015
    FINBASIS                      600       0015
    LSOFE                         600       0015
    ERECRUIT                      600       0015
    SAP_AP                        700       0015
    [PRDVERS]                                   
    01200314690900000432SAP ERP ENHANCE PACKAGE       2005.2 ;                       sap.com ;                      SAP ERP ENHANCE PACKAGE 2005.2 ;                                         -00000000000000
    01200314690900000463SAP ERP ENHANCE PACKAGE       EHP4 FOR SAP ERP 6.0 ;         sap.com ;                      EHP4 FOR SAP ERP 6.0 ;                                                   -00000000000000
    01200615320900001296                                                            sap.com ;                                                                                +00000000000000
    01200615320900001469SAP ERP ENHANCE PACKAGE       SAP ENH PACK 3 FOR SAP ERP 6.0sap.com ;                      SAP ENH PACK 3 FOR SAP ERP 6.0 ;                                         -00000000000000
    01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 ;   EHP4 FOR ERP 6.0_NW701 ;       sap.com ;                      EHP4 FOR SAP ERP 6.0 / NW7.01 ;                                          +00000000000000
    [SWFEATURE]                                                                               
    1                   01200615320900001296SAP ERP                       2005                          sap.com ;                      SAP ERP 6.0: SAP ECC Server
    19                  01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 ;   EHP4 FOR ERP 6.0_NW701 ;       sap.com ;                      EHP4 FOR SAP ERP 6.0 / NW7.01: Discrete Ind. & Mill Products
    23                  01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 ;   EHP4 FOR ERP 6.0_NW701 ;       sap.com ;                      EHP4 FOR SAP ERP 6.0 / NW7.01: Leasing/Contract A/R & A/P
    30                  01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 ;   EHP4 FOR ERP 6.0_NW701 ;       sap.com ;                      EHP4 FOR SAP ERP 6.0 / NW7.01: Central Applications

  • Error in prepare_jspm_queue in Ehp installer for ecc6.0

    Hi,
      When I am running EHPI for our ecc6.0, i getting error in prepare_jspm_queue phase, Log file says 'stack.xml contains no components for this system.' It searched the xml file and gave the error. But in my environment we are not using any java components. But I started the ehpi with both abap and java. now i would like to run abap only if possible. other wise what i can do to over come this error.
    any help is appreciated.
    I am attaching the log here.
    Nov 7, 2011 11:41:36 AM [Info]:                      com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:754) [Thread[main,5,main]]: Phase PREPARE/INIT/PREPARE_JSPM_QUEUE has been started.
    Nov 7, 2011 11:41:36 AM [Info]:                      com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:755) [Thread[main,5,main]]: Phase type is com.sap.sdt.j2ee.phases.PhaseTypePrepareJSPMQueue.
    Nov 7, 2011 11:41:36 AM [Info]:                   com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:409) [Thread[main,5,main]]:   Parameter inputFile=EHPComponents.xml
    Nov 7, 2011 11:41:36 AM [Info]: com.sap.sdt.j2ee.phases.jspm.JSPMQueuePreparatorFactory.createJSPMQueuePreparator(JSPMQueuePreparatorFactory.java:93) [Thread[main,5,main]]: Creating JSPM SP Stack  queue preparator.
    Nov 7, 2011 11:41:37 AM [Info]: com.sap.sdt.ucp.dialog.elim.DialogEliminatorContainer.canBeOmitted(DialogEliminatorContainer.java:96) [Thread[main,5,main]]: Dialog eliminator spStackDialogEliminator allows to omit dialog SPStackLocationDialog
    Nov 7, 2011 11:41:37 AM [Info]:                  com.sap.sdt.util.validate.ValidationProcessor.validate(ValidationProcessor.java:97) [Thread[main,5,main]]: Validatable parameter SP/STACK/LOCATION has been validated by validator RequiredFields.
    Nov 7, 2011 11:41:37 AM [Info]:                  com.sap.sdt.util.validate.ValidationProcessor.validate(ValidationProcessor.java:97) [Thread[main,5,main]]: Validatable parameter SP/STACK/LOCATION has been validated by validator SPStackLocationValidator.
    Nov 7, 2011 11:41:37 AM [Info]: com.sap.sdt.j2ee.phases.jspm.JSPMSpStackQueuePreparator.createQueue(JSPMSpStackQueuePreparator.java:115) [Thread[main,5,main]]: Using SP Stack D:\sap_downloaded\stack.xml.
    Nov 7, 2011 11:41:37 AM [Info]:                   com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseStackTag(SPXmlParser.java:488) [Thread[main,5,main]]: STACK-SHORT-NAME tag is missing. The CAPTION of the stack will be used as stack name.
    Nov 7, 2011 11:41:37 AM [Info]:                   com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseStackTag(SPXmlParser.java:582) [Thread[main,5,main]]: PRODUCT-PPMS-NAME tag is missing. The CAPTION of the product will be used as product PPMS name.
    Nov 7, 2011 11:41:37 AM [Warning]:    com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSoftwareFeatureStackTag(SPXmlParser.java:709) [Thread[main,5,main]]: Software feature SAP ERP 6.0 : SAP ECC Server - 20 (09/2011) found in stack definition file D:\sap_downloaded\stack.xml is not applicable for Java stack. This software feature will be skipped.
    Nov 7, 2011 11:41:37 AM [Info]:                   com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseStackTag(SPXmlParser.java:473) [Thread[main,5,main]]: SAP-NOTE tag is missing in the stack definition file.
    Nov 7, 2011 11:41:37 AM [Info]:                   com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseStackTag(SPXmlParser.java:488) [Thread[main,5,main]]: STACK-SHORT-NAME tag is missing. The CAPTION of the stack will be used as stack name.
    Nov 7, 2011 11:41:37 AM [Info]:                   com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseStackTag(SPXmlParser.java:582) [Thread[main,5,main]]: PRODUCT-PPMS-NAME tag is missing. The CAPTION of the product will be used as product PPMS name.
    Nov 7, 2011 11:41:37 AM [Warning]:    com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSoftwareFeatureStackTag(SPXmlParser.java:709) [Thread[main,5,main]]: Software feature SAP EHP2 FOR SAP NETWEAVER 7.0 : Application Server ABAP - 09 (09/2011) found in stack definition file D:\sap_downloaded\stack.xml is not applicable for Java stack. This software feature will be skipped.
    Nov 7, 2011 11:41:37 AM [Info]:                   com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseStackTag(SPXmlParser.java:488) [Thread[main,5,main]]: STACK-SHORT-NAME tag is missing. The CAPTION of the stack will be used as stack name.
    Nov 7, 2011 11:41:37 AM [Info]:                   com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseStackTag(SPXmlParser.java:582) [Thread[main,5,main]]: PRODUCT-PPMS-NAME tag is missing. The CAPTION of the product will be used as product PPMS name.
    Nov 7, 2011 11:41:37 AM [Warning]:    com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSoftwareFeatureStackTag(SPXmlParser.java:709) [Thread[main,5,main]]: Software feature EHP5 FOR SAP ERP 6.0 : Catch Weight Management - 06 (10/2011) found in stack definition file D:\sap_downloaded\stack.xml is not applicable for Java stack. This software feature will be skipped.
    Nov 7, 2011 11:41:37 AM [Warning]:    com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSoftwareFeatureStackTag(SPXmlParser.java:709) [Thread[main,5,main]]: Software feature EHP5 FOR SAP ERP 6.0 : Central Applications - 06 (10/2011) found in stack definition file D:\sap_downloaded\stack.xml is not applicable for Java stack. This software feature will be skipped.
    Nov 7, 2011 11:41:37 AM [Warning]:    com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSoftwareFeatureStackTag(SPXmlParser.java:709) [Thread[main,5,main]]: Software feature EHP5 FOR SAP ERP 6.0 : Defense & Public Security - 06 (10/2011) found in stack definition file D:\sap_downloaded\stack.xml is not applicable for Java stack. This software feature will be skipped.
    Nov 7, 2011 11:41:37 AM [Warning]:    com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSoftwareFeatureStackTag(SPXmlParser.java:709) [Thread[main,5,main]]: Software feature EHP5 FOR SAP ERP 6.0 : Discrete Ind. & Mill Products - 06 (10/2011) found in stack definition file D:\sap_downloaded\stack.xml is not applicable for Java stack. This software feature will be skipped.
    Nov 7, 2011 11:41:37 AM [Warning]:    com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSoftwareFeatureStackTag(SPXmlParser.java:709) [Thread[main,5,main]]: Software feature EHP5 FOR SAP ERP 6.0 : ERecruiting - 06 (10/2011) found in stack definition file D:\sap_downloaded\stack.xml is not applicable for Java stack. This software feature will be skipped.
    Nov 7, 2011 11:41:37 AM [Warning]:    com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSoftwareFeatureStackTag(SPXmlParser.java:709) [Thread[main,5,main]]: Software feature EHP5 FOR SAP ERP 6.0 : Financial Services - 06 (10/2011) found in stack definition file D:\sap_downloaded\stack.xml is not applicable for Java stack. This software feature will be skipped.
    Nov 7, 2011 11:41:37 AM [Warning]:    com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSoftwareFeatureStackTag(SPXmlParser.java:709) [Thread[main,5,main]]: Software feature EHP5 FOR SAP ERP 6.0 : Financial Supply Chain Mgmt - 06 (10/2011) found in stack definition file D:\sap_downloaded\stack.xml is not applicable for Java stack. This software feature will be skipped.
    Nov 7, 2011 11:41:37 AM [Warning]:    com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSoftwareFeatureStackTag(SPXmlParser.java:709) [Thread[main,5,main]]: Software feature EHP5 FOR SAP ERP 6.0 : Global Trade - 06 (10/2011) found in stack definition file D:\sap_downloaded\stack.xml is not applicable for Java stack. This software feature will be skipped.
    Nov 7, 2011 11:41:37 AM [Warning]:    com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSoftwareFeatureStackTag(SPXmlParser.java:709) [Thread[main,5,main]]: Software feature EHP5 FOR SAP ERP 6.0 : Learning Solution - 06 (10/2011) found in stack definition file D:\sap_downloaded\stack.xml is not applicable for Java stack. This software feature will be skipped.
    Nov 7, 2011 11:41:37 AM [Warning]:    com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSoftwareFeatureStackTag(SPXmlParser.java:709) [Thread[main,5,main]]: Software feature EHP5 FOR SAP ERP 6.0 : Human Capital Management - 06 (10/2011) found in stack definition file D:\sap_downloaded\stack.xml is not applicable for Java stack. This software feature will be skipped.
    Nov 7, 2011 11:41:37 AM [Warning]:    com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSoftwareFeatureStackTag(SPXmlParser.java:709) [Thread[main,5,main]]: Software feature EHP5 FOR SAP ERP 6.0 : Leasing/Contract A/R & A/P - 06 (10/2011) found in stack definition file D:\sap_downloaded\stack.xml is not applicable for Java stack. This software feature will be skipped.
    Nov 7, 2011 11:41:37 AM [Warning]:    com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSoftwareFeatureStackTag(SPXmlParser.java:709) [Thread[main,5,main]]: Software feature EHP5 FOR SAP ERP 6.0 : Media - 06 (10/2011) found in stack definition file D:\sap_downloaded\stack.xml is not applicable for Java stack. This software feature will be skipped.
    Nov 7, 2011 11:41:37 AM [Warning]:    com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSoftwareFeatureStackTag(SPXmlParser.java:709) [Thread[main,5,main]]: Software feature EHP5 FOR SAP ERP 6.0 : Oil & Gas - 06 (10/2011) found in stack definition file D:\sap_downloaded\stack.xml is not applicable for Java stack. This software feature will be skipped.
    Nov 7, 2011 11:41:37 AM [Warning]:    com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSoftwareFeatureStackTag(SPXmlParser.java:709) [Thread[main,5,main]]: Software feature EHP5 FOR SAP ERP 6.0 : Oil & Gas with Utilities - 06 (10/2011) found in stack definition file D:\sap_downloaded\stack.xml is not applicable for Java stack. This software feature will be skipped.
    Nov 7, 2011 11:41:37 AM [Warning]:    com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSoftwareFeatureStackTag(SPXmlParser.java:709) [Thread[main,5,main]]: Software feature EHP5 FOR SAP ERP 6.0 : Hospital - 06 (10/2011) found in stack definition file D:\sap_downloaded\stack.xml is not applicable for Java stack. This software feature will be skipped.
    Nov 7, 2011 11:41:37 AM [Warning]:    com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSoftwareFeatureStackTag(SPXmlParser.java:709) [Thread[main,5,main]]: Software feature EHP5 FOR SAP ERP 6.0 : Strategic Enterprise Mgmt - 06 (10/2011) found in stack definition file D:\sap_downloaded\stack.xml is not applicable for Java stack. This software feature will be skipped.
    Nov 7, 2011 11:41:37 AM [Warning]:    com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSoftwareFeatureStackTag(SPXmlParser.java:709) [Thread[main,5,main]]: Software feature EHP5 FOR SAP ERP 6.0 : Utilities/Waste&Recycl./Telco - 06 (10/2011) found in stack definition file D:\sap_downloaded\stack.xml is not applicable for Java stack. This software feature will be skipped.
    Nov 7, 2011 11:41:37 AM [Warning]:    com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSoftwareFeatureStackTag(SPXmlParser.java:709) [Thread[main,5,main]]: Software feature EHP5 FOR SAP ERP 6.0 : Public Sector Accounting - 06 (10/2011) found in stack definition file D:\sap_downloaded\stack.xml is not applicable for Java stack. This software feature will be skipped.
    Nov 7, 2011 11:41:37 AM [Warning]:    com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSoftwareFeatureStackTag(SPXmlParser.java:709) [Thread[main,5,main]]: Software feature EHP5 FOR SAP ERP 6.0 : Insurance - 06 (10/2011) found in stack definition file D:\sap_downloaded\stack.xml is not applicable for Java stack. This software feature will be skipped.
    Nov 7, 2011 11:41:37 AM [Warning]:    com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSoftwareFeatureStackTag(SPXmlParser.java:709) [Thread[main,5,main]]: Software feature EHP5 FOR SAP ERP 6.0 : SAP ESA ECC-SE - 06 (10/2011) found in stack definition file D:\sap_downloaded\stack.xml is not applicable for Java stack. This software feature will be skipped.
    Nov 7, 2011 11:41:37 AM [Warning]:    com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSoftwareFeatureStackTag(SPXmlParser.java:709) [Thread[main,5,main]]: Software feature EHP5 FOR SAP ERP 6.0 : PLM Core - 06 (10/2011) found in stack definition file D:\sap_downloaded\stack.xml is not applicable for Java stack. This software feature will be skipped.
    Nov 7, 2011 11:41:37 AM [Warning]:    com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSoftwareFeatureStackTag(SPXmlParser.java:709) [Thread[main,5,main]]: Software feature EHP5 FOR SAP ERP 6.0 : EAM config control - 06 (10/2011) found in stack definition file D:\sap_downloaded\stack.xml is not applicable for Java stack. This software feature will be skipped.
    Nov 7, 2011 11:41:37 AM [Warning]:    com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSoftwareFeatureStackTag(SPXmlParser.java:709) [Thread[main,5,main]]: Software feature EHP5 FOR SAP ERP 6.0 : Defense - 06 (10/2011) found in stack definition file D:\sap_downloaded\stack.xml is not applicable for Java stack. This software feature will be skipped.
    Nov 7, 2011 11:41:37 AM [Info]:                      com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSPXml(SPXmlParser.java:424) [Thread[main,5,main]]: Parsing of stack definition file D:\sap_downloaded\stack.xml has finished.
    Nov 7, 2011 11:41:37 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.
    Nov 7, 2011 11:41:37 AM [Error]: com.sap.sdt.j2ee.phases.jspm.JSPMSpStackQueuePreparator.createQueue(JSPMSpStackQueuePreparator.java:145) [Thread[main,5,main]]: The stack D:\sap_downloaded\stack.xml contains no components for this system.
    Nov 7, 2011 11:41:37 AM [Info]:                         com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:906) [Thread[main,5,main]]: Phase PREPARE/INIT/PREPARE_JSPM_QUEUE has been completed.
    Nov 7, 2011 11:41:37 AM [Info]:                         com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:907) [Thread[main,5,main]]: Start time: 2011/11/07 11:41:36.
    Nov 7, 2011 11:41:37 AM [Info]:                         com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:909) [Thread[main,5,main]]: End time: 2011/11/07 11:41:37.
    Nov 7, 2011 11:41:37 AM [Info]:                         com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:910) [Thread[main,5,main]]: Duration: 0:00:00.437.
    Nov 7, 2011 11:41:37 AM [Info]:                         com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:911) [Thread[main,5,main]]: Phase status is error.
    Regards
    K.Prakash

    Hi,
    You can start EHPi tool to upgrade ABAP as well. Please follow SAP note 1245473. Please find below extract from this note:
    < D030182 JUL/02/09 > -
    Dual-Stack Systems Only: Disabling the Java Stack Handling
    If you have updated your ERP 6.0 system with EHP4 and later want to install
    further technical usages for the ABAP stack only, you can disable the Java
    stack handling. Do not use this option for any other purpose then the one
    stated above.
    This option is available as of SAP EHP Installer 7.00 patch level 18. To
    disable the Java stack handling, start the installation program by entering
    the following additional parameter for executing the STARTUP script:
    -srvarg=/DSUService/javadisabled=true
    Thanks
    Sunny

  • Solman upgrade 7.1 error in  PREPARE_JSPM_QUEUE

    Hi All,
    We are upgrading solman from 7.0 EHP1 to 7.1 , getting the below error in  PREPARE_JSPM_QUEUE phase
    " Checking whether product SAP SOLUTION MANAGER with version 7.1 is supported by this EHP Installer.
    Feb 21, 2012 6:04:32 PM [Info]: com.sap.sdt.j2ee.phases.jspm.JSPMSpStackQueuePreparator.validateProducts(JSPMSpStackQueuePreparator.java:309) [Thread[main,5,main]]: The product is not supported.
    Feb 21, 2012 6:04:32 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."
    I had checked the note Note 1431340 - EHPI fails at PREPARE_JSPM_QUEUE phase - stack rejected, no solution got .
    Can anyone advice please
    Regards,
    Nibu Antony

    Hi
    @ Nirmal
    For solman upgrade tool is Solmanup nad version is as below:
    Client Version 1.5.0 Server Version 1.5.0 Server Port 4241 DSUService
    Version: 1.1.6  Configured Plugins 
    Plugin ABAP at Version:      
    1.0.3      
    Plugin J2EE at Version:      
    1.0.5      
    I had already gone through the thread and the note as mentioned in initially, no luck still..

  • An error has occurred during the execution of the PREPARE_JSPM_QUEUE phase

    Hi ,
         During upgrade of EHP1 - NW 700 i am getting a error in configuration step like An error has occurred during the execution of the PREPARE_JSPM_QUEUE phase
    The validation of the deploy queue was not successful. Request to check queue sapjup-queue completed with error. JSPM version is 7.01.4.0.17. Current JSPM log directory is /usr/sap/BIP/DVEBMGS00/j2ee/JSPM/log/log_2009_08_11_11_44_10.
    You can find more information in the log file /EHPI/java/log/PREPARE_JSPM_QUEUE_CSZ_01.LOG.
    Use the information provided to troubleshoot the problem. An SAP Note may provide a solution to this problem. Search for SAP Notes with the following key words: com.sap.sdt.j2ee.phases.PhaseTypePrepareJSPMQueue com.sap.sdt.sapjup.tools.sapjupjspm.JSPMRapiException The validation of the deploy queue was not successful. PREPARE_JSPM_QUEUE INIT NetWeaver Enhancement Package Installation SAPJup Java Enhancement Package Installation
    When reporting problems to SAP Support, attach the trouble ticket file /EHPI/java/log/TroubleTicket_01.txt to your message
    Plz help me to  analyze on this issue.
    Regards,
    Hari

    Hi Vasil Dimitranov
                              Thanks for your response.I have went through the log wat u said and found that only Java Patch JSPM is deployed in my system and the others patches are found be taken from the xml file and not deployed due to this below errors.
    Aug 11, 2009 11:53:33 AM [Error]: java.lang.NullPointerException:
    Aug 11, 2009 11:53:33 AM [Error]: Request to check queue sapjup-queue completed with error.
    Aug 11, 2009 11:53:33 AM [Error]: Request to check queue sapjup-queue completed with error.
    JSPM version is 7.01.4.0.17. Current JSPM log directory is /usr/sap/BIP/DVEBMGS00/j2ee/JSPM/log/log_2009_08_11_11_44_10
    Aug 11, 2009 11:53:33 AM [Info]: Message type received disconnect.
    Aug 11, 2009 11:53:33 AM [Info]: Remote connection is closed.
    Aug 11, 2009 11:53:34 AM [Warning]: Refusing connection.
    Aug 11, 2009 11:53:34 AM [Warning]: Network input/output exception has occurred: Error during read
    Aug 11, 2009 11:53:34 AM [Info]: Phase JSPM/JSPMPhases/JSPM_MAIN has been completed.
    Aug 11, 2009 11:53:34 AM [Info]: Start time: 2009/08/11 11:45:25.
    Aug 11, 2009 11:53:34 AM [Info]: End time: 2009/08/11 11:53:34.
    Aug 11, 2009 11:53:34 AM [Info]: Duration: 0:08:08.764.
    Aug 11, 2009 11:53:34 AM [Info]: Phase status is initial.
    Plz help me on this to analyze regarding the check queue sapjup-queue .
    Thanks in Advance.
    Regards,
    Hari

  • EHP4 stack 3 Java stack error

    HI,
    I'm trying to install EHP4 stack 3 on my ECC system and I'm getting an error when it gets to the Java stack load. 
    I'm getting the error in the PREPARE_JSPM_QUEUE phase
    Could not find $ component in SP stack.Check if stack is valid
    From researching the problem it looks like there is something wrong
    with my XML files that I created through the solution manager?
    this is a brand new install so I'm not sure why I'm getting this error.  Has anyone seen this before?
    Lee

    Hi Uday,
    Yes.  I read this message too but there is no solution or explenation.  A brief touch upon connecting Java to SLD which is not explained very clearly and not in any of the EHP documentation which is making me wonder if that is relevant.   I have opened a ticket with SAP but have not received a response yet.  I was hoping someone else had run into this issue and is familiar with the fix.  It seems to be an XML generation problem from what I can tell and there is a prompt saying you can pass this step with a password.  But It could also be a Java problem.  Any thoughts?
    Lee

  • Error in DEPLOY_ONLINE_DEPL phase EHPI 7.01 SPS05 DualStack ABAP+JAVA

    Hello experts,
    I'm getting an error in DEPLOY_ONLINE_DEPL phase (Downtime Roadmap) under J2EE tab in enhancement package installation in our BW System (Netweaver 7.0 SP 17 to NW 7.01 SPS 05 DualStack ABAP+JAVA)
    The system is running on High Availability server.
    Restarting Q2B 00 instance failed.
    Cannot find instance with instance number 0 on host mcho35au in the cluster.
    I'm not sure, but maybe anything is wrong with my profiles...? I don't know....
    All J2EE deployments has been successfully finished (JSPM).
    I have restarted all instances DVEBMGS00 & SCS01 and Shadow Instance DVEBMGS02. SCS01 Instance is up and running as well.
    Then I have stop EHPI Upgrade and start it again.
    DEPLOY_ONLINE_DEPL_DDB_18.LOG:
    ==========================================
    RequestController.java:178)[Thread[main,5,main]]: Deployment of queue sapjup-queue completedwith error Cannot check the state(running/stoped) of the CI.
    Restarting Q2B 00 Instance failed
    Connot find instance with instance number 0 on host mcho35au in the cluster
    ==========================================
    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 /usr/sap/trans/EPS/in/SMSDXML_CROSSSYS_20091109075202.238.xml. The deployment of the queue failed. Deployment of queue sapjup-queue completed with error Cannot check the state(running/stoped) of the CI. Restarting Q2B 00 instance failed. Cannot find instance with instance number 0 on host mcho35au in the cluster. JSPM version is 7.01.5.0.20. Current JSPM log directory is /usr/sap/Q2B/DVEBMGS00/j2ee/JSPM/log/log_2009_11_14_18_20_03.
    You can find more information in the log file /usr/sap/swdc/EHPI/java/log/DEPLOY_ONLINE_DEPL_DDB_19.LOG.
    ==========================================
    Any ideas ?
    Please help me in this case.
    I'm wating for any feedbacks.
    Thanks a lot in advance !
    Gerd
    Edited by: Gerd Schuster on Nov 14, 2009 6:23 PM

    Problem:
    The DEPLOY_ONLINE_DEPL phase (Downtime Roadmap) under J2EE tab in enhancement package installation in BW System (Netweaver 7.0 SP 17 to NW 7.01 SPS 05 DualStack ABAP+JAVA, system is running on High Availability server) stopped with error:
    RequestController.java:178)[Threadmain,5,main]: Deployment of queue sapjup-queue
    completedwith error Cannot check the state(running/stoped) of the CI.
    Restarting Q2B 00 Instance failed
    Connot find instance with instance number 0 on host mcho35au in the cluster
    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 /usr/sap/trans/EPS/in/SMSDXML_CROSSSYS_20091109075202.238.xml. The deployment
    of the queue failed. Deployment of queue sapjup-queue completed with error Cannot check the
    state(running/stoped) of the CI. Restarting Q2B 00 instance failed. Cannot find instance with instance
    number 0 on host mcho35au in the cluster. JSPM version is 7.01.5.0.20. Current JSPM log directory
    is /usr/sap/Q2B/DVEBMGS00/j2ee/JSPM/log/log_2009_11_14_18_20_03.
    You can find more information in the log file /usr/sap/swdc/EHPI/java/log/DEPLOY_ONLINE_DEPL_DDB_19.LOG.
    Solution:
    stop all instances (shadow instance, SCSxx)
    In a High Availability server you have to modify few parameters in DEFAULT profile temporarily (replace alias-servername with real hostname):
    DEFAULT.PFL: SAPLOCALHOST = mcho35au
    DEFAULT.PFL: SAPDBHOST = mcho35au
    DEFAULT.PFL: rdisp/mshost = mcho35au
    # DEFAULT.PFL: rdisp/vbname = mcho35au_Q2B_00  (<- maby it'snot relevant)
    # DEFAULT.PFL: rdisp/enqname = mcho35au_Q2B_00  (<- maby it'snot relevant)
    # DEFAULT.PFL: rdisp/btcname = mcho35au_Q2B_00  (<- maby it'snot relevant)
    DEFAULT.PFL: rdisp/sna_gateway = mcho35au
    in instance DVEBMGS00 switch profile icman = 0 to 1 (otherwise J2EE instance will not started)
    startsap DVEBMGS00
    Restart EHPI Upgrade (EHPI keep the old DEFAULT.PFL settings in shared memory!)
    ./EHPI/STARTUP jce_policy_zip=90000125.zip
    Repeat phase DEPLOY_ONLINE_DEPL
    Gerd
    Edited by: Gerd Schuster on Nov 16, 2009 2:59 PM

  • 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
    Stane

    Hi 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 XPRA_EXECUTION phase while upgrading patch in solman 7.0.

    Hi all,
    I was upgrading solman system( 7.0 ) from patch level 10 to patch level 13 , while upgrading it throwed error in XPRA_EXECUTION phase. Error is in SAPK-40003INCPRXRPM and SAPK-40004INCPRXRPM.
    Error log is as given below :
    Post-import method SWO_OBJTYPE_AFTER_IMPORT started for SOBJ L, date and time: 20090415070141
    Object type 'BUS2178' generated successfully
    Object type 'BUS2177' generated successfully
    Object type 'BUS2176' generated successfully
    Object type 'BUS2175' could not be generated
    The type 'DPR_SCHEDULING' is unknown.
    Object type 'BUS2174' could not be generated
    The type 'DPR_SCHEDULING' is unknown.
    Object type 'BUS2173' could not be generated
    The type 'DPR_SCHEDULING' is unknown.
    Object type 'BUS2172' could not be generated
    Please help me out as i am stuck.

    HI,
    Did u check is there any dependencies of Solman support packages with other support pakckages.
    Object type 'BUS2174' could not be generated it seems there is a issues with dependencies only.
    Please check the stack guide once then u will come to know all the dependencies.
    -Srini

  • Error in preprocessing phase

    Hi All ,
    We are facing error in preprocessing phase of upgrade to EHP 7 ,Let me know if anyone can help us in this critical situation
    System details:Oracle 11gr2,Linux x86-64 ,
    Below is the error :
    During the phase MAIN_SHDIMP/SUBMOD_SHD2_RUN/RFCDEST_CREATE_S2OX in
    Pre-processing of the SUM we are facing below error.
    1 ETQ233 Calling function module "FUNCTION_EXISTS" by RFC
    2 ETQ373 parameter "FUNCNAME" = "RFC_DESTINATION_CREATE"
    1 ETQ234 Call of function module "FUNCTION_EXISTS" by RFC succeeded
    4 ETQ010 Date & Time: 20140912043336
    1 ETQ359 RFC Login to: System="XXX", AsHost="sapXXXpas" Nr="12",
    GwHost="sapa10pas", GwService="sapgwZZ"
    2 ETQ232 RFC Login succeeded
    4 ETQ010 Date & Time: 20140912043336
    1 ETQ233 Calling function module "RFC_DESTINATION_CREATE" by RFC
    2 ETQ373 parameter "DESTINATION_NAME" = "SAP_UPGRADE_ORIG_SYSTEM"
    2 ETQ373 parameter "USER" = "DDIC"
    2 ETQ373 parameter "HOST" = "sapXXXpas"
    2 ETQ373 parameter "SYSTEMNR" = "11"
    2 ETQ373 parameter "CHECK" = "X"
    1EETQ235 Call of function module "RFC_DESTINATION_CREATE" by RFC failed
    (error-status "3")
    2EETQ360 RFC of "RFC_DESTINATION_CREATE" failed:
    2EETQ361 code/exception : 3
    2EETQ362 key : CALL_FUNCTION_NO_DEST
    2EETQ399 RFC destination SAP_UPGRADE_ORIG_SYSTEM does not exist.
    Regards
    Bharat
    Mob No: 91 9008804153

    Hi Reagan ,
    The issue was taken to SAP development security team :::Below is the  weird issue ::
    Firstly ,for the authorizations to work correctly, all authorization tables must be in a consistent state as below :
    ust04, ust10c, ust10s, ust12, usrbf2, usrbf3.
    If we  want to maintain authorizations, also usr04, usr10, usr12 are  required.
    But here , a mismatch of tables usrbf2 and usrbf3  in 2 instances are the reason for the stuck in the upgrade :::
    SQL> select count(*) from sapsr3.USRBF2 where MANDT = '000' and BNAME =
    'DDIC';
    COUNT(*)
    2997
    SQL> select count(*) from sapsr3.USRBF3 where MANDT = '000' and BNAME =
    'DDIC';
    COUNT(*)
    1
    SQL>
    SQL> select count(*) from sapsr3shd.USRBF2 where MANDT = '000' and
    BNAME =
    'DDIC';
    COUNT(*)
    673
    SQL> select count(*) from sapsr3shd.USRBF3 where MANDT = '000' and
    BNAME =
    'DDIC';
    COUNT(*)
    1
    This issue was resolved by SAP and then upgrade went fine ,This is not an issue with password of DDIC !!!!!
    Regards
    Ram

  • Error during upgrade phase JOB_RSUPGCUA_SHD

    Hi Everyone,
    We are in the process of completing a combined ERP 6.0 Upgrade / Unicode Conversion.  Our starting release is ECC 5.0 (ABAP only) and we are running Oracle 10.2.0.2 on AIX 5.3. 
    We are receiving the following error in phase JOB_RSUPGCUA_SHD:
    1 ETQ201XEntering upgrade-phase "JOB_RSUPGCUA_SHD" ("20080812163717")
    2 ETQ366 Connect variables are set for shadow instance access
    4 ETQ399 System-nr = '56', GwService = 'sapgw56'
    4 ETQ399 Environment variables:
    4 ETQ399   dbs_ora_schema=SAPR3
    4 ETQ399   auth_shadow_upgrade=1
    4 ETQ260 Starting batchjob "RSUPGCUAGEN111"
    4 ETQ010 Date & Time: 20080812163717
    4 ETQ260 Starting batchjob "RSUPGCUAGEN111"
    4 ETQ230 Starting RFC Login to: System = "ENP", GwHost = "aix12j1", GwService = "sapgw56"
    4 ETQ359 RFC Login to: System="ENP", Nr="56", GwHost="aix12j1", GwService="sapgw56"
    4 ETQ232 RFC Login succeeded
    4 ETQ233 Calling function module "SUBST_START_BATCHJOB" by RFC
    2EETQ235 Call of function module "SUBST_START_BATCHJOB" by RFC failed (error-status "10")
    2EETQ261 Start of batchjob "RSUPGCUAGEN111" failed
    1EETQ203 Upgrade phase "JOB_RSUPGCUA_SHD" aborted with errors ("20080812163717")
    We originally had some issues with the shadow system not starting in phase START_SHDI_FIRST.  The source of the problem was the value of paramter ipc/shm_psize_40 in the instance profile of the shadow system.  When we ran "sappfpar check" on the profile, the output indicated that the paramter was too small.  We backed up the profile, increased the parameter to the value "sappfpar check" recommended and then stopped the shadow system via "SAPup stopshd."  We then repeated the phase.  The shadow instance was started successfully and the upgrade proceeded with subsequent phases.
    We encountered the error above several phases later.  The shadow instance is started and I am able to login with user DDIC.  As detailed in the error message above, function module SUBST_START_BATCHJOB is aborting with error code 10.  Based on what I can interpret from source code of the function module, this seems to indicate that there is a problem with the program values.  The SM21 log indicates that "Program name RSUPGCUAGEN111 is invalid." 
    What do we need to do to get past this error?
    Thanks in advance for any assistance,
    Tommye

    for our case it was that the shadow instance was not completely stsarted, some processes were down, cause the ipc pool 40 was too small, i found the error in the killed work processes.
    Probleme resolved as susch. i hope it will help someone.
    Regards

  • Support Pack upgrade error in Import Phase

    Hello,
    Currently I am upgrading SCM system with Support pack level 12 to 20 . When i am applying Basis 12 to 20. I got an error in Import_Proper phase.
    Could you please help me on this? I tried and still searching solution for this..But no luck...
    Os is : AIX and
    Log File:                /usr/sap/trans/log/SAPIB70013.xxx
    Main import
    Transport request   : SAPKB70013
    System              : xxxx
    tp path             : tp
    Version and release: 372.04.71 700
    child process 934006 terminated -> setting rc=12 for this import portion
    sap_dext called with msgnr 1:
    db call info -
    function:   db_report_interface
    fcode:      CLOSE_LINE_MODE
    tabname:    SOURCE
    len (char): 40
    key:        CL_OBJECT_COLLECTION==========CT
    retcode:    1
    SQL error -913 accessing  : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -913, ER
    child process 1212554 terminated -> setting rc=12 for this import portion
    sap_dext called with msgnr 1:
    db call info -
    function:   db_report_interface
    fcode:      CLOSE_LINE_MODE
    tabname:    SOURCE
    len (char): 40
    key:        CL_WDR_APPLICATION_WINDOW=====CT
    retcode:    1
    SQL error -913 accessing  : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -913, ER
    child process 1171520 terminated -> setting rc=12 for this import portion
    sap_dext called with msgnr 1:
    db call info -
    function:   db_report_interface
    fcode:      CLOSE_LINE_MODE
    tabname:    SOURCE
    len (char): 40
    key:        CL_WDY_MD_EVENT_SOURCE========CI
    retcode:    1
    SQL error -913 accessing  : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -913, ER
    child process 1331412 terminated -> setting rc=12 for this import portion
    sap_dext called with msgnr 1:
    db call info -
    function:   db_xrtab
    fcode:      RT_MI_LOAD
    tabname:    ECSCR_DATA
    len (char): 106
    key:        EC_TEST_DATA                  00000000P10                           IECATTDEFAULT
    retcode:    1
    SQL error -904 accessing  : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -904, ER
    insert / update sequence failed due to an error in DBI.
    maybe there's a concurrent process which inserted this table entry at the same time.
    insert / update sequence failed due to an error in DBI.                       
    maybe there's a concurrent process which inserted this table entry at the same time.
    child process 1310922 terminated -> setting rc=12 for this import portion
    sap_dext called with msgnr 1:
    db call info -
    function:   db_xrtab
    fcode:      RT_MI_END
    tabname:    WDY_APP_PROPERTY
    len (char): 64
    key:        DEMO_UIEL_DROPDOWN_BY_IDX     DEMO_VIEW
    retcode:    1
    SQL error -904 accessing  : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -904, ER
    import portion 018446 - 999999 not imported because the child processes died for unknown reason
    child process 1310924 terminated -> setting rc=12 for this import portion
    sap_dext called with msgnr 1:
    db call info -
    function:   db_report_interface
    fcode:      CLOSE_LINE_MODE
    tabname:    SOURCE
    len (char): 40
    key:        CL_WDY_MD_OUTGOING_EVENT======CT
    retcode:    1
    SQL error -913 accessing  : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -913, ER
    child process 1286192 terminated -> setting rc=12 for this import portion
    sap_dext called with msgnr 1:
    db call info -
    function:   db_xrtab
    fcode:      RT_MI_LOAD
    tabname:    ECSCR_DATA
    len (char): 106
    key:        EC_TEST_DATA                  00000000P10                           IECATTDEFAULT
    retcode:    1
    SQL error -904 accessing  : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -904, ER
    import portion 009158 - 018411 not imported because the child processes died for unknown reason
    import portion 018412 - 018527 not imported because the child processes died for unknown reason
    import portion 018528 - 999999 not imported because the child processes died for unknown reason
    sap_dext called with msgnr 1:
    db call info -
    function:   db_xrtab
    fcode:      RT_MI_LOAD
    tabname:    ECSCR_DATA
    len (char): 106
    key:        EC_TEST_DATA                  00000000P10                           IECATTDEFAULT
    retcode:    1
    SQL error -904 accessing  : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -904, ER
    Main import
    End date and time : 20100909034914
    Ended with return code:  ===> 12 <===
         |   ######################################                     
    Thanks and Regards,
    Sankar
    SAP BASIS Consultant

    Hi,
    Thanks for you reply. I restarted import but no luck still. I activated some object also not working. when i call SPAM it is not going to the SPAM pager. Showing dump...
    Runtime Errors         CALL_FUNCTION_NOT_FOUND
    Except.                CX_SY_DYN_CALL_ILLEGAL_FUNC
    Date and Time          10.09.2010 09:41:37
    Short text
         Function module "POSS_UIREQ_OPT_SUBMIT" not found.
    What happened?
         The function module "POSS_UIREQ_OPT_SUBMIT" is called,
         but cannot be found in the library.
         Error in the ABAP Application Program
         The current ABAP program "SAPLSTXC" had to be terminated because it has
         come across a statement that unfortunately cannot be executed.
    Error analysis
         An exception occurred that is explained in detail below.
         The exception, which is assigned to class 'CX_SY_DYN_CALL_ILLEGAL_FUNC', was
          not caught in
         procedure "OPEN_FORM" "(FUNCTION)", nor was it propagated by a RAISING clause.
         Since the caller of the procedure could not have anticipated that the
         exception would occur, the current program is terminated.
         The reason for the exception is:
         The program "SAPLSTXC" contains the CALL FUNCTION statement.
         The name of the function module to be called is "POSS_UIREQ_OPT_SUBMIT".
         No function module exists with the name "POSS_UIREQ_OPT_SUBMIT".
         All function modules are listed in the Function Library (SE37).
    Possible reasons:
    a) Wrong name specified. Pay particular attenti
        upper/lower case and underscores ("_").
        or
    b) Transport error
    c) In the case of an enqueue/dequeue module,
        the lock object may not have been activated
        (ABAP/4 Dictionary).
    When i tried to check function module it is not there..
    Could you please help on this?
    Regards,
    Sankar Basis Consultant

  • PI 7.1 upgrade error in GETSYNC_PROFILES_CHANGED phase

    Hello
    Currently I am upgrading an XI 7.0 system to PI 7.1. The downtime phases have just started and I've hit an error in the phase 'GETSYNC_PROFILES_CHANGED'; the error is 'Not enough space for string replacement'. Based on the phase name, and the previous phases, it looks as if the error is something to do with the profiles. The relevant upgrade logs have no useful info in them except for the string space message.
    I have done the usual SDN, SAP Marketplace and Google searches but could not find an answer to my problem. I have also opened a high priority call with SAP but they have not come up with an answer yet. Does anybody have any useful advice?
    The system being upgraded is running on Windows 2003 Server R2 64bit, has an Oracle 10.2.0.4 DB, and the source system was XI/PI 7.0 SP15.
    Thanks.

    Hello Rohit
    Freespace is more than sufficient:
    C:\ = 5.2GB (O/S)
    D:\ = 18.9GB (Oracle & SAP)
    E:\ = 8.53GB (Oracle)
    Andrew
    Edited by: Andrew Turvey on May 28, 2009 3:48 PM

  • Error in ABAP_Import Phase

    Dear Guru's,
    We are facing some issue on ABAP Import phase, out of 29 Import Monior jobs 2 jobs gets failed.
    Error in Import_ABAP Phase, 2 jobs failed
    Loading of 'DD03L' import package: ERROR
    Loading of 'SACONT01' import package: ERROR
    could anyone suggest me, what could be done to resolve this issue.
    regards,
    Guna

    Hi,
    Thanks for your information.
    We tried with retry option, still in same position.
    We're doing solution manager 7.0 installation on AIX 5.
    (DB) INFO: SACONT01 deleted/truncated #20100429153529
    (DB6) Using LOAD API for table SACONT01
    (RFF) ERROR: invalid checksum in data file "/hm/cdmedia/solman7.0/51033518_Expor
    t2/EXP3/DATA/SACONT01.001"
                 current table was "SACONT01"
    (DB) INFO: disconnected from DB
    /usr/sap/SM1/SYS/exe/run/R3load: job finished with 1 error(s)
    /usr/sap/SM1/SYS/exe/run/R3load: END OF LOG: 20100429153530
    Suggestions appreciated.
    regards,
    Guna

  • Error in ACTIVATE_CURRENT_USAGES phase of portal upgrade (NW04 to NW04s)

    hello gurus,
    i am upgrading Netweaver 04 to netweaver 04s (Enterprise Portal)
    oracle upgrade from 9.2.0.7 to 10.2.0.1 successfully
    but i am getting error in 78 phase out 100 in java upgrade program management
    ACTIVATE_CURRENT_USAGES
    i am unable to track the cause.......
    log file is shown below
    kindly help......
    its urgent
    <!LOGHEADER[START]/>
    <!HELP[Manual modification of the header may cause parsing problem!]/>
    <!LOGGINGVERSION[1.5.3.7185 - 630]/>
    <!NAME[D:\usr\sap\jupgrade\log\ACTIVATE_CURRENT_USAGES_ACU_07.LOG]/>
    <!PATTERN[ACTIVATE_CURRENT_USAGES_ACU_07.LOG]/>
    <!FORMATTER[com.sap.tc.logging.ListFormatter]/>
    <!ENCODING[Cp1252]/>
    <!LOGHEADER[END]/>
    #1.5#C000AC1908C2000000000029014A8CD1000432D6B5DD7008#1181797662421#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:713)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:713)#Java###Phase has been started.#1#UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES#
    #1.5#C000AC1908C200000000002A014A8CD1000432D6B5DDAE88#1181797662437#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:714)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:714)#Java###Phase type is .#1#com.sap.sdt.ucp.phases.PhaseTypeExecuteTask#
    #1.5#C000AC1908C200000000002B014A8CD1000432D6B5DDAE88#1181797662437#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:338)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:338)#Java###  Parameter =#2#inputFile#ExecuteTasks.xml#
    #1.5#C000AC1908C200000000002C014A8CD1000432D6B5DDAE88#1181797662437#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:338)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:338)#Java###  Parameter =#2#taskName#ACTIVATE_CURRENT_USAGES#
    #1.5#C000AC1908C200000000002D014A8CD1000432D6B5DDAE88#1181797662437#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.ucp.phases.PhaseTypeExecuteTask.checkParameters(PhaseTypeExecuteTask.java:191)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.PhaseTypeExecuteTask.checkParameters(PhaseTypeExecuteTask.java:191)#Java###Phase parameters have been checked. All required phase parameters have been set.#1#2#
    #1.5#C000AC1908C200000000002E014A8CD1000432D6B5F009C0#1181797663640#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.tools.cfg.ConfigurationBuilder.buildConfiguration(ConfigurationBuilder.java:297)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.cfg.ConfigurationBuilder.buildConfiguration(ConfigurationBuilder.java:297)#Java###Configuration has been built from input file .#1#D:/usr/sap/jupgrade/config/ExecuteTasks.xml#
    #1.5#C000AC1908C200000000002F014A8CD1000432D6B5F13A70#1181797663718#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.tools.cfg.ConfigurationBuilder.buildConfiguration(ConfigurationBuilder.java:297)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.cfg.ConfigurationBuilder.buildConfiguration(ConfigurationBuilder.java:297)#Java###Configuration has been built from input file .#1#D:/usr/sap/jupgrade/config/ExecuteTasks_WIN.xml#
    #1.5#C000AC1908C2000000000030014A8CD1000432D6B5F13A70#1181797663718#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.tools.cfg.ConfigurationBuilder.buildGlobalConfiguration(ConfigurationBuilder.java:251)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.cfg.ConfigurationBuilder.buildGlobalConfiguration(ConfigurationBuilder.java:251)#Java###Global configuration has been built from input file .#1#D:/usr/sap/jupgrade/config/ExecuteTasks.xml#
    #1.5#C000AC1908C2000000000031014A8CD1000432D6B5F13A70#1181797663718#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##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#2#com.sap.engine.offline.OfflineToolStart#
    #1.5#C000AC1908C2000000000032014A8CD1000432D6B5F178F0#1181797663734#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##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#  #C:
    j2sdk1.4.2_09
    jre
    bin
    java.exe -cp d:/usr/sap/W60/SYS/global/sltools/sharedlib/launcher.jar;d:/usr/sap/W60/SYS/global/sltools/sharedlib; com.sap.engine.offline.OfflineToolStart com.sap.sl.ut.manager.UtlMain d:/usr/sap/W60/SYS/global/sltools/sharedlib;D:/usr/sap/W60/SYS/global/security/lib/tools;D:/usr/sap/w60/jc00/exe/classes12.jar -activated -sid=W60 -dsn=jdbc/pool/W60 -ssprops=D:/usr/sap/W60/SYS/global/security/data/SecStore.properties -ssk=D:/usr/sap/W60/SYS/global/security/data/SecStore.key -log=D:
    usr
    sap
    jupgrade
    log/ACTIVATE_USAGE_AS.LOG -prod_name=NetWeaver -usage_name=AS -usage_vendor=sap.com -action=true#
    #1.5#C000AC1908C2000000000033014A8CD1000432D6B5F178F0#1181797663734#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##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#  #D:
    usr
    sap
    jupgrade
    log
    ACTIVATE_USAGE_AS_ACU_01.OUT#
    #1.5#C000AC1908C2000000000034014A8CD1000432D6B5F178F0#1181797663734#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#Java###Process ID has been started.#1#2#
    #1.5#C000AC1908C2000000000035014A8CD1000432D6B5F1B770#1181797663750#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#Java###Waiting for process ID , name to finish.#2#2#java.exe#
    #1.5#C000AC1908C2000000000036014A8CD1000432D6B6B9BE78#1181797676859#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#Java###Process ID , name has been finished, exit code .#3#2#java.exe#64#
    #1.5#C000AC1908C2000000000037014A8CD1000432D6B6B9BE78#1181797676859#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:735)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:735)#Java###Exception has occurred during the execution of the phase.##
    #1.5#C000AC1908C2000000000038014A8CD1000432D6B6B9FCF8#1181797676875#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.tools.execute.AbstractExtProcessOperation.generateResultProcessingException(AbstractExtProcessOperation.java:579)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.tools.execute.AbstractExtProcessOperation.generateResultProcessingException(AbstractExtProcessOperation.java:579)#Java###Could not activate usage AS. Could not execute 'C:
    j2sdk1.4.2_09
    jre
    bin
    java.exe -cp d:/usr/sap/W60/SYS/global/sltools/sharedlib/launcher.jar;d:/usr/sap/W60/SYS/global/sltools/sharedlib; com.sap.engine.offline.OfflineToolStart com.sap.sl.ut.manager.UtlMain d:/usr/sap/W60/SYS/global/sltools/sharedlib;D:/usr/sap/W60/SYS/global/security/lib/tools;D:/usr/sap/w60/jc00/exe/classes12.jar -activated -sid=W60 -dsn=jdbc/pool/W60 -ssprops=D:/usr/sap/W60/SYS/global/security/data/SecStore.properties -ssk=D:/usr/sap/W60/SYS/global/security/data/SecStore.key -log=D:
    usr
    sap
    jupgrade
    log/ACTIVATE_USAGE_AS.LOG -prod_name=NetWeaver -usage_name=AS -usage_vendor=sap.com -action=true', return code '64'. You can check the file(s) 'D:
    usr
    sap
    jupgrade
    log/ACTIVATE_USAGE_AS_ACU.OUT', 'D:
    usr
    sap
    jupgrade
    log/ACTIVATE_USAGE_AS_ACU.ERR' to which the output of the process has been redirected.##
    #1.5#C000AC1908C2000000000039014A8CD1000432D6B6B9FCF8#1181797676875#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.tools.execute.AbstractExtProcessOperation.execute(AbstractExtProcessOperation.java:176)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.tools.execute.AbstractExtProcessOperation.execute(AbstractExtProcessOperation.java:176)#Java###Error while processing the result.##
    #1.5#C000AC1908C200000000003A014A8CD1000432D6B6BA3790#1181797676890#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.ucp.phases.PhaseTypeExecuteTask.execute(PhaseTypeExecuteTask.java:173)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.ucp.phases.PhaseTypeExecuteTask.execute(PhaseTypeExecuteTask.java:173)#Java###Error while executing PhaseTypeExecuteTask with input file ExecuteTasks.xml and task ACTIVATE_CURRENT_USAGES.##
    #1.5#C000AC1908C200000000003B014A8CD1000432D6B6BA3790#1181797676890#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:779)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:779)#Java###Phase has been completed.#1#UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES#
    #1.5#C000AC1908C200000000003C014A8CD1000432D6B6BA3790#1181797676890#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:780)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:780)#Java###Start time: .#1#2007/06/14 10:37:42#
    #1.5#C000AC1908C200000000003D014A8CD1000432D6B6BA3790#1181797676890#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:781)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:781)#Java###End time: .#1#2007/06/14 10:37:56#
    #1.5#C000AC1908C200000000003E014A8CD1000432D6B6BA3790#1181797676890#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:782)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:782)#Java###Duration: .#1#0:00:14.453#
    #1.5#C000AC1908C200000000003F014A8CD1000432D6B6BA3790#1181797676890#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:783)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:783)#Java###Phase status is .#1#error#
    waiting for solution
    thankx in advance....
    shoeb

    Could you please share us the solution?

Maybe you are looking for

  • CRM_ORDER_MAINTAIN - Appointments

    Hi all A client is using the CRM interaction centre (trxn. CIC0). When a date is set in a transaction within CIC0, they want that date copied to all the follow up activities as well when the user saves. We've already used BADI ORDER_SAVE and FM's CRM

  • Other than the GPS chip in ipad 2 wifi+3g...

    Are there anything else the 3G version has that a regular wifi only doesn't have? I am still having a tough time deciding which one to get tomorrow. I already have a data plan on my iphone 4, but it would be nice to have the option to add a data plan

  • Installing AS and Database on one machine

    Hi all I want to install Oracle Database 10.2.0.3 and Oracle AS 10.1.2.0.2 (Business Intelligence and Forms Developer Topology) on one linux machine (AS 4). I can install the database and the AS as suggested in the installation guides. But now my mac

  • Reply all when CC List Truncated

    Hi, Some of us in our organization noticed that if there are more than 32 cc: addresses on a message received, that a reply-to-all message would only go to those 32 addresses (plus whomever was in the To: fields), and none of the original recipients

  • Message saying i have mail version 6.6 (1510/1503). Cant be used on Mac OX version 10.8.3. what does this mean

    Tonight  I have clicked onto  mail and this message appeared saying i have mail version 6.6 (1510/1503). Cant be used on Mac OX version 10.8.3. Don't know what has happened.  Can anyone help.