Error in PREPARE_JSPM_QUEUE during EHP4 install

Question

Hello,
I'm upgrading my ECC 6.0 system to ECC 6.0 EHP4. in the JAVA configuration phase PREPARE_JSPM_QUEUE I get the following error:
Apr 5, 2011 4:44:04 PM [Error]: Software component sap.com/SAP_JTECHF with version 7.00.21.8 is found on the system but in the stack it is listed with version 7.00.21.0.
Apr 5, 2011 4:44:04 PM [Error]: Software component sap.com/SAP_JTECHS with version 7.00.21.14 is found on the system but in the stack it is listed with version 7.00.21.0.
Apr 5, 2011 4:44:04 PM [Error]: Software component sap.com/LM-TOOLS with version 7.00.21.1 is found on the system but in the stack it is listed with version 7.00.21.0.
Apr 5, 2011 4:44:04 PM [Error]: Software component sap.com/CORE-TOOLS with version 7.00.22.1 is found on the system but in the stack it is listed with version 7.00.22.0.
Apr 5, 2011 4:44:04 PM [Error]: Software component sap.com/SAP-JEE with version 7.00.21.8 is found on the system but in the stack it is listed with version 7.00.21.0.
I have configured the JAVA stack in the Solution Manager so the XML stack contains SP level 21 for software component SAP_JTECHS. What I donu2019t understand is how could the installer read a SP level 21.8. I didn't know the sub versions exists.
Does anyone know how to fix this problem so I could go on with the upgrade.
Kind regards,
Richard Meijn

Answer 1

Hello Richard,
check the XML file generated, on the entries for SAP_JTECHF, SAP_JTECHS, LM-TOOLS, CORE-TOOLS and SAP-JEE components.
For example:
- <software-component>
  <caption>SAP_JTECHF</caption>
  <ppms-number>xxxxxxxxxxxxxxxxxxx</ppms-number>
  <runtime-type>J2EE</runtime-type>
  <name>XXXXXXXXXXXXX</name>
  <version>7.00</version>
  <vendor>sap.com</vendor>
- <support-package>
  <caption>SP021 for SAP_JTECHF 7.00</caption>
  <name>SP021</name>
  <vendor>sap.com</vendor>
  <ppms-number>xxxxxxxxxxxxxxxxxxx</ppms-number>
  <sp-level>021</sp-level>
  <patch-level>0</patch-level>
- <archives>
You'll see on the "patch level" entry (which means the sub version you're referring to) that it should be '0' on the XML file.
The main possibility for this is that MOPZ generated the XML file incorrectly, based on the information it fetched from the SolutionManager. This issue is occuring probably because you have an outdated information or there are missing information in transaction SMSY. Check in SMSY if the Software components for the system are up to date. If not you need send the
system data to a SLD and use LANDSCAPE FETCH to update the JAVA data in SMSY. After have JAVA system components data updated in SMSY you must create a new mopz transaction. This new mopz transaction will not include wrong information in the XML file then.
(remember you need a SLD to maintain the JAVA information. You can use the SLD of the solution manager. Go to the Visual Administrator of the system that you want upgrade and in SLD Data Supplier Service, maintain the User/password/host/port of the SLD of solman and trigger the service. The SLD of solman will be updated with the JAVA information of this system and after run LANDSCAPE fetch job, SMSY will be populated with JAVA information up to date. If you created manually the JAVA instances, MOPZ will not know the SOURCE software components and this will have a big impact in the calculation as MOPZ will not know the source components version.)
Alternatively you can create a XML file manually (with the correct SP and patch levels, of course). This method is supported too, just keep in mind that if you have a ERP system that you want upgrade to EHP4 or a higher EHP version, you must
use MOPZ. If you're implementing EHP1 in Netweaver, you can use the XML file generated in the Service Marketplace without problems.
I hope all this information helps.
Best regards,
Tomas Black