SAP ERP 6.0 SPS11 to SPS21 Using SUM (Software Update Manager)

[Former Member]

Hi,

I'm currently using SUM to update ERP 6.0 from SPS11 to SPS21 but am encountering an error during the PREP_INPUT/SELSTACKXML_ASK phase.

SELSTACKXMLA.LOG output:

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

1 ETQ201 Entering upgrade-phase "SELSTACKXML_ASK" ("20121024232027")

4 ETQ399 Set environment for standard connect:

2 ETQ367 Connect variables are set for standard instance access

4 ETQ399 System-nr = '00', GwService = 'sapgw00' Client = '000'

4 ETQ399 Environment variables:

4 ETQ399   dbs_ora_schema=SAPR3

4 ETQ399   auth_shadow_upgrade=0

1 ETQ200 Executing actual phase 'PREP_INPUT/SELSTACKXML_ASK'.

1 ETQ399 Phase arguments:

2 ETQ399 Arg[0] = ''

2 ETQ399 Arg[1] = 'ASK;READBASIC;CHECK_INITIAL0'

1 ETQ399 Ask user for stack configuration.

4 ETQ399 EhP stack selection ...

1 ETQ399 Read XML stack configuration.

4 ETQ399 Copy stack file 'G:/18102012/stack.xml' to 'E:\usr\sap\SUM\abap\tmp\stack.xml' temporarily to avoid access problems.

4 ETQ399 Reading stack content ...

4 ETQ399 ... reading stack configuration file "E:\usr\sap\SUM\abap\tmp\stack.xml"

1 ETQ359 RFC Login to: System="SB1", AsHost="SB050IEKI11" Nr="00", GwHost="SB050IEKI11", GwService="sapgw00"

2 ETQ232 RFC Login succeeded

4 ETQ010 Date & Time: 20121024232027 

1 ETQ233 Calling function module "OCS_API_GET_STACK_INFO" by RFC

2 ETQ373 parameter "IV_STACK_GUID" = ""

2 ETQ373 parameter "IV_STACK_FILE" = "E:\usr\sap\SUM\abap\tmp\stack.xml"

1 ETQ234 Call of function module "OCS_API_GET_STACK_INFO" by RFC succeeded

4 ETQ010 Date & Time: 20121024232027 

2 ETQ399 Table ET_CVERS_INITIAL (#0):

2 ETQ399 Table ET_CVERS_EXPORT (#0):

2 ETQ399 Table ET_CVERS_TARGET (#0):

2 ETQ374 parameter "EV_RC" = "-99"

2 ETQ373 parameter "EV_MESSAGE" = "System expected the end of the element 'archives' &5&6&7&8"

4 ETQ399 ... Error reading stack info (rc = -99, reason = "System expected the end of the element 'archives' &5&6&7&8")

1EETQ399 Last error code set is 'Error reading stack info, return Code = -99, Reason = 'System expected the end of the element 'archives' &5&6&7&8''

1EETQ204 Upgrade phase "SELSTACKXML_ASK" aborted with severe errors ("20121024232027")

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

I also debugged to see if I could shed any light on it. It seemed to break during the conversion:

OCS_CONVERT_XML_INTO_CVERS

The variable lr_error contained '{O:1*\CLASS=CX_ST_MATCH_ELEMENT}'

I generated the stack.xml in the SMP and not in SolMan. Could this be the issue?

Any help would be much appreciated.

Cheers,

Tony

[former_member189797 · Accepted solution]

Hello Tony,

I have seen similar issue where the issue was indeed with the stack.xml

Could you please check if you are able to open stack.xml in the XML editor. In the similar issue it was not possible to open the stack.xml file in the XML editor. But when the stack.xml was generated using the SOLMAN system it was possible to open it using the XML editor as well as the IE.

But I would suggest to generate the stack.xml using the SOLMAN system only as SAP recommends to use the Solution Manager system to generate the stack.xml file.

So you can try to generate the stack.xml using the solman system and then try it again.

Regards,

Gaurav

[Former Member · Accepted solution]

Thanks Gaurav. However, I can successfully open the file in an editor and it was successfully read by SUM in the first phase.

There just seems to be some sort of mismatch later on in the process.

I'll check MOPZ though anyway to rule that out.

Tony

[Former Member]

Hi all,

I found the problem over the weekend - it was related to the PI_BASIS component. There are two archive entries and SUM could not handle them both:

<archives>

<archive-name abap-delivery-transport="SAPKINBC9H">KINBC9H.CAR

</archive-name>

<archive-name abap-delivery-transport="SAPKINBC9A">KINBC9A.CAR

</archive-name>

</archives>

I worked around the problem by not going to PI_BASIS 2006_1_700 (i.e. staying on 2005_1_700).

Thanks for your input.

Tony

[tomas_black]

Very intersting. And what was the reason SUM could not handle them?

[Former Member]

I'm not exactly sure - my assumption was that there was no looping around archives (i.e. it expected only one). However, I didn't dig any deeper at that stage.

The message has been moved onto another component, so I'll post the result of the analysis here when the processor has updated it.

[Former Member]

Hello Gaurav,

File attached.

Thanks,

Tony

[tomas_black]

Hello Tony,

strange issue indeed. Have you tried regenerating the XML stack file from the SAP MarketPlace? As per your debugging information, SUM is unable to translate the information from the XML file into CVERS table. Like if the file was corrupted, altough I can perfectly read it on my workstation.

Are you using the very last SUM version available?

Generating a new XML file from SolMan is an option, but since you can still get this file from SAP MP it should not preset problems.

Best regards,

Tomas Black

[Former Member]

Hello Thomas,

Yep, I've regenerated a couple of times now and am using the latest SUM.

I noticed that there are a couple of packages on the system lower than SPS11 though, so I'm in the process of pulling those down and will retry the whole thing from scratch.

Best regards,

Tony

[tomas_black]

Good luck!

Tomas Black

[Former Member]

No joy - same error.

Will have to wait until the customer message gets a processor...

[tomas_black]

Hello Tony,

can you please inform the number of the message?

Tomas

[Former Member]

Hello Tomas,

#974967

Thanks,

Tony

[former_member189797]

Hello Tony,

Yes, Please try to generate the stack.xml file using the MOPZ and then try. Its the recommended way.

In the mean time, you can just attach the stack.xml being used here and I can have a look on the

stack.xml.

Regards,

Gaurav