What is VMO ?

[Former Member]

Hi:

The app's deploy fails. At defaultTrace.6.trc (the file that was most recently modified) says:

#false#

#1.5 #00145E2887DA00410000001600000AE0000437FC9B81441B#1187457987123#com.sap.engine.services.webdynpro.WebDynproContainer##com.sap.engine.services.webdynpro.WebDynproContainer#Administrator#1247####25bf774f4db011dc93f800145e2887da#SAPEngine_Application_Thread[impl:3]_16##0#0#Error#1#/System/UserInterface#Java###Failed to deploy application '''' for deployment state listener ''''. <b> #3#local/Drillingcombos#com.sap.tc.webdynpro.serverimpl.wdc.repository.RepositoryContainerHook#com.sap.tc.webdynpro.repository.RepositoryRuntimeException: Failed to deploy the file 'D: usr sap PK0 JC00 j2ee cluster server0 . temp webdynpro public local Drillingcombos webdynpro Applications com.repsolypf.drilling.combos.FiltrosApp FiltrosApp.xml' into the database. Reason: Development Object 'local/DrillingCombos' contains already same repository content. Hint: fully qualified name of the repository VMO must be globally unique. </b> at com.sap.tc.webdynpro.repository.deploy.RepositoryUpdateManager.checkVMOsExistInOtherDC(RepositoryUpdateManager.java:504) at com.sap.tc.webdynpro.repository.deploy.RepositoryUpdateManager.deployRepositoryContent(RepositoryUpdateManager.java:98) at com.sap.tc.webdynpro.serverimpl.wdc.repository.RepositoryContainerHook.onDeploy(RepositoryContainerHook.java:232) at com.sap.engine.services.webdynpro.WebDynproContainer.deploy(WebDynproContainer.java:1007) at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606) at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:321) at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:307) at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292) at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326) at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3184) at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:552) at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1555) at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:312) at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:199) 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) # #1.5 #00145E2887DA00410000001800000AE0000437FC9B884F47#1187457987591#com.sap.engine.services.deploy##com.sap.engine.services.deploy#Administrator#1247####25bf774f4db011dc93f800145e2887da#SAPEngine_Application_Thread[impl:3]_16##0#0#Error#1#/System/Server#Java#deploy_5029##Exception in operation deploy with application local/Drillingcombos.#2#deploy#local/Drillingcombos# #1.5 #00145E2887DA00410000001900000AE0000437FC9B885ED5#1187457987591#com.sap.engine.services.deploy##com.sap.engine.services.deploy#Administrator#1247####25bf774f4db011dc93f800145e2887da#SAPEngine_Application_Thread[impl:3]_16##0#0#Error#1#/System/Audit#Java###Exception #1#com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception in operation deploy with application local/Drillingcombos.

at com.sap.engine.services.deploy.server.application.ApplicationTransaction.rollbackPart(ApplicationTransaction.java:394)

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

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

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

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

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

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

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

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)

Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Cannot deploy application local/Drillingcombos.

at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:330)

at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:307)

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

... 13 more

Caused by: com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application local/Drillingcombos. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?

at com.sap.engine.services.webdynpro.WebDynproContainer.deploy(WebDynproContainer.java:1016)

at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)

at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:321)

... 15 more

#

#1.5 #00145E2887DA00410000001B00000AE0000437FC9B8C3490#1187457987841#com.sap.engine.services.deploy##com.sap.engine.services.deploy#Administrator#1247####25bf774f4db011dc93f800145e2887da#SAPEngine_Application_Thread[impl:3]_16##0#0#Error#1#/System/Server#Plain###

Operation deploy over application local/Drillingcombos finished with errors on server 1018650. For more detailed information see traces of Deploy Service.#

#1.5 #00145E2887DA00410000001D00000AE0000437FC9B8C6E48#1187457987857#com.sap.engine.services.deploy##com.sap.engine.services.deploy#Administrator#1247####25bf774f4db011dc93f800145e2887da#SAPEngine_Application_Thread[impl:3]_16##0#0#Error#1#/System/Server#Java#deploy_5047##Cannot deploy application local/Drillingcombos.#1#local/Drillingcombos#

