SPS-Update: Max. number internal sessions reached

[christoph_ostrop]

When trying to logon via SAPGUI we only get the message:

Maximum number of internal sessions reached

(in our case the message is in German: "Maximale Anzahl interner Modi erreicht")

Situation:   SAP-on-i (AS400)

OS-Vers:  V6R1M0

Kernel 7.01-PL: 150

run BW-System NW-7.01 SPS06 , tried to update to SPS11 with SPAM (7.01-45)

when the update-batchjob (runs for more than 3 hours) shows no significant action,

we tried to logon again -

but "Maximum number of internal sessions reached"

what to do?

Chris

[thomas_obermeier · Accepted solution]

Hi Chris,

Sounds pretty much like what is described in note 1676865, although the target stack is different:

In referenced note 396802 you find a workaround to logon to the system. If you managed to do so you should run report SDB4GEN and disable the workaround again. But the notes explain the steps in sufficient detail...

If this helps, let us know so the notes can be adjusted to cover your case.

Regards,

Thomas

[christoph_ostrop · Accepted solution]

as in note 396802

Im SAPLOGON -> Options -> Additional command line arguments

"/SUPPORTBIT_ON=EMERGENCY_REPAIR" eintragen.

the Logon-Screen is empty, only in the Menü-Line "System" and "Help" ,

but all sub-actions within the help-panel are deactivated or disabled.

no prompted field user password,

only in the status-line the error "Maximum number of internal sessions reached"

[thomas_obermeier · Accepted solution]

Hi,

Just to rule out a misunderstanding: note 396802 is talking about the application SAP Logon which gives you access to your configured systems' GUI, not about the logon screen of this GUI itself.

HTH,

Thomas

[christoph_ostrop · Accepted solution]

first i thought i get totally lost,

but now, i found the mentioned logon-Application (gui with listed SAP-systems to logon to ....)

and were to set the support-bit ...... (Options)

yes, we did as in note 1676865 described and now we can logon again.

Thomas, thank you very much for your helpful answer to this problem "Maximum number of internal sessions reached"

so, now we have to face to the SPAM Update and TP problems of the SPS-update.