cancel
Showing results for 
Search instead for 
Did you mean: 

Portal application not starting after SC transport via NWDI

Former Member
0 Kudos

Hi

We have one Portal application  which stops after Software component transport.

The application could not be started via NWA .

Restart of server starts the application

The error while starting is as follows.

Local [startApp] operation of application [XXXXXXXXXXX] finished with errors for [653] ms on server [ZZZZZZZZZZ] [

>>> Errors <<<

1). com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Application XXXXXXXXXXX cannot be started. Reason: it has hard reference to application YYYYYYYYYYYYY, which is not active on the server because  application fails to start with errors. Contact component owners to investigate the problem with application YYYYYYYYYYYYY.

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:208)

at com.sap.engine.services.deploy.server.application.StartTransaction.beginLocal(StartTransaction.java:184)

at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:549)

at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocal(ParallelAdapter.java:335)

at com.sap.engine.services.deploy.server.DeployServiceImpl.execute(DeployServiceImpl.java:1715)

at com.sap.engine.services.deploy.server.remote.RemoteCommandFactory$StartRemoteCommand.execute(RemoteCommandFactory.java:804)

at com.sap.engine.services.deploy.server.remote.RemoteCommandFactory$RemoteCommand$1.run(RemoteCommandFactory.java:142)

at com.sap.engine.services.deploy.server.remote.RemoteCommandFactory$RemoteCommand$1.run(RemoteCommandFactory.java:137)

at java.security.AccessController.doPrivileged(Native Method)

at javax.security.auth.Subject.doAs(Subject.java:394)

at com.sap.engine.services.deploy.server.remote.RemoteCommandFactory$RemoteCommand.executeInSubjectDoAs(RemoteCommandFactory.java:137)

at com.sap.engine.services.deploy.server.remote.RemoteCaller$1.run(RemoteCaller.java:588)

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)

Regards

Pratyush

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi Michal/Rohit

Thanks for wonderful pointers.

As suggested I checked Application Y

The error while starting application Y is

Exception occurred during ws clients start. Unable to bind service implementation instances for service group

com.sap.engine.services.jndi.persistent.exceptions720.NameNotFoundException: Path to object does not exist. First missing component is [philips.com], the whole lookup name is

Only reference in application Y is

tc~esi~esp~wsrm~app

Regards

Pratyush

rohit_singhal
Active Contributor
0 Kudos

Hi Pratyush,

Could you paste the deployment descriptor for application Y.

Also please paste the entire exception chain that you get on start up of application Y.

Best Regards,

Rohit Singhal

rohit_singhal
Active Contributor
0 Kudos

Hi Pratyush,

Can you please check if the all referenced DC's of your application are also present in the system.

From your error description it seems that during startup of application X, application Y is being searched in the server and is not found.

You might also want to check the sharing references defined in your portalapp.xml, and if all the custom applications referenced are deployed on the server.

Do let me know in case of any concerns.

Best Regards,

Rohit Singhal

Former Member
0 Kudos

Hi Rohit

Thanks for your reply.

Application Y is present in the system but in stoppet state.

We tried to restart application Y via NWA and it threw the same error as mentioned above.

Also when we restart server both X and Y starts.

Regards

Pratyush

rohit_singhal
Active Contributor
0 Kudos

Hi Pratyush,

Could you please confirm if portalapp.xml of Y contains reference for application X, and if portalapp.xml of X contains reference for application Y.

Ideally reference for application would be one way and not bi-directional.

Do let me know in case of any concerns.


Best Regards,

Rohit Singhal

0 Kudos

Hi,

As mentioned in earlier replies, you should maintain the references to other applications - if this is not a portal application, but another java application,

then you should maintain the hard reference via application-j2ee-engine.xml or provider.xml depending on your component type - SDA or EAR.

Moreover, if you start Y application, and it gives such an error, you should check to what other application it has reference to, and make sure to maintain the reference in Y application as well.

Thanks & regards,

Michal