Excepction while trying to start PI rep application

[Former Member]

Hello,

I was given a sandbox with Netweaver 7.31 PI system to complete the configuration and give to dev team for some tests

I think i managed to complete the configuration although i am not familiar with XI/PI at all

However whenever i try to start the /rep/index.jsp i am getting the following exception

Web application [rep] cannot be started. The error is: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Application sap.com/com.sap.xi.repository 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.
at com.sap.engine.services.deploy.server.LifecycleController.startReferencedApplication(LifecycleController.java:686)
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:207)
at com.sap.engine.services.deploy.server.application.StartTransaction.begin(StartTransaction.java:172)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:421)
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:681)
at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:1822)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:2482)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationOnInstanceWait(DeployServiceImpl.java:2734)
at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.lazyStartApplicationAndWait(DeployCommunicatorImpl.java:686)
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:391)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:165)
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)

I patched all JAVA components to SP09 but the error is not gone

Any idea how to get past this issue?

Thank for the help!

[Former Member]

Hi Yavor,

You will note that service : sap.com/com.sap.xi.ib.resources is not running.  Can you start this with NWA?  If not you may well need to patch the whole stack with SUM and try again. 

I had this with PI-AEX NW 7.4 and had to install the base system and complete the initial configuration wizards before patching. Otherwise patching just some components failed and broke the patching tools.  We took it to SP4 in one hit and that worked. 

Hope that helps,

Regards,

Graham

[Former Member]

I have tried starting it manually but no luck

I patched all components for JAVA stack, kernel is updated, however i have not touched the

ABAP stack, do you think this can help?

P.S I forgot to mention the system was built (obviously incomplete) from a system copy, i saw there are lot of issues with PI copies and i am wondering if i shall recreate the sandbox from scratch if not solved in the next couple of days

[Former Member]

Hi

If you have an incomplete system copy, then this is likely to fail.  If you need a system copyfrom DEV, i.e. there is useful information and config in DEV, then you need to perform the system copy properly and successfully- see and follow the Guides.

If you just want a blank PI sandbox for trying things out then installing it from scratch is likely best and fastest.  See your project manager for guidance on this.

Regards,

Graham

[Former Member]

Well when i said incomplete i meant that no configuration was done, the copy might or might not have been ok, it has been done like 9 months ago and the sandbox was not touched.

Anyway thanks for your time, i might end up installing from scratch. although i don't want to give up just yet

[Former Member]

Hi

You need to use /dir/index.jsp instead of rep from 7.1 and above. If sandbox is a copy of another system make sure all host name are changed in Exchange profile else it will point to original system it copied from.

Thanks

Kiran Nekkanti

[Former Member]

Tried both, the error is absolutely the same, the exchange profile was changed using the configuration template and it's fine

[Former Member]

connect to config tool and start the services (rep and directory). you can also check the status in NWA. if they are in error state stop and do full cache refresh and start again.

Have you restarted the system recently by killing all the sessions under sidam. if not please try restarting the application once.

Is it JAVA only instance or Both?

[Former Member]

This dual stack, i restarted the whole system just in case but it didn't help. Applicaitons/services can not be started in NWA  - same error as before.

I have no XI/PI experience whatsoever, just a quick question before reinstalling from scratch

PI is kind of a usage type or Functionality for Netweaver, not a separate setup like ERP, SRM etc? Is my understanding correct ?

[Former Member]

Just as a follow up i ended up reinstalling the sandbox from scratch and completed the setup without issues