17 Replies Latest reply: Jan 15, 2014 7:11 AM by Robin Singh RSS

Error when accessing installed software for technical system in SLD

Jens Schwendemann
Currently Being Moderated

Hi all,

 

we have newly installed SAP PI AEX 7.4 SP4 on AIX / Oracle.

 

If I access SLD --> Technical Systems --> Chose DVF (our SAP PI technical system) --> Installed Software i get an exception "java.lang.NoSuchMethodError: com.sap.sld.api.std.tech.SLD_ApplicationSystem.getAllInstalledSoftwareComponents()Ljava/util/List;"

 

We deployed the latest patches for the components, we think that matter to that process which would be:

AJAX-RUNTIME = SP4 Patch 2 (1000.7.40.4.2.20131112190100)

WD-RUNTIME = SP4 Patch 3 (1000.7.40.4.3.20131124155400)

LM-SLD = SP4 Patch 2 (1000.7.40.4.2.20131114203600)

 

Anyone stumbled upon this?

 

This is the full stack trace:

500 Internal Server Error is returned for HTTP request [http://rs174dvf.hansgrohe.com:50000/webdynpro/resources/sap.com/tc~sld~wd~main/Main]: 
  component [dispatcher], 
  web module [webdynpro/resources/sap.com/tc~sld~wd~main], 
  application [sap.com/tc~sld~wd~main], 
  DC name [], 
  CSN component[], 
  problem categorization [], 
  internal categorization [1708445251]. 
[EXCEPTION]
java.lang.NoSuchMethodError: com.sap.sld.api.std.tech.SLD_ApplicationSystem.getAllInstalledSoftwareComponents()Ljava/util/List;
at com.sap.sld.wd.technicalsystem.InstalledProductComp.supplyInstalledSCVersion(InstalledProductComp.java:327)
at com.sap.sld.wd.technicalsystem.wdp.InternalInstalledProductComp.supplyInstalledSCVersion(InternalInstalledProductComp.java:225)
at com.sap.sld.wd.technicalsystem.wdp.IPublicInstalledProductComp$IInstalledSCVersionNode.doSupplyElements(IPublicInstalledProductComp.java:733)
at com.sap.tc.webdynpro.progmodel.context.DataNode.supplyElements(DataNode.java:110)
at com.sap.tc.webdynpro.progmodel.context.Node.getElementListAsObject(Node.java:263)
at com.sap.tc.webdynpro.progmodel.context.MappedNode.createMappedElementList(MappedNode.java:78)
at com.sap.tc.webdynpro.progmodel.context.MappedNode.supplyElements(MappedNode.java:71)
at com.sap.tc.webdynpro.progmodel.context.Node.getElementListAsObject(Node.java:263)
at com.sap.tc.webdynpro.progmodel.context.Node.getElements(Node.java:270)
at com.sap.tc.webdynpro.progmodel.context.Node.sortElements(Node.java:538)
at com.sap.sld.wd.technicalsystem.InstalledProductCompView.onActionSortSCID(InstalledProductCompView.java:622)
at com.sap.sld.wd.technicalsystem.InstalledProductCompView.onActionProductLeadSelect(InstalledProductCompView.java:750)
at com.sap.sld.wd.technicalsystem.wdp.InternalInstalledProductCompView.onActionProductLeadSelect(InternalInstalledProductCompView.java:566)
at com.sap.sld.wd.technicalsystem.InstalledProductCompView.wdDoModifyView(InstalledProductCompView.java:174)
at com.sap.sld.wd.technicalsystem.wdp.InternalInstalledProductCompView.wdDoModifyView(InternalInstalledProductCompView.java:907)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doModifyView(DelegatingView.java:94)
at com.sap.tc.webdynpro.progmodel.view.View.modifyView(View.java:746)
at com.sap.tc.webdynpro.progmodel.window.ViewController.modifyView(ViewController.java:254)
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:432)
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:438)
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:438)
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:438)
at com.sap.tc.webdynpro.clientserver.phases.ModifyViewPhase.execute(ModifyViewPhase.java:69)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequestPartly(WindowPhaseModel.java:162)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doProcessRequest(WindowPhaseModel.java:110)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:97)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:515)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:58)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doExecute(ClientApplication.java:1671)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doProcessing(ClientApplication.java:1485)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessingStandalone(ApplicationSession.java:908)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessing(ApplicationSession.java:880)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:357)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:326)
at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)
at com.sap.tc.webdynpro.serverimpl.wdc.DispatcherServlet.doContent(DispatcherServlet.java:89)
at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doPost(AbstractDispatcherServlet.java:62)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:152)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:38)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:457)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)
at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:278)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.SessionSizeFilter.process(SessionSizeFilter.java:26)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:475)
at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:269)
at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)

 

Thanks and kind regards

 

