Importing Support Packages - Error during XPRA_EXECUTION

[joo_migueldimas]

Hello,

Database: Oracle 10.2.0.4

Operation System: Windows Server 2008 X64

I´m facing with an error during an importing of support packages in our Solution Manager Ehp1 system (SPS 20 to SPS 25).

I checked the import logs of the queue and I see in there the following error:

Program terminated (job: RDDEXECL, no.: 02083200)
   See job log
Execution of programs after import (XPRA)
End date and time : 20110126020847
Ended with return code:  ===> 12 <===
######################################

When I checked the job log I see in there this:

Job started
Step 001 started (program RDDEXECL, variant , user ID DDIC)
All DB buffers of application server SAPSM were synchronized
Internal session terminated with a runtime error (see ST22)
Job cancelled

I went to ST22 and I see in there that specific short dump which show:

Short text
    XSLT: No valid XML source

What happened?
    The transformation is not possible since the XML source document cannot
    be parsed.

What can you do?
    Note which actions and input led to the error.

    For further help in handling the problem, contact your SAP administrator.

    You can use the ABAP dump analysis transaction ST22 to view and manage
    termination messages, in particular for long term reference.

Error analysis
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_XSLT_RUNTIME_ERROR', was not
     caught in
    procedure "TRANSFORM_FROM_XML" "(METHOD)", nor was it propagated by a RAISING
     clause.
    Since the caller of the procedure could not have anticipated that the
    exception would occur, the current program is terminated.
    The reason for the exception is:
    Either the source document contains invalid XML or it is handled
    incorrectly in the ABAP program that called the transformation.

How to correct the error
    The most common cause of this error is a conflict between the encoding
    specified in the declaration <?xml version="1.0" encoding="..."?> in the
     document and the actual encoding of the data.
    If the document is held in an ABAP string, the actual encoding is the
    system code page. If this does not match the declaration, a parsing
    error may occur.
    These conflicts are a particular issue when XML documents are produced
    in one system and then imported into a system with a different code page
     (as strings).
    For this reason, XML documents should be held as binary data (X strings)
    , if they are extracted from the system or accessed from outside.

    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:

    "XSLT_BAD_SOURCE_CONTEXT" "CX_XSLT_RUNTIME_ERROR"
    "CL_SM_BFR_CONTENT_TRANSPORT===CP" or "CL_SM_BFR_CONTENT_TRANSPORT===CM00E"
    "TRANSFORM_FROM_XML"

    The exception must either be prevented, caught within proedure
    "TRANSFORM_FROM_XML" "(METHOD)", or its possible occurrence must be declared in
     the
    RAISING clause of the procedure.
    To prevent the exception, note the following:

Can you help how to correct this situation for I can continue the update of support packages!

Best regards,

João Dimas - Portugal

[Former Member · Accepted solution]

HI

Check the import log, and paste any errors.

Regards

William Neira

[joo_migueldimas · Accepted solution]

Hello William,

Which import logs do you refer?

I pasted in my first message the log of import... that is the unique error that it appeared.

_________

I checked the SLOG:

STOP  MOVE NAMETABS        SSM 6      20110125215838              SAP_BASIS    SAPSM 20110125214839404   
START MAIN IMPORT          SSM I      20110125215838              SAP_BASIS    SAPSM 20110125214839404   
STOP  MAIN IMPORT          SSM I      20110125235752              SAP_BASIS    SAPSM 20110125214839404   
START TBATG CREATION OF EN SSM n      20110125235752              SAP_BASIS    SAPSM 20110125214839404   
START tp_getprots          SSM Y      20110125235753              SAP_BASIS    SAPSM 20110125214839404   
WARNING: '\SAPSMsapmnt	rans	mpN110126.SSM' : cant open
 (tpfsnam.c:504)
WARNING: '' : cant open
 (tpfsnam.c:584)
WARNING: '\SAPSMsapmnt	rans	mpN110126.SSM' : cant open
 (tpfsnam.c:504)
WARNING: '' : cant open
 (tpfsnam.c:584)
STOP  tp_getprots          SSM Y      20110126000148              SAP_BASIS    SAPSM 20110125214839404   
STOP  TBATG CREATION OF EN SSM n      20110126000148              SAP_BASIS    SAPSM 20110125214839404   
INFO  EXECUTION OF STANDAR SSM 9      not needed                  SAP_BASIS    SAPSM 20110125214839404   
INFO: event SAP_IMPORT_STOP triggered successfully
STOP  imp all              SSM   0004 20110126000149              SAP_BASIS    SAPSM 20110125214839404

I also checked the ULOG which has the following records:

