Skip to Content
Technical Articles
Author's profile photo Roman Gorbenko
Roman Gorbenko
June 4, 2020 1 minute read

Resolution for SM50->Administration->Work Processes->Cancel with/without core does not work

Attention!
SAP BASIS Administrator: The more rights in the system the more responsibility.
additional verification, additional call to the user and additional backup will not be superfluous

Symptoms

Symptoms of zombie processes
Transaction – SM50 (Work Processes of AS Instance)
WP Status – “Running” and Time – <Abnormal values>
For example Time on screen
3296541 seconds -> approx. 38 days (absolutely abnormal values)

Addition verification:
Transaction – SM04 (User Sessions of AS Instance)
Verification of abnormal situation – Session for the user from previous screenshot not exists in the list

Prerequisites

You try to execute
SM50->Administration->Work Processes->Cancel with/without core
but no results

Resolution for Windows

  1. Open Powershell as Administrator
  2. Get-Process -id <Process ID from SM50>

  1. Stop-Process -id <Process ID from SM50> -force

Resolution for Linux

  1. Logon as the root user
  2. ps aux | grep <Process ID from SM50>
  3. kill -9 <Process ID from SM50>

Conclusion.

SAP BASIS Routine task with examples from real life was provided

Assigned Tags

      4 Comments
      You must be Logged on to comment or reply to a post.
      Author's profile photo S Sriram
      S Sriram

      Hi Roman.

      Nice one

      Regards

      SS

      Author's profile photo Roman Gorbenko
      Roman Gorbenko
      Blog Post Author

      Thank you so much, Mr.Sriram

      Author's profile photo Isaias Freitas
      Isaias Freitas

      Hi,

      I do not know exactly how "Stop-Process" (on Windows) works. But the "-force" option seems to point to something similar to a "kill -9".

      I would say that using "kill -9" (or equivalent on Windows) should be the last resource. First maybe try with "kill -2" or "kill -6".

      If "kill -9" had to be used, then I would advise taking a clean restart of SAP as soon as possible, as terminating a process with signal 9 can lead to inconsistencies in the SAP shared memory areas and resource deadlocks. It is not possible to predict what issues might occur after a process was terminated with signal 9, but they would range from random errors to a complete instance standstill / hanging situation.

      By clean restart, I mean:

      • On Windows, a server reboot (Windows restart).
      • On Linux / UNIX:
        - stop SAP
        - execute "cleanipc XX remove" (where "XX" is the SAP instance number)
        - start SAP

      Regards,

      ISaías

      Author's profile photo Roman Gorbenko
      Roman Gorbenko
      Blog Post Author

      Hello, ISaías

      Thank you so much for the useful tips.