cancel
Showing results for 
Search instead for 
Did you mean: 

WebDynpro DC Deployment Problem

Former Member
0 Kudos

Hi ,

I am working on web dynpro DC. while deploying Dc am getting following waring .

--- Deploying file(s):

F:\NWDS\workspace.jdi\0\DCs\asianpaints.com\erecdyn\_comp\gen\default\deploy\asianpaints.com~erecdyn.ear

--- Status:

Deploy finished with warnings.

--- Description:

S U M M A R Y

~~~~~~~~~~~~~~~~~~~

Successfully deployed: 0

Deployed with warnings: 1

Failed deployments: 0

~~~~~~~~~~~~~~~~~~~

1. File:F:\NWDS\workspace.jdi\0\DCs\asianpaints.com\erecdyn\_comp\gen\default\deploy\asianpaints.com~erecdyn.ear

Name:erecdyn

Vendor:asianpaints.com

Location:J2N_ERECTT_D

Version:20080711123240

Deploy status:Warning

Version:HIGHER

Description:

1. Warning occurred on server 6358450 during update asianpaints.com/erecdyn : References Test: There are no matching deploy time references (described in META-INF/SAP_MANIFEST.MF) for the following runtime references [sap.com/mail, sap.com/activation, sap.com/tcsecwssecservice, sap.com/jnet, sap.com/asianpaints.comerecapp, sap.com/jsse, sap.com/asianpaints.comhelplib, sap.com/asianpaints.comerecnapp, sap.com/IAIKSecurity, sap.com/webservices] (described in the META-INF/application-j2ee-engine.xml)., file: asianpaints.com~erecdyn.ear, column 0, line 0, severity: warning

Warning occurred on server 6358450 during update asianpaints.com/erecdyn : com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5035] Application asianpaints.com/erecdyn cannot be started. Reason: it has hard reference to resource asianpaints.com~erecapp with type application, which is not active on the server.

at com.sap.engine.services.deploy.server.ReferenceResolver.processReferenceToApplication(ReferenceResolver.java:822)

at com.sap.engine.services.deploy.server.ReferenceResolver.processMakeReference(ReferenceResolver.java:580)

at com.sap.engine.services.deploy.server.ReferenceResolver.beforeStartingApplication(ReferenceResolver.java:496)

at com.sap.engine.services.deploy.server.application.StartTransaction.beginCommon(StartTransaction.java:166)

at com.sap.engine.services.deploy.server.application.StartTransaction.begin(StartTransaction.java:134)

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

at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:445)

at com.sap.engine.services.deploy.server.application.ParallelAdapter.super_MakeAllPhases(ParallelAdapter.java:337)

at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:550)

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

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

at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeNestedParallelTransaction(ApplicationTransaction.java:665)

at com.sap.engine.services.deploy.server.application.UpdateTransaction.finalActions(UpdateTransaction.java:670)

at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:456)

at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:2528)

at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:493)

at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:393)

at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.update(ApplicationDeployer.java:61)

at com.sap.engine.services.dc.gd.impl.InitialApplicationDeployer.performDeployment(InitialApplicationDeployer.java:95)

at com.sap.engine.services.dc.gd.impl.InitialGenericDeliveryImpl.deploy(InitialGenericDeliveryImpl.java:59)

at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:158)

at com.sap.engine.services.dc.cm.deploy.impl.BulkOnlineDeployProcessor.deploy(BulkOnlineDeployProcessor.java:48)

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

at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)

at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor.deploy(AbstractDeployProcessor.java:77)

at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:726)

at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:576)

at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:270)

at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:192)

at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:875)

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

at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70)

at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62)

at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37)

at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:877)

at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53)

at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58)

at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108)

at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304)

Warning occurred on server 6358450 during update asianpaints.com/erecdyn : com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5030] Clusterwide exception: server ID 6358450:com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5035] Application asianpaints.com/erecdyn cannot be started. Reason: it has hard reference to resource asianpaints.com~erecapp with type application, which is not active on the server.

at com.sap.engine.services.deploy.server.ReferenceResolver.processReferenceToApplication(ReferenceResolver.java:822)

at com.sap.engine.services.deploy.server.ReferenceResolver.processMakeReference(ReferenceResolver.java:580)

at com.sap.engine.services.deploy.server.ReferenceResolver.beforeStartingApplication(ReferenceResolver.java:496)

at com.sap.engine.services.deploy.server.application.StartTransaction.beginCommon(StartTransaction.java:166)

at com.sap.engine.services.deploy.server.application.StartTransaction.begin(StartTransaction.java:134)

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

at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:445)

at com.sap.engine.services.deploy.server.application.ParallelAdapter.super_MakeAllPhases(ParallelAdapter.java:337)

at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:550)

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

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

at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeNestedParallelTransaction(ApplicationTransaction.java:665)

at com.sap.engine.services.deploy.server.application.UpdateTransaction.finalActions(UpdateTransaction.java:670)

