1993319 - "XSLT_BAD_SOURCE_CONTEXT" error in ACT_UPG phase during upgrade

During an Upgrade using SUM , the Upgrade stops in ACT_UPG phase with a runtime error.

You can view the following logs in DIR_PUT or upgrade log directory with similar logs, as mentioned below:

SAPup.log:
==========
CURRENTPHASE MAIN_TRANSEXEC/ACT_TRANS
...started at 20140204150021
...begin processing at 20140204150022
..finished at 20140204150455 with status FAILED.
# Error message set: 'Detected 171 aborted activities in 'ACTUPG.ELG'
Calling 'E:\usr\sap\<SID>\DVEBMGS02\exe/tp' failed with return code 12,
check USR\SAP\SUM\abap\log\SAPup.ECO for details'
...begin dialog at 20140204150458
...end dialog at 20140204151607

ACT_UPG.ELG:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPA-XXXXXXXXXXXXXX.<SID>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1AETR012XProgram canceled (job "RDDMASGL", number "15002600")
1AEPU320 See job log"RDDMASGL""15002600""<SID>"
1 ETP111 exit code           : "12"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Job Log in SM37 of Shadow instance :
=======
Job log overview for job:RDDMASGL / 11372600
Job started
Step 001 started (program RDDMASGL, variant IMPACTMRG, user ID DDIC
Start of mass activation
Internal session terminated with a runtime error
XSLT_BAD_SOURCE_CONTEXT (see ST22
Job cancelled

=====================================================================
ST22 Dump shows :
=====================================================================
Category               XSLT Runtime Error
Runtime Errors         XSLT_BAD_SOURCE_CONTEXT
Except.                CX_XSLT_RUNTIME_ERROR
Short Text
    XSLT: No valid XML source
 
What happened?
    The transformation cannot be carried out because the XML source document cannot be parsed.
 
Error analysis
     An exception has occurred which is explained in more detail below.
     The exception is assigned to class 'CX_XSLT_RUNTIME_ERROR' and was not caught in
     procedure
     "PARSE_DDL2" "(METHOD)", nor was it propagated by a RAISING clause.
  Since the caller of the procedure could not have anticipated this exception, the current program was terminated
  The reason for the exception is:
     Either the source document contains invalid XML, or the ABAP program that called the transformation is handling it incorrectly.
 How to correct the error
 The exception must either be prevented, caught in procedure
"PARSE_DDL2"
      "(METHOD)", or
     the possibility of it occurring must be declared in the RAISING clause
     in the procedure.
     To prevent the exception, note the following:
     The most common cause of this error is a conflict between the encoding
     specification in an encoding declaration in program <?xml
version="1.0"
     encoding="..."?> and the actual encoding of the data.
     "CL_DDL_PARSER=================CP" bzw.
CL_DDL_PARSER=================CM008
     "PARSE_DDL2"

• SAP Netweaver 740
• ABAP system, Enhancement Package Installation, Release upgrade.

RDDMASGL, ACT_UPG, XSLT, ACT_TRANS, SUM, runtime error, XSLT_BAD_SOURCE_CONTEXT, Upgrade, Update. , KBA , BC-UPG-TLS-TLA , Upgrade tools for ABAP , Problem