Skip to Content

Hello Friends,

Hopefully you have read my first document Solution Manager 7.2 – Upgrade – I – Technical Checks and Preparations. Now you have your solution Manager ready to upgrade new version. ” Isn’t that exciting?” Lets begain our ride to upgrade Solution Manager

  • Install minimum support pack stack 01 in to your existing solution manager 7.1 before start upgrading to Solution manager 7.2
  • Take the good backup of your existing Solution Manager system
  • Upgrade Wily Introscope Enterprise Manager to latest version

          Upgrade Guide can be found at link below

          SAP reference Note: 797147 – Introscope Installation for SAP Customers

  • Make sure LMDB have no errors and Solution manager system verification check successfully completed.

Transaction Code: LMDB


  • Upload all System data in LMDB to SAP Support Portal


          SAP Notes:

               2002546 – CP: Direct upload of landscape data to the customer profile

               2177157 – Uploading system data in Solution Manager 7.2 SP01

               1891878 – “Upload to SAP Support Portal” in LMDB does not send data

               1784080 – System information upload from LMDB to Support Portal fails

  • Check your existing solution manager system preparation, Basic configuration and Managed system configuration up-to-date
  • Upgrade CR_CONT in SLD to latest available version

               SAP reference Note: 669669 – Update of SAP System Component Repository in SLD

               After fully synchronization completed deactivate synchronization

               Part 1


               Part 2


               Set SLD to read only mode


  • Change diagnosis agents’ authentication via certificate (SolMan SPS 11 or High)

          2013578 – Diagnostics Agent cannot connect to the Solman using certificate based method – Solman 7.10 SP11/SP12/SP13/SP14


          P4 Port settings


          Generate Certificate






          Restart System and check all Agents are connected


              Note: Make sure all Diagnostic agent JVM is higher that 1.6

  • Use Maintenance Planner to create stack file and download STACK Files


  • Perform Content Activation as required

               For more information, please look at:

               If you have use none of functionality in solution manager 7.1 you can skip “Content Activation”

                    Data and Applications Affected:

               Solution Documentation.

               Change Request Management

               Quality Gate Management

               IT Portfolio and Project Management

               Test Management

               Business Process Monitoring

  • Start SUM and Upgrade SAP Solution Manager
  • Apply Notes as per SUM list


     NW_JAVA  source Media Number : 51050526


          Note: During Deployment remove any 7.02 deploy version from JAVA calculated queue as per SAP note: 2227300

BI_MMR 7.02         

Can not upgrade


BI_UDI 7.02      

If definitely need upgrade to

BI_UDI 7.40


If definitely need upgrade to



If definitely need upgrade to


LM-TOOLS 7.02 

If definitely need upgrade to

SAP IKS 7.40


If definitely need upgrade to


CAF 7.02 

If definitely need upgrade to

SAP CAF 7.40

          SAP ABAP Components


          Perform this step prior system downtime in SUM tool (Step 5.5)



                    Execute Preprocessing for SolMan SW Maintanance:


                    Note: This will lock other dialog users, enable DAA Maintanance mode, unregister web services and stop all background jobs

     Now Continue till SUM Procees complete

               2016-03-06 9-15-07 AM.png

Now as you see upgrade process is completed we will move to next part of upgrade process and it is regarding Support pack stack 01 corrections.

Thank you for reading and please dont forget to provide feedback.

Yogesh Patel

Solution Manager 7.2 – Upgrade – I – Technical Checks and Preparations

Solution Manager 7.2 – Upgrade – II – Actual Upgrade Process

Solution Manager 7.2 – Upgrade – III – Dual Stack Split

Solution Manager 7.2 – Upgrade – IV – Correction After Dual Stack Split

Solution Manager 7.2 – Upgrade – V – SolMan Support Pack Stack 01 Correction

To report this post you need to login first.


