SAP Knowledge Base Article - Preview

2749750 - After SP update XI applications are not starting and deployment fails in NWDS and objects are not editable in ESR

Symptom

There are multiple symptoms noticed in your system after an SP update:

  • Some XI applications are not starting, such as the Process Integration Tools http(s)://<host>:<port>/dir page is not available or PI Monitoring Tools http(s)://<host>:<port>/pimon. When you check the default traces you can find the following entries which show why the application sap.com/com.sap.xi.directory cannot be started.

#2.0�#2019 02 01 09:52:46:175#+0300#Error#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.002038#BC-JAS-JMS#jmsconnector#C000AC120188009B0000003B00A801FE#28947650000000003##com.sap.engine.services.deploy.server.TransactionManager#Guest#0##361E8848256111E9B458000001B9B4C2#361e8848256111e9b458000001b9b4c2#FB1887FA25ED11E9CF790000001927A6#0#Thread[HTTP Worker [@1667666659],5,Dedicated_Application_Thread]#Plain##
Global [startApp] operation of application [sap.com/com.sap.xi.ib.resources] failed with errors on server process [XXX].#

#2.0�#2019 02 01 09:52:46:175#+0300#Error#com.sap.engine.services.deploy.server.TransactionManager#
com.sap.ASJ.dpl_ds.0020380#BC-JAS-JMS#jmsconnector#C000AC120188009B0000003C00A801FE#28947650000000003##com.sap.engine.services.deploy.server.TransactionManager#Guest#0##361E8848256111E9B458000001B9B4C2#361e8848256111e9b458000001b9b4c2#FB1887FA25ED11E9CF790000001927A6#0#Thread[HTTP Worker [@1667666659],5,Dedicated_Application_Thread]#Plain##
Global [startApp] operation of application [sap.com/com.sap.xi.ib.resources] finished with errors for [40] ms on server process [XXX] [
>>> Errors <<<
1). com.sap.engine.services.jmsconnector.exceptions.BaseDeploymentException: JMS error.
at com.sap.engine.services.jmsconnector.container.JmsContainerImpl.loadDestination(JmsContainerImpl.java:1304)
at com.sap.engine.services.jmsconnector.container.JmsContainerImpl.prepareStart(JmsContainerImpl.java:668)
at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.prepareStart(ContainerWrapper.java:509)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:403)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:332)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:560)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocal(ParallelAdapter.java:335)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:2565)
at com.sap.engine.services.deploy.server.LifecycleController.startReferencedApplication(LifecycleController.java:679)
at com.sap.engine.services.deploy.server.LifecycleController.startReferencedComponent(LifecycleController.java:213)
at com.sap.engine.services.deploy.server.LifecycleController.startReferencedComponents(LifecycleController.java:179)
at com.sap.engine.services.deploy.server.application.StartTransaction.beginCommon(StartTransaction.java:208)
at com.sap.engine.services.deploy.server.application.StartTransaction.begin(StartTransaction.java:173)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:423)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhases(ParallelAdapter.java:486)
at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhases(StartTransaction.java:700)
at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:2001)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:2661)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationOnInstanceWait(DeployServiceImpl.java:2913)
at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.lazyStartApplicationAndWait(DeployCommunicatorImpl.java:712)
at com.sap.engine.services.servlets_jsp.server.deploy.impl.ApplicationManager.start(ApplicationManager.java:174)
at com.sap.engine.services.servlets_jsp.server.deploy.impl.ApplicationManager.analyseAppStatusMode(ApplicationManager.java:287)
at com.sap.engine.services.servlets_jsp.server.DeployContext.startLazyApplication(DeployContext.java:408)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.getContext(HttpHandlerImpl.java:1189)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleError(HttpHandlerImpl.java:90)
at com.sap.engine.services.httpserver.server.ResponseImpl.sendError(ResponseImpl.java:290)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.sendApplicationStoppedResponse(ApplicationSelector.java:366)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:223)
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:468)
at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:262)
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)
Caused by: javax.jms.JMSSecurityException: User: Guest has not permission: vpName: default, type: administration, action: create_topic, destination: jms/topic/xi/AIILogging
at com.sap.jms.server.sc.UMESecurityProvider.checkPermission(UMESecurityProvider.java:223)
at com.sap.jms.server.sc.UMESecurityProvider.checkCreateTopicPermission(UMESecurityProvider.java:169)
at com.sap.jms.server.JMSVirtualProviderProcessor.destinationCreate(JMSVirtualProviderProcessor.java:624)
at com.sap.jms.server.RMIJMSVirtualProviderProcessor.destinationCreate(RMIJMSVirtualProviderProcessor.java:98)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.sap.engine.services.rmi_p4.P4DynamicSkeleton.dispatch(P4DynamicSkeleton.java:241)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:483)
at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:83)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:185)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:302)

] [
>>> without warnings <<<].#

