Solution Manager Maintenance Optimizer error

[Former Member]

Dear Experts,

we have a Solution Manager (Solman) 7.0 EHP1 on our landscape, with component SAP_BASIS 7.01 SP11, ST 4.00 SP 29: we need to install

support packages on an Enterprise Portal system 7.31, SP04, we need to bring it to SP09. Therefore, we are using solution manager's maintenance

optimizer (Mopz) to generate a stack.xml file with all details about packages to download and apply to Portal through Software Update

Manager (SUM). We have already synchronized Portal SLD content with Solman SLD (CIM and CR models updated) and fetched Solman SLD Content with transaction SMSY_SETUP (job Landscape_fetch). We have set Enterprise Portal product instance as relevant and assigned product version SAP

EHP1 FOR SAP NETWEAVER 7.3 to Portal system in SMSY transaction. We then launch Mopz but it stops immediately, giving us several errors such

as: "System XXX: Installed Product Instance SAP EHP1 FOR SAP NETWEAVER 7.3 NW Product Description not assigned!", and these errors repeat for

other product instances. We then flagged these product instances as relevant in SMSY, and launch another Mopz transaction: this way we can

obtain an (apparently) valid stack.xml file, but then, when we launch SUM and give that stack.xml as input, we obtain several errors like these: "Software component with name XXX and vendor sap.com is duplicated in the stack definition file." In fact, we searched in xml stack file and we found several entries for that software components.

We suppose problems are lying in the definition of Portal system in SMSY: how can we set correct product versions, product instances, etc. in SMSY so as to generate a correct stack.xml file to give as input to SUM? Moreover, is it possible to generate valid stack.xml file through Mopz in Solman 7.0 SP11 to update Enterprise Portal 7.31 ?

In the attachment you can find Portal components infos and erro log from SUM.

Thanks in advance,

DEFINE-TARGET-SOURCE_01.txt.zip

[Former Member]

Ok so now we have installed Landscape Verification Tool (transaction LVSM) SP03 in our Solman 7.0 (ST SP29), component ST-LV 1.0 SP03 (yes it is supported for our Solman, thanks Kroone), but unfortunately this tool doesn't help us: we tried to correct some issues checked with the tool, generated new stack.xml file from Solman Maintenance Optimizer (mopz), but SUM tool rejects the stack.xml at validation phase.

Any suggestions on how to proceed?

[Former Member]

You can execute the landscape verification check.

I beleive in 7.01 this was available as an addon to SolMan, but I'm not sure (it's been a while since I touched a SolMan that old ).

[Former Member]

Hi Kroone, thanks for support. Unfortunately Landscape Verification Check (LVSM transaction) is available as add on on Solution Manager 7.0, SP18 , but we have SP11 right now...

[Former Member]

If you are sure you are on 7.01 (so with the EhP1) then you have to be at least at SP18.

So my guess, looking at your component version you are on SP29 and you can install the addon.

Even better would be (but this isn't really helpful) to upgrade your SolMan to 7.1