Importing Support Packages - Error during XPRA_EXECUTION

Question

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

Answer 1

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