SAPGui Maximum runtime exceeded

Let the world know ...Tweet about this on TwitterShare on Google+0Share on Facebook0Email this to someoneShare on LinkedIn0

Systems you work with have a timeout parameter. You may be logged on or an anonymous user, in both cases the system creates a session for you and controls its lifetime. This is not to remind you to get your work done rapidly, but mostly to ensure that a long living session is not eating up too much resource (so, short, yes, it is to ensure you get your work done rapidly). The timeout period for a session depends on your system. Normal time is between 10 minutes to 30 minutes. In a SAP NetWeaver ABAP system, the time is set by default to 10 minutes, or 600 seconds. The counter is reset each time a commit is issued by the running ABAP program.

It can, however happen that you reach a timeout.

What to do? I have to say that my system was a little bit busy. I restarted my dev system and all went back into normal. As an alternative, you can change the timeout parameter. How to do this and why you should not do this is explained in SAP Note 25528.

  • Profile parameter: rdisp/max_wprun_time
  • Tx: RZ10 (permanent change)
  • Tx: RZ11 (only until next restart)
Let the world know ...Tweet about this on TwitterShare on Google+0Share on Facebook0Email this to someoneShare on LinkedIn0

One thought on “SAPGui Maximum runtime exceeded

  1. Pingback: Install your own SAP NetWeaver ABAP system | It`s full of stars!

Leave a Reply

Your email address will not be published. Required fields are marked *