SAP Basis Tech Supports

Symptom

This note lists all kind of related topics and notes that help to analyze problems with SAPGUI screens running inplace in the Netweaver Business Client (NWBC).
Other terms

1058567 NWBC: Konfiguration des SAPGUI-Routerstring

Solution
1. ABAP patch(es)

Note 1098315 : Business Client runtime sends SAPGUI service 0
This solves many (not all!) of the following kind of error message:
“partner xyz not reached. WSAEADDRNOTAVAIL: Can’t assign request adress.”

2. Configuration issues

* This setting will make the analysis easier as SAPGUI normally is invisible during startup. This property makes it visible as early as possible. You can add it to My Documents\NWBCClient.ini:
[SETTINGS]
WINGUI_ALWAYS_VISIBLE=1
* Error message “Could not start SAPGUI; reinstall SAPGUI for Windows” comes up when SAPGUI link is clicked. Please make sure that the following OCX is installed in your sapgui directory:
sapfewse.cox
If not, please install the SAP GUI Scripting installation component:
[x] SAP GUI for Windows
[x] SAP GUI Suite
[x] SAP GUI Scripting
Note 1136338 : “NWBC: Profile parameter sapgui/user_scripting_disable_recording must be FALSE”
This note explains a SAPGUI specific setting that enables (s. NWBC docu) SAPGUI’s scripting component, which is used from NWBC. With a wrong setting the SAPGUI screen remains invisible. If the configuration WINGUI_ALWAYS_VISIBLE is set to 1, transaction S000 becomes visible after the start of any SAPGUI link.
Note 1058567: “NWBC: HowTo for “partner xyz not reached” problems”
Note 1155862: How to fix this “hostname ‘xyz’ unknown…” error.
Note 1310185: “NWBC: SAP Router configuration for SAPGUI”
Note 1141728: “NWBC: SSO configuration for SAPGUI screens”
In order to start SAPGUI inplace in NWBC we need SSO2 cookies. This note refers to other important notes listing all details about the backend configuration of SSO2.
NWBC shows Switch to / Retry popups:
If a SAPGUI screen shows the following size checking warning dialog this will lead to the following dialog in NWBC:
“Server Busy.
This action cannot be completed because the other program is busy. Choose [Switch To] to activate the busy program…”
Please read note 570861 in order to switch off the screen size checking feature of SAPGUI.

3. Workarounds

3.1 GOS Container not visible
With NWBC’s default setting the GOS container, a toolbar control shown left of the current screen’s title in normal SAPGUI, is not shown.
In order to make the GOS container visible, add the current property to your My Documents\NWBCClient.ini:
[SETTINGS]
WINGUI_TITLEBAR=1
You need at least PL 10 of NWBC 1.