The SID and message server host would disappear from the logon pad entry and if I looked at the details I’d get an error “ Message server has been changed and no group/server is available“ SM04, which would generate a messageĮrror parsing SAP GUI command line ‘ /FULLMENU SNC_PARTNERNAME=”p:…” SNC_QOP=0 /UPDOWNLOAD_CP=0 /SplashScreeOff /Theme=corbu /FontSize=100 /AccMode=0 /Rtl=0’Īnd then odd things started happening with the associate SAP GUI logon pad entry. So i choose to setup a user defined entry, and once connected to the backend, tried to start a GUI transaction, eg. The best summary of the behavior i can give is that the newly defined system would randomly disappear from the list of systems to create a logon entry for When setting up a connection to a new system in the logon pad (New Entry –> User Defined –> Connection Type: Group/Server Selection) you’ll need to include the port # now ( :) which Andreas mentions in this threadĪll was well until i tried creating NWBC logon entry. In our environment we rely on message server logon load balancing for our SAP GUI connections. Issues with Message Server Logon Load Balancing This all seemed to work great when I installed the new front end tools, but I ran into issues as soon as I started trying to setup new system connections. And if you had a previous version of SAP GUI installed, your ini files and etc/services relevant enteries were migrated to these new files the first time you launch the logon pad. These new files (in %APPDATA%\SAP\Common\) are SAPUILandscapeGlobal.xml and SAPUILandscape.xml. The new NWBC 5.0 and SAP GUI 7.40 when installed together leverage a new common set of XML files for managing connection entries.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |