cancel
Showing results for 
Search instead for 
Did you mean: 

NWBC 5.0 application crashing

jinson_venattu3
Explorer
0 Kudos

The TM users in my company are getting unexpected NWBC crash issues. The NWBC application they use suddenly stops responding and they lose the work they were doing. This has been happening for over six months now and we have upgraded the desktop application from NWBC 3.5 PL14 to NWBC 4.0 and now to the latest NWBC 5.0 PL 10. The crashes are not as frequent with NWBC 5.0 as they were for 3.5, but users with 5.0 still get them.

Here's the screenshot of what users see after the system stops responding. This could happen in any screen of TM like the Transportation Cockpit, edit freight order, tendering etc. We have found no way to consistantly replicate this at will, but the users get this sometimes 2-3 times a day.

We have sent this to SAP multiple times along with all kinds of logs and trace files that they have asked for from the affected desktops and the final response we always got was to upgrade to a new patch level or version of NWBC. Following their recommendations, we have applied several ABAP runtime patches, server level patches and notes, UI rendering patches, SAP GUI patch level upgrades, NWBC patch level upgrades and finally to NWBC 5.0 version upgrade to PL10. Eevn after going through all this, we still have users who get this error.  

The desktops that the transportation users use are high performance machines with the best possible CPU and memory powers. We have also done all the  recommended IE security settings.

Here's where we are now;

SystemCurrent Version
SAP TMTM 9.0 SP11
SAPGUI740 PL5 Hotfix 1
NWBC5.0 PL10
Internet ExplorerIE 11
OSWindows 7 Enterprise

It seems to be an issue related to the NWBC window desktop application, but we are not able to find the root cause. Request your help.


thanks,

Jinson.

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member182454
Participant
0 Kudos
jinson_venattu3
Explorer
0 Kudos

Thanks Indraneel. We have followed this document when we upgraded to 5.0 and still we have the same issues.