Assembly error SAP ESS Component concurrency-lock-denied
Hi,
we are always getting the following exception while assembling SAP-ESS Component in our NWDI:
(Step: Repository-export)
20101213121125 Info :PropagationList CMS_sap.com_SAP_ESS_26_4da649762a8311dfca0e005056942f98 added to export.
20101213121125 Info :Include sources physically into archive.
20101213121231 Fatal :caused by Exception:com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: VcmFailure received: Precondition Failed "concurrency-lock-denied":communication error: VcmFailure received: Precondition Failed "concurrency-lock-denied"
com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: VcmFailure received: Precondition Failed "concurrency-lock-denied"
at com.sap.cms.tcs.client.Export.getContents(Export.java:45)
at com.sap.cms.tcs.core.RepositoryExportTask.processRepositoryExport(RepositoryExportTask.java:167)
at com.sap.cms.tcs.core.RepositoryExportTask.process(RepositoryExportTask.java:333)
at com.sap.cms.tcs.process.ProcessStep.processStep(ProcessStep.java:77)
at com.sap.cms.tcs.process.ProcessStarter.process(ProcessStarter.java:206)
at com.sap.cms.tcs.core.TCSManager.assemblePropagationRequests(TCSManager.java:739)
at com.sap.cms.pcs.assembly.manager.AssemblyManager.assemble(AssemblyManager.java:1068)
at com.sap.cms.pcs.assembly.manager.AssemblyManager.startLevelAssembly(AssemblyManager.java:468)
at com.sap.cms.pcs.assembly.manager.AssemblyManager.startQueueAssembly(AssemblyManager.java:350)
Any suggestions?
Our System: NWDI 7.11 Patch 05
OS: Linux (amd64) - SAP DB (7.7.07)
Hello Golo.
Can you please recreate the problem whilst running the diagtool?
Note 1227928 Diagtool for troubleshooting NWDI (detailed logs)
There might be more information to work on.
Thanks
Kenny
Similar Messages
-
CMS import for SAP ESS component(SP 15) fails with fatal error.
Hi,
We are working on EP 7.0 SP 15. We have a requirement for changes to be made to SAP delivered ESS codes. We have set up the NWDI and and from the checkin tabn of CMS, the components SAP-JEE (7.00 SP18 ), SAP_JTECHS(7.00 SP18 ), SAP_PCUI-GP(SP 18), EP_BUILDT (7.00 SP18 )and SAP_BUILDT (7.00 SP18 )have been imported successfully to the development tab. But when we try to import the SAP ESS 600(SP level 15) from Checkin tab to the Development tab, the import fails. The exception chain as checked by clicking Details button in teh Develepoment tab of CMS shows the details as:
20090610145206 Info :Starting Step Repository-check at 2009-06-10 14:52:06.0283 +5:00
20090610145206 Info :Component:sap.com/SAP_ESS
20090610145206 Info :Version :MAIN_ERP05PAT_C.20090427083436
20090610145206 Info :1. propagation request is of type TCSSoftwareComponent
20090610145206 Info :Propagatable:d647b419330511de9f130030057116fe exists allready in the repository. No import necessary.
20090610145232 Fatal :VcmFailure received
20090610145232 Fatal :caused by Exception:com.tssap.dtr.client.lib.deltavlib.VcmFailure: Internal Server Error [(pre||post)-condition failed: Internal Server Error]:Internal Server Error [(pre||post)-condition failed: Internal Server Error]
com.tssap.dtr.client.lib.deltavlib.VcmFailure: Internal Server Error [(pre||post)-condition failed: Internal Server Error]
at com.tssap.dtr.client.lib.deltavlib.impl.AbstractCommand.checkedExecute(AbstractCommand.java:196)
at com.tssap.dtr.client.lib.deltavlib.impl.VersionSet.integrate(VersionSet.java:160)
at com.tssap.dtr.client.lib.deltavlib.impl.VersionSet.integrate(VersionSet.java:148)
at com.sap.cms.tcs.client.DTRCommunicator.integrateChangelist(DTRCommunicator.java:544)
at com.sap.cms.tcs.core.RepositoryImportTask.integrateResource(RepositoryImportTask.java:816)
at com.sap.cms.tcs.core.RepositoryImportTask.processRepositoryImport(RepositoryImportTask.java:367)
at com.sap.cms.tcs.core.RepositoryImportTask.process(RepositoryImportTask.java:651)
at com.sap.cms.tcs.process.ProcessStep.processStep(ProcessStep.java:77)
at com.sap.cms.tcs.process.ProcessStarter.process(ProcessStarter.java:206)
at com.sap.cms.tcs.core.TCSManager.checkPropagationRequests(TCSManager.java:517)
at com.sap.cms.pcs.transport.importazione.ImportManager.importazione(ImportManager.java:179)
at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.execImport(ImportQueueHandler.java:500)
at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.startImportCheck(ImportQueueHandler.java:130)
at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImportCheck(CmsTransportProxyBean.java:720)
at com.sap.cms.pcs.transport.proxy.LocalCmsTransportProxyLocalObjectImpl0_0.startImportCheck(LocalCmsTransportProxyLocalObjectImpl0_0.java:1844)
at com.sap.cms.ui.wl.Custom1.ImportCheck(Custom1.java:9968)
at com.sap.cms.ui.wl.wdp.InternalCustom1.wdInvokeEventHandler(InternalCustom1.java:3156)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingCustomController.invokeEventHandler(DelegatingCustomController.java:89)
at com.sap.tc.webdynpro.clientserver.event.CustomEventProcessor.handleServerEvent(CustomEventProcessor.java:45)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleServiceEvent(WindowPhaseModel.java:361)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:128)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processPhaseLoop(WebDynproWindow.java:345)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:152)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:321)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
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:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
20090610145232 Fatal :caused by Exception:com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: VcmFailure received: Internal Server Error [(pre||post)-condition failed: Internal Server Error]:communication error: VcmFailure received: Internal Server Error [(pre||post)-condition failed: Internal Server Error]
com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: VcmFailure received: Internal Server Error [(pre||post)-condition failed: Internal Server Error]
at com.sap.cms.tcs.client.DTRCommunicator.integrateChangelist(DTRCommunicator.java:563)
at com.sap.cms.tcs.core.RepositoryImportTask.integrateResource(RepositoryImportTask.java:816)
at com.sap.cms.tcs.core.RepositoryImportTask.processRepositoryImport(RepositoryImportTask.java:367)
at com.sap.cms.tcs.core.RepositoryImportTask.process(RepositoryImportTask.java:651)
at com.sap.cms.tcs.process.ProcessStep.processStep(ProcessStep.java:77)
at com.sap.cms.tcs.process.ProcessStarter.process(ProcessStarter.java:206)
at com.sap.cms.tcs.core.TCSManager.checkPropagationRequests(TCSManager.java:517)
at com.sap.cms.pcs.transport.importazione.ImportManager.importazione(ImportManager.java:179)
at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.execImport(ImportQueueHandler.java:500)
at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.startImportCheck(ImportQueueHandler.java:130)
at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImportCheck(CmsTransportProxyBean.java:720)
at com.sap.cms.pcs.transport.proxy.LocalCmsTransportProxyLocalObjectImpl0_0.startImportCheck(LocalCmsTransportProxyLocalObjectImpl0_0.java:1844)
at com.sap.cms.ui.wl.Custom1.ImportCheck(Custom1.java:9968)
at com.sap.cms.ui.wl.wdp.InternalCustom1.wdInvokeEventHandler(InternalCustom1.java:3156)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingCustomController.invokeEventHandler(DelegatingCustomController.java:89)
at com.sap.tc.webdynpro.clientserver.event.CustomEventProcessor.handleServerEvent(CustomEventProcessor.java:45)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleServiceEvent(WindowPhaseModel.java:361)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:128)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processPhaseLoop(WebDynproWindow.java:345)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:152)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:321)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
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:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
20090610145232 Info :Step Repository-check ended with result 'fatal error' ,stopping execution at 2009-06-10 14:52:32.0796 +5:00
The above log is displayed when I click the import -check button on the development tab of CMS. The same error is displayes when the import button is clicked with only the last sentence changed to:
Step Repository-check ended with result 'fatal error'
Can anyone help me on this.... ?
Thanks,
Sonali.
Edited by: Sonali M S on Jun 10, 2009 1:16 PMHi Bala,
The problem still remails even after making changes in Visual Admin as per the thread Re: Assembly finished with errors
Also from http://<server>:<port>/nwa we have run the configuration task for "Initial setup of functional unit Development Infrastructure (DI all-in-one)" and there we donot have the option for individual CBS, CMS and DTR installations as told in the thread.
The other thread import into devlopment failed tells about the SAP note: 988010 iin which it is mentioned that this has been fixed in SP 11 for 7.00 version. We are already on SP 18. So it is assumable that this thing has already been fixed.
Can there be any other reason for this?
Thanks,
Sonali. -
Assembling ESS component fails in NWDI.
Hello Experts,
Did any one see this error before?
We have checked in all our changes and trying to assemble ESS component. Now While assembling I finished with errors. Can any suggest waht we need to do?
Do I have to reimport SCA file. But, does the reimport wipe-off all the change which already exist in there.
NWDI 7.0
Following is the error log.
20081030103948 Info :Starting Step Repository-export at 2008-10-30 10:39:48.0509 -5:00
20081030103948 Info :Start export of sources
20081030103948 Info :Component: sap.com/SAP_ESS Version :JDI_Tr713M_C.20081030153947 is processed now.
20081030103948 Info :1. PR is of type TCSSoftwareComponent
20081030103948 Info :Start reading sources of SC sap.com,SAP_ESS from DTR http://www.corp
20081030103948 Detail :Start creating PropagationList 'CMS_sap.com_SAP_ESS_22_9b90b2d48e6711ddcd0c001a642a9542'.
20081030105301 Detail :Created PropagationList '0e0dc992a69711ddcc2d001a642a9542'.
20081030105301 Info :PropagationList CMS_sap.com_SAP_ESS_22_9b90b2d48e6711ddcd0c001a642a9542 added to export.
20081030105301 Info :Include sources physically into archive.
20081030110346 Fatal :caused by Exception:com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: VcmFailure received: Could not perform Export Request. Response status = 500 (Internal Server Error):communication error: VcmFailure received: Could not perform Export Request. Response status = 500 (Internal Server Error)
com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: VcmFailure received: Could not perform Export Request. Response status = 500 (Internal Server Error)
at com.sap.cms.tcs.client.Export.getContents(Export.java:45)
at com.sap.cms.tcs.core.RepositoryExportTask.processRepositoryExport(RepositoryExportTask.java:167)
at com.sap.cms.tcs.core.RepositoryExportTask.process(RepositoryExportTask.java:333)
at com.sap.cms.tcs.process.ProcessStep.processStep(ProcessStep.java:77)
at com.sap.cms.tcs.process.ProcessStarter.process(ProcessStarter.java:206)
at com.sap.cms.tcs.core.TCSManager.assemblePropagationRequests(TCSManager.java:739)
at com.sap.cms.pcs.assembly.manager.AssemblyManager.assemble(AssemblyManager.java:1068)
at com.sap.cms.pcs.assembly.manager.AssemblyManager.startLevelAssembly(AssemblyManager.java:468)
at com.sap.cms.pcs.assembly.manager.AssemblyManager.startQueueAssembly(AssemblyManager.java:350)
at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startAssembly(CmsTransportProxyBean.java:1096)
at com.sap.cms.pcs.transport.proxy.LocalCmsTransportProxyLocalObjectImpl2_0.startAssembly(LocalCmsTransportProxyLocalObjectImpl2_0.java:2302)
at com.sap.cms.ui.wl.Custom1.startComponetAssembly(Custom1.java:16703)
at com.sap.cms.ui.wl.Custom1.assembleQueue(Custom1.java:4845)
at com.sap.cms.ui.wl.wdp.InternalCustom1.assembleQueue(InternalCustom1.java:2901)
at com.sap.cms.ui.wl.Worklist.handleAssemblyOptionsEvent(Worklist.java:1625)
at com.sap.cms.ui.wl.wdp.InternalWorklist.wdInvokeEventHandler(InternalWorklist.java:2991)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
at com.sap.tc.webdynpro.progmodel.controller.Component.fireEvent(Component.java:284)
at com.sap.cms.ui.wl.wdp.InternalWorklists.wdFireEventAssemblyOptionsEvent(InternalWorklists.java:482)
at com.sap.cms.ui.wl.Worklists.fireAssemblyOptionsEvent(Worklists.java:247)
at com.sap.cms.ui.wl.wdp.InternalWorklists.fireAssemblyOptionsEvent(InternalWorklists.java:402)
at com.sap.cms.ui.wl.AssemblyOptionsPopup.startAssembly(AssemblyOptionsPopup.java:1360)
at com.sap.cms.ui.wl.AssemblyOptionsPopup.onActionStartAssemblyAndAttachToCTS(AssemblyOptionsPopup.java:715)
at com.sap.cms.ui.wl.wdp.InternalAssemblyOptionsPopup.wdInvokeEventHandler(InternalAssemblyOptionsPopup.java:660)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:321)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
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(AccessController.java:215)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
20081030110346 Info :Remove software component SAP_ESS from further processing.
20081030110346 Info :Step Repository-export ended with result 'error' at 2008-10-30 11:03:46.0265 -5:00Boiler,
I remember having this issue and we did a restart of the NWDI server and it helped...try it..
Shikhil -
Error in Deployment of SAP ESS 100 SP16 ess/au/addr
Hello Gurus
Greetings !..
I am trying to Deploy SAP ESS 100 SP16 for Netweaver 2004s using SDM but getting error while i deploy in the phase ess/au/addr.
Please check for the log below if any one can helpout soon....
May 22, 2007 10:16:50... Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
May 22, 2007 10:16:50... Info: Finished successfully: development component 'ess/at/fam'/'sap.com'/'MAIN_xss04VAL_C'/'680352'/'0', grouped by
May 22, 2007 10:16:50... Info: Starting to save the repository
May 22, 2007 10:16:52... Info: Finished saving the repository
May 22, 2007 10:17:04... Info: Starting: Update: Selected development component 'ess/at/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'680388'/'0' updates currently deployed development component 'ess/at/pdata'/'sap.com'/'MAIN_ERP05VAL_C'/'766644'/'0'.
May 22, 2007 10:17:04... Info: SDA to be deployed: E:\usr\sap\SND\JC01\SDM\root\origin\sap.com\ess\at\pdata\MAIN_xss04VAL_C\0\680388\sap.com_essatpdata.sda
May 22, 2007 10:17:04... Info: Software type of SDA: J2EE
May 22, 2007 10:17:04... Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
May 22, 2007 10:17:06... Info: Begin of log messages of the target system:
07/05/22 22:17:04 - ***********************************************************
07/05/22 22:17:04 - Start updating EAR file...
07/05/22 22:17:04 - start-up mode is lazy
07/05/22 22:17:04 - EAR file updated successfully for 78ms.
07/05/22 22:17:04 - Start updating...
07/05/22 22:17:04 - EAR file uploaded to server for 219ms.
07/05/22 22:17:05 - Successfully updated. Update took 734ms.
07/05/22 22:17:05 - Deploy Service status:
07/05/22 22:17:05 - Application : sap.com/essatpdata
07/05/22 22:17:05 -
07/05/22 22:17:05 - sap.com/essatpdata - WEBDYNPRO
07/05/22 22:17:05 - ***********************************************************
May 22, 2007 10:17:06... Info: End of log messages of the target system.
May 22, 2007 10:17:06... Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
May 22, 2007 10:17:06... Info: Finished successfully: development component 'ess/at/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'680388'/'0', grouped by
May 22, 2007 10:17:07... Info: Starting to save the repository
May 22, 2007 10:17:08... Info: Finished saving the repository
May 22, 2007 10:17:21... Info: Starting: Initial deployment: Selected development component 'ess/au'/'sap.com'/'MAIN_xss04VAL_C'/'681439'/'0' will be deployed.
May 22, 2007 10:17:21... Info: SDA to be deployed: E:\usr\sap\SND\JC01\SDM\root\origin\sap.com\ess\au\MAIN_xss04VAL_C\0\681439\sap.com_ess~au.sda
May 22, 2007 10:17:21... Info: Software type of SDA: J2EE
May 22, 2007 10:17:21... Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
May 22, 2007 10:17:25... Info: Begin of log messages of the target system:
07/05/22 22:17:21 - ***********************************************************
07/05/22 22:17:21 - Start updating EAR file...
07/05/22 22:17:21 - start-up mode is lazy
07/05/22 22:17:21 - EAR file updated successfully for 188ms.
07/05/22 22:17:21 - Start deploying ...
07/05/22 22:17:22 - EAR file uploaded to server for 859ms.
07/05/22 22:17:24 - Successfully deployed. Deployment took 2547ms.
07/05/22 22:17:24 - Application : sap.com/ess~au
07/05/22 22:17:24 -
07/05/22 22:17:24 - sap.com/ess~au - WEBDYNPRO
07/05/22 22:17:24 - ***********************************************************
May 22, 2007 10:17:25... Info: End of log messages of the target system.
May 22, 2007 10:17:25... Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
May 22, 2007 10:17:25... Info: Finished successfully: development component 'ess/au'/'sap.com'/'MAIN_xss04VAL_C'/'681439'/'0', grouped by software component 'SAP_ESS'/'sap.com'/'MAIN_xss04VAL_C'/'1000.100.0.11.0.20060117105520''/'0'
May 22, 2007 10:17:25... Info: Starting to save the repository
May 22, 2007 10:17:27... Info: Finished saving the repository
May 22, 2007 10:17:39... Info: Starting: Initial deployment: Selected development component 'ess/au/addr'/'sap.com'/'MAIN_xss04VAL_C'/'681471'/'0' will be deployed.
May 22, 2007 10:17:39... Info: SDA to be deployed: E:\usr\sap\SND\JC01\SDM\root\origin\sap.com\ess\au\addr\MAIN_xss04VAL_C\0\681471\sap.com_essauaddr.sda
May 22, 2007 10:17:39... Info: Software type of SDA: J2EE
May 22, 2007 10:17:39... Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
May 22, 2007 10:17:40... Info: Begin of log messages of the target system:
07/05/22 22:17:39 - ***********************************************************
07/05/22 22:17:39 - Start updating EAR file...
07/05/22 22:17:39 - start-up mode is lazy
07/05/22 22:17:39 - EAR file updated successfully for 94ms.
07/05/22 22:17:39 - Start deploying ...
07/05/22 22:17:40 - EAR file uploaded to server for 297ms.
07/05/22 22:17:40 - ERROR: Not deployed. Deploy Service returned ERROR:
java.rmi.RemoteException: Cannot deploy application sap.com/essauaddr..
Reason: Clusterwide exception: Failed to deploy application sap.com/essauaddr. 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 sap.com/essauaddr. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?
at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:567)
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: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)
Caused by: com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application sap.com/essauaddr. 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)
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)
... 10 more
For detailed information see the log file of the Deploy Service.
07/05/22 22:17:40 - ***********************************************************
May 22, 2007 10:17:40... Info: End of log messages of the target system.
May 22, 2007 10:17:40... Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
May 22, 2007 10:17:40... Error: Aborted: development component 'ess/au/addr'/'sap.com'/'MAIN_xss04VAL_C'/'681471'/'0', grouped by software component 'SAP_ESS'/'sap.com'/'MAIN_xss04VAL_C'/'1000.100.0.11.0.20060117105520''/'0':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot deploy application sap.com/essauaddr..
Reason: Clusterwide exception: Failed to deploy application sap.com/essauaddr. 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 sap.com/essauaddr. 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)
May 22, 2007 10:17:40... Info: Starting to save the repository
May 22, 2007 10:17:42... Info: Finished saving the repository
May 22, 2007 10:17:54... Info: Starting: Initial deployment: Selected software component 'SAP_ESS'/'sap.com'/'MAIN_xss04VAL_C'/'1000.100.0.11.0.20060117105520''/'0' will be deployed.
May 22, 2007 10:17:54... Error: Aborted: software component 'SAP_ESS'/'sap.com'/'MAIN_xss04VAL_C'/'1000.100.0.11.0.20060117105520''/'0':
Failed deployment of SDAs:
development component 'ess/au/addr'/'sap.com'/'MAIN_xss04VAL_C'/'681471'/'0' : aborted
Please, look at error logs above for more information!
Hope for a prompt response.
Reply awaited urgently....
Thanks in Advance
Thanks & Best Regards
AshishHello Gerard Christopher
Yes i got the problem solved, actually SAP ESS 600 & SAP MSS 600 are the component we have to use. As we were on WAS 7.00 and ERP 2005 so
SAP ESS 600
SAP MSS 600
SAP PSS 600
SAP ASR 600
SAP PCUI_GP 600
Try with this you will able to solve.
Thanks & best Regards
Ashish -
Error deploying SAP ESS and MSS
Hello, I get the following error while I'm updating these BP with JSPM
Versions are SAP ESS 633.0.0 and SAP MSS 630.0.0 both versions has been released recently, the day 2011-07-08.
... Error: Unresolved dependencies found for the following SDAs:
1.: development component 'mss/exp/pla'/'sap.com'/'MAIN_ERP553VA_C'/'10472816'/'0'
dependency:
name: 'tc/aii/base/offline/facade'
vendor: 'sap.com'
There is no component either in SDM repository or in Deployment batch that resolves the dependency.
dependency:
name: 'tc/bl/exception/lib'
vendor: 'sap.com'
There is no component either in SDM repository or in Deployment batch that resolves the dependency.
dependency:
name: 'tc/ddic/runtime/facade'
vendor: 'sap.com'
There is no component either in SDM repository or in Deployment batch that resolves the dependency.
dependency:
name: 'tc/wd/api'
vendor: 'sap.com'
There is no component either in SDM repository or in Deployment batch that resolves the dependency.
dependency:
name: 'tc/bl/logging/api'
vendor: 'sap.com'
There is no component either in SDM repository or in Deployment batch that resolves the dependency.
Which is this component that I'm missing?
I got file SAPESS00_0-20006842.SCA for SAP ESS 633 and SAPMSS00_0-10009854.SCA for SAP MMS 630. and I placed both in the following path /usr/sap/trans/EPS/in and also they were the only ones that SWDC showed me when I was looking for.
Thanks in advance.
Edited by: Santiago Ruiz Ramos on Jul 18, 2011 9:42 AMOf course, these are the files
SAPESS00_0-20006842.SCA corresponding with SP00 for SAP ESS 633
SAPMSS00_0-10009854.SCA --> SP00 for SAP MSS 630
Also these othes files are present
SP00 for SAP PCUI_GP 633 --> SAPPCUIGP00_0-20006843.SCA
BP ERP05 ESS 1.41 BPERP5ESS09 --> BPERP5ESS09_0-10006126.SCA
SP04 for BP ERP05 MSS 1.51 --> BPERP5MSS04P_1-10007670.SCA
SP04 for BP ERP05 COMMON PARTS 1.51 --> BPERP5COM04_2-10007526.SCA
But only with the first two I get dependency problems as you can see in my first writing. Thanks in advance.
Edited by: Santiago Ruiz Ramos on Jul 26, 2011 7:08 AM -
Send data: "Error obtaining concurrency lock ()"
Hello,
after migration of SAP Backend System to a different provider, I am getting the error:
"Error obtaining concurrency lock ()" whenever I send data from an input schedule. Data can still be read from database and I can send comments without problems.
The other posts and sap notes concerning similar error messages relate to packages and script logic, but I am simply sending data from an input schedule, no package nor script logic involved.
Reprocessing dimensions/refreshing client side files did not solve the issue.
Does somebody know how to solve the problem?Hi,
We are also having similar problem while working with the Data Manager.
We have tried below solutions but nothing has worked.
1. Running the Data Manager Package with out the Default Logic.
2. RSPLSE has some entries in Locking Conflict Tab.
3. SM12 does not have any entries pending.
How do we delete the entries present in T-code RSPLSE?
As per the previous post by Florian, "After the administrator updated the server entries, the lock errors in BW and BOPC dont occur any more", which server entries that we are refering here? And how do we delete those entries?
Thanks
Ravi Akasapu -
SAP ESS Family Member/dependants java.lang.NullPointerException error
Hi
We are have the following problem when trying to edit or add a new child dependent fro Family member dependents. In the backend it works fine but on ess it dumps. There is no st22. we have looked all the notes and the previous sdn thread for this and applied the relevant patches as suggested in the notes. Have any of you encounter this problem and how did you guys resolve it??
The initial exception that caused the request to fail, was:
java.lang.NullPointerException
at com.sap.xss.per.vc.detailfooter.VcPersInfoDetailFooter.onBeforeOutput(VcPersInfoDetailFooter.java:229)
at com.sap.xss.per.vc.detailfooter.wdp.InternalVcPersInfoDetailFooter.onBeforeOutput(InternalVcPersInfoDetailFooter.java:188)
at com.sap.xss.per.vc.detailfooter.VcPersInfoDetailFooterInterface.onBeforeOutput(VcPersInfoDetailFooterInterface.java:144)
at com.sap.xss.per.vc.detailfooter.wdp.InternalVcPersInfoDetailFooterInterface.onBeforeOutput(InternalVcPersInfoDetailFooterInterface.java:136)
at com.sap.xss.per.vc.detailfooter.wdp.InternalVcPersInfoDetailFooterInterface$External.onBeforeOutput(InternalVcPersInfoDetailFooterInterface.java:212)
... 55 more
See full exception chain for details.
System Environment
Client
Web Dynpro Client Type HTML Client
User agent Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; InfoPath.3; .NET CLR 1.1.4322)
Version null
DOM version null
Client Type msie7
Client Type Profile ie6
ActiveX enabled
Cookies enabled
Frames enabled
Java Applets enabled
JavaScript enabled
Tables enabled
VB Script enabled
Server
Web Dynpro Runtime Vendor: SAP, build ID: 7.0104.20090324111057.0000 (release=NW701_04_REL, buildtime=2009-06-12:08:35:57[UTC], changelist=58858, host=pwdfm106), build date: Mon Dec 07 22:38:32 GMT+02:00 2009
J2EE Engine 7.01 PatchLevel 97888.
Java VM Java HotSpot(TM) 64-Bit Server VM, version:1.4.2_30-b04, vendor: Sun Microsystems Inc.
Operating system Windows 2003, version: 5.2, architecture: amd64
Session & Other
Session Locale en_ZA
Time of Failure Tue Jun 28 07:52:35 GMT+02:00 2011 (Java Time: 1309240355891)
Web Dynpro Code Generation Infos
sap.com/pb
SapDictionaryGenerationCore 7.0108.20100922154735.0000 (release=NW701_08_REL, buildtime=2010-12-06:09:22:16[UTC], changelist=96611, host=pwdfm319.wdf.sap.corp)
SapDictionaryGenerationTemplates 7.0108.20100922154735.0000 (release=NW701_08_REL, buildtime=2010-12-06:09:22:20[UTC], changelist=96611, host=pwdfm319.wdf.sap.corp)
SapGenerationFrameworkCore 7.0108.20100922154919.0000 (release=NW701_08_REL, buildtime=2010-12-06:09:16:25[UTC], changelist=96647, host=pwdfm319.wdf.sap.corp)
SapIdeWebDynproCheckLayer 7.0108.20100922160824.0000 (release=NW701_08_REL, buildtime=2010-12-06:09:26:26[UTC], changelist=96858, host=pwdfm319.wdf.sap.corp)
SapMetamodelCommon 7.0108.20100922155425.0000 (release=NW701_08_REL, buildtime=2010-12-06:09:17:08[UTC], changelist=96742, host=pwdfm319.wdf.sap.corp)
SapMetamodelCore 7.0108.20100922155425.0000 (release=NW701_08_REL, buildtime=2010-12-06:09:17:05[UTC], changelist=96742, host=pwdfm319.wdf.sap.corp)
SapMetamodelDictionary 7.0108.20100922154738.0000 (release=NW701_08_REL, buildtime=2010-12-06:09:20:28[UTC], changelist=96612, host=pwdfm319.wdf.sap.corp)
SapMetamodelWebDynpro 7.0108.20100922160830.0000 (release=NW701_08_REL, buildtime=2010-12-06:09:24:08[UTC], changelist=96859, host=pwdfm319.wdf.sap.corp)
SapWebDynproGenerationCTemplates 7.0108.20101115095814.0000 (release=NW701_08_REL, buildtime=2010-12-06:09:31:20[UTC], changelist=99321, host=pwdfm319)
SapWebDynproGenerationCore 7.0108.20100922160824.0000 (release=NW701_08_REL, buildtime=2010-12-06:09:26:29[UTC], changelist=96858, host=pwdfm319.wdf.sap.corp)
SapWebDynproGenerationTemplates 7.0108.20101115095814.0000 (release=NW701_08_REL, buildtime=2010-12-06:09:31:20[UTC], changelist=99321, host=pwdfm319)
sap.com/tcwddispwda
No information available null
sap.com/pb_api
SapDictionaryGenerationCore 7.0108.20100922154735.0000 (release=NW701_08_REL, buildtime=2010-12-06:09:22:16[UTC], changelist=96611, host=pwdfm319.wdf.sap.corp)
SapDictionaryGenerationTemplates 7.0108.20100922154735.0000 (release=NW701_08_REL, buildtime=2010-12-06:09:22:20[UTC], changelist=96611, host=pwdfm319.wdf.sap.corp)
SapGenerationFrameworkCore 7.0108.20100922154919.0000 (release=NW701_08_REL, buildtime=2010-12-06:09:16:25[UTC], changelist=96647, host=pwdfm319.wdf.sap.corp)
SapIdeWebDynproCheckLayer 7.0108.20100922160824.0000 (release=NW701_08_REL, buildtime=2010-12-06:09:26:26[UTC], changelist=96858, host=pwdfm319.wdf.sap.corp)
SapMetamodelCommon 7.0108.20100922155425.0000 (release=NW701_08_REL, buildtime=2010-12-06:09:17:08[UTC], changelist=96742, host=pwdfm319.wdf.sap.corp)
SapMetamodelCore 7.0108.20100922155425.0000 (release=NW701_08_REL, buildtime=2010-12-06:09:17:05[UTC], changelist=96742, host=pwdfm319.wdf.sap.corp)
SapMetamodelDictionary 7.0108.20100922154738.0000 (release=NW701_08_REL, buildtime=2010-12-06:09:20:28[UTC], changelist=96612, host=pwdfm319.wdf.sap.corp)
SapMetamodelWebDynpro 7.0108.20100922160830.0000 (release=NW701_08_REL, buildtime=2010-12-06:09:24:08[UTC], changelist=96859, host=pwdfm319.wdf.sap.corp)
SapWebDynproGenerationCTemplates 7.0108.20101115095814.0000 (release=NW701_08_REL, buildtime=2010-12-06:09:31:20[UTC], changelist=99321, host=pwdfm319)
SapWebDynproGenerationCore 7.0108.20100922160824.0000 (release=NW701_08_REL, buildtime=2010-12-06:09:26:29[UTC], changelist=96858, host=pwdfm319.wdf.sap.corp)
SapWebDynproGenerationTemplates 7.0108.20101115095814.0000 (release=NW701_08_REL, buildtime=2010-12-06:09:31:20[UTC], changelist=99321, host=pwdfm319)
sap.com/tcwdcorecomp
No information available null
Detailed Error Information
Detailed Exception Chain
java.lang.NullPointerException
at com.sap.xss.per.vc.detailfooter.VcPersInfoDetailFooter.onBeforeOutput(VcPersInfoDetailFooter.java:229)
at com.sap.xss.per.vc.detailfooter.wdp.InternalVcPersInfoDetailFooter.onBeforeOutput(InternalVcPersInfoDetailFooter.java:188)
at com.sap.xss.per.vc.detailfooter.VcPersInfoDetailFooterInterface.onBeforeOutput(VcPersInfoDetailFooterInterface.java:144)
at com.sap.xss.per.vc.detailfooter.wdp.InternalVcPersInfoDetailFooterInterface.onBeforeOutput(InternalVcPersInfoDetailFooterInterface.java:136)
at com.sap.xss.per.vc.detailfooter.wdp.InternalVcPersInfoDetailFooterInterface$External.onBeforeOutput(InternalVcPersInfoDetailFooterInterface.java:212)
at com.sap.pcuigp.xssfpm.wd.FPMComponent.callOnBeforeOutput(FPMComponent.java:603)
at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:569)
at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:438)
at com.sap.pcuigp.xssfpm.wd.FPMComponent.access$600(FPMComponent.java:78)
at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.raiseEvent(FPMComponent.java:938)
at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.raiseEvent(FPMComponent.java:1101)
at com.sap.xss.per.vc.overview.VcPersInfoOverview.create(VcPersInfoOverview.java:225)
at com.sap.xss.per.vc.overview.wdp.InternalVcPersInfoOverview.create(InternalVcPersInfoOverview.java:161)
at com.sap.xss.per.vc.overview.BizCardsView.onActionNew(BizCardsView.java:164)
at com.sap.xss.per.vc.overview.wdp.InternalBizCardsView.wdInvokeEventHandler(InternalBizCardsView.java:172)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:321)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:733)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:668)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)
at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:869)
at com.sap.tc.webdynpro.portal.pb.impl.localwd.LocalApplicationProxy.sendDataAndProcessAction(LocalApplicationProxy.java:77)
at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1363)
at com.sap.portal.pb.PageBuilder.SendDataAndProcessAction(PageBuilder.java:327)
at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:873)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java:755)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doPortalDispatch(WindowPhaseModel.java:717)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:136)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:321)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
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:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)You need the latest SP for resolving this ie front end version. Please check what version you are on and accordingly you need
to patch your system
1. http://service.sap.com/
2. SAP Support Portal - > Software Download
3. Download > Support packages and patches > Entry by application
group
4. SAP Application components
5. SAP ERP
6. SAP ERP ENHANCE PACKAGE
7. EHP4 FOR SAP ERP 6.0 / NW7.01
8. Entry by component
9. SAP XSS (Self Services)
10.SAP ESS 603 (# OS independent)
download the below version-
SAPESS06_8-20002355.SCA SP06 for SAP ESS 603
Now extract the below file from the downloaded SAP_ESS .sca
-ess~xx
Now Logon to SDM,go to deployment tab and open the deployment
configuration tab -
choose the radio button
-Update deployed SDA/SCA that have any version
-deploy -ess~xx sda files.
It will resolve the issue.
Edited by: Siddharth Rajora on Jun 28, 2011 5:17 PM -
JSPM Error with SAP-JEE component SP16
Hi
I am depolying a queue in JSPM SP16.1 for an ECC6 700 SR3 installed ABAP/Java system and it errors with the component SAP-JEE SP16 (installed level is SP14 as delivered in the SR3 kit)
The log has the messages:
Oct 8, 2008 1:49:57 PM Warning: Caught CVersProxyAccessException while saving repository: CVersAccessException: Cannot access CVers due to missing or incorrect configuration.
Additional error message is:
com.sap.sdm.apiint.serverext.servertype.TargetServiceException: Cannot provide connect data for database target system "CONFIG_DB".
Additional error message is:
com.sap.sdm.serverext.servertype.dbsc.DatabaseConnectException: Creation of DataSource for database "WFQ" failed. (com.sap.sql.log.OpenSQLException: Error while accessing secure store: Encryption or decryption is not possible because the full version of the SAP Java Crypto Toolkit was not found (iaik_jce.jar is required, iaik_jce_export.jar is not sufficient) or the JCE Jurisdiction Policy Files don't allow the use of the "PbeWithSHAAnd3_KeyTripleDES_CBC" algorithm..)
regards
MichaelHi Philipp
My version is 700 and the database is DB2/400 for IBM System i.
The sapcrypto is treated differently on this platform, so I havent done anything with it as yet.
I logged a message with SAP which has gone to the BC-JAS-SEC queue and the reply I received is below. Please let me know if this has helped you as I have not had the chance to get back to the system to try these steps :
regards
Michael.
To do the further investigation, may I check info below with you:
- are you able to read the content of the
/sapbwtest/global/security/lib/tools/iaik_jce.jar file with jar
- do you have the full strength JCE files installed for this JDK?
See note: 739043
- What user is used to connect to the Database from the java side in
the secure store? check if the password is correct or the user
is unlocked.
Make sure the connection details in Secure Store are the correct ones
you can check it in the config tool:
the jdbc/pool/<SID>/Password and jdbc/pool/<SID>/User
Edited by: Michael Power on Oct 15, 2008 8:52 PM -
Unexpected error decoding JSF component: {0} in SAP BO 4.0 sp2
Hi,
Am getting the above mentioned error repeatidly. I tried clearing the tomcat cache folder and restarted the tomcat but that couldnt help me to resolve the issue, Help me to resolve the issue.Hi Abhi,
Please refer the below KBA regarding your issue
1710454 - Unexpected error decoding JSF component BI 4.0
https://service.sap.com/sap/support/notes/1710454
Thanks,
Daya -
Hi Experts,
Iam having problem with my ESS page while iam clicking on it its showing error like this please help me in this.
Overview
500 Internal Server Error
SAP NetWeaver Application Server 7.00/Java AS 7.00
Failed to process request. Please contact your system administrator.
[Hide]
Overview
500 Internal Server Error
SAP NetWeaver Application Server 7.00/Java AS 7.00
Failed to process request. Please contact your system administrator.
[Hide]
Error Summary
While processing the current request, an exception occured which could not be handled by the application or the framework.
If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
Root Cause
The initial exception that caused the request to fail, was:
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: ComponentUsage(FPMConfigurationUsage): Active component must exist when getting interface controller. (Hint: Have you forgotten to create it with createComponent()? Should the lifecycle control of the component usage be "createOnDemand"?
at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.ensureActiveComponent(ComponentUsage.java:773)
at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.getInterfaceControllerInternal(ComponentUsage.java:348)
at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.getInterfaceController(ComponentUsage.java:335)
at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdGetFPMConfigurationUsageInterface(InternalFPMComponent.java:245)
at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.changeToExceptionPerspective(FPMComponent.java:861)
... 58 more
See full exception chain for details.
System Environment
Client
Web Dynpro Client Type HTML Client
User agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; InfoPath.1; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30)
Version null
DOM version null
Client Type msie6
Client Type Profile ie6
ActiveX enabled
Cookies enabled
Frames enabled
Java Applets enabled
JavaScript enabled
Tables enabled
VB Script enabled
Server
Web Dynpro Runtime Vendor: SAP, build ID: 7.0013.20070717142021.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:13:14[UTC], changelist=455669, host=pwdfm101), build date: Thu May 29 11:29:48 IST 2008
J2EE Engine 7.00 patchlevel 109044.44
Java VM Java HotSpot(TM) 64-Bit Server VM, version:1.4.2 1.4.2.13-070317-20:54-IA64W IA64W, vendor: Hewlett-Packard Company
Operating system HP-UX, version: B.11.31, architecture: IA64W
Session & Other
Session Locale en
Time of Failure Fri Aug 29 11:57:24 IST 2008 (Java Time: 1219991244104)
Web Dynpro Code Generation Infos
sap.com/pb
SapDictionaryGenerationCore 7.0013.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:57:42[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates 7.0013.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:57:50[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
SapGenerationFrameworkCore 7.0013.20060719095755.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:44:42[UTC], changelist=411255, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer 7.0013.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:04:26[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon 7.0013.20061002105432.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:45:30[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore 7.0013.20061002105432.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:45:23[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary 7.0013.20060719095619.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:54:53[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro 7.0013.20070703112649.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:00:50[UTC], changelist=454024, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCTemplates 7.0013.20070717142021.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:15:27[UTC], changelist=455669, host=pwdfm101)
SapWebDynproGenerationCore 7.0013.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:04:37[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates 7.0013.20070717142021.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:15:27[UTC], changelist=455669, host=pwdfm101)
sap.com/tcwddispwda
No information available null
sap.com/pb_api
SapDictionaryGenerationCore 7.0013.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:57:42[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates 7.0013.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:57:50[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
SapGenerationFrameworkCore 7.0013.20060719095755.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:44:42[UTC], changelist=411255, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer 7.0013.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:04:26[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon 7.0013.20061002105432.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:45:30[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore 7.0013.20061002105432.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:45:23[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary 7.0013.20060719095619.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:54:53[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro 7.0013.20070703112649.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:00:50[UTC], changelist=454024, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCTemplates 7.0013.20070717142021.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:15:27[UTC], changelist=455669, host=pwdfm101)
SapWebDynproGenerationCore 7.0013.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:04:37[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates 7.0013.20070717142021.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:15:27[UTC], changelist=455669, host=pwdfm101)
sap.com/tcwdcorecomp
No information available null
Detailed Error Information
Detailed Exception Chain
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: ComponentUsage(FPMConfigurationUsage): Active component must exist when getting interface controller. (Hint: Have you forgotten to create it with createComponent()? Should the lifecycle control of the component usage be "createOnDemand"?
at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.ensureActiveComponent(ComponentUsage.java:773)
at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.getInterfaceControllerInternal(ComponentUsage.java:348)
at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.getInterfaceController(ComponentUsage.java:335)
at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdGetFPMConfigurationUsageInterface(InternalFPMComponent.java:245)
at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.changeToExceptionPerspective(FPMComponent.java:861)
at com.sap.pcuigp.xssfpm.java.MessageManager.handleException(MessageManager.java:258)
at com.sap.pcuigp.xssfpm.java.MessageManager.raiseException(MessageManager.java:103)
at com.sap.pcuigp.xssfpm.wd.BackendConnections.connectModelInternal(BackendConnections.java:323)
at com.sap.pcuigp.xssfpm.wd.BackendConnections.initBackend(BackendConnections.java:256)
at com.sap.pcuigp.xssfpm.wd.BackendConnections.connectModel(BackendConnections.java:154)
at com.sap.pcuigp.xssfpm.wd.wdp.InternalBackendConnections.connectModel(InternalBackendConnections.java:237)
at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.connectModel(FPMComponent.java:841)
at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.connectModel(FPMComponent.java:1071)
at com.sap.pcuigp.xssfpm.wd.BackendConnections.init(BackendConnections.java:141)
at com.sap.pcuigp.xssfpm.wd.wdp.InternalBackendConnections.init(InternalBackendConnections.java:233)
at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:182)
at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:748)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:283)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:733)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:668)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)
at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:860)
at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:220)
at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1246)
at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:354)
at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:547)
at com.sap.portal.pb.PageBuilder.wdDoRefresh(PageBuilder.java:591)
at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:822)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java:755)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doPortalDispatch(WindowPhaseModel.java:717)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:136)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:313)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:684)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
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)
Failed to process request. Please contact your system administrator.
Regards,
Shilpa.
Edited by: pasumarthi shilpa on Sep 1, 2008 6:40 AMhi Shilpa,
Please go to transaction SWFVISU and check whether the package name and all is correct or not
coz u'll see thr sometime package is diff.
and most of time u need change package name according to ur pkg.
And
check whether system object and aliases are properly mapped to the user.
Expecting your co-operation,If suggession becomes solution or useful to find the solution.
Thanks
mahendra -
Hi All,
When i click any of ess worksets i am getting following error.
How to resolve the following error ?
500 Internal Server Error
SAP NetWeaver Application Server 7.00/Java AS 7.00
Failed to process request. Please contact your system administrator.
[Hide]
Error Summary
While processing the current request, an exception occured which could not be handled by the application or the framework.
If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
Root Cause
The initial exception that caused the request to fail, was:
com.sap.mw.jco.JCO$Exception: (101) RFC_ERROR_PROGRAM: 'password' missing
at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:457)
at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1015)
at com.sap.mw.jco.JCO$Client.connect(JCO.java:3238)
at com.sap.dictionary.runtime.mdi.DataProvider.<init>(DataProvider.java:91)
at com.sap.dictionary.runtime.mdi.DataProvider.<init>(DataProvider.java:123)
... 74 more
See full exception chain for details.
System Environment
Client
Web Dynpro Client Type HTML Client
User agent Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.0.3705; .NET CLR 1.1.4322; Media Center PC 4.0; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30; InfoPath.1)
Version null
DOM version null
Client Type msie7
Client Type Profile ie6
ActiveX enabled
Cookies enabled
Frames enabled
Java Applets enabled
JavaScript enabled
Tables enabled
VB Script enabled
Server
Web Dynpro Runtime Vendor: SAP, build ID: 7.0011.20070125102926.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:18:32[UTC], changelist=434634, host=pwdfm101), build date: Thu May 03 16:21:20 CDT 2007
J2EE Engine 7.00 patchlevel
Java VM Java HotSpot(TM) Server VM, version:1.4.2_13-b06, vendor: Sun Microsystems Inc.
Operating system Windows 2003, version: 5.2, architecture: x86
Session & Other
Session Locale en_US
Time of Failure Tue Jun 26 05:43:00 CDT 2007 (Java Time: 1182854580625)
Web Dynpro Code Generation Infos
sap.com/pb
SapDictionaryGenerationCore 7.0011.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:02:43[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates 7.0011.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:02:51[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
SapGenerationFrameworkCore 7.0011.20060719095755.0000 (release=645_VAL_REL, buildtime=2007-01-31:19:49:49[UTC], changelist=411255, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer 7.0011.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:08:25[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon 7.0011.20061002105432.0000 (release=645_VAL_REL, buildtime=2007-01-31:19:50:48[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore 7.0011.20061002105432.0000 (release=645_VAL_REL, buildtime=2007-01-31:19:50:27[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary 7.0011.20060719095619.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:00:20[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro 7.0011.20061227101814.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:05:13[UTC], changelist=431317, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCTemplates 7.0011.20070125102926.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:21:35[UTC], changelist=434634, host=pwdfm101)
SapWebDynproGenerationCore 7.0011.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:08:35[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates 7.0011.20070125102926.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:21:35[UTC], changelist=434634, host=pwdfm101)
sap.com/tcwddispwda
No information available null
sap.com/pb_api
SapDictionaryGenerationCore 7.0011.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:02:43[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates 7.0011.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:02:51[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
SapGenerationFrameworkCore 7.0011.20060719095755.0000 (release=645_VAL_REL, buildtime=2007-01-31:19:49:49[UTC], changelist=411255, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer 7.0011.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:08:25[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon 7.0011.20061002105432.0000 (release=645_VAL_REL, buildtime=2007-01-31:19:50:48[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore 7.0011.20061002105432.0000 (release=645_VAL_REL, buildtime=2007-01-31:19:50:27[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary 7.0011.20060719095619.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:00:20[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro 7.0011.20061227101814.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:05:13[UTC], changelist=431317, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCTemplates 7.0011.20070125102926.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:21:35[UTC], changelist=434634, host=pwdfm101)
SapWebDynproGenerationCore 7.0011.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:08:35[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates 7.0011.20070125102926.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:21:35[UTC], changelist=434634, host=pwdfm101)
sap.com/tcwdcorecomp
No information available null
Detailed Error Information
Detailed Exception Chain
com.sap.tc.webdynpro.services.exceptions.TypeNotFoundException: type com.sap.pcuigp.xssfpm.wd.model.types.Ext_Service could not be loaded: com.sap.dictionary.runtime.DdException: failed to create provider: 'password' missing
at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:250)
at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getDataType(DataTypeBroker.java:213)
at com.sap.tc.webdynpro.progmodel.context.DataAttributeInfo.init(DataAttributeInfo.java:318)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initUnmappedAttributes(NodeInfo.java:687)
at com.sap.tc.webdynpro.progmodel.context.DataNodeInfo.doInit(DataNodeInfo.java:238)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:671)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:674)
at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
at com.sap.tc.webdynpro.progmodel.controller.Component.getCustomControllerInternal(Component.java:448)
at com.sap.tc.webdynpro.progmodel.controller.Component.getController(Component.java:377)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.getPublicInterface(DelegatingComponent.java:181)
at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdGetBackendConnectionsController(InternalFPMComponent.java:209)
at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:186)
at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:707)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:269)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:779)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:714)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:261)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:69)
at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:860)
at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:220)
at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1248)
at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:353)
at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:551)
at com.sap.portal.pb.PageBuilder.wdDoInit(PageBuilder.java:190)
at com.sap.portal.pb.wdp.InternalPageBuilder.wdDoInit(InternalPageBuilder.java:150)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:707)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:269)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:759)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:712)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:261)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:160)
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.dictionary.runtime.DdException: failed to create provider: 'password' missing
at com.sap.dictionary.runtime.ProviderFactory.internalGetProvider(ProviderFactory.java:254)
at com.sap.dictionary.runtime.ProviderFactory.getProvider(ProviderFactory.java:146)
at com.sap.dictionary.runtime.DdDictionaryPool.getProvider(DdDictionaryPool.java:97)
at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:79)
at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:48)
at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:149)
at com.sap.dictionary.runtime.DdBroker.getSimpleType(DdBroker.java:170)
at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:242)
... 62 more
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
at com.sap.dictionary.runtime.ProviderFactory.internalGetProvider(ProviderFactory.java:229)
... 69 more
Caused by: com.sap.mw.jco.JCO$Exception: (101) RFC_ERROR_PROGRAM: 'password' missing
at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:457)
at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1015)
at com.sap.mw.jco.JCO$Client.connect(JCO.java:3238)
at com.sap.dictionary.runtime.mdi.DataProvider.<init>(DataProvider.java:91)
at com.sap.dictionary.runtime.mdi.DataProvider.<init>(DataProvider.java:123)
... 74 moreHi,
I think you might have using SICF to test web service.
To test the same you need J2EE instance.
go to transaction
WSADMIN ->administrative settings and enter the j2ee server address (http://server.domain.com:port) and then click on your service and click test.
if you dont have a j2ee instance, you can use some free third party tools to test your WS.
goto this URL to get webservice studio
http://www.gotdotnet.com/Community/UserSamples/Details.aspx?SampleGuid=65a1d4ea-0f7a-41bd-8494-e916ebc4159c
*******please reward points if the information is helpful to you************* -
Hi All,
I have an ESS Portal, Earlier I had it connected to Dev Systema and was working pefectly fine. Now we have tried mapping it to IDES. For this I have created one system for which connection Test are working fine and Made changes in JCO(change in client and Message server only). Basis Guys has done SSO and User creation.
But when we click on ESS it is giving error:
500 Internal Server Error
SAP NetWeaver Application Server 7.00/Java AS 7.00
Failed to process request. Please contact your system administrator.
[Hide]
Error Summary
While processing the current request, an exception occured which could not be handled by the application or the framework.
If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
Root Cause
The initial exception that caused the request to fail, was:
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: ComponentUsage(FPMConfigurationUsage): Active component must exist when getting interface controller. (Hint: Have you forgotten to create it with createComponent()? Should the lifecycle control of the component usage be "createOnDemand"?
at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.ensureActiveComponent(ComponentUsage.java:773)
at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.getInterfaceControllerInternal(ComponentUsage.java:348)
at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.getInterfaceController(ComponentUsage.java:335)
at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdGetFPMConfigurationUsageInterface(InternalFPMComponent.java:245)
at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.changeToExceptionPerspective(FPMComponent.java:862)
... 60 more
Please let me know am I missing something?? where can be the problem?
Thanks for your support....
Regards,
Honey SachdevaThanks for your quick response Arun!!
Arun, We have technical system in SLD which points to IDES system.
For JCO we have made changes in client and m,essage server, for apllication JCO we have Ticket as Used Method and for Metadata we have User/Password as Used method which is same as we have kept it when it was pointing to Dev system.
have created a system for IDES for which Connector properties, ITS and WebAS tests are passed.
Still in dialma, where can be the issue.
Regards,
Honey -
Global employees (MGE) error in ESS
Hi all,
I am in the process of activating management of global employees in ESS. The leave screens & leave balances work fine for employees with 2 PERNR i.e. i get the pop-up box in ESS.
The problem i have is with the address and bank screens. I get the following error in ESS: Global Employee scenario: Please refer to the IMG Employee Self-Service -> General Settings -> Concurrent/Global Employee
I have activated the address and bank services in IMG node "Assign CE/GE Group Definition Settings to ESS Applications" but its not working like Leave request did.Actual message in ESS:
Critical error.
Global Employee scenario: Please refer to the IMG Employee Self-Service -> General Settings -> Concurrent/Global Employee:
com.sap.pcuigp.xssfpm.java.FPMRuntimeException
at com.sap.pcuigp.xssfpm.java.MessageManager.raiseException(MessageManager.java:112)
at com.sap.pcuigp.xssfpm.java.MessageManager.raiseException(MessageManager.java:122)
at com.sap.pcuigp.xssutils.pernr.EmployeeGroupInfo.init(EmployeeGroupInfo.java:140)
at com.sap.pcuigp.xssutils.pernr.wdp.InternalEmployeeGroupInfo.init(InternalEmployeeGroupInfo.java:183)
at com.sap.pcuigp.xssutils.pernr.FcEmployeeServices.initPernr(FcEmployeeServices.java:270)
at com.sap.pcuigp.xssutils.pernr.FcEmployeeServices.onInit(FcEmployeeServices.java:226)
at com.sap.pcuigp.xssutils.pernr.wdp.InternalFcEmployeeServices.onInit(InternalFcEmployeeServices.java:273)
at com.sap.pcuigp.xssutils.pernr.FcEmployeeServicesInterface.onInit(FcEmployeeServicesInterface.java:135)
The switch HCM_ESS_CE is active, and parts of MGE seem to be working because i can do leave requests for Global employees and i get the assignment pop-up box in ESS for this. I have activated the EMPLOYEE_ADDRESS_nn_SERVICE applications in IMG node "Assign CE/GE Group Definition Settings to ESS Applications"
I'm wondering if anyone has got address screen working for Global employees? -
Must all SAP MSS, SAP ESS and SAP PCUI_GP be of the same SP level?
Hello,
in order to fix an error in XSS we need to upgrade SAP PCUI_GP to SP 10. Is it therefore necessary to upgrade also the rest of the components building XSS (SAP MSS and SAP ESS) also to SP 10 or can they stay on SP 9 as they are now? Is there an official SAP document answering my question?
Regards,
Adamadam,
the MSS and ESS should work independently, but both require PCUI_GP as a base-component, so these versions should be equal.
you can try to use different SP-levels, but this is not supported & what's the problem to keep them on the same level?
depending on the changes on each SP-level (e.g. if there are only country-specific changes for countries you don't need or text-corrections, check the notes for the SP-levels) you can risk it...
kr, achim -
Hi all. I trying to install Employee Self Services component in a SAP Enterprise Portal 70... I have installed all other components required for this propouse:
IS-HER CSS
SAP PSS
SAP ASR
SAP PCUI.
Whe i install SAP ESS 600 with the JSPM it show me the following error:
ERROR: Not deployed. Deploy Service returned ERROR:
java.rmi.RemoteException: Cannot deploy application sap.com/essauaddr..
Reason: Clusterwide exception: Failed to deploy application sap.com/essauaddr. 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 sap.com/essauaddr. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?
at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:567)
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:313)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:199)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
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 sap.com/essauaddr. 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:1050)
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)
Thanks in advanceHi Kai... this is the information contained in the jsmp.trc file...
Nov 1, 2007 11:25:51 AM [Info]: com.sap.sdt.cvl.provider.impl.ArchiveComponentsProvider [Thread[main,5,main]]: Reading information from new software component archives
Nov 1, 2007 11:25:51 AM [Info]: com.sap.sdt.cvl.provider.impl.ArchiveComponentsProvider [Thread[main,5,main]]: Processing file
<server>\sapmnt\trans\EPS\in\SAPESS07P_12-20000512.SCA
Nov 1, 2007 11:25:51 AM [Path]: com.sap.sdt.cvl.provider.impl.ArchiveComponentsProvider.readAllComponents [Thread[main,5,main]]: Exiting method
Nov 1, 2007 11:25:51 AM [Info]: com.sap.sdt.cvl.validator.impl.ComponentValidator [Thread[main,5,main]]: Validating own dependencies of component sap.com/SAP_ESS
Nov 1, 2007 11:25:51 AM [Info]: com.sap.sdt.cvl.provider.impl.CVERSComponentsProvider [Thread[main,5,main]]: Reading from system database version for component sap.com/SAP_ESS
Nov 1, 2007 11:25:51 AM [Info]: com.sap.sdt.cvl.validator.impl.ComponentValidator [Thread[main,5,main]]: Own dependency validation of component sap.com/SAP_ESS, version 600.7.12, provider SAP AG - no old existing version found
Nov 1, 2007 11:25:51 AM [Info]: com.sap.sdt.cvl.validator.impl.ComponentValidator [Thread[main,5,main]]: Validating foreign dependencies of component sap.com/SAP_ESS
Nov 1, 2007 11:25:51 AM [Info]: com.sap.sdt.cvl.validator.impl.ComponentValidator [Thread[main,5,main]]: Foreign dependency validation of component sap.com/SAP_ESS - no foreign requirements
Nov 1, 2007 11:34:05 AM [Error]: com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl [Thread[main,5,main]]: Deployment of archive
<server>\sapmnt\trans\EPS\in\SAPESS07P_12-20000512.SCA has been terminated. Aborted: software component 'SAP_ESS'/'sap.com'/'MAIN_ERP05PAT_C'/'1000.600.0.7.12.20070314050106''/'0':
Failed deployment of SDAs:
development component 'ess/au/addr'/'sap.com'/'MAIN_ERP05PAT_C'/'798665'/'0' : aborted
Please, look at error logs above for more information!
Nov 1, 2007 11:34:05 AM [Error]: com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl.deployList(DeploymentManagerImpl.java:433) [Thread[main,5,main]]: Error during deployment. See F:/usr/sap/TD1/DVEBMGS00/SDM/program/log/sdmcl20071101102751.log for details.
Nov 1, 2007 11:34:05 AM [Error]: com.sap.sdt.jspm.deployment.deploy.DeploymentManager [Thread[main,5,main]]: com.sap.sdt.j2ee.tools.deploymentmgr.DeploymentManagerDeploymentException: Error during deployment. See F:/usr/sap/TD1/DVEBMGS00/SDM/program/log/sdmcl20071101102751.log for details.
at com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl.deployList(DeploymentManagerImpl.java:433)
at com.sap.sdt.j2ee.tools.deploymentmgr.AbstractDeploymentManager.deployDeploymentUnits(AbstractDeploymentManager.java:347)
at com.sap.sdt.jspm.deployment.deploy.DeploymentManager.deployDeployableUnits(DeploymentManager.java:1765)
at com.sap.sdt.jspm.deployment.deploy.DeploymentManager.deployQueue(DeploymentManager.java:628)
at com.sap.sdt.jspm.deployment.DeploymentFacade.deployQueue(DeploymentFacade.java:320)
at com.sap.sdt.jspm.gui.deployment.DeployQueueStep.processUI(DeployQueueStep.java:351)
at com.sap.sdt.jspm.gui.deployment.DeploymentProcessController.execute(DeploymentProcessController.java:406)
at com.sap.sdt.jspm.gui.DialogController.execute(DialogController.java:553)
at com.sap.sdt.jspm.phases.PhaseTypeJSPM.execute(PhaseTypeJSPM.java:113)
at com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:738)
at com.sap.sdt.ucp.pce.ctrl.PhaseExecutor.executePhase(PhaseExecutor.java:295)
at com.sap.sdt.ucp.pce.ctrl.PhaseExecutor.execute(PhaseExecutor.java:226)
at com.sap.sdt.ucp.pce.ctrl.ActionExecutor.executeClassRef(ActionExecutor.java:204)
at com.sap.sdt.ucp.pce.ctrl.ActionExecutor.execute(ActionExecutor.java:114)
at com.sap.sdt.ucp.pce.ctrl.ActionListSequentialExecutor.executeAction(ActionListSequentialExecutor.java:400)
at com.sap.sdt.ucp.pce.ctrl.ActionListSequentialExecutor.execute(ActionListSequentialExecutor.java:273)
at com.sap.sdt.ucp.pce.ctrl.ActionListSequentialExecutor.doExecute(ActionListSequentialExecutor.java:229)
at com.sap.sdt.ucp.pce.ctrl.ActionListSequentialExecutor.execute(ActionListSequentialExecutor.java:152)
at com.sap.sdt.ucp.pce.ctrl.ActionExecutor.executeListContainer(ActionExecutor.java:161)
at com.sap.sdt.ucp.pce.ctrl.ActionExecutor.execute(ActionExecutor.java:110)
at com.sap.sdt.ucp.pce.ctrl.ActionListSequentialExecutor.executeAction(ActionListSequentialExecutor.java:400)
at com.sap.sdt.ucp.pce.ctrl.ActionListSequentialExecutor.execute(ActionListSequentialExecutor.java:273)
at com.sap.sdt.ucp.pce.ctrl.ActionListSequentialExecutor.doExecute(ActionListSequentialExecutor.java:229)
at com.sap.sdt.ucp.pce.ctrl.ActionListSequentialExecutor.execute(ActionListSequentialExecutor.java:152)
at com.sap.sdt.ucp.pce.ctrl.ActionExecutor.executeListContainer(ActionExecutor.java:161)
at com.sap.sdt.ucp.pce.ctrl.ActionExecutor.execute(ActionExecutor.java:110)
at com.sap.sdt.ucp.pce.ctrl.ExecutionDirector.executeAction(ExecutionDirector.java:144)
at com.sap.sdt.ucp.admin.ContextExecutor.executePce(ContextExecutor.java:148)
at com.sap.sdt.ucp.admin.ContextExecutor.execute(ContextExecutor.java:85)
at com.sap.sdt.jspm.main.CmdExecutor.runContext(CmdExecutor.java:127)
at com.sap.sdt.jspm.main.CmdExecutor.executeRun(CmdExecutor.java:100)
at com.sap.sdt.jspm.main.CmdExecutor.execute(CmdExecutor.java:82)
at com.sap.sdt.tools.main.MainProgram.execute(MainProgram.java:477)
at com.sap.sdt.jspm.main.Jspm.main(Jspm.java:190)
Maybe you are looking for
-
Hello all, We have created an variant for the warehouse activity monitor and would like tok know the t-code to view the variant that has been created. pl. advise. Thanks, Maxx
-
Is it possible to load an instructional DVD with several separate chapters onto my iMac and then somehow access the different chapters as needed remotely on my iPad?
-
Can BI 4.0 be installed on Windows enterprise instead of Windows server?
Can I install BI 4.0 FP3 on my laptop which runs Windows 7 enterprise instead of on a windows server? The prerequisite check gives only "yellow warning" fo rthe windows server version and shows as "optional". Does that mean it is OK to install on a
-
Dual homed bgp route perference help
Good Morning, sir I have a question regarding bgp route preference. We have multi-homed BGP on remote site. Let's call this site , site_a has verizon and at&t MPLS connection using bgp. Currently, at&t route is preferred using as path prepend meth
-
Help requested to transfer iTunes to a new CPU
I have an extensive iTunes library on my current windows CPU which I would like to transfer to a MS Surface Pro so I can give my old CPU to my mother. Help. This is not an intuitive process.