Jens

  • Re: Error when accessing installed software for technical system in SLD
    Robin Singh
    Currently Being Moderated


    Hi Jens,

     

    Did you find a solution to your problem?

     

    Actually we also updated our  PI AEX 7.31 from SP06 to SP10 and right after the update we are getting the same error when trying to access installed software in SLD under technical systems.

     

    java.lang.NoSuchMethodError: com.sap.sld.api.std.tech.SLD_ApplicationSystem.getAllInstalledSoftwareComponents()Ljava/util/List;

     

     

    I have also performed all the post update steps mentioned in the Support package stack guide SAP netweaver 7.3 SPS09 but still the same error.

     

    Can anyone help??

     

     

    Regards

    Robin Singh

    • Re: Error when accessing installed software for technical system in SLD
      Jens Schwendemann
      Currently Being Moderated

      Hi Robin,

       

      we opened a call for that, which is still pending, unfortunatelly. I would encourage you to do the same which might help to increase pressure on this issue.

       

      I will keep you posted with a resolution as soon as SAP reports back.

       

      Kind regards
      Jens

    • Re: Error when accessing installed software for technical system in SLD
      Sven H.
      Currently Being Moderated

      Hello Jens,

      hello Robin,

       

      same SLD error on our PI AEX 7.31 system which we patched to SPS 9.

      Did someone got a reply from SAP yet?

       

      Kind regards

      Sven

      • Re: Error when accessing installed software for technical system in SLD
        Robin Singh
        Currently Being Moderated

        Hi Sven,

         

        Sorry still no useful reply.

        All they are asking for is more data for diagnosis.

         

        I think they have encountered a major issue with this Support stack level, which probably would take same more time to resolve.

         

        Regards,

        Robin Singh

      • Re: Error when accessing installed software for technical system in SLD
        Jens Schwendemann
        Currently Being Moderated

        Same here,

         

        had the call priority increase to high and had an additional call for further priorisation. No answer so far. Seems just like they're kicking the can down the road until 7.40 SP5 / 7.31 SP10 arrives.

         

        The bug prevented us from assigning products to technical systems. We worked around the original issue by leveraging the following trick. This is what we did, though I'm not sure it is advisable to go down that road because you will be working under the hood of the failing SLD.

         

        *****************************************************************************************************

        * Please read the whole list as the figures 1-7 may be obsolete, based on our experience

        * However, we did not try this procedure without the steps 1-7 so YMMV

        *****************************************************************************************************

         

        1. Export the respective products from the failing SLD

        2. Identify some working SLD in your environment. For us it was the Solution Managers's SLD.
        3. Import the products in the working SLD

        4. Assign the products to the technical system in the working SLD (for us it was a SAP system, so it was already in the working SLD due to RZ70 / forwarding, if your technical system isn't there yet, you first might want to import that, too)

        5. Export the technical system from the working SLD

        6. Import the technical system in the failing SLD

        7. We thought that this would suffice, unfortunatelly the products seemed not available when trying to assign them to the business system. So we did the assignment manually.

        ------

        So it may suffice if you just do this instead of exporting and importing any products / systems.

        8. Go CIM Instances

        9. Open Class with Instances "Application Server ABAP" (or the kind of instance you want to assign products to)

        10. Select the technical system you want assign the products to

        11. Create a new association

        12. Select "Installed Product On Application System"

        13. Select your product

        14. Click on "Associate"

        15. Switch back to business systems from the SLD home page

        16. Reckon that your associated product shows up in the list of installed products

        17. To be on the safe side, I deselected the product, saved this and reselected it and saved again.

         

        HTH

        Cheers

         

        Jens

      • Re: Error when accessing installed software for technical system in SLD
        Sven H.
        Currently Being Moderated

        Hello,

         

        SAP answered our call with not really much of a help.

         

        Suggestion is to implement SP stack 11 for NW 7.31 as mentioned in SAP note 1935121 version 3 from 21-Nov-2013. Unfortunately SP stack 10 just got available two weeks ago, so it will take a while until SP stack 11.

         

        I updated the SAP call and will keep you posted with the answers.

         

        Are there any other known missing functionalities besides "The bug prevented us from assigning products to technical systems" which was mentioned by Jens?

         

        Regards

        Sven

         

        Message was edited by: Sven H.

  • Re: Error when accessing installed software for technical system in SLD
    Abhinav verma
    Currently Being Moderated


    Hi Jens,

     

    I have faced the similar issue in my last project.

     

    While opening the SLD,ID and IR ,i was getting the same errror.

     

    Can you do one thing,please ask your basis team to check the user id of the SLD and then try.We have already raised OSS notes for this.You can check that note.You can give reference that similar problem also occured in past.

     

    Main reason:-It is because of the system user id of the SLD.Your basis team can check whether it is locked or  not.

    After doing this restart your system and again login.It will work.

     

    Regards,

    Abhi

  • Re: Error when accessing installed software for technical system in SLD
    Robin Singh
    Currently Being Moderated

    Hi all,

     

    Good news.

    The issue is finally resolved.

     

    SAP has released a patch for the software component SAP 7.31 SP09 LM-CORE.

    We installed the latest patch i.e "Patch 04" which was released on 13th Dec in our system.

    We are now able to access installed software under technical systems.

     

    Jens : check for the latest patch of the above mentioned SC for your release.

     

    Sven : You can use the this patch for your release.

     

    As expected SAP was planning to resolve the issue in the next patch, which accounted for the delay.

     

    Regards,

    Robin Singh

  • Re: Error when accessing installed software for technical system in SLD
    Robin Singh
    Currently Being Moderated

    Hi Jens,

     

    Has your issue been resolved ?

    Did SAP release the latest patch for LM-CORE 7.40 SP04?

     

     

    Regards,

    Robin

  • Re: Error when accessing installed software for technical system in SLD
    Jens Schwendemann
    Currently Being Moderated

    Hi all,

     

    I would like to inform you that our issue was resolved by deploying the latest patches for 7.40 SP4, particularly LM-CORE 7.4 SP4 Patchlevel 3. Please be aware that there's now a SCA dependency available at service.sap.com/swdc, so we also deployed all other dependent SCAs.

     

    As of the time writing this, those are the dependent SCAs

    Software Component VersionSupport PackageMin. Patch Level
    ENGINEAPI 7.40SP0043
    J2EE ENGINE APPLICATIONS 7.40SP0046
    J2EE ENGINE CORE TOOLS 7.40SP0045
    J2EE ENGINE FACADE 7.40SP0041
    J2EE ENGINE FRAMEWORK 7.40SP0046
    J2EE ENGINE SERVERCORE 7.40SP0047
    LM SLD 7.40SP0042

     

    HTH

     

    Cheers

     

    Jens

Actions