APServiceSSM 20110126013719 RFC: tp XPA ALL SSM pf=\SAPSMsapmnt	rans inTP_DOMAIN_SSM.PFL -Dclientcascade=yes -Dstoponerror=8 -Drepeatonerror=8 -Dsourcesystems= -Dbuffreset=yes -Dbatch_proc=1 tag=spam -Dtransdir=\SAPSMsapmnt	rans  (pid=5276)
APServiceSSM 20110126020829 RFC: tp SHOWPARAMS SSM pf=\SAPSMsapmnt	rans inTP_DOMAIN_SSM.PFL -Dtransdir=\SAPSMsapmnt	rans  (pid=5196)
APServiceSSM 20110126020830 RFC: tp CONNECT SSM pf=\SAPSMsapmnt	rans inTP_DOMAIN_SSM.PFL -Dtransdir=\SAPSMsapmnt	rans  (pid=5196)
APServiceSSM 20110126020831 RFC: tp XPA ALL SSM pf=\SAPSMsapmnt	rans inTP_DOMAIN_SSM.PFL -Dclientcascade=yes -Dstoponerror=8 -Drepeatonerror=8 -Dsourcesystems= -Dbuffreset=yes -Dbatch_proc=1 tag=spam -

Any idea what´s happen?!

Kind regards,

João Dimas - Portugal

[Former Member · Accepted solution]

Hi

Check SAP Note 1509252 - Short dump when importing bus. function repository

Regards

William Neira

[joo_migueldimas · Accepted solution]

Yeah William... that is the solution for this error! Thank you very mutch

Tell me... how do you found this note? You searched in SAP Marketplace with the following words, wasn´t it??

"XSLT_BAD_SOURCE_CONTEXT" "CX_XSLT_RUNTIME_ERROR" "CL_SM_BFR_CONTENT_TRANSPORT===CP"

Many thanks I will give you the max points!

Kind regards,

João Dimas - Portugal

[Former Member · Accepted solution]

Hello William,

I had the same problem.

Thank you so much for your help. You saved me.

Best regards,

manoliv

[Former Member · Accepted solution]

William,

I also had this issue while applying patches in SOLMAN. The difficult part when you get this message while in the middle of patching depending on what phase SNOTE will not allow you to implement anything.

I did not specifically get the message for this issue, but to avoid this I renamed the buffer file in \usr\sap\trans\buffer\SMP and implemented the note and after that was complete renamed the buffer back and all is well. I just wanted add that and thank you for the note # 1509252

Ray

[Former Member · Accepted solution]

FYI.

I faced the same problems during the Update of SOLMAN form SPS18 to SPS25 exactly by the import of "SAPK-1507RINSTPL ST-ICO 150_700: patch 0027".

I could implement the Note via SNOTE without any problems, I don't have to manipulate the import queue as in the case of Ray.

Maybe something to do with our Support Package Level or SPAM/SAINT PL!

Of Course the Manual Post-Implement as described in the Note should be done afterward.

Best regards,

Khouri

[joo_migueldimas · Accepted solution]

Hello,

Exactly Hodhod!! In my case I didn't have to handle the import queue too... but in future if that happens to somebody, the procedure applied by Ray is correct!

Best regards,

João Dimas - Portugal

[Former Member · Accepted solution]

Spot on William!

This resolved this issue smoothly. Thank you man!

[Former Member · Accepted solution]

Spot on guys,

[craig_janey]

Fix worked great thanks for the Note Ray!

[Former Member]

I was also stuck in XPRA_EXECUTION phase, while applying ST-ICO 150_700: patch 0027/28/29/30/31 in Solman 7.1 @ AIX system.

Error details

Job started

Step 001 started (program RDDEXECL, variant , user ID DDIC)

All DB buffers of application server pmfsapci were synchronized

Internal session terminated with a runtime error (see ST22)

Job cancelled

Category XSLT Runtime Error

Runtime Errors XSLT_BAD_SOURCE_CONTEXT

Except. CX_XSLT_RUNTIME_ERROR

Below mentioned sap note also work for me.

Note 1509252 - Short dump when importing bus. function repository contents.

Just apply this note and re-import the queue, you can see the magic.

Thanks,

Sudhir Kumar

[Former Member]

The issue is resolved. Hence closing the thread.

[joo_migueldimas]

Hey Amit... OK man, take it easy... I know that! I always close everything, when I think it is completely finished, and I don´t know if you read, but I ask one thing to William... if he not answer until tomorrow I close this thread.

Every day I come here, so do not worry! I already said a lot of times that in other threads...

I already said exactly that in many posts here in SDN, because in fact there are many users here that do not close the messages and worse, often they close it without posting the solution

Kind regards,

João Dimas - Portugal

[Former Member]

Hi

I search in marketplace with "TRANSFORM_FROM_XML", only one note appear.

Regards

William Neira