(sapevt.exe/SAP TRIGGER RDDIMPDP) Background jobs cannot be started. Please check trace file dev

Your SPAM / SAINT update execution stuck / hanging at the triggering batch events (sapevt). In SLOG or tp system log, the following error keeps occurring.

WARNING: The following call returned with exit code 5: 
WARNING: E:\usr\sap\SID\DVEBMGS00\exe\sapevt.exe SAP_IMPORT_STOP name=SID nr=00 pf=\\ITSITI\sapmnt\SID\SYS\profile\DEFAULT.PFL -t 
WARNING: Please check trace file dev_evt. 
WARNING: (This warning is harmless if no further warnings follow.) 
STOP imp all SID 0200 20200403033556 SIDadm ITSITI 20200403033037000816

From DEV_EVT log file, below error message is captured,

Fri Apr 03 03:32:43 2020
Trace File of External Event Raiser (Level=0, Append=0)

******* Complete Call: *******
E:\usr\sap\SID\DVEBMGS00\exe\sapevt.exe
SAP_TRIGGER_RDDIMPDP
name=SID
nr=00
pf=\\ITSITI\sapmnt\SID\SYS\profile\DEFAULT.PFL
******* End of Call *******

EventID: SAP_TRIGGER_RDDIMPDP
SAP message server host: ITSITI
SAP message server service (new): 3901
SAP message server service (old): sapmsSID
*** ERROR ***: MsSndTypeOnce, rc = -9
*** ERROR ***: Event raise failed
*** ERROR ***: Get message server parameters, rc = 5

Solution

There are multiple causes for this issue and you can refer to SAP Note 2036084 – WARNING: Background job RDDIMPDP could not be started or terminated abnormally to identify your exact error cause on the scenarios.

For our issue specifically, the SAP Note 2036084 state,

Scenario B: The transport seems to be hanging. The SLOG shows an error with exit code 5:
The message server port is not configured properly, or another service is using it.
Please refer to the SAP KBA 2074984 – RDDIMPDP job cannot be started due to duplicated services

We are able to rectify the issue due to duplicate port configured for message server. From SAP Note 2074984 ,

Firstly make sure the items from the points below are fulfilled:
Profile parameters and ports are set as described in SAP note 449270
RDDIMPDP job is scheduled as described by article 1712442
Additionaly, ensure that the port used for the message server is not used in any other service: Check service file (/etc/service on UNIX or \%WIND_DIR%\system32\drivers\etc on WINDOWS) for duplicates of this port. Do the same for the port specified in rdisp/msserv_internal in case this parameter is defined.
Remark: Check SAP Notes 826779 and 821875 in order to determine whether rdisp/msserv_internal parameter has to be defined.

Our colleague encountered below error message,

Fri Feb 14 00:53:47 2020
Trace File of External Event Raiser (Level=2, Append=0)

******* Complete Call: *******
sapevt.exe
SAP_IMPORT_STOP
name=SID
-t
******* End of Call *******

EventID: SAP_IMPORT_STOP
*** ERROR ***: Cannot determine mshost

The solution is to refer on Scenario A.

Logon to the TMS domain controller system, client 000.
Run transaction STMS -> System Overview -> double click on the affected system -> Transport Tools tab
Remove the parameter SYSTEM_PF
Save, distribute and activate the TMS configuration.
Implement the SAP Note 2785030 in the development system and transport the code corrections to all systems in the TMS domain

Reference

2074984 – RDDIMPDP job cannot be started due to duplicated services
2304534 – Events cannot be triggered by sapevt. MSOP_ACCESS_DENIED
SAP Note 2036084 – WARNING: Background job RDDIMPDP could not be started or terminated abnormally
449270 – Job RDDIMPDP is not triggered by sapevt
1712442 – Transport request hung during import. Background job RDDIMPDP is not scheduled.