Symptom
You have configured a logon group in the transaction SMLG.
The SAP GUI at the end user's computer was configured to connect to SAP using that group.
The logon works. However, the users always log on at the same instance, even if the current "favorite" ("best") instance (SMLG -> goto -> load distribution) is a different one.
For example, the group "MYGROUP" was created and it includes the instances "server1_TST_00" and "server2_TST_00".
When using this group, all users always logon to "server1_TST_00" even if "server2_TST_00" is listed as the current instance in the SMLG / load distribution screen.
An even strange issue can be simulated by creating a new group that has only one instance (e.g., "server2_TST_00"), and even though SAP GUI was reconfigured to use this new group, the users still logon to instance "server1_TST_00".
Observation: the logon works only if the instances have the same instance number. If different instance numbers are used, the logon fails because the Dispatcher port number (32xx) does not match the target server.
Read more...
Environment
- SAP NetWeaver ABAP based product
- ABAP Platform based product
Product
Keywords
KBA , BC-CST-LG , Logon group based load balancing , BC-FES-GUI , SAP GUI for Windows , BC-CST , Client/Server Technology , BC-NET , Obsolete - Formerly used for network tests , BC-CCM-CNF-GRP , Workload Balancing and Group Management , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.