Skip to Content

Hi All,

I would like to discuss one of the possible way to troubleshoot the error “Work process restarted; session terminated” error from Basis perspective.

If you are not from SAP Basis team and facing this error, you might need additional authorization for few transactions mentioned below.

I will be discussing the generic steps to be followed and also the error I came across in my scenario.

To give a heads up my SAP GUI session was getting terminated while searching a role with certain Authorization Value from SUIM transaction.

Sometimes while working on SAP GUI the user session gets terminated with this error and below pop up

Below are the steps I followed to find the root cause and fix this error:

Step1 : Check SAP system log (SM21)

Check SM21 logs for the particular user whose session is getting terminated with this error.

This would give you a basic idea on what is triggering the issue.

If you could understand this log from your previous experience you cracked the issue in Step 1, if not go to Step 2

In my case, the issue was with DB Rollback failed.

Step2 : Check the relevant work process trace (ST11)

The work process trace should give you more information on the error, in most of the cases the work process gets terminated when the heap memory and extended memory gets exhausted. So check your system memory configuration if these settings are maintained correctly.

If you feel that memory configuration is not the issue or if the error still occurring after changing the memory settings goto Step3.

In my case, the WP trace provided the below information.

And I see that the my work process is using both heap memory and extended memory before getting restarted.

You will be able to see this in ST02

Refer SAP note : 1825408 – MSS: DbSlRollback96 while DBIF already active

Step3 : Collect User trace from ST12.

This would help you to find the ABAP statement / SQL query that is using the work process memory and based on the results you can take required actions to fix the issue.

In my case, from the performance trace I see that the work process was getting stuck on Fetch statement on Object DD04VV

Step4 : Search for SAP notes in service market place or work with your development team to investigate these expensive SQL statements and this should solve your issue.

In my case, the issue was that the View DD04V was missing a join condition and I have implemented the below SAP notes to fix the issue.

2054335 – PFCG : Shortdump when starting the authorization maintenance / incorrect maintenance dialog popup

1993453 – Error during evaluation of authorization intervals in the report SUSR_TABLES_WITH_AUTH

Hope this blog would help you to fix your error sooner.

Leave your comments if you feel I should have done something different or need to include any additional steps to this procedure.

To report this post you need to login first.

2 Comments

You must be Logged on to comment or reply to a post.

Leave a Reply