Hi,
I have a problem with a user session that got stuck in a back-end system. The user is permanently running a DEBUG process that cannot be killed through SM50. Bad thing is that debugging can't be activated by anyone in the system because of this process.
This could have been solved by killing the process by PID on OS level. I don't have physical access to the system, that's why I used SM49 to force a KILLTASK to the server, but problem is that this doesn't really kill the process. I get kill confirmation, but the process continues, only it's PID changes. I tried SAPNTKILL as well - same result.
Any ideas why would this be happening? Am I doing something wrong? Is bouncing the server the only solution?
Yuri
Bluesky
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.