cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to view or change authorisations in PFCG

Former Member
0 Kudos

Hi All,

When trying to edit or display the authorization data in PFCG the system seems to start loading but after a while it times out and closes down the session then we get the error.

Can you please advise what could be the reason and how to get resolved?

Thanks in Advance

Regards,

Satyardha

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member182657
Active Contributor
0 Kudos

Hi,

Could you share the system log from SM21 and are you getting any dumps under ST22.Also make sure correct timeout values for the parameters into the systems.

Check with values of parameter rdisp/gui_auto_logout & rdisp/max_wprun_time

Regards,

Former Member
0 Kudos

Thanks for your reply.

The logs I have found are

Unexpected return value 1 when calling up DbSlR

Function ROLLBACK on connection R/3 failed

Error in DB rollback/SyFlush, return code 016384

and I couldn't find any dumps regarding this.

I have checked both parameters, they are set to default values.

Could you/anyone please let me know "rdisp/gui_auto_logout"- parameter responsible?

How this is related to time out error.

Regards,

Satyardha

former_member182657
Active Contributor
0 Kudos

Hi Satyardha,


Error in DB rollback/SyFlush, return code 016384

Issue related with memory management here (Extended or Heap area ).For that could you check solution under SAP KBA   1342311 - DB6: DbSlRollbackDB6 while DBIF already active

Hope this will help you.

Regards,

Former Member
0 Kudos


Hi Reddy,

Just on other side can you check space on your file system and also on tablespace as well.


Regards,

Deepanshu Sharma

Former Member
0 Kudos

rdisp/gui_auto_logout parameter denotes how long a user session can remain idle.

suppose if set to 600 seconds if the user session is idle for 600 secs GUI auto logs out the session.


Are you able to execute other transactions apart from PFCG.. Please check the WP utilization.

This issue happening all of a sudden or after Kernel upgrade/ system copy?