Skip to Content
We are currently upgrading Netweaver Portal from SP 12 to SP 17. Let me share information about problems faced and fixes applied… We have a content rich portal with wide range of applications.

  • PDK iViews
  • Webdynpro’s
  • BSP’s
  • to list few.
    We just completed upgrading our development landscape from SP 12 to SP 17. Everything looked smooth, all the custom application developed were working fine. We were extremely happy. But upgrades aren’t meant to be smooth… I hope SDN community members will agree with me !!!

    Issue 1:

    While using the Portal Content Studio to change iView properties, it was noticed that certain nodes in the Content Administration tree will not load.

    Fix 1:

    This problem was fixed by changing the configuration of service From the service configuration option, edit this service and set the value of properties

  • Upgrade desktop objects at startup
  • Upgrade imported desktop objects
  • to true and restart the service.

    Issue 2:

    Further when you right click the context menu for creating iViews, Pages, Roles… doesnt appear, instead you will get to see standard browser context menu appears.

    Fix 2:

    It was found that if folders contain objects with broken delta links/dependecies this problem surfaces in SP17. The only solution available as of now is to find the object which has these dependencies and delete those.
    As we proceed with our upgrade, will try to post more information about issues and resolutions.

    To report this post you need to login first.


    You must be Logged on to comment or reply to a post.

    1. Former Member
      Hi Pras,

      Nice short Blog!!

      Are you aware of any upgrade related issues effecting XI related applications as we are soon going to be upgrading from SP14 to SP17.




    Leave a Reply