how to exclude S/W component during upgrade using SUM

[Former Member]

Hi All,

We are upgrading our pre-production PI system. This also serves rehearsal upgrade that we will also perform for the production system.

During Configuration roadmap steps, the SUM process stopped due to error occurred during the execution of the "Show validation result" step... message below.

Jul 28, 2014 10:00:19 PM [Error ]: The following problem has occurred during step execution: com.sap.sdt.util.diag.DiagException: Validation of deployment queue completed with error: The stack does not match the system. Probably the system was

changed after the stack was generated. Synchronize the system with SAP Solution Manager and then generate a new stack.

Software component seeburger.com/AS2Adapter is found on the system but not in the list of expected system components in the stack.

The stack xml file we are using during this upgrade is a converted copy of the stack xml generated during the upgrade of dev system. This same stack xml file was working when we applied the update in QAS. We used the report RPT_MOPZ_COPY_STACK_XML to convert the stack xml file.

May we ask if there is a way to exclude the component mentioned in the message so that we can still use the stack xml file, thus, we can ensure that the systems are aligned in terms of the version of the components.

We would appreciate your response for inputs. Thanks.

Regards,

Philip

[Former Member]

If there is a difference in software component of Quality and Production you will not be able to use stack file generated for Quality system. It will be better if you will generate new Stack file using MOPZ. Before that dont forget to sync your production system with SLD.

Br,

Koushal Solanki

[Former Member]

Hi,

Also the stack XML can be edited but this should only be done by SAP AG and only if there is some reason why you cannot make the landscape consistent as per Reagan's suggestion.

The XML in question would be named something like stack.xml you can get this to SAP?

Also make sure before you regenerate your mops stack that the LMDB entries and so forth  are consistent in the landscape run software verification check after ensuring update SLD entries and so forth as this can also cause problems.

Kind Regards,

Johan

[Reagan]

Hello

Check and compare all the components deployed in all the systems in the landscape.

If there are differences then first get the landscape consistent and then get the upgrade done.

http://<hostname>:50000/monitoring/ComponentInfo

Regards

RB

[Former Member]

Hallo,

"Software component seeburger.com/AS2Adapter is found on the system but not in the list of expected system components in the stack."

This sounds like your DEV system (for which the original stack xml was created) doesn't have the Seeburger adapter installed whereas your pre-production instance has it installed.

Refer to  note 1711612 - RPT_MOPZ_COPY_STACK_XML Report Troubleshooting and the link in that note: How-to guide for the stack XML copy report (SAP note 1600302):

"The ABAP report ‘RPT_MOPZ_COPY_STACK_XML’ delivered in SAP Note 1600302 replaces system-specific tags in the stack configuration XML, to generate a copy for an identical product system."

Hence your stack xml is not valid and you will need to create one from maintenance optimiser (rather than through report RPT_MOPZ_COPY_STACK_XML.

Regards,

Thomas.