Symptom
When accessing SM37 and trying to open the job log of a finished/canceled batch job, the error "Error reading job log JOBLGX*" is triggered.
Also, in the PID column on SM37, the PID number of the affected jobs is not found in SM51:
SM37 ->
JobName Job CreatedB Status Start date Start Time Executing server WP no. PID
JOB WITHOUT JOB LOG -> EXAMPLE_JOB EXAMPLE_USER Finished 05.07.2024 12:17:57 example_AP1_00 6 20.426 <- PID does not exist in example_AP1_00 work processes
JOB WITH JOB LOG -> EXAMPLE_JOB EXAMPLE_USER Finished 05.07.2024 00:54:06 example_AP1_00 7 19.334 <- Exists in example_AP1_00 work processes
SM51 -> example_AP1_00 ->
Read more...
Environment
SAP_BASIS 740
SAP_BASIS 750 | SAP S/4 HANA 1511
SAP_BASIS 751 | SAP S/4 HANA 1610
SAP_BASIS 752 | SAP S/4 HANA 1709
SAP_BASIS 753 | SAP S/4 HANA 1809
SAP_BASIS 754 | SAP S/4 HANA 1909
SAP_BASIS 755 | SAP S/4 HANA 2020
SAP_BASIS 756 | SAP S/4 HANA 2021
Product
Keywords
BT167, Message no. BT167, missing joblog, Error 2 for write/read access to a file, PID. , KBA , BC-CCM-BTC , Background Processing , Known Error
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.