NWBC 5.0 & SAPGUI 7.40 - Tips 'n Tricks

[TomVanDoo]

Right, I installed the latest and greatest tools from SAP last week, and I ran into a load of trouble.

Step by step, I managed to sort most of them out, but for those that are still struggling, let me list some of the issues I encountered and how I fixed them

SAPLogon.ini

It all starts here. You've just installed the new SAPGUI 7.40, and gone are all your system connections. very annoying...

Here's how to fix it:

It all starts in your SAPGUI configuration. You need to know where your config files are stored.

Go to your windows explorer and navigate to this folder. You'll see some files there. These are the ones you need:

When you launch your SAPLogon, an automatic migration will happen from your SapLogonTree.xml (which may refer to saplogon.ini and shorcuts.ini)

In case you have multiple saplogon.ini files, you can hook them up in your SapLogonTree.xml and they will be migrated as well.

<Files>



<File type="Connections" name="saplogon.ini"/>



<File type="Shortcuts" name="sapshortcut.ini"/>



</Files>

That migration program will create 2 new files:

In some cases all of this fails and the SAPUILandscape.xml stays empty. Arf.

In such cases, you can launch the NWBC 5.0 and restart the migration from there.

(Keep the CTRL key pressed down while you click through the menu)

Be sure to select the right view in both your NWBC and your SAPLogon as the tree is structured differently from what it used to be.

In NWBC you can select the workspace to work in

In SAPLogon, you can change the view

NWBC navigation tree

Getting strange error messages on your NWBC navigation tree?

Those have to do with your menu selection. Typically in the NWBC, you'll want to see your specific user menu, rather than the general SAP Menu.

Normally the user menu is defaulted, but if you're like me, and you click on everything, you may have turned it off.

Here's how to fix it:

From the NWBC menu, you can go to settings->personalization and make sure the SAP Menu is unchecked.

Blue crystal theme in SAPGUI

Don't use it, yet. [update: PS, this is fixed since a while (a big while) and the blue crystal theme does look better than Corbu, so switch]

Some buttons and screen areas tend to disappear in this new theme.

Take transaction PFCG for example. If I want to add a folder as a sidepanel, I can't see the button for extra node options any more.

These guys:

Don't appear anymore in Blue_crystal

So do yourself a favor, and wait until some patches appear.

Passwords in shortcuts

I know, this is a bad practice, but if you have 300 systems in your SAPLogon like me, it's an easy solution.

Which, BTW, no longer works. You can still enter your password in the shortcut, but after a restart of the SAPLogon, they are removed.

Here's how to overcome that issue:

In the sapuiLandscape.xml file, you can manually add your passwords for each shortcut with the addition passwd="<pass>".

Obviously, this creates a securiy risk, so I don't advise it.

To prevent loss of your password entries, just make the file read-only.

[Edit] Don't make the SAPUILandscape.xml file readonly. While it will still work for you initially, at some point in time, NWBC is going to make a backup of the file, and if it can't access it's own backups, it won't start at all!

To figure this out, look into the logs: C:\Users\<user>\AppData\Local\SAP\NWBC\Traces

In earlier saplogons, I had an option to encrypt the password. (making it at least a little bit safer) That option doesn't seem to work on the new XML file :sad:

On the upside, if you create NWBC entries for all your systems, you can have your browser remember the passwords :smile:

Duplicated NWBC entries

You may have experienced that your NWBC logon entries (so not the SAPGUI logon entries, but the specific NWBC entries) get duplicated every time you launch the NWBC. At least I have. Which is really annoying, cause it makes your NWBC go slower and slower on each launch.

And after about 20 relaunches, you get a massive SAPUILandscape XML file and neither your NWBC, nor your saplogon will start anymore.

