Since the last patch implementation in our (clinical) system with severeal dialog instances and an integrated Web Dispatcher, we have been experiencing an issue when using NWBC.
When launching a tile, the following error may occur:
partner ‘hostname:port’ not reached
WASECONNREFUSED: Connection refused
Would you like a detailed error description?
It is noticeable that the hostname:port combination shown in the error message is incorrect — it’s a mix of two correct values:
The hostname always refers to the server where the user was previously logged in.
The port value, however, correctly refers to the current server where the user is logged in.
We were able to narrow the issue down to what seems to be a faulty cache.
After running the report /UI2/INVALIDATE_GLOBAL_CACHES, which among other things clears the table NWBC_NAV_TREE, the issue disappears — but only temporarily. The first login to the initial dialog instance works fine. However, after logging into a different dialog instance, the error reappears.
We have had an open ticket with SAP for over two weeks now, but unfortunately, support has not yet understood the problem. We repeatedly receive suggestions pointing to a supposed network configuration or connection issue. The problem has been described in detail in writing and with screenshots; earlier today I even explained it in a Teams call. After one hour, the support engineer asked for the output of
niping -v -h hostname — without specifying from which host to which this should be executed. Two escalations have not improved the situation.
Since the beginning of this week, we are working with a temporary workaround:
A custom enhancement deletes the user-specific entries in table NWBC_NAV_TREE whenever a tile is clicked.
The following patches were implemented:
IS-H 618: SP 43
HR 608: SP 145 → 148
EA-HR 608: SP 145 → 148
SAP_GWFND 750 SP33
SAP_BASIS 750 SP33
SAP_ABA 750 SP33
SAP_BW 750 SP33
SAP_UI 754 SP17
Has anyone experienced a similar or identical issue?
Thanks
Matthias
Bluesky
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.