at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:456)

at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:2528)

at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:493)

at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:393)

at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.update(ApplicationDeployer.java:61)

at com.sap.engine.services.dc.gd.impl.InitialApplicationDeployer.performDeployment(InitialApplicationDeployer.java:95)

at com.sap.engine.services.dc.gd.impl.InitialGenericDeliveryImpl.deploy(InitialGenericDeliveryImpl.java:59)

at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:158)

at com.sap.engine.services.dc.cm.deploy.impl.BulkOnlineDeployProcessor.deploy(BulkOnlineDeployProcessor.java:48)

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

at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)

at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor.deploy(AbstractDeployProcessor.java:77)

at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:726)

at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:576)

at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:270)

at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:192)

at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:875)

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

at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70)

at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62)

at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37)

at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:877)

at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53)

at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58)

at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108)

at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304)

What can be problem??? how can i resolve this issue?

Accepted Solutions (1)

Accepted Solutions (1)

nikhil_bose
Active Contributor
0 Kudos

kavita,

did you check deploy & run time reference for all used DCs?

nikhil

Former Member
0 Kudos

"check deploy & run time reference " , means what i hv to do exactly???

nikhil_bose
Active Contributor
0 Kudos

tick checkbox of Deploy and Runtime Dependance Types and try

nikhil

Former Member
0 Kudos

yes , i tries tht too. both check boxes were ticked. still giving same warning. i hv added same used DCs to aonther webdynpro project , that project got deployed successfully.

Also i would like to mention that , this DC was earlier working in Netweaver 7.0. I took back up by exporting as zip file. Then using back up i created new DC in Netweaver 7.0 ( migrated to 7.1). I have even migrated 3 more WebDynpro Dcs to Netweaver 7.1 and are working fine , but problem with this DC only

Former Member
0 Kudos

i resolved this issue. Thnx a lot.

Former Member
0 Kudos

Hi Kavita,

What you've done to solve your problem?

Thanks and regards,

Eduardo

Former Member
0 Kudos

hey there

I also would like to know about how to resolve this issue as mine looks pretty much similar.

Caused by: java.rmi.RemoteException: [ERROR CODE DPL.DS.6125] Error occurred while starting application locally and wait.; nested exception is: 
	com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5035] Application demo.sap.com/todo~wdp cannot be started. Reason: it has hard reference to resource todo~app with type application, which is not active on the server.
	at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationLocalAndWait(DeployCommunicatorImpl.java:687)
	at com.sap.engine.services.servlets_jsp.server.deploy.impl.ApplicationManager.start(ApplicationManager.java:178)
	... 46 more
Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5035] Application demo.sap.com/todo~wdp cannot be started. Reason: it has hard reference to resource todo~app with type application, which is not active on the server.
	at com.sap.engine.services.deploy.server.ReferenceResolver.processReferenceToApplication(ReferenceResolver.java:843)
	at com.sap.engine.services.deploy.server.ReferenceResolver.processMakeReference(ReferenceResolver.java:580)
	at com.sap.engine.services.deploy.server.ReferenceResolver.beforeStartingApplication(ReferenceResolver.java:496)
	at com.sap.engine.services.deploy.server.application.StartTransaction.beginCommon(StartTransaction.java:166)
	at com.sap.engine.services.deploy.server.application.StartTransaction.beginLocal(StartTransaction.java:140)
	at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:482)
	at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:256)
	at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:400)
	at com.sap.engine.services.deploy.server.DeployServiceImpl.regularStartApplicationLocalAndWait(DeployServiceImpl.java:3202)
	at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:3194)
	at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationLocalAndWait(DeployCommunicatorImpl.java:685)
	... 47 more
Caused by: com.sap.engine.services.orpersistence.container.deploy.ActionException: [ERROR CODE DPL.DS.5030] Clusterwide exception: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at TODO, the whole lookup name is jdbc/TODO/TODODS.
	at com.sap.engine.services.jndi.implserver.ServerContextImpl.getLastContainer(ServerContextImpl.java:241)
	at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:559)
	at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:343)
	at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:266)
	at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:286)

btw: this is just an extract of the whole mess how come that one gets no hints of where to look for the actual problems? this is quite messy 'specially for ones that are new to the topic....

as well there seems to be a problem with the data persistence - anyone any idea on these issues?

Edited by: Sebastian Timmel on Dec 11, 2008 3:02 PM

Former Member
0 Kudos

Hi Sebastian ,

righy click on webdynpro dc ->properties -> webdynpro and check references for dc mentioned for hard reference and just remove that entry from references. it will resolve ur problem.

Reply me back if this helped u.

Regards

Kavita

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi,

Check if all used DCs are deployed correctly on the server

Regards,

Apurva

Former Member
0 Kudos

i hv checked all used DCs. All r deployed successfully. Even i created another Webdynpro DC and added all those DCs as used DCs. That test project deployed successfully.