Skip to Content

Hello,

Hope all of you are doing well !!

Recently I have upgraded Netweaver from 7.0 EHP2 to Netweaver 7.3 EHP1 SP6 in Enterprise Portal due to one of the advanced requirement of ESS, MSS functionality. During this upgrade project , I have encountered various issues, which I thought to explain the troubleshooting process in SCN so that it could help to save time of my SCN friends.

1. During BIND_PATCH phase of EXTRACTION stage it was giving dump (in logs, nothing major was showing ), which we have raised to SAP and we found that following components need to be uninstalled to process further (from starting i.e. by deleting SUM directory and by creating new XML after removing below mentioned components):-

  1. sap.com

BP_ERP5***

  1. 1.0 SP18 (1000.1.0.18.0.20100828050255)

MAIN_ERP05VAL_C

  1. sap.com

BP_ERP5COM

  1. 1.51 SP5 (1000.1.51.5.1.20110819102941)

MAIN_ERP55VAL_C

  1. sap.com

BP_ERP5ESS

  1. 1.41 SP9 (1000.1.41.9.0.20110314090127)

MAIN_ERP54VAL_C

  1. sap.com

BP_ERP5HRA

  1. 1.41 SP3 (1000.1.41.3.0.20090430053938)

MAIN_ERP54VAL_C

  1. sap.com

BP_PPM_DC

  1. 450.700 SP13 (1000.450.700.13.0.20120412084047)

MAIN_PPM45VAL_C

  1. sap.com

BPERPEIC

  1. 1.40 SP7 (1000.1.40.7.0.20100714082435)

MAIN_ERP54VAL_C

  1. sap.com

BPERPERCAD

  1. 1.40 SP8 (1000.1.40.8.0.20100916042531)

MAIN_ERP54VAL_C

  1. sap.com

BPERPERCRE

  1. 1.40 SP8 (1000.1.40.8.0.20100916042545)

MAIN_ERP54VAL_C

  1. sap.com

BPMSSADDON

  1. 1.0 SP0 (1000.1.0.0.1.20110708141210)

MAIN_ADDON1VA_C

  1. sap.com

ISFSICMAPP

603 SP7 (1000.603.0.7.0.20100914080507)

MAIN_ERP53VAL_C

  1. sap.com

SAP_ESS

603 SP8 (1000.603.0.8.0.20110225121802)

MAIN_ERP53VAL_C

  1. sap.com

SAP_MSS

600 SP19 (1000.600.0.19.0.20110207050012)

MAIN_ERP05VAL_C

  1. sap.com

SAPPCUI_GP

603 SP8 (1000.603.0.8.0.20110225121839)

MAIN_ERP53VAL_C

So, remove these components through SDM and continue by creating new XML (MOPZ).

Note that , before creation of MOPZ (after removal of these components) , you need to fetch SLD Data Supplier job from EP (Visual Admin) to Solution manager (Central SLD) and then run LANDSCAPE_FETCH job in Solution Manager. Also please check the time stamp of latest changes in Technical Components , database, System information etc. in SMSY to double confirm whether latest changes of EP server is replicated to SMSY or not as it may lead to wrong stack calculation in MOPZ.

2. Again to overcome wrong instance detected issue in “CHECK_INSTANCES_DETECTED” phase, please follow 871523 note and delete the obsolete node in config tool of EP server.

3. To avoid error during ‘DEPLOY_ONLINE_SHD_DM’ phase, please perfom following steps:-

  1. Remove SAP.COM/CAF through SDM . (Please make sure whether the same component is also applicable for your scenario)
  2. Remove duplicate profiles/old profiles both from profile directory and also from upgrade directory.
  3. Stop antivirus service from Virus Scan Console and also  from services.msc .
  4. Maintain the administrator password in config-tool secure storage.

4.  To avoid error during ‘REMOVE_OBSOLETE_JARFILES’, rename/delete the jar files available under ‘usr\sap\<SID>\SUM\java\<SID>\SYS\global\security\lib\tools’ path before this phase itself in EXECUTION stage.

5.   For configuring ADS with SSL, in addition with general configuration steps, also follow the below mentioned steps :-

  1. Import global signed certificates in EP.
  2. Import Wildcard certificate in R3 system under STRUST > SSL client SOAP client certificate and click on Add To Certificate List.
  3. Also please check whether ADSUSER and ADS_AGENT users are having sufficient rights or not. Add ADSCallers role & group to these users both in portal.
  4. Then execute https://<FQDN of host name>:<port>/wsnavigator and login with Administrator ID. (As we have used SSL)
  5. Select Logical Destination  as ConfigPort_Document and search for AdobeDocumentServicesVi and click on NEXT till it shows successfully executed ๐Ÿ™‚ .

6.  Also take care of following parameters :-

  Login to NWA > Configuration > Infrastructure Management > Application Modules > and maintain the protocol parameter as HTTP .


7. Apart from these , if you would face issue while starting the SCS instance of shadow instance in any of the phase in PRE-PROCESSING stage, then maintain following parameter in SCS instance under upgrade directory :-

                                   “service/protectedwebmethods = NONE” and restart the instance to restart the upgrade again.

Humble request you all to suggest in case any additional point can be put in this document to inherit more guidance .

Regards,

Nilutpal.

To report this post you need to login first.

1 Comment

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

Leave a Reply