16 Replies Latest reply: Jan 5, 2012 10:05 AM by abhijeet mukkawar RSS

Process Component "Activation not possible"

Chinnu Y
Currently Being Moderated

Hi Folks,

 

I am trying to go with my first BPM example, "My Name Age". When the process component and WD component got deployed, I almost thought its going to work. Its only when I tried to activate the latest version of the process component, I realized its not done yet.

 

I get this message every time I try to activate the component "Activation not possible".

 

Experts, please help me get through with this...

 

Thanks and regards,

Nrisimhanadh Yandamuri

  • Re: Process Component "Activation not possible"
    abhijeet mukkawar
    Currently Being Moderated

    Can you see this version of process deployed? If so and it is not activated, it looks to be an issue with version..

    Check : http://forums.sdn.sap.com/thread.jspa?threadID=2023362

     

    -Abhijeet

  • Re: Process Component "Activation not possible"
    Satish Jhariya
    Currently Being Moderated

    Hi,

     

     

    Which user you are using for activation ?

     

    Can you try with the user having following roles:

    SAP_BPM_SUPERADMIN, SAP_BPM_SUPERDISPLAY

     

    Best Regards

    Satish Kumar

    • Re: Process Component "Activation not possible"
      Chinnu Y
      Currently Being Moderated

      Thanks Abhijeet,

       

      That might be the problem, NWDS is at one SP level higher than that of the server.

      I requested our basis to download the right version so that I can give it another try.

       

       

      Hi Satish jhariya,

       

      I tried assigning the roles to the user. Buttons are enabled, and I can activate/deactivate the standard processes, but not those I deployed.

       

      Wish me all the best with the matching NWDS version while I get some more help.

       

      Thanks and regards,

      Nrisimhanadh Yandamuri

      • Re: Process Component "Activation not possible"
        abhijeet mukkawar
        Currently Being Moderated

        Yes Chinnu, that should preciesely be the reason. What happens is you deploy content with newer version but Server doesnt understand it.

         

        -Abhijeet

         

        Edited by: Abhijeet on Jan 3, 2012 5:43 AM

        • Re: Process Component "Activation not possible"
          Chinnu Y
          Currently Being Moderated

          Thanks Abhijeet,

           

          That is what is confusing. Process component gets deployed successfully without any errors.

          Also, I did not find any errors when I try to activate a process component version. What I get is just a warning "Activation not possible" on top of the screen. Checked the logs and traces too, no luck. I could not find a error there too.

           

          Now, I have this problem, how do we download NWDS with a lower SP level? or should we upgrade the SP level of the server?

           

          Any clues?

           

          Best regards,

          Nrisimhanadh Yandamuri

          • Re: Process Component "Activation not possible"
            abhijeet mukkawar
            Currently Being Moderated

            It wont activate just because its not compatible.

             

            About bringing them to same level, its better to upgrade server than downgrade NWDS :

            1) Upgrade is always - rather mostly - backward compatible, but I doubt the same for downgrade. So, better upgrade.

            2) Also it wont be good to downgrade NWDS as you need to do it on all client machines.

             

            -Abhijeet

          • Re: Process Component "Activation not possible"
            abhijeet mukkawar
            Currently Being Moderated

            But, yes, you should also consider impact of upgrading server if ther are some applications deployed earlier. If there are other running applications, and you are not very sure of effect of upgrade on them, you better deal with local NWDS stuff. Coz that wont affect existing applications. Also correcting NWDS wont be very hectic for smaller team size.

             

            -Abhijeet

            • Re: Process Component "Activation not possible"
              Chinnu Y
              Currently Being Moderated

              Thanks Abhijeet,

               

              One thing bothering me us the sp level of BPEM-CORE component which is at higher SP level (SP4) while the rest of the components are at SP0, what confuses me is what should be the SP level of NWDS should be. SP4? or SP0?

              • Re: Process Component "Activation not possible"
                abhijeet mukkawar
                Currently Being Moderated

                Not quite sure how SP of other components will affect development process.For BPM, guess, designtime should be in line with runtime.

                 

                -Abhijeet

                • Re: Process Component "Activation not possible"
                  Chinnu Y
                  Currently Being Moderated

                  I found this error in error log after deploying?

                  Deployment status in NWDS shows that the components are deployed, but, if I looking to logs immediately, I get this error.

                   

                   

                  Services Registry Log Error

                  ----


                  |  05-Jan-12  10:45:50.904

                  |  Method   : findServiceDefinitions()

                  |  Class    : com.sap.esi.uddi.sr.local.LocalServicesRegistry

                  |  ThreadID : 166

                  ----


                  |  Message  : com.sap.esi.uddi.sr.local.exceptions.ValidationException: No classification system with key QName: Namespace= http://uddi.sap.com/classification; Name=  CompositeName found in the registry.

                  ----


                  |

                  |       com.sap.esi.uddi.sr.local.validators.ClassificationValueValidator.validate(ClassificationValueValidator.java:156)

                  |       com.sap.esi.uddi.sr.local.validators.ServiceDefinitionValidator.validateSearchAttributes(ServiceDefinitionValidator.java:255)

                  |       com.sap.esi.uddi.sr.local.LocalServicesRegistry.findServiceDefinitions(LocalServicesRegistry.java:332)

                  |       com.sap.esi.esp.service.server.sr.local.SOALocalSRPublisherImpl.findInterfaceDefinitionsByName(SOALocalSRPublisherImpl.java:1358)

                  |       com.sap.esi.esp.service.server.sca.actions.SCAServicesAction.getServiceDefinitionList(SCAServicesAction.java:252)

                  |       com.sap.esi.esp.service.server.sca.actions.SCAServicesAction.<init>(SCAServicesAction.java:64)

                  |       com.sap.esi.esp.service.server.sca.SmartConfigPlugin.updateEventActionWithRollbackSupport(SmartConfigPlugin.java:192)

                  |       com.sap.esi.esp.service.server.sca.SmartConfigPlugin.executeEvent(SmartConfigPlugin.java:309)

                  |       com.sap.esi.esp.service.server.sca.SmartConfigPlugin.executeEvent(SmartConfigPlugin.java:281)

                  |       com.sap.engine.services.sca.deploy.ApplicationUpdate.perform(ApplicationUpdate.java:195)

                  |       com.sap.engine.services.sca.deploy.SCACompositeContainer.invoke(SCACompositeContainer.java:297)

                  |       $Proxy33.makeUpdate(Unknown Source)

                  |       com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.makeUpdate(ContainerWrapper.java:408)

                  |       com.sap.engine.services.deploy.server.application.UpdateTransaction.makeComponents(UpdateTransaction.java:545)

                  |       com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:282)

                  |       com.sap.engine.services.deploy.server.application.UpdateTransaction.begin(UpdateTransaction.java:256)

                  |       com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:426)

                  |       com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:478)

                  |       com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:2016)

                  |       com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:623)

                  |       com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:520)

                  |       com.sap.engine.services.dc.gd.impl.ApplicationDeployer.update(ApplicationDeployer.java:74)

                  |       com.sap.engine.services.dc.gd.impl.InitialApplicationDeployer.performDeployment(InitialApplicationDeployer.java:141)

                  |       com.sap.engine.services.dc.gd.impl.InitialGenericDeliveryImpl.deploy(InitialGenericDeliveryImpl.java:57)

                  |       com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:213)

                  |       com.sap.engine.services.dc.cm.deploy.impl.BulkOnlineDeployProcessor.deploy(BulkOnlineDeployProcessor.java:67)

                  |       com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor$DeployProcessorHelper.visit(AbstractDeployProcessor.java:282)

                  |       com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:84)

                  |       com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor.deploy(AbstractDeployProcessor.java:100)

                  |       com.sap.engine.services.dc.cm.deploy.impl.DeployThread.run(DeployThread.java:39)

                  |       com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)

                  |       com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)

                  |       com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)

                  |

                  ----


                   

                  Thanks and regards,

                  Nrisimhanadh Yandamuri

                   

                  Edited by: Chinnu on Jan 5, 2012 6:20 AM

Actions