Error during the phase XPRA_EXECUTION - Importing SPs in SAP EHP5

[joo_migueldimas]

Hello,

I´m facing with an error during an update/importing of support package in sap system ERP 6.0 EHP5 to stack 05 and stack 08 for SAP NW EHP2.

This error is in phase XPRA_EXECUTION. I checked some log files:

SLOG:

INFO: event SAP_IMPORT_STOP triggered successfully
STOP  imp all              QAS   0000 20110928114655              SAP_BASIS    SAPQAS 20110928114635423   
START EXECUTION OF REPORTS QAS R      20110928114744              SAP_BASIS    SAPQAS                     
START tp_getprots          QAS R      20110928114745              SAP_BASIS    SAPQAS                     
ERROR SAPKB70204           QAS R 0012 20110928115553 SAPUSER      SAP_BASIS    SAPQAS                                            
ERROR SAPKA70208           QAS R 0012 20110928121707 SAPUSER      SAP_BASIS    SAPQAS                     
ERROR SAPK-70206INSAPBSFND QAS R 0012 20110928121808 SAPBSFNDUSER SAP_BASIS    SAPQAS                     
STOP  tp_getprots          QAS R      20110928122150              SAP_BASIS    SAPQAS                     
STOP  EXECUTION OF REPORTS QAS R      20110928122150              SAP_BASIS    SAPQAS                     
START EXECUTION OF REPORTS QAS R      20110928125518              SAP_BASIS    SAPQAS                     
START tp_getprots          QAS R      20110928125519              SAP_BASIS    SAPQAS                     
ERROR SAPKB70204           QAS R 0012 20110928125534 SAPUSER      SAP_BASIS    SAPQAS                     
ERROR SAPK-70202INSAPBSFND QAS R 0012 20110928125625 SAPBSFNDUSER SAP_BASIS    SAPQAS              
ERROR SAPKB70208           QAS R 0012 20110928130832 SAPUSER      SAP_BASIS    SAPQAS                     
ERROR SAPKA70208           QAS R 0012 20110928130933 SAPUSER      SAP_BASIS    SAPQAS                     
ERROR SAPK-70206INSAPBSFND QAS R 0012 20110928131034 SAPBSFNDUSER SAP_BASIS    SAPQAS                     
STOP  tp_getprots          QAS R      20110928131044              SAP_BASIS    SAPQAS                     
STOP  EXECUTION OF REPORTS QAS R      20110928131044              SAP_BASIS    SAPQAS                     
START EXECUTION OF REPORTS QAS R      20110928140128              SAP_BASIS    SAPQAS                     
START tp_getprots          QAS R      20110928140128              SAP_BASIS    SAPQAS                     
ERROR SAPKB70204           QAS R 0012 20110928140144 SAPUSER      SAP_BASIS    SAPQAS                     
ERROR SAPK-70202INSAPBSFND QAS R 0012 20110928140234 SAPBSFNDUSER SAP_BASIS    SAPQAS                     
ERROR SAPKH60501           QAS R 0012 20110928140335 SAPAPPLUSER  SAP_BASIS    SAPQAS                     
ERROR SAPK-60501INEAAPPL   QAS R 0012 20110928140436 EAAPPLUSER   SAP_BASIS    SAPQAS                     
ERROR SAPKB70205           QAS R 0012 20110928140536 SAPUSER      SAP_BASIS    SAPQAS                     
ERROR SAPKA70205           QAS R 0012 20110928140637 SAPUSER      SAP_BASIS    SAPQAS                     
ERROR SAPK-70203INSAPBSFND QAS R 0012 20110928140737 SAPBSFNDUSER SAP_BASIS    SAPQAS                     
ERROR SAPKH60502           QAS R 0012 20110928140838 SAPAPPLUSER  SAP_BASIS    SAPQAS                     
ERROR SAPK-60502INEAAPPL   QAS R 0012 20110928140938 EAAPPLUSER   SAP_BASIS    SAPQAS                     
ERROR SAPKA70206           QAS R 0012 20110928141039 SAPUSER      SAP_BASIS    SAPQAS                     
ERROR SAPKH60503           QAS R 0012 20110928141140 SAPAPPLUSER  SAP_BASIS    SAPQAS                     
ERROR SAPKB70207           QAS R 0012 20110928141240 SAPUSER      SAP_BASIS    SAPQAS                     
ERROR SAPKH60504           QAS R 0012 20110928141341 SAPAPPLUSER  SAP_BASIS    SAPQAS                     
ERROR SAPKB70208           QAS R 0012 20110928141441 SAPUSER      SAP_BASIS    SAPQAS                     
ERROR SAPKA70208           QAS R 0012 20110928141542 SAPUSER      SAP_BASIS    SAPQAS                     
ERROR SAPK-70206INSAPBSFND QAS R 0012 20110928141643 SAPBSFNDUSER SAP_BASIS    SAPQAS                     
STOP  tp_getprots          QAS R      20110928141653              SAP_BASIS    SAPQAS                     
STOP  EXECUTION OF REPORTS QAS R      20110928141653              SAP_BASIS    SAPQAS

