Symptom
Following situations may require a Scheduler manual restart to help with successful q/t RFC processing:
- Inbound Scheduler (SMQR) or Outbound Scheduler (SMQS) mechanism is stuck (e.g. SM04 user locked).
- Pending RFC sessions in Transaction AL08 causing the schedulers not to trigger any new queues
Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.
Read more...
Environment
- SAP NetWeaver
- SAP NetWeaver Application Server for SAP S/4HANA
- ABAP PLATFORM - Application Server ABAP
Product
Keywords
SMQ1, SMQ2, SM58, QUEUED RFC, TRANSACTIONAL RFC, deregistration, registration, restart scheduler, qout scheduler, qin scheduler, inbound, outbound, stuck, hanging, lost, dump, inactive, waiting, active, SM04, user locked, RSARFCEX, RSTRFCQDS , KBA , BC-MID-RFC-QT , Queued RFC (qRFC) and transactional RFC (tRFC) , BC-MID-RFC , RFC , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview