cancel
Showing results for 
Search instead for 
Did you mean: 

Netweaver 7.4 AS Java Toolbar and Drop-Down not responding (Solution Manager SPS 08)

pat_ste_rr
Explorer
0 Kudos
748

Hello Experts

After Upgrading the Solution Manager (installation from scratch) in my Company we ran into a few problems. As described in the titel when accessing the AS Java instance (f.e. /nwa) and trying to use the toolbar or other elements on the web dynpro. The Maintenance Certificate was installed succesfully via telnet (es described per note) but researching the problem we are currently facing feels a bit harder.

The Note 2527906 fits the situation exactly with the only problem being, that for upgrade the used components are on the newest patchlevel (as per maintenance planner). I can upload a full list of the used components from the Maintenance plan (if nessesary).

Our current next plan would be to research weather we need to patch the NW or install any kind of AS Java extension.

While trying to solve the problem my collegue and I changed a few parameters as described in other notes with the result that we gained nothing (but loosing time in the process)

Summary:

After installation of Solution Manager Java Stack, we were unable to access Web Dynpro Elements, Post Upgrade we are still unable to do so. Components as described in Note 2527906 are up to date.

Edit 1: Here is the list of Components

1. ADSSAP ; 7.40 17.0

2. AJAX-RUNTIME ; 7.40 17.0

3. BASETABLES ; 7.40 17.0

4. BC-FES-IGS LINUX_X86_64 ; 7.53 8.0

5. BI-WDALV ; 7.40 11.0 ; 7.40 17.0

6. CFG_ZA ; 7.40 17.0

7. CFG_ZA_CE ; 7.40 17.0

8. CORE-TOOLS ; 7.40 17.0

9. DI_CLIENTS ; 7.40 17.0

10. ENGFACADE ; 7.40 17.0

11. ENGINEAPI ; 7.40 17.0

12. EP-BASIS-API ; 7.40 17.0

13. ESI-UI ; 7.40 11.0 ; 7.40 17.0

14. ESP_FRAMEWORK ; 7.40 17.0

15. ESREG-BASIC ; 7.40 17.0

16. ESREG-SERVICES ; 7.40 17.0

17. FRAMEWORK ; 7.40 17.0

18. FRAMEWORK-EXT ; 7.40 17.0

19. ISAGENT ; 8 25.0

20. ISAGENT_MIN_J5 ; 9.5 06.1

21. J2EE-APPS ; 7.40 17.0

22. J2EE-FRMW ; 7.40 17.0

23. JSPM ; 7.40 17.0

24. LMCFG ; 7.40 17.0

25. LM-CORE ; 7.40 17.0

26. LMCTC ; 7.40 17.0

27. LM-CTS ; 7.40 17.0

28. LM-CTS-UI ; 7.40 11.0 ; 7.40 17.0

29. LM-MODEL-BASE ; 7.40 17.0

30. LM-MODEL-NW ; 7.40 17.0

31. LMNWABASICAPPS ; 7.40 17.0

32. LMNWABASICCOMP ; 7.40 17.0

33. LMNWABASICMBEAN ; 7.40 17.0

34. LMNWACDP ; 7.40 17.0

35. LMNWATOOLS ; 7.40 17.0

36. LMNWAUIFRMRK ; 7.40 11.0 ; 7.40 17.0

37. LM-SERVICE ; 7.20 8.0

38. LM-SLD ; 7.40 11.0 ; 7.40 17.0

39. MESSAGING ; 7.40 17.0

40. ODATA-CXF-EXT ; 7.40 17.0

41. SAP_BUILDT ; 7.40 11.0 ; 7.40 17.0

42. SAPHOSTAGENT LINUX_X86_64 ; 7.21 41.0

43. SAPJVM LINUX_X86_64 ; 6.01 114.0

44. SAP KERNEL UNICODE LINUX_X86_64 ; 7.53 300.0

45. SAP-XI3RDPARTY ; 7.40 11.0

46. SECURITY-EXT ; 7.40 11.0 ; 7.40 17.0

47. SERVERCORE ; 7.40 17.0

48. SOAMONBASIC ; 7.40 17.0

49. SR-UI ; 7.40 17.0

50. SUPPORTTOOLS ; 7.40 17.0

51. UDDI ; 7.40 17.0

52. UISAPUI5_JAVA ; 7.40 11.0 ; 7.50 13.0

53. UMEADMIN ; 7.40 17.0 54. WD-ADOBE ; 7.40 17.0

55. WD-APPS ; 7.40 17.0

56. WD-RUNTIME ; 7.40 17.0

57. WD-RUNTIME-EXT ; 7.40 17.0

58. WSRM ; 7.40 17.0

Here only the ones that where upgraded:

5. BI-WDALV ; 7.40 11.0 ; 7.40 17.0

13. ESI-UI ; 7.40 11.0 ; 7.40 17.0

28. LM-CTS-UI ; 7.40 11.0 ; 7.40 17.0

36. LMNWAUIFRMRK ; 7.40 11.0 ; 7.40 17.0

38. LM-SLD ; 7.40 11.0 ; 7.40 17.0

46. SECURITY-EXT ; 7.40 11.0 ; 7.40 17.0

52. UISAPUI5_JAVA ; 7.40 11.0 ; 7.50 13.0

Accepted Solutions (1)

Accepted Solutions (1)

Viktor
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hello Patrick,

The KBA 2527906 is a good approach. You should apply the solution described in it, as usually these UI related issues are caused by coding errors in the component AJAX-RUNTIME/WD-RUNTIME.

According to the component list, that you pasted under your question, you have the 0 patch levels everywhere. However e.g. the latest AJAX RUNTIME 7.40 SP17 patch level is patch 20 at the moment.

So you should update the system to the highest patch levels, so that you will have all the available fixes.

Please also consider the needed dependencies.

Best Regards,

Viktor

pat_ste_rr
Explorer
0 Kudos

Installing the current patches fixed the problem.

Since we didn't explicitly patched the ABAP System by now or checked for additional patches for the used components (that would be installed while running the SUM)

Since we are aware of this we will check proactive when we install the next system wheather there are nessesary patches that we should install while Upgrading with SUM.

While researching the patches we didn't found any kind of comprehensive note with all nessesary patched components. If someone is aware how to find such kind of note I would be greatful.

Regards

Patrick

Answers (2)

Answers (2)

kaus19d
Active Contributor
0 Kudos

Hi,

This issue would be fixed when you do next level upgrade

Thanks,

Kaushik

Johan_sapbasis
Active Contributor
0 Kudos

Hi,

When you created your maintenance planner transaction did you choose the steps for the java stack listed here. This could be why you are on SPS0, not saying it is so but I had a similar issue when patching portal.

2022451 Add Java Patches - Things to consider.

Only core components were patched rest were on level o.

Kind Regards,

Johan