Solution : https://service.sap.com/sap/support/notes/449270 (SAP Service marketplace login required)
Summary : Key words : Related Notes :
During SAP system upgrades or transport applications, there may be instances where the transport appears to stall. The issue often presents itself through error logs in the SLOG and dev_evt files, indicating failed background job initiators due to misconfigured system identifiers in the sapevt tool. Reasons for this may include improper handling of the QoS-settings on Windows 2000 platforms or incorrect configurations set in the DEFAULT.PFL, especially when the tp program is executed from an application server instead of a message server. To address this, SAP administrators must ensure that a correctly configured DEFAULT.PFL is accessible across all application servers in the SAP landscape. The PFL file should properly define system-relevant parameters such as rdisp/mshost, rdisp/msserv, and SAPSYSTEM. Additionally, checking and updating the services file for accurate sapms
rdisp/mshost = <hostname>rdisp/msserv = sapms<sid>sapsystem = 00, pflb12/system_pf=/usr/sap/trans/bin/default, \usr\sap\a11\sys\profile\default, maintainthe transport profile parameter <sid>/system_pf, btcevtraise sap message server host, set orare set incorrectly, \%wind_dir%\system32\drivers\etcand, sapms<sid> service exists, sap message server host, sap message server service
978127 SAP NetWeaver 2004s SR2 Installation: IBM eServer iSeries 972262 Inst.NW 7.0(2004s)SR2/Business Suite 2005 SR2-UNIX 967123 SAP NetWeaver 7.0 / Business Suite 2005 SR2: Windows 855897 SAP Business Suite 2005 Installation:IBM DB2 for i5/OS 805447 iSeries: Known problems with secondary languages 556941 Transport FAQ: Error scenarios 180940 Microsoft QoS support 11661 Event-driven call of background jobs does not work