You must be Logged on to comment or reply to a post.

      1. Former Member

        Thanks Yogesh.  One more question.  Is there some “trick” to entering more than one DVD mount point in the SUM screen?  The SUM 1.0 SP16 guide indicates that entering more than one is possible, but the SUM screen does not seem to allow entry of more than one, even though there are multiple lines available on the screen. 

            1. Yogesh Patel
              Post author

              I dont think you can add additional lines but you can try manually typing in to empty lines there and see.


              1. Former Member

                Yes, that is the actual problem, it is not possible to type anything into any of the fields of the  already provided additional lines.  I tried to enter the DVD Type, Description, and the Mount Point, but nothing can be entered into those fields, even though they appear to be open for entry.

  1. Yuksel AKCINAR

    Thanks for th document Yogesh.

    I will try to upgrade one of our customer’s SM 7.1 SP12.

    I think your documents will help me.


    Yuksel AKCINAR

  2. Former Member

    HI Yogesh

    I cant find the location
    Configure LMDB Object Server To Deactivate as mentioned in Part 2 above.
    I have checked LMDB admin and logged online to SLD admin.
    I dont see the admin screen.


    1. Yogesh Patel
      Post author

      Hello JP,

      Someone send alert to moderator and document is set to – Need More Work – Status.

      I dont know what I am missing in there??? I have to check it in detail


  3. Former Member

    Hi Yogesh

    When you generate the xml stack file. Will that also include the Java Dvds 51050949  ?

    I am getting the following Error in the SUM tool during Java config An error occured during the execution of Create stack from stack file of action configure.

    Service failed with the following message

    Cannot construct a support package stack from file F:\Download\MP_Stack_044_.xml.


  4. Former Member

    Hello Yogesh Patel,

    We are planning to upgrade SolMan 7.1 to 7.2
    I have a doubt, as we are keeping the DB (oracle) as it is. Is TREX installation mandatory for that.
    Also, what would happen if we do not install TREX?

    Nitin Soni


    1. Yogesh Patel
      Post author

      Hello Nitin,

      I am not too sure about your system configuration.

      But as far I know you can upgrade TREX.

      Question you need to ask is – What will happen to Indexes created by TREX?


  5. Former Member

    Hi Yogesh,

    Any idea what could be the possible solution of below error.I got during execution phase of SOLMAN 7.2 upgrade…
    Severe error(s) occurred in phase MAIN_PROFSTART/SUBMOD_PROFSTART1/MODPROF_V2BACKUP!

    Last error code set:
    File ‘/usr/sap/SID/SYS/profile/NO_INFO’ does not exist: No such file or directory



    1. Former Member


      Hi ,


      We have similar issue in the same phase. Have you found solution for this issue ? If  yes, can you please share what  you did to fix the issue ?



  6. Former Member

    I ran into the same error about a missing “NO_INFO” file, during an EHP8 upgrade on ERP, using SUM SP19 PL4.  Note 2314382 talks about this error, but the resolution did not resolve my error.  Since the error is referring to a non critical file that is missing, I simply created an empty “NO_INFO” file in the profile directory, and then repeated the failed step.

    My EHP8 upgrade process is still active currently, so I cannot confirm that this work-around did not cause other issues, but the SUM process has proceeded on through several other steps, so I am hopeful that the issue has been bypassed.  The note below may help others with a similar error, however.




    Russel Robbins


        1. Former Member

          Yep i have seen it, it did not help, as it mentioned by Russel ;). I mean much probably there was an issue with initial distributed installation….


          In case somebody get the same error.
          I created the file with touch command (the same like Russel did), upgrade successfully  finished, with no issues, only satellite  ABAP application servers kernel was not updated, so I did it manually later on.


          Will be good to know what exactly is executed on this phase.

          I guess sapcpe binaries copy should be executed on this step. 

          1. Former Member


            I had the same error in upgrade-phase


            I solved removing duplicate profile files on the main profile directory and local ERS profile directory for HA system.

            Agostinho Andrade


  7. Former Member


    I am getting an error when installing SCS server. After SCS server started it fails on get process command. (GetProcessList

    FAIL: NIECONN_BROKEN (No such file or directory), NiRawRead failed in plugin_sapfrecv())

    Did you get this error? If yes how did you resolve it?


  8. Former Member

    Hello Yogesh,

    At which point of the upgrade should the SPAU adjustments be performed once SUM finishes: before or after the dual-stack split?

    Thank you,

  9. Former Member

    Hi Yogesh


    SAP note: 2227300

    BI_MMR 7.02 Can not upgrade Remove

    we don’t have the remove option in the list, only revert or deploy (during the phase Build Component) how can we have this option ?

    Thanks in advance


  10. Former Member

    Hi Yogesh,

    I have added the BI_MMR component in the queue to update to sp19 and I am facing issues in Deploy Shadow instance phase and looks like the issue is due to this package and wondering whether I can remove the package from the queue without reverting the SUM and start over again.



  11. Reza Ejersbo

    Hi yogesh,

    We have solution manager 7.2 sp5 install,

    From LMDB -> Display and Edit Logical Component Groups and start ”

    I get:

    404   Not Found:

    Error: Requested resource does not exist.

    SAP Technology Troubleshooting Guide


    Details: Go to main page of this application.


    Is any body had this error,







  12. Reza Ejersbo


    Thanks to you,

    Any idea why I get this erroe:

    404   Not Found:

    Error: Requested resource does not exist.

    SAP Technology Troubleshooting Guide



    Details: Go to main page of this application.

  13. Reza Ejersbo


    Thanks for help I will do that.

    The problem is When I try using :Display and Edit Logical Component Groups and start ”

    LMDB trying to use Java port 50200 and not 50000 abap port.



    1. Yogesh Patel
      Post author


      This might be the configuration issue on ABAP and JAVA connectivity.

      Can you please verify steps below

      Infrastructure Preparation >> (Step) 2.1 Define HTTP Connectivity


      Thank you


  14. Reza Ejersbo


    Thanks again for repy,

    I had check it. The configuration is correct.

    ABAP Application server using port 50000 and JAVA using 50200.

    There is just happened when i am using “Display and Edit Logical Component Groups and start”  from LMDB.

    From soladm working find with port 50000. LMDB start also in port 50000.


  15. Reza Ejersbo


    Not every thing working 🙁

    I Have still problem when i am using “Display and Edit Logical Component Groups and start”  from LMDB. Url using 50200 and not 50000.




Leave a Reply