the only solution is to delete the NWBCOptions.XML and NWBCOptions.BAK and to clean out your SAPUILANDSCAPE.XML file of all NWBC entries. (that's why I keep a backup of that file)

The reason for this is simple. Every time you launch the NWBC, it executes the migration tool. But there seems to be a bug in there which causes it to migrate every NWBC entry which is not located in the root of your workspaces again, and again, and again,...

Solution: open up your registry editor and find following key:

HKEY_CURRENT_USER --> Software --> SAP --> NWBC --> Settings --> LShape --> DontUseSapGuiMigrationTool

and set it to True.

That should stop the NWBC from migrating your NWBC entries all the time. At least it did for me.

Update:

There is a new patch available for NWBC 5.0

Patch Level 4, which again fixes some quirks:

- The annoying mouse cursor

- The instance id that always got reset to 00 now stays remembered when you change it

- No more duplicating of histoic NWBC entries (at least not for me)

the Password addition in shortcuts doesn't seem to work anymore, at all. not in SAPGUI, not in NWBC and it ignores the regedit entry to store passwords completely.

The best alternative I have to offer, is by using the NWBC for what it's intended:

connect to the NWBC service of your SAP system.

Logon goes via HTTPS in browser

let the browser remember your password.

Update 2:

PL5 for NWBC was released a couple of weeks back.

More info was released of the transition role of NWBC

Launch error

I noticed a strange quirk with a fresh NWBC installation on the Laptop of one of my colleagues. For some reason, the darn thing wouldn't start. the splash screen would show for half a second, and then everything disappeared again. There were some errors in the logging with regards to the .Net framework (which was fine by the way)

The solution turned out to be: Launch the NWBC once via the NWBCCore.exe

After that, the regular shortcut worked just fine.

[Mark_Teichmann]

Nice blog, Tom.

Looks like the release was not tested properly before releasing it to the public.

I am using Blue Crystal-Theme without greater problems so far. But inspired by your blog I started PFCG. It instantly crashes my SAP Gui I tried it on a 7.40 ERP and also on a 7.02 ERP.

Cheers,

Mark

[TomVanDoo]

Auch! maybe the blue_crystal theme was an afterthought and they didn't spend enough time testing it?

In the NWBC, it automatically switches back to Corbu. (at least for me it does)

Apart from the theme, and the initial trouble, I'm quite pleased with the new sapgui and the NWBC.

There don't seem to be that many changes, but the logon tree and the workspaces already make a difference for me.

[Former Member]

Fantastic .......Enjoyed every bit of it .....

Bravos....

-Dexter

[Former Member]

Thi Tom,

That is really helpful, it helped me a lot with my logon pad. which i lost because we used a serverside logon pad.

I have been in contact with development team on NWBC 5.0 on this topic and they would take it into consideration

[ro9]

Hi!

"glad" to hear that there are othere who is also experiencing problems with the new 7.40/nwbc 50 combo.

I cant launch PFCG either - i crashes rigt away.
Will try to revert the theme to Corbu again

[TomVanDoo]

There are more issues than just the ones I listed.

for example: the code editor keeps crashing if you connect to a NW 7.0 system and try to use the new-frontend editor.

If you stick to the old editor, it doesn't crash.

I use the NWBC5 for all my activities (demos, development, customizing,...) and I find it to be unstable and buggy.

So my advise would be, wait for patch level 3. Hopefully SAP will tackle many of these issues.

[JK]

thanks for saplogon.ini migration procedure 🙂

[Former Member]

Hi Tom,

Great blog post! Thanks for sharing. I had many issues with the initial release of SAP GUI 7.4 as everyone else, but I just downloaded the SAP GUI 7.4 Patch level 1 that was released today and it fixed many of the issues that I was seeing (Including missing router strings, SAP GUI and NWBC 5.0 not working together, color issues with the ABAP editor). I also checked PFCG with the Blue Crystal theme and it looks like SAP fixed the issue with the missing buttons as well!

Let me know if you have any thoughts on the patch and if there are any issues that anyone else is still seeing.

Thanks,

Imran

[TomVanDoo]

Hi Imran,

I too installed PL1 for the SAPGUI 7.40, and it fixes quite a lot of issues I encountered before. (if not all) Looks like I can start recommending the new GUI and NWBC now to my customers.

cheers!

[Former Member]

Hi Tom,

Nice blog. I had found these solutions after much efforts and then came across your blog.My luck..

I have one last problem for which i could not find any help or solution.

I have installed NWBC 5.0 along with SAP GUI 7.40. Both xml files are in the Roaming folder and old ini files were migrated correctly.

Only issue is I cannot create Group/Server Selection connection types in NWBC 5.0. It gives the error hostname NiHL GetNodeAddr unknown .

I cud create the same connection entries when i install SAP GUi 7.4 w/o NWBC.

What shud i be missing?

i have not set any env variable for configuration file path nor any other cosmetic changes.

What can be the issue and if u know of any solution for that?

Thanks ,
Deep Desai

[Former Member]

Hi Tom,

Thank you for this blog. It helped me solving the issue with the duplicate entries in the NWBC. However, I had to use a slightly other procedure.

I started the SAPLogon first, which converted my SAPLogon.ini to the XML files. After each start I got a new entry called "NWBC Admin Configuration (001)(001)" in the SAPLogon and the NWBC got duplicates also. Even when setting the registry entry DontUseSapGuiMigrationTool to True.

To solve it, I removed the SAPUILandscape.xml, SAPUILandscapeGlobal.xml and the NWBCOptions.XML and NWBCOptions.BAK like you wrote, but also the favorites from NWBC. Then I put back the SAPLogon.ini and set the registry option as you described. Next thing was starting the NWBC and performed the migration by SAP GUI tool.

Both NWBC as SAPLogon execute, without generating the duplicates.

I'm using SAPGUI 7.40 patchlevel 1 and NWBC 5.0 PL2 from a new installation, running on Windows 7 x64. I have uninstalled the previous versions of NWBC, SAPGUI 7.30 and related addons before the installation. Also i removed all previous installation locations. I left the Registry untouched.

Maybe its of use for somebody else.

Best regards,

Edward

[Former Member]

Hi Tom

I experienced also the duplicate entries in my NWBC. I just removed the duplicate entries from the client (no fuss with XML-files). The folder LShape was missing in my registry but I just added it and now it works.

Keep up the good work!

ps.: I run on NWBC 5.0 PL3 and Gui 740 PL1.

[achmad_dimyati5]

Hi Tom,

Currently I am working to create new frontend server to upgrade current SAPGUI clients.

Just want to get your opinion.

Is it stable enough to use SAPGUI 7.40 as the frontend server and upgrade current SAPGUI clients?

I have tried the patch 0 and it's really headache. Is it Patch 1 a lot better?

Thanks a lot,

Regards,

Achmad

[TomVanDoo]

I wouldn't use patch level 0 if I were you.

I understand that many customers are weary of using latest versions, as they contain a lot of bugs, but in this instance, definitely go for patch level 1 because it fixes a heapload of issues in the initial release.

is it stable enough? yes, in my opinion, it is. but remember: at the end of the day, I'm just an SAP consultant

[ChristianSass]

Hi,

I've tried your hint for "passwords in shortcuts" but it doesn't work. Do I have to place the "passwd"-tag at a certain position?

I tried:

passwd="mypassword"

password="mypassword"

pw="mypassword"

I use SAP GUI 7400.1.1.1098

Thx

[former_member182293]

Hi,

Same story. How can we activate storing password anywhere for shortcuts? I 'm looking a solution too.

[former_member182293]

If you install both NWBC and GUI  this cause not storing password in sap shortcuts. I have uninstalled NWBC till find(or SAP offer) a better solution to save pass with shortcuts.

[ChristianSass]

It doesn't work in my case -> it's driving me

I uninstalled NWBC and placed passwd="with_my_password" in the landscape file. Did you do anything else?

Thx

[achmad_dimyati5]

After Patch 2 has been released and without NWBC 5.0 installation, I found out SAPGUI 7.40 is quite stable and didn't find any bugs at least for 10 days used.

I think one of the main issue because the integration between SAPGUI 7.40 and NWBC 5.0.

So if you plan to move from SAPGUI 7.30 simply because it will reach end full of support by July 2015, just move to SAPGUI 7.40 Patch 2 without NWBC 5.0.

[TomVanDoo]

update: There is a new patch available for NWBC 5.0

Patch Level 4, which again fixes some quirks:

- The annoying mouse cursor

- The instance id that always got reset to 00 now stays remembered when you change it

- No more duplicating of histoic NWBC entries (at least not for me)

the Password addition in shortcuts doesn't seem to work anymore, at all. not in SAPGUI, not in NWBC and it ignores the regedit entry to store passwords completely.

The best alternative I have to offer, is by using the NWBC for what it's intended:

connect to the NWBC service of your SAP system.

Logon goes via HTTPS in browser

let the browser remember your password.

[achmad_dimyati5]

Hi Tom,

To get the password field enable in SAPLogon please follow these steps:

Create a shortcut

Close your SAPGUI session and SAP Logon

Run Regedit

HKEY_CURRENT_USER\Software\SAP\SAPShortcut

Right Click on SAPShortcut --> New --> Key

Type as Security

Right Click on Security --> New --> String Value

Type EnablePassword

Put value as 1

After that open again SAPLogon

You can put the password after that.

But as I have said in my previous comment, I only use SAPLogon 7.40 Patch 2 and without NWBC.

[Former Member]

I have lost much time to get a stable configuration (Windows 7), that's how I actually got it:

1. To install  SAP GUI 7.4 (search for SAP GUI for Windows in the catalog) then install

SAP GUI FOR WINDOWS 7.40 CORE

then go to Support packages and Patches and the install the four available so far

- SAP GUI for Windows 7.40 patch 1

- SAP GUI for Windows 7.40 PL 01 Hotfix 1 (note 1489891)

- SAP GUI for Windows 7.40 patch 2

- SAP GUI for Windows 7.40 PL 02 Hotfix 1 (note 1489891)

The error "NiHL GetNodeAddr unknown" is solved by one of these patches.

    2. To install NWBC 5.0 (search for NETWEAVER BUSINESS CLIENT in the catalog) then go directly to Support packages and Patches and download

NWBC500_4-20011985.EXE

This patch is in fact a new release of the complete software, so no need to install the old version.

Then launch NWBC and go to Settings -> Personalize, in the chapter Logon, untick the option “Hide system selector on startup”, so that you always have the selector screen to choose the system.

If you had no NWBC systems before, click on the icon Create and enter connection detail

If you click on the icon right to the icon Create, you will see that you have three options:

• New systems connection (NWBC)
• New systems connection (SAP logon)
• New shortcut (SAP logon)

If you have a script error SL__FORM after logon, it is related to the SP level of SAPUI, give this note to your BC friends,

2039046 - NWBC Logon - Script Error in lightspeed.js: Unable to get value of the property 'SL__FORM'

There is no role attached to your user by default. If you want to do some tests, you have to go to SU01 in the GUI, and add a role (check for *AIO* roles for example)

NWBC runs on Internet Explorer, so if you have Internet Security errors you must add the NWBC server to the trusted sites:

Launch IE -> Tools -> Options -> Tab Security ->Trusted Sites and click on the SITES button, add the server name and save.

Hope it helps !!!

[dkle]

interesting:

there is no more "Redo migration by NWBC" option in NWBC 5.0 PL05.

In the big picture I have to say there are still many unsolved issues if all of the following products are used on a single computer:

1. SAP GUI 740
2. NWBC 5.0 PL05
3. AO 2.0 SP03

Main problem is that workspace usage/creation is not unified.

[achmad_dimyati5]

Hi All,

SAPGUI PL03 has been released and still contains quite interesting notes.

2141360 NWBC 5.0 - NWBC Connections entries disappear after creation

2077230 SAPLogon 740: Missing SAPRouter string for System

2137611 SAPLogon 740:new created entries disappear after restarting

Actually, I got above issue since first time installing SAPGUI 7.40 (PL0) and together NWBC 5.0. Then I decided to install SAPGUI 7.40 only without NWBC. The problem has been solved by PL02.

I hope this PL03 really solve it when you put both together.

Best Regards,

Achmad

[Former Member]

Hi Daniel

Regarding your comment about workspace usage/creation - you mean the saplogon.ini and now the new xml file approach? 

I have not tried it yet, but I have another client software from SAP (EasyDMS) that I worry will not work with the xml concept (i.e. I will have to maintain XML approach for NWBC/SAPGUI and INI for EasyDMS). 

[achmad_dimyati5]

Hi Eric,

In case you don't use NWBC, you can use only SAPLogon 7.40 and this will keep the saplogon.ini as the config file similar like previous version. The XML file wont be used.

[dkle]

Hi Eric,

no, I mean xml file approach only because all three tools are using the new xml file approach because of NWBC 5.0.

But the saplogon.ini file does not disappear because of this, so your/other tool/s should still be able to use it. But you probably would have to maintain both configuration concepts individually and the saplogon.ini file manually via Notepad.

Regards

Daniel

[Former Member]

Yes, understood that - but I guess I was "hopeful" that the xml file approach will make things easier at least for running GUI and NWBC.  We have not yet 'pulled the trigger' to tackle NWBC in earnest yet, but this shared config approach helps to make me comfortable.  But then you throw in 'other tools' that use the INI file and, ugh, have to juggle and keep them maintained/deployed to user computers. 

Overall, is your experience with the XML approach a positive one?

[dkle]

The idea behind the XML approach is very good, but the initial problems with this new config method are dampening the mood.

SAP GUI and NWBC in the latest versions are "ready for XML" in my opinion. And if you have EasyDMS already deployed and configured you won't have to adapt it.

I am curious, did NWBC 5.0 receive positive feedback from your endusers?

[Former Member]

We have not yet rolled it out.  Key hurdle is bandwidth on the support team side manifested by these key points:

1. Time to setup the iniitial distribution/registry updates to end user desktops via corporate software distribution tool (SCCM, not the SAP installation server) and testing the ongoing approach for rolling out patches and xml/ini updates.  It seems like there is "always something" that goes wrong with this!

2. "Fear" that we will start getting support calls for features of NWBC that don't work as users try all the cool things it can do.

3. Uncertainty what we may or may not need to do with end-user roles in PFCG so that a user's first logon experience is positive (e.g. may be wrong,but I think if someone who has lots of roles assigned might get a messy page).  I'm sure there is an answer for this, just haven't looked hard enough.

[achmad_dimyati5]

Hi Eric, regarding sapuilandscape.xml and the stability, could you test PL03? I just quick test and it seems quite ok now, finally.

Regarding other application such as EasyDMS, ACL which still use saplogon.ini, you can use converter tool from xml to ini. Its available under saplogon for Java.

For maintenance xml and ini, I just use group policy and bat files. It's quite straight forward. The bat script will be a lot  easier if use standard installation directory as well as one type Windows version in user site.

For NWBC and role menu, via setting in PFCG, we can hide menu from certain roles for NWBC. Create some roles only for menu standarisation. And hide the rest of menu from others.

[former_member195791]

This release is horrendous...

[Former Member]

Yes, this release and whole process of updating the GUI is horrendous...  I go to SAP Support Portal and download the Core and should get the latest Version with Patches.  Not then have to immediately Patch the download.

[Former Member]

I've come to accept that that the family of ALL client software is excluded from the Run Simple mantra at SAP! 

Kidding aside, it is this complexity and cost that helps to create a desire to put things into the cloud.  Although then you deal with browser compatibility issues. 

Oh well.

[TomVanDoo]

Cloud does not necessarily mean that you'll have a browser as client.

Other than that: Typically, the end-user does not install the client software. this is normally done by someone from IT.

As you can see, I was pretty fast to raise a bunch of issues with the release of the NWBC, but that doesn't mean I think it's uphauling.

I Believe the new NWBC releases are crucial in the long term strategy of SAP regarding their UX roadmap.

However, it is impossible to revamp the entire Front-End part of SAP overnight, into Fiori. So the NWBC plays a role in that transition. Which also means that there will be more releases with minor adjustments (and bugs).

We can now all sit here and complain about the (plenty) bugs, or we can raise the issues and look for solutions.

With PL5, yet a whole bunch of bugs have been fixed.

[TomVanDoo]

Hi Achmat,

I'm well aware of the regedit settings, but for some reason, they don't work anymore on my machine.

It could be limited to my machine in particular, but I'm not certain about it.

Thanks for reposting the procedure though, as there were multiple questions regarding passwords.

Cheers!

[Sven]

Hi Tom, same here, what I did:

1. installed 7.4(PL01)+NWBC5 over 7.3 -> password field invisible
2. uninstalled the above, reinstalled 7.3 -> password filed visible
3. installed 7.4(PL03 highest now available) over 7.3 -> password field invisible
4. removed SAPGUI following How uninstall completely SAPGUI 7.20...
5. installed 7.4(PL03) -> password field invisible

On my other computer after applying latest patch password filed is visible on 7.4(03) without NWBC5. I hope someone will find a solution for our issue. Community, any ideas?

Regards, Sven

[Former Member]

Patch Level 6 has been released for NWBC 5.0 on June 3rd

Details are in note 2030419

• PL6: Shipped on June 03th 2015

Corrections for:

• Fixed a problem with NWBC popup windows where a logon screen appears in an external browser window.
• Fixed a problem with portal session locks if the NWBC window is completely closed.
• Fixed a problem with resizing of the right side panel if a SAPGUI transaction is launched within.
• Fixed a problem that caused nwbc to freeze sometimes when switching the active theme.
• Fixed out of memory issue in landscape area.

Improvements:

• Improved integration of SAPUI5 Inbox overlayed popups (requires SAPUI5 version 1.30 and higher).
• Made nwbc run more stable in case of registry access issues.
• Favorites and pinned tabs which refer to nodes in the user menu are now checked for inconsistencies and repaired

[Former Member]

Hi,

when installing SAP GUI 7.40 on my new laptop I experienced the same problem: all system connections maintained in the 7.30-version were gone.

I could fix this by manually deleting the file "SAPUILandscape.xml". When opening SAP GUI 7.40 for the next time, this file was created again - but this time in the right way so that all systems were available 🙂

Hope this helps...

Best regards,

Andreas

[damian_storozenko]

Hi Andreas,

The data migration automatically are not execute correctly.

You execute the next steps depending your configuration file.

#####################################

SAP Note: 2075150

#####################################

http://service.sap.com/sap/support/notes/2075073

The default local configuration file path is the same as in the older SAP GUI releases:

%APPDATA%\SAP\Common

cd C:\Program Files (x86)\SAP\FrontEnd\SAPgui

saplogon.exe /INI_FILE=%APPDATA%\SAP\Common\saplogon.ini  /LSXML_FILE=%APPDATA%\SAP\Common\SAPUILandscape.xml

#####################################

The environment variable SAPLOGON_INI_FILE=[Path]\[name] to specify the user INI.

The new environment variable SAPLOGON_LSXML_FILE=[Path]\[name] to specify the user landscape file that should be created.

SAPLOGON_INI_FILE

C:\WINDOWS\saplogon.ini

SAPLOGON_LSXML_FILE

C:\Windows\SAPUILandscape.xml

cd C:\Program Files (x86)\SAP\FrontEnd\SAPgui

saplogon.exe /INI_FILE=C:\Windows\saplogon.ini  /LSXML_FILE=C:\Windows\SAPUILandscape.xml

Best regards,

Damián

[christoph_ostrop]

to use NWBC 5.0 on WTS (windows terminal server) has an issue,

that sap-connections get lost (after disconnect - and re-connect RDP)

RDP disconnect - connect ,  SAP session is lost, and NWBC hangs

NWBC 5.0 PL-7, RDP-session, open NWBC and SAP-appl., RDP-disconnect, and RDP-connect, NWBC-session i...

and

NWBC 5.0 and (from SAP) used MS-Tools MS.NET + MS.VisualStudio 2012, installation issues

[StevenDeSaeger]

Just installed 7.40 & NWBC ... same issues as mentioned here ... this document saved my day ... thanks for that ( bedankt ! )

Gr,

Steven

[TomVanDoo]

Tsss. This is already a year old. I expected a De Saeger to be faster with adoption of new technology. Version 6 will be out soon.

Glad it could help though

[StevenDeSaeger]

Hahahaha you have caughted me there    Been too busy with SAPUI5 & other client front-end technologies to worry about SAPGUI lately ...

Weird though this still isn't fixed properly then by SAP ?  Just downloaded the latest 7.40 compilation last week ...

Anyways ... 🙂

[younmazz]

Hi Tom

The article about converting SAPLogin.ini helped me lot. I have been struggling in saving old connections after update BC5.0 & GUI 7.4,

Thanks to this blog I was able to scratch and get away my itches ....

Thanks !

Regards,

Jin

[burkhard_berger]

Hi Tom,

I created an installation package including PL6. My problem: If I want to install 740 on a new pc, I have no entries in the saplogon (because there a no saplogon.ini etc. to migrate, of course). What do I have to do to get entries in SAPGUI 7.40?

Best regards

Burkhard

[havder]

Hi Burkhard,

If you’re running the installation off an installation server, my suggestion is to set up the entries based on the first point in this post, or create the entries from scratch, and then copy the SAPUILandscape.xml file to a folder on your installation server (e.g. \\your_sap_inst_serv\CustomerFiles\SAPUILandscape.xml)

In the package you have created, go to “Package Configuration” and “Modify Parameters”. Set the parameter SapGui.LandscapeFileOnServer to \\your_sap_inst_serv\CustomerFiles\SAPUILandscape.xml

That way any new installation of that package would read the entries from the SAPUILandscape.xml file located on your installation server and could easily be maintained centrally.

It’s what I have done and it works great for us, I hope it helps

BR

Sam

[Former Member]

Hello,

After installing SAP 7.4 & BC 5.0 (saplogon.ini is in a server), connections are not available in Analysis 2.2. I copied old saplogon.ini under Windows and Common Folders, but is not working. Please help me..Thanks

[Former Member]

Do I Need to configure manually the Ao_app.config?

[TomVanDoo]

Do you have the latest patches of the Sap Business client installed?

SAP business client as of version 5 no longer uses the saplogon.ini. it will migrate the saplogon.ini on first use to a sapuilandscape.xml file

Everything is described in the document above, or in the ensuing discussion. I would urge you to see if you can find any hints in the information already listed. It's meant as a self-service troubleshooting guide.

As for the Ao_app.config: I don't know what that is, so can't help you on that.

my guess: first migrate the saplogon.ini on the server to the sapuilandscape,

(you can do that by copying it to a test-laptop, install SAP Business Client, start it, configure it to use the local saplogon.ini. And have it automatically migrated.)

Then replace the saplogon.ini on the server, with that sapuilandscape.xml and make sure the config of the business client, when you roll it out, points to that server-based sapuilandscape folder.