SOLMAN patching to stack 06 using SUM1.0 sp05

[Former Member]

Hello Guys,

We are currently at solman 7.1 sp04 and planning to upgrade to sp06.

I am using sum tool for patching.i have generated the XML from solman and download the files.

During the configuration phase of java i am getting the following error.

<!--LOGHEADER[START]/-->

<!--HELP[Manual modification of the header may cause parsing problem!]/-->

<!--LOGGINGVERSION[2.0.7.1006]/-->

<!--NAME[C:\dump\SUM\SUM\sdt\log\SUM\SHOW-VALIDATION-RESULT_04.LOG]/-->

<!--PATTERN[SHOW-VALIDATION-RESULT_04.LOG]/-->

<!--FORMATTER[com.sap.tc.logging.TraceFormatter(%d [%6s]: %m)]/-->

<!--ENCODING[UTF8]/-->

<!--LOGHEADER[END]/-->

Sep 28, 2012 1:19:43 AM [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 sap.com/SAP_JTECHF is found on the system but not in the list of expected system components in the stack.

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

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

There are 17 more error messages. See them all in C:\dump\SUM\SUM\sdt\log\SUM\CHECK-QUEUE_02.LOG.

.

During XML generation i didnt add the java patches as it was giving waring the intergrity of XML will have to be maintained manually.

Now i cant repeat as it giving same error.

Option 2 & 3 asks for password.Which password is required...?

Regards

Abhishek

[former_member186895]

I did upgradation to sp10 with normal spam/saint and jspm without any error.

SUM have lots of error.

Thanks

Ramesh yadav

[former_member186895]

HI,

Directly go for sp10.

why you want to go for sp06?

sp10 is best and easy to upgrade. please upgrade using normal method spam and jspm.

Thanks

Ramesh yadav

[Former Member]

All,

SAP OSS helped me get through this issue, I hope this information will be of some help to others...

Firstly they asked me to up the logging level in SUM, and send them the log files.  After doing this they came back with Note 1595918 JSPM: Validation fails due to mismatch at software features.

I followed this note as requested.  At this point it was necessary to reset the upgrade, however, the SUM tool would not let me do so.  I was getting the following errors:

Unable to reset the upgrade

Unable to execute the SDT request list SUM

Revoke is not allowed for the current operation configure.

Starting with a fresh SUM directory, I could not start a new upgrade as the system was indicating:

Severe error(s) occured in phase PREP_INIT/VALCHK_INI!

Last error code set: BBPCRM is in an undefined state, that is not safe

to

be upgraded, reason Upgrade wasn't completed - Call the SAP Support

SAP said:

As you are in the prepare phase you may reset the upgrade using:

  SAPup reset prepare

  as described in upgrade guide.

I ran the SAPup reset prepare, and it cleaned up the system.  I was then able to start with a fresh upgrade directory (SUM tool), and move forward with the patch.

Good Luck!

Tom

[former_member328114]

I got the same error during Solman7.1 SP10 upgrade. Tom's solution worked for me

Thanks,

Srini.

[Former Member]

Thanks to Tom, this fixed my problem as well. The Solman system is currently on SP6 and I was applying SP10 using SUM when the error occurred.

My specific issue was:

Software feature SAP SOLUTION MANAGER 7.1: Solution Manager ABAP Stack with ID 012003146909000027951 is found on the system but not in the list of expected system software features in the stack.

There were 2 entries in table BC_SL_SWFEATURE with the same Prod_ID of "01200314690900002795". The one was for ABAP and the other JAVA. I only deleted the ABAP row leaving the JAVA entry.

The command I used to reset the service pack upgrade was SAPup as in:

..../SUM/abap/bin/SAPup reset prepare

I then renamed the SUM directory, unpacked SUM again from the SAR file, which by the was SUM10SP09_2-20006676.SAR (ie SUM 1.0 SP9 Patch 2 for X86_64)

--Greg

[Former Member]

Dear Tom,

i get the same issue by updating my SolMan 7.1 from SP08 to SP10, but i have no luck with note 1595918.

My error message:

      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 feature SAP
      SOLUTION MANAGER 7.1: Solution Manager ABAP Stack with ID
      012003146909000027951 is found on the system but not in the list of
      expected system software features in the stack. Software component
      sap.com/JSPM with version 7.02.12.0 is found on the system but in the
      stack it is listed with version 7.02.0.0. Software component
      sap.com/SWLIFECYCL with version 7.02.12.0 is found on the system but in
      the stack it is listed with version 7.02.0.0. There are 1 more error
      messages. See them all in
      /eva8k/sapmnt/SP10/SUM/sdt/log/SUM/CHECK-QUEUE_01.LOG.
   

  and my entries in the tables are:

BC_SL_DWFEATURE

1;01200314690900002795;SAP SOLUTION

MANAGER;7.1;sap.com;SAP SOLUTION MANAGER 7.1: Solution Manager ABAP Stack

1;01200615320900003225;SAP NETWEAVER; SAP EHP2 FOR SAP NETWEAVER

7.0;sap.com;SAP EHP2 FOR SAP NETWEAVER 7.0: Application Server ABAP

BC_SL_DWFEATUREINC

1;01200615320900003225;1;01200314690900002795;SAP NETWEAVER; SAP EHP2

FOR SAP NETWEAVER 7.0;sap.com;SAP EHP2 FOR SAP NETWEAVER 7.0: Application Server

ABAP

2;01200314690900004988;1;01200314690900002795;SAP_NW_UI_EXTENSIONS_100_702;sap.com;UI

ADD-ON 1.0 FOR NW 7.02: SAPUI5 DevToolkit: Client Libs

Do you know, which entry must be changed?

Regards Oliver

[Former Member]

Hi Oliver,

Did you re-sync with the solution manager, and then re-create the stack.xml?  Your issues look similar, but I would start by re-syncing, regenerating the stack, and resetting the upgrade.

Sorry, it's been a while since I've looked at this issue, let us know if you are still having difficulty after re-sync, regen, reset.

Tom

[Former Member]

This sounds like a discrepancy between the installed components and what Solution Manger thinks is installed.  Have you checked your system configuration in SMSY?  All components have to be listed with the correct patch level there, because it's what the maintenance optimizer uses to build the stack.xml file.

[Former Member]

Has anyone found a solution to this?  I'm getting the same error patching Solution Manager 7.0 EHP1 to SPS30.  I've submitted an OSS message, but have not heard back.

[former_member185239]

Hi Abhishek,

Can you attach the stack.xml file or paste the content of file and there is an issue with patches in sp06.

With JSPM it will give warning and sap will say continue with it.

You can contact SAP.

With Regards

Ashutosh Chaturvedi

[former_member196567]

Hi mates,

I'm getting a similar error, the only difference is that  the ABAP Stack ID seems to be unknown(!) ... What went wrong ?

sap.com.

Jan 23, 2013 12:46:59 PM [Error ]: Software feature SAP SOLUTION MANAGER 7.1: Solution Manager ABAP Stack with ID 012003146909000027951 is found on the system but not in the list of expected system software features in the stack.

Jan 23, 2013 12:46:59 PM [Error ]: Stack validation completed with errors.

Jan 23, 2013 12:46:59 PM [Info  ]: Overall validation message : 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 feature SAP SOLUTION MANAGER 7.1: Solution Manager ABAP Stack with ID 012003146909000027951 is found on the system but not in the list of expected system software features in the stack.

Thanks in advance!

Cheers Petros

[denny-k]

have you checked the systemnumber in lmdb? open the xml and look for the number and change it.

[former_member196567]

Yes, LMDB shows this number but as I interpret the error message, something seems to be wrong with the stack file (which I generated for a second time just to be sure..)

This is what I find in the XML file:

- <sp-stack>

<caption>07 (10/2012)</caption>

<ppms-number>67837800103300003796</ppms-number>

<stack-type gen-time="20130123144520" gen-version="M4">system</stack-type>

<sap-note>0001752273</sap-note>

<release-date>20121022</release-date>

- <product>

<caption>SAP SOLUTION MANAGER 7.1</caption>

<name>SAP SOLUTION MANAGER</name>

<version>7.1</version>

<ppms-number>01200314690900002795</ppms-number>

<vendor>sap.com</vendor>

</product>

- <replaced-product>

<caption>SAP SOLUTION MANAGER 7.0 EHP 1</caption>

<name>SAP SOLUTION MANAGER</name>

<version>4.0 EHP 1</version>

<ppms-number>01200314690900000833</ppms-number>

<vendor>sap.com</vendor>

</replaced-product>

- <replaced-product>

<caption>SAP SOLUTION MANAGER 7.0</caption>

<name>SAP SOLUTION MANAGER</name>

<version>4.0</version>

<ppms-number>01200314690900000235</ppms-number>

<vendor>sap.com</vendor>

</replaced-product>

- <replaced-product>

<caption>SL TOOLSET 1.0</caption>

<name>SL TOOLSET</name>

<version>1.0</version>

<ppms-number>01200615320900005323</ppms-number>

<vendor>sap.com</vendor>

</replaced-product>

- <replaced-product>

<caption>SAP SOLUTION MANAGER 3.1</caption>

<name>SAP SOLUTION MANAGER</name>

<version>3.1</version>

<ppms-number>01200615320900001194</ppms-number>

<vendor>sap.com</vendor>

</replaced-product>

- <replaced-product>

<caption>SAP SOLUTION MANAGER 2.2</caption>

<name>SAP SOLUTION MANAGER</name>

<version>2.2</version>

<ppms-number>01200615320900001197</ppms-number>

<vendor>sap.com</vendor>

</replaced-product>

- <replaced-product>

<caption>SAP SOLUTION MANAGER 2.1</caption>

<name>SAP SOLUTION MANAGER</name>

<version>2.1</version>

<ppms-number>01200615320900001198</ppms-number>

<vendor>sap.com</vendor>

</replaced-product>

- <replaced-product>

<caption>SAP SOLUTION MANAGER 3.2</caption>

<name>SAP SOLUTION MANAGER</name>

<version>3.2</version>

<ppms-number>01200615320900001255</ppms-number>

<vendor>sap.com</vendor>

</replaced-product>

- <sp-feature-stack>

<caption>SAP SOLUTION MANAGER 7.1 : Solution Manager ABAP Stack - 07 (10/2012)</caption>

- <software-feature selectively-installable="N">

<caption>SAP SOLUTION MANAGER 7.1: Solution Manager ABAP Stack</caption>

<name>SAP SOLUTION MANAGER</name>

<version>7.1</version>

<vendor>sap.com</vendor>

<ppms-number>012003146909000027951</ppms-number>

- <included-feature selectively-installable="N">

<caption>SAP EHP2 FOR SAP NETWEAVER 7.0: Application Server ABAP</caption>

<name>SAP NETWEAVER</name>

<version>SAP EHP2 FOR SAP NETWEAVER 7.0</version>

<vendor>sap.com</vendor>

<ppms-number>012006153209000032251</ppms-number>

</included-feature>

</software-feature>

which one is wrong ?

Thanks & Cheers

Petros

[denny-k]

have you tried to change the ppms-number? a "1" is missing? what does the landscape verification says?

[former_member196567]

Hi,

I gave it a try and edited the XML stack file but unfortunately with no effect.

I'm not sure what exactly is wrong with those ppms, they look consinstent/plausible:

[bfewell]

Did you find a solution to this problem?  I have the same issue upgrading to stack 8 from stack 4 with SUM 1.0 SP 8.

[paul_power]

Hello Abhishek,

Software component xxxxxx is found on the system but not in the list of
expected software components in the stack.

Check SAP note 1469745 which seems to suit this issue

regards,

Paul

[Former Member]

Thanks Paul, and i had gone through this note.

I tried the doing the manual corrections mentioned in the note but wasn't helpful.

Since note mentioned to update JSPM which i am not using for patching.

Regards

Abhishek