#2.0�#2019 02 01 09:52:46:176#+0300#Error#com.sap.engine.services.deploy.server.LifecycleController#
com.sap.ASJ.dpl_ds.005039#BC-JAS-JMS#jmsconnector#C000AC120188009B0000003E00A801FE#28947650000000003##com.sap.engine.services.deploy.server.LifecycleController#Guest#0##361E8848256111E9B458000001B9B4C2#361e8848256111e9b458000001b9b4c2#FB1887FA25ED11E9CF790000001927A6#0#Thread[HTTP Worker [@1667666659],5,Dedicated_Application_Thread]#Plain##
Application sap.com/com.sap.xi.directory cannot be started. Reason: it has hard reference to application sap.com/com.sap.xi.ib.resources, which is not active on the server because application fails to start with errors. Contact component owners to investigate the problem with application sap.com/com.sap.xi.ib.resources.#

  • In NWA -> Operations -> Start & Stop it can be seen that the applications have errors such as "Failed to start" or "Implicit Stopped(dependency failed)":

    Failed+to+Start.png

    Implicit stopped.png

  • You are using the NetWeaver Developer Studio (NWDS) to deploy objects in the Enterprise Services Repository(ESR). You are trying to deploy an object and it fails with the error:

"Cannot deploy. You are not authorized".

  • You are using the Enterprise Services Builder(ESB) to edit objects in Enterprise Services Repository(ESR). You are not able to edit the objects and get the error:

"User Guest has not permission: vpName: default, type: topic, action: produce, destination: jms/topic/xi/repository/SYNCHRONIZED_CACHE"

esr_edit_error.jpg


Read more...

Environment

  • SAP enhancement package 1 for SAP NetWeaver Process Integration 7.1
  • SAP NetWeaver 7.3
  • SAP enhancement package 1 for SAP NetWeaver 7.3
  • SAP NetWeaver 7.4
  • SAP NetWeaver 7.5

Product

SAP NetWeaver 7.3 ; SAP NetWeaver 7.4 ; SAP NetWeaver 7.5 ; SAP NetWeaver Process Integration 7.1 ; SAP enhancement package 1 for SAP NetWeaver 7.3 ; SAP enhancement package 1 for SAP NetWeaver Process Integration 7.1

Keywords

Process Integration 7.11, PI 7.11, Process Integration 7.30, PI 7.30, Process Integration 7.31, PI 7.31, Process Orchestration 7.4, PI 7.4, PO 7.4, Process Orchestration 7.5, PI 7.5, PO 7.5, XI, AEX, jms/topic/xi/repository/SYNCHRONIZED_CACHE, jms/topic/xi/AIILogging, sap.com/com.sap.xi.ib.resources, UMESecurityProvider, SP13 upgrade , KBA , BC-XI-CON-AFW , J2EE Adapter Framework , BC-JAS-SEC , Security, User Management , BC-XI-IBC , Integration Builder - Configuration , BC-XI-CON-AFW-AAE , Advanced Adapter Engine , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.