Skip to end of metadata
Go to start of metadata

Users were getting error "Maximum number of connected terminals reached" while logon to R/3 System.

Error Logs:

Trace file: /usr/sap/<SID>/DVEBMGS<nr>/work/dev_w0

M  *** ERROR => DpTmAdmGetIdx: bad list index 200 [dpxxtool.c   2556]
M  *** ERROR => DpTmAdmGetIdx: bad list index 200 [dpxxtool.c   2556]
M  *** ERROR => DpTmAdmGetIdx: bad list index 200 [dpxxtool.c   2556]
M  *** ERROR => DpTmAdmGetIdx: bad list index 200 [dpxxtool.c   2556]

Trace file:  /usr/sap/<SID>/DVEBMGS<nr>/work/dev_disp

Network error of client T44, NiBufReceive (-6: NIECONN_BROKEN), dp_tm_status=3
Client address of T44 is 10.200.115.125(<Terminal name>)
***LOG Q04=> DpRTmPrep, NiBufReceive (21571 44 <Terminal name>) [dpxxdisp.c   9813]
RM-T44, U21571, 000             , <Terminal name>, 00:36:45, M0, W0, SESS, 2/0
Network error of client T106, NiBufReceive (-6: NIECONN_BROKEN), dp_tm_status=3
Client address of T44 is 10.200.115.125(<Terminal name>)
***LOG Q04=> DpRTmPrep, NiBufReceive (21571 44 <Terminal name>) [dpxxdisp.c   9813]
RM-T106, U21563, 000             , <Terminal name>, 00:26:45, M0, W0, SESS, 2/0

 

Root cause:

The space available in the C table tm_adm is not sufficient for another terminal to log on to this applicatin server.  The number of table elements is determined by the profile parameter 'rdisp/tm_max_no' when the application server is started. Important: For internal purposes one entry for each work process and
one entry for each CPIC connection is made in tm_adm in addition to an entry for each work process.

Parameter 'rdisp/tm_max_no' value was set to 200 and when number of terminals exceed 200, users were getting an error "Maximum number of connected terminals reached" during login screen initiation.

Solution:

Instance restarted.

Logon to SAP system. Execute T-code RZ10 to change profile parameter.

Change profile parameter 'rdisp/tm_max_no' to more than 200.

Restart SAP instance.


 

  • No labels

2 Comments

  1. Former Member

    Thanks Ganesh, this is very helpful! One minor correction..

    In the solution, you state "Change profile parameter 'rdisp/tm_max_no' to more than 2000.". I believe you mean "Change profile parameter 'rdisp/tm_max_no' to more than 200."

  2. Former Member

    We have this error on our system. Log Q04 but the user aren't disconnect and the parameter rdisp/tm_max_no ahve been already increase.

    And this error "Maximum number of connected terminals reached" never happen but log Q04 happen 600 times per day