ULOG:

qas00        20110928140120 RFC: tp CONNECT QAS pf=/usr/sap/trans/bin/TP_DOMAIN_QAS.PFL -Dtransdir=/usr/sap/trans  (pid=4804)
qas00        20110928140124 RFC: tp SHOWPARAMS QAS pf=/usr/sap/trans/bin/TP_DOMAIN_QAS.PFL -Dtransdir=/usr/sap/trans  (pid=4910)
qas00        20110928140124 RFC: tp CONNECT QAS pf=/usr/sap/trans/bin/TP_DOMAIN_QAS.PFL -Dtransdir=/usr/sap/trans  (pid=4910)
qas00        20110928140127 RFC: tp XPA ALL QAS pf=/usr/sap/trans/bin/TP_DOMAIN_QAS.PFL -Dclientcascade=yes -Dstoponerror=8 -Drepeatonerror=8 -Dsourcesystems= -Dbuffreset=yes -Dbatch_proc=1 tag=spam -Dtransdir=/usr/sap/trans  (pid=4910)

[joo_migueldimas]

I see in Import logs the next error message:

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

I checked that job log and I see in there a Dump message. Next I will post here this dump:

Category               ABAP Programming Error
Runtime Errors         OBJECTS_OBJREF_NOT_ASSIGNED
Except.                CX_SY_REF_IS_INITIAL
ABAP Program           CL_SRT_WSP_DT_CHANGE_INT======CP
Application Component  BC-ESI-WS-ABA
Date and Time          28.09.2011 14:01:29

Short text: Access via 'NULL' object reference not possible.

What happened?
Error in the ABAP Application Program
The current ABAP program "CL_SRT_WSP_DT_CHANGE_INT======CP" had to
be terminated because it has come across a statement that unfortunately cannot be executed.

Error analysis:
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_REF_IS_INITIAL', was not caught in
procedure "ADD_ENTRY" "(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:
You attempted to use a 'NULL' object reference (points to 'nothing') access a component
(variable: "CL_SRT_WSP_DT_CHANGE_INT=>M_SRT_NUM_RANGE").
An object reference must point to an object (an instance of a class) before it can be used
to access components. Either the reference was never set or it was set to 'NULL' using the
CLEAR statement.

How to correct the error:
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:
"OBJECTS_OBJREF_NOT_ASSIGNED" "CX_SY_REF_IS_INITIAL"
"CL_SRT_WSP_DT_CHANGE_INT======CP" or "CL_SRT_WSP_DT_CHANGE_INT======CM007"
"ADD_ENTRY"

Can you help me to analyze and correct this problem?

Thank you,

JDimas

[sunny_pahuja2]

Could you please paste log of this phase from upgrade log directory ?

Thanks

Sunny

[joo_migueldimas]

Hello Sunny,

Sorry... I don´t understand what you asked... you talked about an upgrade log directory...!? What you mean?!... it has nothing to do with it.

My system is an ECC 6.0 EHP5 and I´m performing a support package importing activity, the stack 05 and during the phase XPRA_EXECUTION this importing activity (SPAM) stopped with this error that I showed in the previous post!

Can you help me please?

Kind regards,

JDimas

[sunny_pahuja2]

Hi,

Ya, its my mistake. I thought you are upgrading to EHP5. Could you please check dbsl library patch level. Please make sure that it is latest.

Thanks

Sunny

[Former Member]

Hello João,

I am facing the same problem. Do you have found a solution for this problem?

Thanks and kinds regards,

Mark

[joo_migueldimas]

Hello Mark,

I solved this error after I open a sap message... the solution was:

Running WRKJOB XDNQASLSN shows:

Job //XDNQASLSN not found.

Using CALL STRRMTDB according note 1257635 I have started this XDNQASLSN job now in QUSRWRK.

XDNQASLSN QSECOFR BCH .0 PGM-XDNCONTROL TIMW

The cause of the error was that there was no XDNQASLSN job running.

This is an important job as it's the listener job for XDN- the Direct Drive DBSL program for IBM i, so in essence without it the import was failing when it was trying to connect to the databse.

I hope this helps

Kind regards,

JDimas

[Former Member]

Hello João,

thanks, it helped :-).

Kind regards,

Mark