#1.5 #00145E2887DA00410000001E00000AE0000437FC9B8C708D#1187457987857#com.sap.engine.services.deploy##com.sap.engine.services.deploy#Administrator#1247####25bf774f4db011dc93f800145e2887da#SAPEngine_Application_Thread[impl:3]_16##0#0#Error#1#/System/Audit#Java###Exception #1#com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Cannot deploy application local/Drillingcombos. at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:330) at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:307) at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292) at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326) at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3184) at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:552) at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1555) at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:312) at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:199) 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) Caused by: com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application local/Drillingcombos. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine? at com.sap.engine.services.webdynpro.WebDynproContainer.deploy(WebDynproContainer.java:1016) at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606) at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:321) ... 15 more # #1.5 #00145E2887DA00410000001F00000AE0000437FC9B8C798F#1187457987857#com.sap.engine.services.rmi_p4##com.sap.engine.services.rmi_p4#Administrator#1247####25bf774f4db011dc93f800145e2887da#SAPEngine_Application_Thread[impl:3]_16##0#0#Warning##Plain###com.sap.engine.services.rmi_p4.DispatchImpl.throwException MSG: P4 Call execution: Exception in execute operation :<deploy(java.lang.String,java.lang.String[],java.util.Properties)> : Cannot deploy application local/Drillingcombos.. Reason: Clusterwide exception: Failed to deploy application local/Drillingcombos. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?; nested exception is: com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application local/Drillingcombos. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine? called from: 16128 server id: -1# #1.5 #00145E2887DA0034000000C100000AE0000437FC9CEC3182#1187458010919#com.sapportals.wcm.repository.manager.sfs.FSRepositoryManager#sap.com/irj#com.sapportals.wcm.repository.manager.sfs.FSRepositoryManager#Guest#0####391fe6504d9511dc99b400145e2887da#Thread[Thread-71,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Plain###getting mapped math - java.io.IOException: Logon failure: unknown user name or bad password at java.io.WinNTFileSystem.canonicalize0(Native Method) at java.io.Win32FileSystem.canonicalize(Win32FileSystem.java:333) at java.io.File.getCanonicalPath(File.java:513) at com.sapportals.wcm.repository.util.file.StdFileImpl.getCanonicalPath(StdFileImpl.java:74) at com.sapportals.wcm.repository.util.file.StdFileImpl.getCanonicalFile(StdFileImpl.java:70) at com.sapportals.wcm.repository.manager.sfs.FSRepositoryManager.startUpImpl(FSRepositoryManager.java:141) at com.sapportals.wcm.repository.manager.AbstractRepositoryManager.start(AbstractRepositoryManager.java:523) at com.sapportals.wcm.crt.CrtThreadSafeComponentHandler.tryToStart(CrtThreadSafeComponentHandler.java:246) at com.sapportals.wcm.crt.CrtThreadSafeComponentHandler$1.run(CrtThreadSafeComponentHandler.java:252) at java.util.TimerThread.mainLoop(Timer.java:432) at java.util.TimerThread.run(Timer.java:382) # #1.5 #00145E2887DA00350000000800000AE0000437FC9FB94214#1187458057918#com.sap.security.core.persistence##com.sap.security.core.persistence.[cf=com.sap.security.core.persistence.datasource.imp.LDAPPersistence][md=searchPrincipalDatabag][cl=22580]#Administrator#1255####50c171f24db011dc946c00145e2887da#SAPEngine_Application_Thread[impl:3]_10##0#0#Warning##Java###Paged search is enabled with criteria , extended search possible

at the ide (NWDS 7.0.12):

Caught exception during application deployment from SAP J2EE Engine's deploy service:

java.rmi.RemoteException: Cannot deploy application local/Drillingcombos.. Reason: Clusterwide exception: Failed to deploy application local/Drillingcombos. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?; nested exception is: com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application local/Drillingcombos. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?

(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)

Deployment exception : The deployment of at least one item aborted

Thanks a lot for your time on this thread.

Rocío.

Edited by: Armin Reichert on Jan 28, 2008 6:06 PM

[BeGanz · Accepted solution]

Hi Rocio,

look at <a href="http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=DISPL_TXT&_NNUM=784677">SAP Note 784677</a>.

Regards, Bertram

Deployment destroys other DC

Deployment of a Web Dynpro DC destroys another (previously deployed) DC. The thrown exception is "Cannot find repository information for ..." or other effects indicating that some data is missing (or is superfluous) in the Web Dynpro Runtime Repository.

Reason: A qualified name (for a class, Web Dynpro Application, Web Dynpro Component) must be used only in one DC. The DC concept provides assigning packages uniquely to a DC for reaching this goal. However, the DC tools do not enforce this restriction. If a Web Dynpro Component (or Application) with the same qualified name is contained in more than one DC then deploying one of the DCs destroys the meta data in the runtime repository of the other DC.

NOTE: Beginning with SAP NetWeaver 04s SP Stack 11 the deployment manager will check the existance of the same package in an already deployed DC during deployment. In case such a package collision is detected the DC deployment is aborted. This check will not be provided within SAP NetWeaver 04.

[Former Member]

2 WD projects have the same custom iview name with the same package. Rename one iview.