2036084 - WARNING: Background job RDDIMPDP could not be started or terminated abnormally.

Symptom

This issue can happen when an import has to be made into the system, therefore it can happen during an ABAP stack upgrade/update, a Support Package installation or a Transport Request import.

Scenario A: The transport seems to be hanging. The SLOG shows an error with exit code 4 or exit code 7:

ERROR: System <SID>. Warning.        <timestamp> :
ERROR:       The following call returned with exit code 4:
ERROR:        sapevt.exe SAP_TRIGGER_RDDIMPDP -t name=<SID>
ERROR:       Background jobs cannot be started.
ERROR:       Please check trace file dev_evt.
ERROR:       (This warning is harmless if no further warnings follow.

or:

WARNING: System <SID>. Warning.        <timestamp> :
ERROR:       The following call returned with exit code 7:
ERROR:         sapevt.exe SAP_TRIGGER_RDDIMPDP -t name=<SID>
ERROR:       Background jobs cannot be started.
ERROR:       Please check trace file dev_evt.
WARNING:       (This warning is harmless if no further warnings follow.)

In the dev_evt file, the following message can be seen:

Trace File of External Event Raiser (Level=0, Append=0)
******* Complete Call: *******
sapevt.exe:
SAP_TRIGGER_RDDIMPDP
name=<SID>
******* End of Call *******

EventID: SAP_TRIGGER_RDDIMPDP
*** ERROR ***: Cannot determine mshost

Scenario B: The transport seems to be hanging. The SLOG shows an error with exit code 5:

WARNING: System <SID>. Warning. <timestamp> :
ERROR: The following call returned with exit code 5:
ERROR: sapevt.exe SAP_TRIGGER_RDDIMPDP -t name=<SID>
Background jobs cannot be started.
ERROR: Please check trace file dev_evt.
WARNING: (This warning is harmless if no further warnings follow.)

In dev_evt file, the following is displayed:

******* Complete Call: *******
sapevt.exe
SAP_TRIGGER_RDDIMPDP
name=<SID>
******* End of Call *******

EventID: SAP_TRIGGER_RDDIMPDP
SAP message server host: <hostname>
SAP message server service (new): <port>
SAP message server service (old): sapms<SID>
...
*** ERROR ***: DpBtcSendEvtMessage, rc = -9
*** ERROR ***: Event raise failed
...
*** ERROR ***: Get message server parameters, rc = 5

Scenario C: The upgrade stops. The SAPup.ECO and the SLOG shows an error with Invalid entry found in table TRJOB. Function: J:

SAPup.ECO:

ERROR: System <SID>. Error detected  <date and time> :
ERROR:       Invalid entry found in table TRJOB. Function: J Jobcount: 13442100.
ERROR:       Background job RDDIMPDP could not be started or terminated abnormally.
ERROR:       Please check the system. Use transactions SM21, SM37, SM50.

SLOG:

Based on transaction SM37, it seems that the background job for RDDIMPDP is not being executed:

Job                              Spool Job doc Created B Status          Start date Start time Duration(sec.) Delay (sec.)
RDDIMPDP                                                        Scheduled                                                    0               0
RDDIMPDP                                                        Released 0              0

Scenario D: The upgrade or transport import stops. The SLOG shows an error with exit code -9:

SLOG:

WARNING: System <SID>. Warning.        <date and time> :
ERROR:       The following call returned with exit code -9:
ERROR:         sapevt.exe SAP_TRIGGER_RDDIMPDP -t name=<SID>
ERROR:       Background jobs cannot be started.
ERROR:       Please check trace file dev_evt.
WARNING:       (This warning is harmless if no further warnings follow.)

dev_evt:

*** ERROR ***: MsSndTypeOnce, rc = -9
*** ERROR ***: Event raise failed

Scenario E: The upgrade or transport import stops. The SLOG shows an error with exit code -20:

SLOG:

WARNING: System <SID>. Warning. <date and time>  :
ERROR:       The following call returned with exit code -20:
ERROR:         <DIR_HOME>\sapevt.exe
SAP_TRIGGER_RDDIMPDP -t name=<SID> nr=<no> pf=<DIR_PROFILE>\DEFAULT.PFL
ERROR:       Background jobs cannot be started.
ERROR:       Please check trace file dev_evt.

dev_evt:

*** ERROR ***: MsSndTypeOnce, rc = -20
*** ERROR ***: Event raise failed

dev_ms:

[Thr 10008] *** ERROR => MsSClientHandle: client <IP number of client> (
<IP number of client>) is EXTERNAL, access denied [msxxserv.c 4863]

Scenario F: The upgrade or transport import stops. The SLOG shows an error with exit code -43:

SLOG:

WARNING: System <SID>. Warning. <date and time>:
ERROR: The following call returned with exit code -43:
ERROR: sapevt.exe SAP_TRIGGER_RDDIMPDP name=<SID> tpsid=<SID> pf=<DIR_PROFILE>\DEFAULT.PFL -t
ERROR: Background jobs cannot be started.
ERROR: Please check trace file dev_evt.
WARNING: (This warning is harmless if no further warnings follow.)

dev_evt:

*** ERROR => DlLoadLib()==DLENOACCESS - LoadLibrary("<DIR_LIBRARY>\sapcrypto.dll")
Error 126 = "The specified module could not be found." [dlnt.c 322]
*** ERROR => ssfPkiInitSAPCryptolib: SsfSupInitEx("<DIR_LIBRARY>\sapcrypto.dll")==10 (SSF_SUP_NOLIB) [ssfxxpki.c 209]
*** ERROR => ssfPkiInitSAPCryptolib: FAILED to load SAPCRYPTOLIB ssfPKI functions unavailable! [ssfxxpki.c 258]
PKI library initialization failed

Environment

SAP NetWeaver release independent.

Product

SAP NetWeaver 2004 ; SAP NetWeaver 7.0 ; SAP NetWeaver 7.3 ; SAP NetWeaver 7.4 ; SAP NetWeaver 7.5 ; SAP enhancement package 1 for SAP NetWeaver 7.0 ; SAP enhancement package 1 for SAP NetWeaver 7.3 ; SAP enhancement package 2 for SAP NetWeaver 7.0 ; SAP enhancement package 3 for SAP NetWeaver 7.0

Keywords

RDDIMPDP, SLOG, exit code 4, exit code 5, exit code 7, exit code -9, exit code -20, exit code -43, SAP_TRIGGER_RDDIMPDP, Event raise failed, MsSndTypeOnce, rc = -20, rc = -9, rc = 5, Cannot determine mshost, Function: J, system/secure_communication , KBA , BC-CTS-TMS , Transport Management System , BC-UPG-TLS-TLA , Upgrade tools for ABAP , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.