I had only two connections, and these were manually added to the previous NWBC 4.0 client.
#GOOGLE UUID GENERATOR INSTALL#
After upgrading from SAPGUI 7.30 and NWBC 4.0 to a combined NWBC5.0 & SAPGUI 7.40 install I ran into some of the same symptoms as you mention, although not the exact same, but perhaps worth mentioning.Īfter the upgrade I no longer had the connections normally listed in the saplogon.ini file.
Hope this helps some of you with you NWBC/GUI setups and deployments! Once I added these entries for the new systems, i didn’t have any of the buggy behavior mentioned earlier, and was able to re-setup my logon entries permenantly, and call SAP GUI t-codes from my NWBC sessions via the message server load balanced connections! I happened to have a SDK on my computer which came with Microsoft’s uuidgen tool, so I opted to use that.
#GOOGLE UUID GENERATOR GENERATOR#
If you do a google search for uuid generator you’ll find plenty. (note: the entire xml file is NOT shown here)Īt first I wasn’t sure if there was any logic to creating the uuid, then i found in the Installation Guide on page 67 that you could use any uuid generator to do so. It is composed of uuid = generated uuid, name = System ID (SID), host = message server host, and port = message server port. The key is to create your message server entries in your %APPDATA%\SAP\Common\ SAPUILandscapeGlobal.xml file. Needless to say I would say there is some sort of bug going on here, but I did find a way to get these working. 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 kommentar(er)
