Strange behaviour on Dynpro deployments

[Former Member]

Hello,

I have a strange problem when I deploy Dynpro applications through the NWDS.

When I first deploy the application I get:

<b>Deployment finished with warning :

The referenced application "sap.com/tc_wddispwda" can"t be started.

Check the causing exception for details.</b>

If right afterwards I deploy the application again it deploys with no problems.

If I deploy it again, again I receive this warning and so on and so forth circulatory - One time I get it and one time I don't.

Any ideas what can cause this strange behaviour?

Message was edited by:

Roy Cohen

[Former Member]

Well, a restart of the engine seems to have solved the problem.

Sometimes the most simple solutions are the cure...

[Former Member]

Hi ,

I think the error was sap.com/tc_wddispwda

Not sure of the cause of the problem .. You can login to Visual Admin.. server - services- configuration adapter.. webdynpro -tc_wddispwda -> Property Sheet Default and change expiration time or cache time.. and try.

Regards

Bharathwaj

[Former Member]

Hi, Roy

And could you tell us what traces(defaultTrace.trc or

application.log) do you get when this error happened?

Best Regards.

Sejoon

[Former Member]

Hi Sejoon,

The defaultTrace doesn't say much, the same as I get on the NWDS console:

server ID

4060051:com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to prepare application ''local/MappingReportsProject'' for startup. Reason=

Clusterwide exception: Failed to start application ''local/MappingReportsProject'': The referenced application ''sap.com/tc_wddispwda'' can''t be started. Check the causing exception for details. Hint: Is the referenced application deployed correctly on the server?

at com.sap.engine.services.webdynpro.WebDynproContainer.prepareStart(WebDynproContainer.java:1490)

at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)

at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:171)

at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:301)

at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:342)

at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:126)

at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:245)

at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4761)

at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4666)

at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4639)

at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1163)

at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)

at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)

at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)

at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)

at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)

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

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)