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
Ashish
Hello 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
Similar Messages
-
Time out error on deploying to SAP-J2EE engine.
I got a problem while deploying to SAP-J2EE engine using ant. It takes a lot of time and then throws a time out error.
The problem is with the web.xml file pointing to a DTD in the internet, I have pasted some part of the web.xml below,
<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE web-app
PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.2//EN"
"http://java.sun.com/j2ee/dtds/web-app_2_2.dtd">
<web-app>
<display-name>MyPay</display-name>
<description>MyPay</description>
Once I write down the DTD description in the web.xml itself, it works fine.
I have pasted the error trace below,
j2eedeploy:
[echo] Deploying to Local environment...
[echo] C:\Java\Projects/MyPay/dist/MyPay.ear
BUILD FAILED
C:\Java\Projects\MyPay\build.xml:445: java.lang.RuntimeException: ERROR: ID90507: Error occured during getting EARDescriptor : Failed to load resource from the context classloader of the current thread! Loading from classloader was caused by: java.net.ConnectException: Connection timed out: connect
Exception is :
java.io.IOException: Failed to load resource from the context classloader of the current thread! Loading from classloader was caused by: java.net.ConnectException: Connection timed out: connect
at com.sap.engine.lib.xml.parser.URLLoaderBase.resolveEntity(URLLoaderBase.java:148)
at com.sap.engine.lib.xml.parser.XMLParser.scanDTD(XMLParser.java:1271)
at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2795)
at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2830)
at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:229)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261)
at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280)
at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342)
at com.sap.engine.lib.xml.parser.DOMParser.parse(DOMParser.java:101)
at com.sap.engine.lib.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:127)
at com.inqmy.lib.xml.StandardDOMParser.parse(StandardDOMParser.java:127)
at com.inqmy.lib.xml.StandardDOMParser.parse(StandardDOMParser.java:120)
at com.inqmy.services.servlets_jsp.descriptor.jar.WebWar.getWebDescriptor(WebWar.java:98)
at com.inqmy.deploy.tool.deployer.ExtendedEarReader.loadDescriptorFromFile(ExtendedEarReader.java:175)
at com.inqmy.deploy.tool.deployer.ExtendedEarReader.getFullEarDescriptor(ExtendedEarReader.java:104)
at com.inqmy.deploy.manager.DeployManagerImpl.setEar(DeployManagerImpl.java:355)
at com.inqmy.deploy.manager.DeployManagerImpl.setEar(DeployManagerImpl.java:325)
at com.pg.sap.deploy620.SAPDeploy620Manager.process(SAPDeploy620Manager.java:84)
at com.pg.ant.tasks.j2ee620.J2ee620EngineDeployTask.execute(J2ee620EngineDeployTask.java:40)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
at org.apache.tools.ant.Task.perform(Task.java:364)
at org.apache.tools.ant.Target.execute(Target.java:341)
at org.apache.tools.ant.Target.performTasks(Target.java:369)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40)
at org.eclipse.ant.internal.ui.antsupport.EclipseDefaultExecutor.executeTargets(EclipseDefaultExecutor.java:32)
at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
at org.eclipse.ant.internal.ui.antsupport.InternalAntRunner.run(InternalAntRunner.java:423)
at org.eclipse.ant.internal.ui.antsupport.InternalAntRunner.main(InternalAntRunner.java:137)Thanks for your reply Kalyan,
The problem seems to be with my system, because I had run the same ant script in another system and it deployed successfully.
The problem does not seem to be with the dtd, whereas it seems that the SAP-J2EE engine is not able to open the link to the dtd giving a time out error.
Is it possible to switch off the validation process of the SAP-J2EE engine of an xml with the dtd? -
Error in deployment of ESS package
Hi,
We are importing the business package for ESS.
During the import of PCUI_GP16.sca; ESS16.sca components(version
selected based on the SAP note 761266) through SDM we are getting the
error,due to which deployment fails. Error log file is pasted below.
Infrasture details are as below:
Backend: SAP E.C.C. 5.0 SP16 640 kernel based
Portal : EP7.0 700 kernel based
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7185 - 630]/>
<!NAME[/usr/sap/BMD/DVEBMGS01/SDM/program/log/sdmlog20071017.log]/>
<!PATTERN[sdmlog20071017.log]/>
<!FORMATTER[com.sap.tc.logging.TraceFormatter(%24d %s: %m)]/>
<!ENCODING[UTF8]/>
<!LOGHEADER[END]/>
Oct 17, 2007 3:35:10 PM Info:
Oct 17, 2007 3:35:10 PM Info: ===============================================
Oct 17, 2007 3:35:10 PM Info: = Starting to execute command 'remotegui' =
Oct 17, 2007 3:35:10 PM Info: ===============================================
Oct 17, 2007 3:35:18 PM Info: SDM started successfully.
Oct 17, 2007 3:38:46 PM Info:
Oct 17, 2007 3:38:46 PM Info: ============================================
Oct 17, 2007 3:38:46 PM Info: = Starting to execute command 'server' =
Oct 17, 2007 3:38:46 PM Info: ============================================
Oct 17, 2007 3:38:46 PM Info: Starting SDM - Software Deployment Manager...
Oct 17, 2007 3:38:47 PM Info: tc/SL/SDM/SDM/sap.com/SAP AG/7.0012.20070328121310.0000
Oct 17, 2007 3:38:52 PM Info: SDM operation mode successfully set to: Integrated
Oct 17, 2007 3:38:53 PM Info: JStartupFramework is active
Oct 17, 2007 3:38:53 PM Info: Operation mode of SDM in JStartupFramework is "Integrated".
Oct 17, 2007 3:38:53 PM Info: Check if Server is running already.
Oct 17, 2007 3:38:53 PM Info: OK server is not running. Enable SDM Process in JStartupFramework.
Oct 17, 2007 3:38:53 PM Info: enabling SDM Process with JStartupFramework
Oct 17, 2007 3:38:53 PM Info: enabled SDM Process with JStartupFramework
Oct 17, 2007 3:38:53 PM Info: Successfully enabled SDM Process in JStartupFramework.
Oct 17, 2007 3:38:57 PM Info:
Oct 17, 2007 3:38:57 PM Info: ============================================
Oct 17, 2007 3:38:57 PM Info: = Starting to execute command 'server' =
Oct 17, 2007 3:38:57 PM Info: ============================================
Oct 17, 2007 3:38:57 PM Info: Starting SDM - Software Deployment Manager...
Oct 17, 2007 3:38:57 PM Info: tc/SL/SDM/SDM/sap.com/SAP AG/7.0012.20070328121310.0000
Oct 17, 2007 3:39:01 PM Info: SDM operation mode successfully set to: Integrated
Oct 17, 2007 3:39:02 PM Info: JStartupFramework is requesting to start the SDM Server.
Oct 17, 2007 3:39:02 PM Info: Start the SDM Server integrated in the JStartupFramework.
Oct 17, 2007 3:39:02 PM Info: Initializing Network Manager (50117)
Oct 17, 2007 3:39:02 PM Info: Starting SDM Server listening on port 50118
Oct 17, 2007 3:39:02 PM Info: SDM started successfully.
Oct 17, 2007 3:39:03 PM Info: Opened client connection to loopback (IP address loopback/127.0.0.1, remote port 50633)
Oct 17, 2007 3:39:03 PM Info: SDM started successfully.
Oct 17, 2007 3:39:03 PM Info: Close client connection to loopback/127.0.0.1, remote port 50633
Oct 17, 2007 3:43:00 PM Info:
Oct 17, 2007 3:43:00 PM Info: ===============================================
Oct 17, 2007 3:43:00 PM Info: = Starting to execute command 'remotegui' =
Oct 17, 2007 3:43:00 PM Info: ===============================================
Oct 17, 2007 3:43:03 PM Info: SDM started successfully.
Oct 17, 2007 3:43:29 PM Info: Opened client connection to az18u188 (IP address az18u188/10.196.160.28, remote port 50805)
Oct 17, 2007 3:43:30 PM Info: Request for Logon as admin accepted
Oct 17, 2007 3:44:56 PM Info: Loading archive '/usr/sap/trans/EPS/in/ESS16_0-10002965.SCA'
Oct 17, 2007 3:45:25 PM Info: Loading archive '/usr/sap/trans/EPS/in/ESS16P_1-10002965.SCA'
Oct 17, 2007 3:46:05 PM Info: Actions per selected component:
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/de/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212790'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/no/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212889'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/cn/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212751'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/es/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212845'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/tra/tre'/'sap.com'/'MAIN_xss04VAL_C'/'1212869'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/wtcor'/'sap.com'/'MAIN_xss04VAL_C'/'1212723'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/no/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212788'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/jp/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212760'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/rem'/'sap.com'/'MAIN_xss04VAL_C'/'1212734'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/ph/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212849'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/tw/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212878'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/th/pid'/'sap.com'/'MAIN_xss04VAL_C'/'1212837'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/fi/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212851'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/ch/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212830'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/kr/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212873'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/org'/'sap.com'/'MAIN_xss04VAL_C'/'1212719'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/jp/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212757'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/ph/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212907'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/fi/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212854'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/ph/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212850'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/ph/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212906'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/tw/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212748'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/au'/'sap.com'/'MAIN_xss04VAL_C'/'1212807'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/au/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212809'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/nz/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212823'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/de/dcomp'/'sap.com'/'MAIN_xss04VAL_C'/'1212791'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/es/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212843'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/se/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212772'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/jp/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212759'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/th/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212902'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/za/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212893'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/se/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212773'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/no/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212789'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/be/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212839'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/za/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212800'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/br/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212766'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/dk/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212826'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/au/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212895'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/kr/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212786'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/no/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212890'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/fr/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212754'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/cn/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212753'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/ve/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212816'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/ar/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212740'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/pt/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212745'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/ar/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212742'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/es/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212844'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/id/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212819'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/ie/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212875'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/id/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212821'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/se/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212886'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/us'/'sap.com'/'MAIN_xss04VAL_C'/'1212767'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/za/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212801'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/sg'/'sap.com'/'MAIN_xss04VAL_C'/'1212802'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/ch/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212829'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/skl'/'sap.com'/'MAIN_xss04VAL_C'/'1212720'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/cat'/'sap.com'/'MAIN_xss04VAL_C'/'1212718'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/mx/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212896'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/pt/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212747'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/br/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212765'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/fr/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212755'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/tra'/'sap.com'/'MAIN_xss04VAL_C'/'1212716'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/mx/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212813'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/pt/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212746'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/ar/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212874'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/nl/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212882'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/at/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212887'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/us/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212768'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected software component 'SAP_ESS'/'sap.com'/'MAIN_xss04VAL_C'/'1000.100.0.16.0.20070410060436''/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/au/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212808'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/ca/empeq'/'sap.com'/'MAIN_xss04VAL_C'/'1212778'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/th/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212903'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/sg/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212803'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/hk/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212796'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/dk/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212828'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/th/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212838'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/ca/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212779'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/au/tax'/'sap.com'/'MAIN_xss04VAL_C'/'1212811'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/nz/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212898'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/nz/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212825'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/cn/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212752'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/it/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212846'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/dk/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212899'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/hk/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212891'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/sg/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212894'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/ve/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212817'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/dk/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212827'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/my/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212835'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/ar/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212741'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/gb/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212783'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/fi/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212853'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/it/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212905'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/my/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212901'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/rep'/'sap.com'/'MAIN_xss04VAL_C'/'1212714'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/gb/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212782'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/th/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212836'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/gb/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212784'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/be/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212842'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/tra/trp'/'sap.com'/'MAIN_xss04VAL_C'/'1212871'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/wiw'/'sap.com'/'MAIN_xss04VAL_C'/'1212722'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/fr/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212756'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/nz/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212824'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/br/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212764'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/ca/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212888'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/in/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212857'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/za/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212892'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/id/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212897'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/sg/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212804'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/nl/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212762'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/xx'/'sap.com'/'MAIN_xss04VAL_C'/'1212795'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/id/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212820'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/nl/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212761'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/fr/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212881'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/at/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212776'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/kr/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212787'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/tim'/'sap.com'/'MAIN_xss04VAL_C'/'1212735'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/jp/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212758'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/tw/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212879'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/ca/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212777'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/de/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212793'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/sg/perid'/'sap.com'/'MAIN_xss04VAL_C'/'1212806'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/ve/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212818'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/au/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212810'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/at/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212774'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/br/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212883'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/com'/'sap.com'/'MAIN_xss04VAL_C'/'1212736'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/per'/'sap.com'/'MAIN_xss04VAL_C'/'1212721'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/de'/'sap.com'/'MAIN_xss04VAL_C'/'1212737'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/us/w4'/'sap.com'/'MAIN_xss04VAL_C'/'1212771'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/in/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212858'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/cn/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212880'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/my/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212834'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/grt/srv'/'sap.com'/'MAIN_xss04VAL_C'/'1212738'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/sg/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212805'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/tra/trr'/'sap.com'/'MAIN_xss04VAL_C'/'1212715'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/ca/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212780'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/us/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212769'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/hk/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212799'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/id/pid'/'sap.com'/'MAIN_xss04VAL_C'/'1212822'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/it/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212848'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/in/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212855'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/ie/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212876'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/at/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212775'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/cod'/'sap.com'/'MAIN_xss04VAL_C'/'1212717'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/de/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212792'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/tra/trp/trt'/'sap.com'/'MAIN_xss04VAL_C'/'1212872'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/pt/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212877'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/lea'/'sap.com'/'MAIN_xss04VAL_C'/'1212727'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/gb/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212781'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/my/pid'/'sap.com'/'MAIN_xss04VAL_C'/'1212833'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/se/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212885'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/ch/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212900'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/us/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212770'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/de/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212794'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/it/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212847'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/ie/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212744'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/tw/pid'/'sap.com'/'MAIN_xss04VAL_C'/'1212750'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/hk/perid'/'sap.com'/'MAIN_xss04VAL_C'/'1212798'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/in/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212856'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/be/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212841'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/mx/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212812'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/fi/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212852'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/nl/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212763'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/ve/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212815'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/kr/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212785'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/be/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212840'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/mx/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212814'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/tra/tre/trs'/'sap.com'/'MAIN_xss04VAL_C'/'1212908'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/tw/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212749'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/hk/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212797'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/au/rep'/'sap.com'/'MAIN_xss04VAL_C'/'1212739'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/ch/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212831'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/tra/tri'/'sap.com'/'MAIN_xss04VAL_C'/'1212870'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/my/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212832'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/ie/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212743'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/ben'/'sap.com'/'MAIN_xss04VAL_C'/'1212713'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/us/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212884'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/es/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212904'/'0' will be deployed.
Oct 17, 2007 3:46:26 PM Info: Saved current Engine state.
Oct 17, 2007 3:46:29 PM Info: Starting: Initial deployment: Selected development component 'ess/ben'/'sap.com'/'MAIN_xss04VAL_C'/'1212713'/'0' will be deployed.
Oct 17, 2007 3:46:29 PM Info: SDA to be deployed: /usr/sap/BMD/DVEBMGS01/SDM/root/origin/sap.com/ess/ben/MAIN_xss04VAL_C/0/1212713/ess~ben.sda
Oct 17, 2007 3:46:29 PM Info: Software type of SDA: J2EE
Oct 17, 2007 3:46:30 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Oct 17, 2007 3:48:00 PM Info: Begin of log messages of the target system:
07/10/17 15:46:31 - ***********************************************************
07/10/17 15:46:45 - Start updating EAR file...
07/10/17 15:46:45 - start-up mode is lazy
07/10/17 15:46:45 - EAR file updated successfully for 483ms.
07/10/17 15:46:45 - Start deploying ...
07/10/17 15:47:23 - EAR file uploaded to server for 34995ms.
07/10/17 15:47:55 - Successfully deployed. Deployment took 31943ms.
07/10/17 15:47:55 - Application : sap.com/ess~ben
07/10/17 15:47:55 -
07/10/17 15:47:55 - sap.com/ess~ben - WEBDYNPRO
07/10/17 15:47:55 - ***********************************************************
Oct 17, 2007 3:48:00 PM Info: End of log messages of the target system.
Oct 17, 2007 3:48:00 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Oct 17, 2007 3:48:00 PM Info: Finished successfully: development component 'ess/ben'/'sap.com'/'MAIN_xss04VAL_C'/'1212713'/'0', grouped by software component 'SAP_ESS'/'sap.com'/'MAIN_xss04VAL_C'/'1000.100.0.16.0.20070410060436''/'0'
Oct 17, 2007 3:48:00 PM Info: Starting to save the repository
Oct 17, 2007 3:48:02 PM Info: Finished saving the repository
Oct 17, 2007 3:48:09 PM Info: Starting: Initial deployment: Selected development component 'ess/cat'/'sap.com'/'MAIN_xss04VAL_C'/'1212718'/'0' will be deployed.
Oct 17, 2007 3:48:09 PM Info: SDA to be deployed: /usr/sap/BMD/DVEBMGS01/SDM/root/origin/sap.com/ess/cat/MAIN_xss04VAL_C/0/1212718/ess~cat.sda
Oct 17, 2007 3:48:09 PM Info: Software type of SDA: J2EE
Oct 17, 2007 3:48:09 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Oct 17, 2007 3:48:38 PM Info: Begin of log messages of the target system:
07/10/17 15:48:09 - ***********************************************************
07/10/17 15:48:11 - Start updating EAR file...
07/10/17 15:48:11 - start-up mode is lazy
07/10/17 15:48:11 - EAR file updated successfully for 287ms.
07/10/17 15:48:11 - Start deploying ...
07/10/17 15:48:26 - EAR file uploaded to server for 11797ms.
07/10/17 15:48:33 - Successfully deployed. Deployment took 6856ms.
07/10/17 15:48:33 - Application : sap.com/ess~cat
07/10/17 15:48:33 -
07/10/17 15:48:33 - sap.com/ess~cat - WEBDYNPRO
07/10/17 15:48:33 - ***********************************************************
Oct 17, 2007 3:48:38 PM Info: End of log messages of the target system.
Oct 17, 2007 3:48:38 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Oct 17, 2007 3:48:38 PM Info: Finished successfully: development component 'ess/cat'/'sap.com'/'MAIN_xss04VAL_C'/'1212718'/'0', grouped by software component 'SAP_ESS'/'sap.com'/'MAIN_xss04VAL_C'/'1000.100.0.16.0.20070410060436''/'0'
Oct 17, 2007 3:48:38 PM Info: Starting to save the repository
Oct 17, 2007 3:48:39 PM Info: Finished saving the repository
Oct 17, 2007 3:48:47 PM Info: Starting: Initial deployment: Selected development component 'ess/cod'/'sap.com'/'MAIN_xss04VAL_C'/'1212717'/'0' will be deployed.
Oct 17, 2007 3:48:47 PM Info: SDA to be deployed: /usr/sap/BMD/DVEBMGS01/SDM/root/origin/sap.com/ess/cod/MAIN_xss04VAL_C/0/1212717/ess~cod.sda
Oct 17, 2007 3:48:47 PM Info: Software type of SDA: J2EE
Oct 17, 2007 3:48:47 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Oct 17, 2007 3:49:02 PM Info: Begin of log messages of the target system:
07/10/17 15:48:47 - ***********************************************************
07/10/17 15:48:49 - Start updating EAR file...
07/10/17 15:48:49 - start-up mode is lazy
07/10/17 15:48:49 - EAR file updated successfully for 159ms.
07/10/17 15:48:49 - Start deploying ...
07/10/17 15:48:56 - EAR file uploaded to server for 5159ms.
07/10/17 15:49:00 - Successfully deployed. Deployment took 3408ms.
07/10/17 15:49:00 - Application : sap.com/ess~cod
07/10/17 15:49:00 -
07/10/17 15:49:00 - sap.com/ess~cod - WEBDYNPRO
07/10/17 15:49:00 - ***********************************************************
Oct 17, 2007 3:49:02 PM Info: End of log messages of the target system.
Oct 17, 2007 3:49:02 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Oct 17, 2007 3:49:02 PM Info: Finished successfully: development component 'ess/cod'/'sap.com'/'MAIN_xss04VAL_C'/'1212717'/'0', grouped by software component 'SAP_ESS'/'sap.com'/'MAIN_xss04VAL_C'/'1000.100.0.16.0.20070410060436''/'0'
Oct 17, 2007 3:49:02 PM Info: Starting to save the repository
Oct 17, 2007 3:49:03 PM Info: Finished saving the repository
Oct 17, 2007 3:49:10 PM Info: Starting: Initial deployment: Selected development component 'ess/fi/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212852'/'0' will be deployed.
Oct 17, 2007 3:49:10 PM Info: SDA to be deployed: /usr/sap/BMD/DVEBMGS01/SDM/root/origin/sap.com/ess/fi/addr/MAIN_xss04VAL_C/0/1212852/essfiaddr.sda
Oct 17, 2007 3:49:10 PM Info: Software type of SDA: J2EE
Oct 17, 2007 3:49:10 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Oct 17, 2007 3:49:32 PM Info: Begin of log messages of the target system:
07/10/17 15:49:10 - ***********************************************************
07/10/17 15:49:12 - Start updating EAR file...
07/10/17 15:49:12 - start-up mode is lazy
07/10/17 15:49:13 - EAR file updated successfully for 101ms.
07/10/17 15:49:13 - Start deploying ...
07/10/17 15:49:19 - EAR file uploaded to server for 3943ms.
07/10/17 15:49:23 - Successfully deployed. Deployment took 4561ms.
07/10/17 15:49:23 - Application : sap.com/essfiaddr
07/10/17 15:49:23 -
07/10/17 15:49:23 - sap.com/essfiaddr - WEBDYNPRO
07/10/17 15:49:23 - ***********************************************************
Oct 17, 2007 3:49:32 PM Info: End of log messages of the target system.
Oct 17, 2007 3:49:32 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Oct 17, 2007 3:49:32 PM Warning: Finished with warnings: development component 'ess/fi/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212852'/'0', grouped by software component 'SAP_ESS'/'sap.com'/'MAIN_xss04VAL_C'/'1000.100.0.16.0.20070410060436''/'0':
Caught exception during application startup from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Error occurred while starting application sap.com/ess/fi/addr and wait.
Reason: Clusterwide exception: server ID 19733050:com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to prepare application ''sap.com/essfiaddr'' for startup. Reason=
Clusterwide exception: Failed to start application ''sap.com/essfiaddr'': The referenced application ''sap.com/ess~per'' can''t be started. Check the causing exception for details. Hint: Is the referenced application deployed correctly on the server?
at com.sap.engine.services.webdynpro.WebDynproContainer.prepareStart(WebDynproContainer.java:1519)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:171)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:301)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:342)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:126)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:245)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4707)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4612)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4585)
at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1163)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java: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(AccessController.java:215)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Oct 17, 2007 3:49:33 PM Info: Starting to save the repository
Oct 17, 2007 3:49:34 PM Info: Finished saving the repository
Oct 17, 2007 3:49:41 PM Info: Starting: Initial deployment: Selected development component 'ess/fi/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212853'/'0' will be deployed.
Oct 17, 2007 3:49:41 PM Info: SDA to be deployed: /usr/sap/BMD/DVEBMGS01/SDM/root/origin/sap.com/ess/fi/bank/MAIN_xss04VAL_C/0/1212853/essfibank.sda
Oct 17, 2007 3:49:41 PM Info: Software type of SDA: J2EE
Oct 17, 2007 3:49:41 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Oct 17, 2007 3:50:00 PM Info: Begin of log messages of the target system:
07/10/17 15:49:41 - ***********************************************************
07/10/17 15:49:44 - Start updating EAR file...
07/10/17 15:49:44 - start-up mode is lazy
07/10/17 15:49:44 - EAR file updated successfully for 92ms.
07/10/17 15:49:44 - Start deploying ...
07/10/17 15:49:51 - EAR file uploaded to server for 4462ms.
07/10/17 15:49:55 - Successfully deployed. Deployment took 4569ms.
07/10/17 15:49:55 - Application : sap.com/essfibank
07/10/17 15:49:55 -
07/10/17 15:49:55 - sap.com/essfibank - WEBDYNPRO
07/10/17 15:49:55 - ***********************************************************
Oct 17, 2007 3:50:00 PM Info: End of log messages of the target system.
Oct 17, 2007 3:50:00 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Oct 17, 2007 3:50:00 PM Warning: Finished with warnings: development component 'ess/fi/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212853'/'0', grouped by software component 'SAP_ESS'/'sap.com'/'MAIN_xss04VAL_C'/'1000.100.0.16.0.20070410060436''/'0':
Caught exception during application startup from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Error occurred while starting application sap.com/ess/fi/bank and wait.
Reason: Clusterwide exception: server ID 19733050:com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to prepare application ''sap.com/essfibank'' for startup. Reason=
Clusterwide exception: Failed to start application ''sap.com/essfibank'': The referenced application ''sap.com/ess~per'' can''t be started. Check the causing exception for details. Hint: Is the referenced application deployed correctly on the server?
at com.sap.engine.services.webdynpro.WebDynproContainer.prepareStart(WebDynproContainer.java:1519)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:171)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:301)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:342)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:126)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:245)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4707)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4612)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4585)
at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1163)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java: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(AccessController.java:215)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Oct 17, 2007 3:50:00 PM Info: Starting to save the repository
Oct 17, 2007 3:50:02 PM Info: Finished saving the repository
Oct 17, 2007 3:50:10 PM Info: Starting: Initial deployment: Selected development component 'ess/fi/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212851'/'0' will be deployed.
Oct 17, 2007 3:50:10 PM Info: SDA to be deployed: /usr/sap/BMD/DVEBMGS01/SDM/root/origin/sap.com/ess/fi/fam/MAIN_xss04VAL_C/0/1212851/essfifam.sda
Oct 17, 2007 3:50:10 PM Info: Software type of SDA: J2EE
Oct 17, 2007 3:50:10 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Oct 17, 2007 3:50:29 PM Info: Begin of log messages of the target system:
07/10/17 15:50:10 - ***********************************************************
07/10/17 15:50:12 - Start updating EAR file...
07/10/17 15:50:12 - start-up mode is lazy
07/10/17 15:50:12 - EAR file updated successfully for 103ms.
07/10/17 15:50:12 - Start deploying ...
07/10/17 15:50:19 - EAR file uploaded to server for 4423ms.
07/10/17 15:50:24 - Successfully deployed. Deployment took 4678ms.
07/10/17 15:50:24 - Application : sap.com/essfifam
07/10/17 15:50:24 -
07/10/17 15:50:24 - sap.com/essfifam - WEBDYNPRO
07/10/17 15:50:24 - ***********************************************************
Oct 17, 2007 3:50:29 PM Info: End of log messages of the target system.
Oct 17, 2007 3:50:29 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Oct 17, 2007 3:50:29 PM Warning: Finished with warnings: development component 'ess/fi/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212851'/'0', grouped by software component 'SAP_ESS'/'sap.com'/'MAIN_xss04VAL_C'/'1000.100.0.16.0.20070410060436''/'0':
Caught exception during application startup from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Error occurred while starting application sap.com/ess/fi/fam and wait.
Reason: Clusterwide exception: server ID 19733050:com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to prepare application ''sap.com/essfifam'' for startup. Reason=
Clusterwide exception: Failed to start application ''sap.com/essfifam'': The referenced application ''sap.com/ess~per'' can''t be started. Check the causing exception for details. Hint: Is the referenced application deployed correctly on the server?
at com.sap.engine.services.webdynpro.WebDynproContainer.prepareStart(WebDynproContainer.java:1519)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:171)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:301)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:342)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:126)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:245)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4707)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4612)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4585)
at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1163)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java: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(AccessController.java:215)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Oct 17, 2007 3:50:29 PM Info: Starting to save the repository
Oct 17, 2007 3:50:30 PM Info: Finished saving the repository
Oct 17, 2007 3:50:39 PM Info: Starting: Initial deployment: Selected development component 'ess/fi/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212854'/'0' will be deployed.
Oct 17, 2007 3:50:39 PM Info: SDA to be deployed: /usr/sap/BMD/DVEBMGS01/SDM/root/origin/sap.com/ess/fi/pdata/MAIN_xss04VAL_C/0/1212854/essfipdata.sda
Oct 17, 2007 3:50:39 PM Info: Software type of SDA: J2EE
Oct 17, 2007 3:50:39 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Oct 17, 2007 3:50:56 PM Info: Begin of log messages of the target system:
07/10/17 15:50:39 - ***********************************************************
07/10/17 15:50:41 - Start updating EAR file...
07/10/17 15:50:41 - start-up mode is lazy
07/10/17 15:50:41 - EAR file updated successfully for 118ms.
07/10/17 15:50:41 - Start deploying ...
07/10/17 15:50:47 - EAR file uploaded to server for 3980ms.
07/10/17 15:50:52 - Successfully deployed. Deployment took 4287ms.
07/10/17 15:50:52 - Application : sap.com/essfipdata
07/10/17 15:50:52 -
07/10/17 15:50:52 - sap.com/essfipdata - WEBDYNPRO
07/10/17 15:50:52 - ***********************************************************
Oct 17, 2007 3:50:56 PM Info: End of log messages of the target system.
Oct 17, 2007 3:50:56 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Oct 17, 2007 3:50:56 PM Warning: Finished with warnings: development component 'ess/fi/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212854'/'0', grouped by software component 'SAP_ESS'/'sap.com'/'MAIN_xss04VAL_C'/'1000.100.0.16.0.20070410060436''/'0':
Caught exception during application startup from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Error occurred while starting application sap.com/ess/fi/pdata and wait.
Reason: Clusterwide exception: server ID 19733050:com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to prepare application ''sap.com/essfipdata'' for startup. Reason=
Clusterwide exception: Failed to start application ''sap.com/essfipdata'': The referenced application ''sap.com/ess~per'' can''t be started. Check the causing exception for details. Hint: Is the referenced application deployed correctly on the server?
at com.sap.engine.services.webdynpro.WebDynproContainer.prepareStart(WebDynproContainer.java:1519)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:171)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:301)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:342)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:126)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:245)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4707)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4612)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4585)
at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1163)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java: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(AccessController.java:215)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Oct 17, 2007 3:50:56 PM Info: Starting to save the repository
Oct 17, 2007 3:50:57 PM Info: Finished saving the repository
Oct 17, 2007 3:51:05 PM Info: Starting: Initial deployment: Selected development component 'ess/in/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212857'/'0' will be deployed.
Oct 17, 2007 3:51:05 PM Info: SDA to be deployed: /usr/sap/BMD/DVEBMGS01/SDM/root/origin/sap.com/ess/in/addr/MAIN_xss04VAL_C/0/1212857/essinaddr.sda
Oct 17, 2007 3:51:05 PM Info: Software type of SDA: J2EE
Oct 17, 2007 3:51:05 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Oct 17, 2007 3:51:29 PM Info: Begin of log messages of the target system:
07/10/17 15:51:05 - ***********************************************************
07/10/17 15:51:07 - Start updating EAR file...
07/10/17 15:51:07 - start-up mode is lazy
07/10/17 15:51:07 - EAR file updated successfully for 92ms.
07/10/17 15:51:07 - Start deploying ...
07/10/17 15:51:18 - EAR file uploaded to server for 9799ms.
07/10/17 15:51:23 - Successfully deployed. Deployment took 4606ms.
07/10/17 15:51:23 - Application : sap.com/essinaddr
07/10/17 15:51:23 -
07/10/17 15:51:23 - sap.com/essinaddr - WEBDYNPRO
07/10/17 15:51:23 - ***********************************************************
Oct 17, 2007 3:51:29 PM Info: End of log messages of the target system.
Oct 17, 2007 3:51:29 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Oct 17, 2007 3:51:29 PM Warning: Finished with warnings: development component 'ess/in/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212857'/'0', grouped by software component 'SAP_ESS'/'sap.com'/'MAIN_xss04VAL_C'/'1000.100.0.16.0.20070410060436''/'0':
Caught exception during application startup from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Error occurred while starting application sap.com/ess/in/addr and wait.
Reason: Clusterwide exception: server ID 19733050:com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to prepare application ''sap.com/essinaddr'' for startup. Reason=
Clusterwide exception: Failed to start application ''sap.com/essinaddr'': The referenced application ''sap.com/ess~per'' can''t be started. Check the causing exception for details. Hint: Is the referenced application deployed correctly on the server?
at com.sap.engine.services.webdynpro.WebDynproContainer.prepareStart(WebDynproContainer.java:1519)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:171)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:301)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:342)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:126)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:245)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4707)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4612)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4585)
at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1163)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java: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(AccessController.java:215)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:1I thinkw aht is happening some of the components which are in error, are referencing some components which are not yet deployed.
Please try and deploy the components which are in error again.
Regards
Jayesh -
Error while deploying ESS through SDM
Hi,
While deploying ESS through SDM i got following error for one of the files:
Starting Deployment of tc/sl.ut.content.erp.xss
Aborted: development component 'tc/sl.ut.content.erp.xss'/'sap.com'/'MAIN_ERP53PAT_C'/'2433758'/'0', grouped by software component 'SAP_ESS'/'sap.com'/'MAIN_ERP53PAT_C'/'1000.603.0.0.1.20080207103154''/'0':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Error occurred while deploying ear file ./temp/deploy/work/deploying/tc_sl.ut.content.erp.xss.ear. Reason: None of the available containers recognized the components of application sap.com/tc~sl.ut.content.erp.xss; it is not possible to make deploy.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of tc/sl.ut.content.erp.xss finished with Error (Duration 13250 ms)
Can anyone please tell what exactly the issue could be because of which that particular file is not recognized.
Thanks & regards,
AnupreetHi,
Its always advisable to use JSPM for the installation. Copy all the installable files in the JSPM temp folder and the instalation will be taken care and you don't have to worry about dependencies.
If you are using SDM make sure that you deploy PCUI_GP component FIRST, then the other components in any order.
Regards
Deb -
SAP Netweaver 04 SP16 deployed with Xalan 2.60 or Xalan 2.70
SAP Netweaver 04 SP16 deployed with Xalan 2.60 or Xalan 2.70
Have you tried to port and run (Sneak Preview) SAPNetWeaver java 04 SP16 or 04S SP7 with a later version on Xalan version 2.60 or Xalan version 2.70 along with jdk 1.4.2_(8 or greater)?
What specifically is failing? What patches or work around have you used to overcome compatibility issues with Xalan?
When we run Sneak Preview SAPNetWeaver java 04 SP16 SP7 with a version on Xalan version 2.60 or Xalan version 2.70 along with jdk 1.4.2_11, We get error 503 Service Unavailable, Application cannot be started
Details: com.sap.engine.services.deploy.container.ExceptionInfo: Error while parsing file data-source-aliases.xml.Hi
SAP does not allow usage of any other XML parsers with SAP web AS.
please have a look at this link
http://help.sap.com/saphelp_nw04/helpdata/en/36/ef353e39011a38e10000000a114084/frameset.htm
"Setting system properties in a system that supports more than one parser is prohibited".
The Error which you are getting is because one of the
java.system properties for parsing is
getting changed by xalan. These system properties are explictly set by the SAP XML implementation which it does not allow you to change.
Also can you please let me know where are you placing the xalan jar file ? is it deployed as a j2ee library or part of war ?
Hope this helps. please mark points for helpful answers
regards
rajesh kr -
Error in Deploying java components - SAP NW CE 7.2 installation on Windows
Hi,
I am installing NW CE 7.2 on a windows machine. I opted for custom installation. I get the below error at "Deploy java components step. Any clue on why is this happening and how to resolve ?
<html> <head> </head> <body> <p> An error occurred while processing option SAP NetWeaver 7.2 Developer Edition > Install > Custom Server Installation( Last error reported by the step :Execution of Deploy Controller Runner tool '"C:\Program Files\sapinst_instdir\NW72\INSTALL\DEVSYSTEM\sapjvm\sapjvm_6\bin\java.exe" -classpath "C:/Program Files/sapinst_instdir/NW72/INSTALL/DEVSYSTEM/install/lib;E:/usr/sap/TR6/SYS/global/security/lib/tools/iaik_jce.jar;E:/usr/sap/TR6/SYS/global/security/lib/tools/iaik_jsse.jar;E:/usr/sap/TR6/SYS/global/security/lib/tools/iaik_smime.jar;E:/usr/sap/TR6/SYS/global/security/lib/tools/iaik_ssl.jar;E:/usr/sap/TR6/SYS/global/security/lib/tools/w3c_http.jar;E:/usr/sap/TR6/J00/j2ee/j2eeclient/sap.comtcexceptionimpl.jar;E:/usr/sap/TR6/J00/j2ee/j2eeclient/sap.comtcjeclientlibimpl.jar;E:/usr/sap/TR6/J00/j2ee/j2eeclient/sap.comtcloggingjavaimpl.jar;C:/Program Files/sapinst_instdir/NW72/INSTALL/DEVSYSTEM/install/lib/tcje~cl_deploy.jar" -Xmx256m -Ddc.api.verbose=false com.sap.engine.services.dc.api.cmd.Runner deploy -l "C:/Program Files/sapinst_instdir/NW72/INSTALL/DEVSYSTEM/deploy.lst" -e stop -u lower -w safety --lcm bulk -t 14400000 --host L-156007555 --port 50004' aborts with return code 104. Error message is <b>'undefinedStatus:AlreadyDeployedDescription: 1. Already deployed component has version:1000.7.20.1.0.20091117001100.</b> SOLUTION: Check 'undefined' and '' for more information.). You can now: </p> <ul> <li> Choose <i>Retry</i> to repeat the current step. </li> <li> Choose <i>View Log</i> to get more information about the error. </li> <li> Stop the option and continue with it later. </li> </ul> <p> Log files are written to C:\Program Files/sapinst_instdir/NW72/INSTALL/DEVSYSTEM. </p> </body></html>
Regards,
RukmaniThe below msg is from sapinst_dev.log
<html> <head> </head> <body> <p> An error occurred while processing option SAP NetWeaver 7.2 Developer Edition > Install > Custom Server Installation( Last error reported by the step :Execution of Deploy Controller Runner tool '"C:\Program Files\sapinst_instdir\NW72\INSTALL\DEVSYSTEM\sapjvm\sapjvm_6\bin\java.exe" -classpath "C:/Program Files/sapinst_instdir/NW72/INSTALL/DEVSYSTEM/install/lib;E:/usr/sap/TR6/SYS/global/security/lib/tools/iaik_jce.jar;E:/usr/sap/TR6/SYS/global/security/lib/tools/iaik_jsse.jar;E:/usr/sap/TR6/SYS/global/security/lib/tools/iaik_smime.jar;E:/usr/sap/TR6/SYS/global/security/lib/tools/iaik_ssl.jar;E:/usr/sap/TR6/SYS/global/security/lib/tools/w3c_http.jar;E:/usr/sap/TR6/J00/j2ee/j2eeclient/sap.comtcexceptionimpl.jar;E:/usr/sap/TR6/J00/j2ee/j2eeclient/sap.comtcjeclientlibimpl.jar;E:/usr/sap/TR6/J00/j2ee/j2eeclient/sap.comtcloggingjavaimpl.jar;C:/Program Files/sapinst_instdir/NW72/INSTALL/DEVSYSTEM/install/lib/tcje~cl_deploy.jar" -Xmx256m -Ddc.api.verbose=false com.sap.engine.services.dc.api.cmd.Runner deploy -l "C:/Program Files/sapinst_instdir/NW72/INSTALL/DEVSYSTEM/deploy.lst" -e stop -u lower -w safety --lcm bulk -t 14400000 --host L-156007555 --port 50004' aborts with return code 104. Error message is <b>'undefinedStatus:AlreadyDeployedDescription: 1. Already deployed component has version:1000.7.20.1.0.20091117001100.</b> SOLUTION: Check 'undefined' and '' for more information.). You can now: </p> <ul> <li> Choose <i>Retry</i> to repeat the current step. </li> <li> Choose <i>View Log</i> to get more information about the error. </li> <li> Stop the option and continue with it later. </li> </ul> <p> Log files are written to C:\Program Files/sapinst_instdir/NW72/INSTALL/DEVSYSTEM. </p> </body></html> -
SDM Error while deploying apllication in fresh installation of SAP.
hi friends
i installed Web AS and EP, and trying to deploy first WebDynpro Application in SDM then getting following Error...
I am giving SDM password = Masterpassword.
Error>>>>>>>>
Mar 13, 2007 7:23:10 PM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
[001]Deployment aborted
Settings
SDM host : bconedel4
SDM port : 50118
URL to deploy : file:/C:/DOCUME1/NARPAL1.SIN/LOCALS~1/Temp/temp49789Test.ear
Result
=> deployment aborted : file:/C:/DOCUME1/NARPAL1.SIN/LOCALS~1/Temp/temp49789Test.ear
Aborted: development component 'Test'/'local'/'LOKAL'/'0.2007.03.13.19.22.41'/'0':
Cannot login to the SAP J2EE Engine using user and password as provided in the Filesystem Secure Store. Enter valid login information in the Filesystem Secure Store using the SAP J2EE Engine Config Tool. For more information, see SAP note 701654.
com.sap.sdm.serverext.servertype.inqmy.extern.DeployManagerAuthExceptionWrapper: Wrong security credentials detected while trying to obtain connection to the J2EE Engine.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.checkLoginCredentials.DMAUTHEXC)
Deployment exception : The deployment of at least one item abortedHI I DONE ACCORDING TO THE SAP NOTES..... now got different error
see this and suggest me the needful..
Mar 14, 2007 12:48:34 PM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
[002]Deployment aborted
Settings
SDM host : bconedel4
SDM port : 50118
URL to deploy : file:/C:/DOCUME1/NARPAL1.SIN/LOCALS~1/Temp/temp11908Test.ear
Deployment exception : Server bconedel4 did not accept login request as apiadmin on port 50118 - Connection between SDM client and server is broken
Inner exception was :
Server bconedel4 did not accept login request as apiadmin on port 50118 - Connection between SDM client and server is broken -
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 -
Error during deploying *.ear to sap using ant
I want to deploy ear to sap with ant script,but it can not work.The error information as follows,can anybody give me some advice if you had the similar error,thanks.
C:\usr\sap\LJ1\J00\j2ee\deployment\ant>ant -f example_build.xml deploy -v
Apache Ant version 1.7.0 compiled on December 13 2006
Buildfile: example_build.xml
Detected Java version: 1.6 in: D:\Java\jdk1.6.0_18\jre
Detected OS: Windows 2003
parsing buildfile C:\usr\sap\LJ1\J00\j2ee\deployment\ant\example_build.xml with
URI = file:/C:/usr/sap/LJ1/J00/j2ee/deployment/ant/example_build.xml
Project base dir set to: C:\usr\sap\LJ1\J00\j2ee\deployment\ant
parsing buildfile jar:file:/D:/Perforce/tools/ant1.7.0/lib/ant.jar!/org/apache/t
ools/ant/antlib.xml with URI = jar:file:/D:/Perforce/tools/ant1.7.0/lib/ant.jar!
/org/apache/tools/ant/antlib.xml
[property] Loading C:\usr\sap\LJ1\J00\j2ee\deployment\ant\cfg\ant.properties
Build sequence for target(s) `deploy' is [deploy]
Complete build sequence is [deploy, import_ear, undeploy, params, ]
deploy:
[sapdeploy] Starting deployment with the following properties:
[sapdeploy] Version Handling Rule: all
[sapdeploy] Error Handling Strategies: [error action: 'prerequisites', error str
ategy: 'stop', error action: 'deploy', error strategy: 'stop']
[sapdeploy] The targeted SAP J2EE Engines are: [server host: 'localhost', server
port '50004', user name 'Administrator'.]
[sapdeploy] Deploy timeout: null
[sapdeploy] Starting to validate the data...
[sapdeploy] Validation ended
[sapdeploy] root dir c:\temp
[sapdeploy] Selected archives for deployment:
[sapdeploy] 1: 'c:\temp\dataservices-samples.war'
[sapdeploy] 2: 'c:\temp\test.ear'
[sapdeploy] Starting validation for the engine 'server host: 'localhost', server
port '50004', user name 'Administrator'.'
[sapdeploy] Engine data validated successfully
[sapdeploy] Starting deployment for the engine 'server host: 'localhost', server
port '50004', user name 'Administrator'.'
[sapdeploy] An error occured during the deployment.
[sapdeploy] The result of the deployment is: Error
[sapdeploy] Deployment ended
BUILD SUCCESSFUL
Total time: 0 secondsThe problem has been resolved,I make a stupid mistake.The reason caused the error is that the user of server was locked.I hope these will be helpful for people troubled by the same mistake.
-
Error when deploying SAP KMC-CM.
Hello,
On my Solution Manager 7.0 (NW04S) i try to patch the java part of the solution manager.
Everything went well but with the last one (KMC-CM) i receive an error : my actuel SP level is 11 and i try to apply SP14 (KMCCM14P_2-10003464.SCA) but it ends in error.
This is the log :
May 23, 2008 7:23:25 AM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
May 23, 2008 7:23:25 AM Error: Aborted: development component 'tc/kmc/km.appl.srv.index/idxws/ear'/'sap.com'/'SAP AG'/'7.0014.20071113170027.0000'/'1', grouped by software component 'KMC-CM'/'sap.com'/'SAP AG'/'1000.7.00.14.2.20080428150146''/'1':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot deploy application sap.com/tckmckm.appl.srv.indexidxwsear..
Reason: Exception during generation of components of application sap.com/tckmckm.appl.srv.indexidxwsear in container EJBContainer.; nested exception is:
com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application sap.com/tckmckm.appl.srv.indexidxwsear in container EJBContainer.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
May 23, 2008 7:23:25 AM Info: Starting to save the repository
May 23, 2008 7:23:26 AM Info: Finished saving the repository
Does this ring a bell for someone ?
Regards,
Marc.We got the same error with update of KMC-CM:
Jun 19, 2008 1:23:50 PM Error: Aborted: development component 'tc/kmc/km.appl.srv.index/idxws/ear'/'sap.com'/'SAP AG'/'7.0013.20070808101344.0000'/'1', grouped by software component 'KMC-CM'/'sap.com'/'SAP AG'/'1000.7.00.13.1.20071122103542''/'1':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot deploy application sap.com/tckmckm.appl.srv.indexidxwsear..
Reason: Exception during generation of components of application sap.com/tckmckm.appl.srv.indexidxwsear in container EJBContainer.; nested exception is:
com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application sap.com/tckmckm.appl.srv.indexidxwsear in container EJBContainer.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Jun 19, 2008 1:23:50 PM Info: Starting to save the repository
Did you already solve this problem?
mvg Kees -
Error While Deploying A Web Service
Hello All,
I am trying to deploy a Web Service however when I am doing so I keeping getting this exception any idea what could be wrong:
5056bf5661#SAPEngine_Application_Thread[impl:3]_130##0#0#Error#1#/System/Server#Java#deploy_5029##Exception in operation update with application sap.com/reg~equip.#2#update#sap.com/reg~equip#
#1.5#005056BF5661006E000009A100000F5000043492CC869AC9#1183705008343#com.sap.engine.services.deploy##com.sap.engine.services.deploy#J2EE_ADMIN#93423####0d48d6a02b8e11dcba6b005056bf5661#SAPEngine_Application_Thread[impl:3]_130##0#0#Error#1#/System/Audit#Java###Exception {0}#1#com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception in operation update with application sap.com/reg~equip.
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:3155)
at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:667)
at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1278)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:309)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:194)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:122)
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 sap.com/reg~equip.
at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:328)
at com.sap.engine.services.deploy.server.application.UpdateTransaction.begin(UpdateTransaction.java:164)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
... 13 more
Caused by: com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Webservices common deployment exception! The reason is: Error occurred, trying to update web services for application sap.com/reg~equip. . Additional info: none
at com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.updateWebServices(WSUpdateProcessor.java:164)
at com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.updateWebServices(WSUpdateProcessor.java:118)
at com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.updateWebServices(WSUpdateProcessor.java:86)
at com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateManager.makeUpdate(WSUpdateManager.java:52)
at com.sap.engine.services.webservices.server.deploy.WSDeployer.makeUpdate(WSDeployer.java:274)
at com.sap.engine.services.deploy.server.application.UpdateTransaction.makeComponents(UpdateTransaction.java:400)
at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:319)
... 15 more
Caused by: com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Webservices deployment exception! The reason is: Error occurred, trying to generate web services deployment files for application sap.com/reg~equip. . The error refers to application: none, jar: {2}, web service: {3}.
at com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.generateDeployFiles(WSUpdateProcessor.java:296)
at com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.deployWebServices(WSUpdateProcessor.java:262)
at com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.updateWebServices(WSUpdateProcessor.java:155)
... 21 more
Caused by: com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Webservices common deployment exception! The reason is: Error occurred, parsing com.sap.engine.services.webservices.server.deploy.descriptors.sapwebservices.WSDescriptor descriptor, application sap.com/reg~equip, web service EmmServiceWS, location message: type: jar file, location: D:\\usr\\sap\\ERP\\DVEBMGS10\\j2ee\\cluster\\server0\\.\\temp\\deploy\\work\\deploying\\reader1183705000828\\sap.com~reg~equip~ejbmodule.jar . . Additional info: {1}
at com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.parseWSDescriptor(WSDefinitionFactory.java:907)
at com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.loadWebService(WSDefinitionFactory.java:176)
at com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.loadWebServices(WSDefinitionFactory.java:158)
at com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.generateDeployFiles(WSUpdateProcessor.java:284)
... 23 more
Caused by: com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Webservices common deployment exception! The reason is: Error occurred, trying to parse source type: zip entry, zip file location: D:\\usr\\sap\\ERP\\DVEBMGS10\\j2ee\\cluster\\server0\\.\\temp\\deploy\\work\\deploying\\reader1183705000828\\sap.com~reg~equip~ejbmodule.jar, entry: com/sap/reg/equip/appsrv/emmservice/EmmServiceWSVi.videf . Additional info: {1}
at com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.parseVI(WSDefinitionFactory.java:925)
at com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.parseWSDescriptor(WSDefinitionFactory.java:817)
... 26 more
Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.XmlUnmarshalException: XML Deserialization Error. XML Node [VirtualInterface.Functions][http://xml.sap.com/2002/10/metamodel/vi] have minOccurs>0 in schema definition but is missing in node [VirtualInterface][http://xml.sap.com/2002/10/metamodel/vi].
at com.sap.engine.services.webservices.jaxrpc.encoding.GeneratedComplexType._loadInto(GeneratedComplexType.java:1197)
at com.sap.engine.services.webservices.jaxrpc.encoding.GeneratedComplexType.deserialize(GeneratedComplexType.java:945)
at com.sap.engine.services.webservices.server.deploy.descriptors.vi.VInterfaceParser.getVInterface(VInterfaceParser.java:46)
at com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.parseVI(WSDefinitionFactory.java:920)
... 27 moreHi,
Could not diagonise from this stack trace alone. But what doubt is that there is something wrong with cardinality in your web service. Otherwise something may have gone wrong like you mishandling a list or some mismatch like that.
Regards,
Srinivasan Subbiah -
Flex error while deploying a VC application
Hi Experts,
Though I have rarely worked on VC developments, I have to troubleshoot an issue wherein we are getting following error while deploying a VC Application.
Error: Error in compiling flex application. Consult log file for details.
I have got a log file and it has written out 100s of lines of log, however, following is the important part from the log file:
#00145E9635CE0060000016940015E0C60004A07BE7C55172#1302353936732#/System/Server/VCServer
#sap.com/VisualComposerServerEar04
#com.sap.portal.vc.server#ganeshb#35216##n/a##b1528d4062a811e0aedc00145e9635ce
#SAPEngine_Application_Thread[impl:3]_12##0#0#Debug#1#/System/Server/VCServer#Plain###
Server Error:Failed to import model - attribute is missing in imported file bytes are <?xml version="1.0" encoding="UTF-8"?>
Any help on how to resolve this?
Thanks in advance,
Ameya
Edited by: Ameya Pimpalgaonkar on Nov 16, 2011 7:31 AMHi Ameya,
If its VC 7.0 then you must be using Flash Compiler.Try changing the compiler to Flash at this path
Tools->Options->Compiler->Change 'Runtime filed to Flash'.I hope this should solve your problem.
Naga -
While Deploying, an error is bieng displayed:
Mar 13, 2008 12:40:49 PM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
[002]Deployment aborted
Settings
SDM host : RPULSE
SDM port : 50118
URL to deploy : file:/C:/DOCUME1/SANJYO1.LEN/LOCALS~1/Temp/temp31832RsuPr.ear
Result
 deployment aborted : file:/C:/DOCUME1/SANJYO1.LEN/LOCALS~1/Temp/temp31832RsuPr.ear
Aborted: development component 'RsuPr'/'local'/'LOKAL'/'0.2008.03.13.12.40.22'/'0':Caught exception while checking the login credentials for SAP J2EE Engine. Check whether the SAP J2EE Engine is up and running.com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot connect to Host: [RPULSE] with user name: [Administrator] Check your login information. Exception is: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during getInitialContext operation. No server is running. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.] at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:494) at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:363) at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662) at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243) at javax.naming.InitialContext.init(InitialContext.java:219) at javax.naming.InitialContext.<init>(InitialContext.java:195) at com.sap.engine.deploy.manager.DeployManagerImpl.checkCredentials(DeployManagerImpl.java:2983) at com.sap.sdm.serverext.servertype.inqmy.extern.DeployManagerAuthMethodInvoker.invokeCheckCredentialsInternal(DeployManagerAuthMethodInvoker.java:51) at com.sap.sdm.serverext.servertype.inqmy.extern.ExternalMethodInvoker.invokeCheckCredentials(ExternalMethodInvoker.java:45) at com.sap.sdm.serverext.servertype.inqmy.extern.ExternalMethodInvoker.invokeCheckCredentials(ExternalMethodInvoker.java:32) at com.sap.sdm.serverext.servertype.inqmy.extern.EngineOnlineDeployerImpl.checkLoginCredentials(EngineOnlineDeployerImpl.java:173) at com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performDeployment(EngineApplOnlineDeployerImpl.java:168) at com.sap.sdm.serverext.servertype.inqmy.extern.EngineDeployerImpl.deploy(EngineDeployerImpl.java:96) at com.sap.sdm.serverext.servertype.inqmy.EngineProcessor.executeAction(EngineProcessor.java:224) at com.sap.sdm.app.proc.deployment.impl.PhysicalDeploymentActionExecutor.execute(PhysicalDeploymentActionExecutor.java:60) at com.sap.sdm.app.proc.deployment.impl.DeploymentActionImpl.execute(DeploymentActionImpl.java:186) at com.sap.sdm.app.proc.deployment.controllers.internal.impl.DeploymentExecutorImpl.execute(DeploymentExecutorImpl.java:48) at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.executeAction(ExecuteDeploymentHandler.java:83) at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.handleEvent(ExecuteDeploymentHandler.java:60) at com.sap.sdm.app.proc.deployment.states.StateBeforeNextDeployment.processEvent(StateBeforeNextDeployment.java:127) at com.sap.sdm.app.proc.deployment.states.InstContext.processEventServerSide(InstContext.java:73) at com.sap.sdm.app.proc.deployment.states.InstContext.processEvent(InstContext.java:59) at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.doPhysicalDeployment(DeployerImpl.java:128) at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.deploy(DeployerImpl.java:97) at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.deploy(DeployerImpl.java:68) at com.sap.sdm.apiimpl.local.DeployProcessorImpl.deploy(DeployProcessorImpl.java:74) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.sdm.is.cs.remoteproxy.server.impl.RemoteProxyServerImpl.requestRemoteCall(RemoteProxyServerImpl.java:127) at com.sap.sdm.is.cs.remoteproxy.server.impl.RemoteProxyServerImpl.process(RemoteProxyServerImpl.java:38) at com.sap.sdm.apiimpl.remote.server.ApiClientRoleCmdProcessor.process(ApiClientRoleCmdProcessor.java:84) at com.sap.sdm.is.cs.session.server.SessionCmdProcessor.process(SessionCmdProcessor.java:67) at com.sap.sdm.is.cs.cmd.server.CmdServer.execCommand(CmdServer.java:76) at com.sap.sdm.client_server.launch.ServerLauncher$ConnectionHandlerImpl.handle(ServerLauncher.java:286) at com.sap.sdm.is.cs.ncserver.NetCommServer.serve(NetCommServer.java:43) at com.sap.sdm.is.cs.ncwrapper.impl.ServiceWrapper.serve(ServiceWrapper.java:39) at com.sap.bc.cts.tp.net.Worker.run(Worker.java:50) at java.lang.Thread.run(Thread.java:534)Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance. at com.sap.engine.services.security.remote.login.RemoteLoginContextExt.<init>(RemoteLoginContextExt.java:34) at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:81) at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:355) ... 38 moreCaused by: java.lang.SecurityException: com.sap.engine.services.security.exceptions.BaseSecurityException: This call must be performed from a system thread. at com.sap.engine.services.security.login.SecuritySession.setExpirationPeriod(SecuritySession.java:337) at com.sap.engine.services.security.login.TicketGenerator.getSecuritySession(TicketGenerator.java:129) at com.sap.engine.services.security.login.SecurityContext.load(SecurityContext.java:211) at com.sap.engine.services.rmi_p4.Message.loadContextObject(Message.java:345) at com.sap.engine.services.rmi_p4.Message.parseMessage(Message.java:239) at com.sap.engine.services.rmi_p4.Message.getByteArrayInputStream(Message.java:314) at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:208) 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) at com.sap.engine.services.security.exceptions.BaseSecurityException.writeReplace(BaseSecurityException.java:349) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at java.io.ObjectStreamClass.invokeWriteReplace(ObjectStreamClass.java:896) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1011) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278) at com.sap.engine.services.rmi_p4.DispatchImpl.throwException(DispatchImpl.java:144) at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:212) 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) (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.checkLoginCredentials.DMEXC)
Deployment exception : The deployment of at least one item abortedHello Umang
What are you trying to deploy?
How is it related to ESR?
regards
Rathish -
Error While Deploying the Ear .
HI ,
I am getting an error while deploying my ear through Deploy Tool . the ear get loaded but fails to deploy... the error message i got is pasted below...
It gives error about EJBContainer, but the J2EE Engine's Visual Admin shows the service is runing
Any help is highly appreaciated
Eror Message.....
06/05/13 18:49:09 - ***********************************************************
06/05/13 18:49:10 - Start updating EAR file...
06/05/13 18:49:10 - start-up mode is lazy
06/05/13 18:49:12 - EAR file updated successfully for 2078ms.
06/05/13 18:49:12 - Start deploying ...
06/05/13 18:49:14 - EAR file uploaded to server for 1172ms.
06/05/13 18:49:16 - ERROR: Not deployed. Deploy Service returned ERROR:
java.rmi.RemoteException: Cannot deploy application sap.com/omnidocs_ejb..
Reason: Exception during generation of components of application sap.com/omnidocs_ejb in container EJBContainer.; nested exception is:
com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application sap.com/omnidocs_ejb in container EJBContainer.
at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:554)
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:304)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:193)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:122)
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: Exception during generation of components of application sap.com/omnidocs_ejb in container EJBContainer.
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:621)
at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:319)
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:3139)
at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:539)
... 10 more
Caused by: java.lang.NoClassDefFoundError: com/newgen/omni/jts/txn/NGOServerInterface
Loader Info -
ClassLoader name: [Deployment:Runtime:sap.com/omnidocs_ejb]
Parent loader name: [Frame ClassLoader]
References:
common:service:http;service:servlet_jsp
service:ejb
common:service:iiop;service:naming;service:p4;service:ts
service:jmsconnector
library:jsse
library:servlet
common:library:IAIKSecurity;library:activation;library:mail;library:tcsecssl
library:ejb20
library:j2eeca
library:jms
library:opensql
common:library:com.sap.security.api.sda;library:com.sap.security.core.sda;library:security.class;library:webservices_lib;service:adminadapter;service:basicadmin;service:com.sap.security.core.ume.service;service:configuration;service:connector;service:dbpool;service:deploy;service:jmx;service:jmx_notification;service:keystore;service:security;service:userstore
interface:resourcecontext_api
interface:webservices
interface:cross
interface:ejbserialization
Resources:
C:\usr\sap\J2E\JC00\j2ee\cluster\server0\temp\deploy\1147526354539
C:\usr\sap\J2E\JC00\j2ee\cluster\server0\temp\deploy\1147526354539\omnidocs_ejb.jar
Loading model: {parent,references,local}
The error occurred while trying to load "com.newgen.omni.jts.txn.oracle.docdb.NGOConnectCabinet".
at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:389)
at com.sap.engine.services.ejb.deploy.verifier.CheckUtils.loadClass(CheckUtils.java:25)
at com.sap.engine.services.ejb.deploy.verifier.session.SessionBeanCheck.check(SessionBeanCheck.java:42)
at com.sap.engine.services.ejb.deploy.verifier.Verifier.checkBean(Verifier.java:82)
at com.sap.engine.services.ejb.deploy.verifier.Verifier.check(Verifier.java:46)
at com.sap.engine.services.ejb.deploy.DeployAdmin.generate(DeployAdmin.java:253)
at com.sap.engine.services.ejb.EJBAdmin.deploy(EJBAdmin.java:2144)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)
... 16 more
For detailed information see the log file of the Deploy Service.
06/05/13 18:49:16 - ***********************************************************
<b></b>Hi
I would suggest you to do the deployment of the EAR using NWDS rather that using deploy tool. for Doing this please follow this link for creating ,building and deplopying as ear using dev studio
http://help.sap.com/saphelp_nw04/helpdata/en/08/51ec41b9a24f4a8359c61ae4a02db1/frameset.htm
Anyways if you ar still tied up using deploy tool pleas cross verify that all the dependent jars (including jars which NgoServerinterface will beusing internally has to be in the classpath . Would be great if you can post the stack trace
hope this helps !<b> please mark points for helpful answers .</b>
regards
rajeshkr -
Error in deployment:java.lang.NullPointerException:sdu name can not be null
HI Everyone!
I try to deploy my web dynpro project to SAP J2EE engine. Configuration about SAP J2EE Engine is OK, but there is an error during the deployment. Here is the deployment trace:
2007-6-28 14:56:27 /userOut/daView_category (com.sap.ide.eclipse.deployer.DVBaseLog) [Thread[Deploy Thread,6,main]] INFO: deployment trace
14:56:24.207 [info #300] [#4]: Trying to connect to 'secude-vmcn0001:50004' as 'administrator'
14:56:24.207 [debug #100] [#4]: Session::getContext.[ B E G I N ].timerId=16
14:56:25.161 [debug #100] [#4]: Session::getContext.[ E N D ].timerId=[id:#16, elapsed: 954 ms.]
14:56:25.161 [info #300] [#4]: Connected to 'secude-vmcn0001:50004' as 'administrator'
14:56:25.161 [debug #100] [#4]: DeployProcessor::ctor:New deploy processor created.deployerId=4
14:56:25.161 [info #300] [#4]: +++++ Starting D E P L O Y action +++++
14:56:25.161 [info #300] [#4]: Selected archives for deployment
14:56:25.161 [info #300] [#4]: D:\NetWeaverWorkspace\Workspace\Dashboard\Dashboard.ear
14:56:25.536 [debug #100] [#4]: DeployProcessor::deploy:going to generate Session id, deployerId=4
14:56:25.755 [debug #100] [#4]: DeployProcessor::deploy:got Session id='14',time:[id:#17, elapsed: 594 ms.], deployerId=4
14:56:25.974 [info #300] [#4]: Upload archives to the server.Remote upload path is 'C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\tcbldeploy_controller\archives\14'
14:56:25.974 [debug #300] [#4]: DeployProcessor::uploadItemsToServer:Going to upload 'D:\NetWeaverWorkspace\Workspace\Dashboard\Dashboard.ear' on the server.deployerId=4
14:56:26.427 [info #300] [#4]: File 'D:\NetWeaverWorkspace\Workspace\Dashboard\Dashboard.ear' uploaded successfully as 'C:/SAP/JP1/JC00/j2ee/cluster/server0/temp/tcbldeploy_controller/archives/14/Dashboard.ear'. Time:[id:#18, elapsed: 453 ms.]
14:56:26.427 [info #300] [#4]: Archives uploaded.time:[#18: 0.453 sec]
14:56:26.427 [debug #100] [#4]: DeployProcessor::deployItems:enter.timerId=19, deployerId=4
14:56:26.427 [debug #100] [#4]: DeployProcessor::internalCreateAndInitDeployer:get deployer from server, deployerId=4
14:56:26.427 [debug #100] [#4]: DeployProcessor::internalCreateAndInitDeployer:deployer get successfully:[id:#20, elapsed: 0 ms.], deployerId=4
14:56:26.630 [info #300] [#4]: component version handling rule is UpdateAllVersions
14:56:26.849 [info #300] [#4]: Error strategies:
14:56:26.849 [debug #100] [#4]: DeployProcessor::internalCreateAndInitDeployer:deployer initialized sucessfully:[id:#20, elapsed: 422 ms.], deployerId=4
14:56:26.849 [debug #100] [#4]: DeployProcessor::internalCreateAndInitDeployer:total time:[#20: 0.422 sec], deployerId=4
14:56:26.849 [info #300] [#4]: Starting deployment
14:56:27.177 [debug #100] [#4]: DeployProcessor::internalMapSdus:sduMapperVisitor.setCompositeDeploymentItem(null),remoteSdu=name: 'null', vendor: 'null', location: 'LOKAL', version: '0.2007.06.28.14.28.59', software type: 'J2EE', dependencies: '[]'
14:56:27.177 [debug #300] [#4]: DeployProcessor::deployItems:finally.Total Time:[#19: 0.75 sec], deployerId=4
14:56:27.177 [info #300] [#4]: +++++ End D E P L O Y action +++++
And here is the exception detail:
2007-6-28 14:56:27 /userOut/daView_category (com.sap.ide.eclipse.deployer.DVBaseLog) [Thread[Deploy Thread,6,main]] ERROR: java.lang.NullPointerException: sdu name can not be null.
at com.sap.engine.services.dc.api.model.impl.SduImpl.<init>(SduImpl.java:39)
at com.sap.engine.services.dc.api.model.impl.SdaImpl.<init>(SdaImpl.java:51)
at com.sap.engine.services.dc.api.model.impl.ModelFactoryImpl.createSda(ModelFactoryImpl.java:43)
at com.sap.engine.services.dc.api.model.SduMapperVisitor.createSda(SduMapperVisitor.java:52)
at com.sap.engine.services.dc.api.model.SduMapperVisitor.visit(SduMapperVisitor.java:64)
at com.sap.engine.services.dc.repo.impl.SdaImpl.accept(SdaImpl.java:136)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.internalMapSdus(DeployProcessorImpl.java:704)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:487)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:155)
at com.sap.ide.eclipse.deployer.dc.deploy.DeployProcessor70.deploy(DeployProcessor70.java:185)
at com.sap.ide.eclipse.sdm.threading.DCDeployThread.run(DCDeployThread.java:115)
It seems that there is something wrong about 'SDU', but i don't know what is it, and i can not find the answer both in sdn.sap.com and here.
Anyone can help me on this?
Thanks in Advance,
MKHi Sumit,
Thank you for your concern.
Below is a trace file on my server:
C:\SAP\JP1\JC00\j2ee\cluster\server0\log\defaultTrace.0.trc
#1.5 #000C296B3F6A000D0000000200000A3000EF90978C2E8C29#1183013784131#/System/Server/Deployment##com.sap.engine.services.tcxblxdeploy_controller#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Info#1#com.sap.engine.services.tcxblxdeploy_controller#Plain###The session id 14 is associated with correlator id 67431500000169001. Use this correlator id to filter the trace and log messages.#
#1.5 #000C296B3F6A000D0000000300000A3000EF90978C2E8C29#1183013784131#/System/Server/Deployment##com.sap.engine.services.tcxblxdeploy_controller#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Info#1#com.sap.engine.services.tcxblxdeploy_controller#Plain###++++++++++++++ Starting deployment ++++++++++++++#
#1.5 #000C296B3F6A000D0000000400000A3000EF90978C2E8C29#1183013784131#/System/Server/Deployment##com.sap.engine.services.tcxblxdeploy_controller#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Info#1#com.sap.engine.services.tcxblxdeploy_controller#Plain###Archives specified for deployment are: #
#1.5 #000C296B3F6A000D0000000500000A3000EF90978C2E8C29#1183013784131#/System/Server/Deployment##com.sap.engine.services.tcxblxdeploy_controller#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Info#1#com.sap.engine.services.tcxblxdeploy_controller#Plain###C:/SAP/JP1/JC00/j2ee/cluster/server0/temp/tcbldeploy_controller/archives/14/Dashboard.ear#
#1.5 #000C296B3F6A000D0000000600000A3000EF90978C2E8C29#1183013784131#/System/Server/Deployment##com.sap.engine.services.tcxblxdeploy_controller#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Info#1#com.sap.engine.services.tcxblxdeploy_controller#Plain###Start loading archives ...#
#1.5 #000C296B3F6A000D0000000700000A3000EF90978C2E8C29#1183013784147#/System/Server/Deployment##com.sap.engine.services.tcxblxdeploy_controller#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Info#1#com.sap.engine.services.tcxblxdeploy_controller#Plain###Archives are loaded.#
#1.5 #000C296B3F6A000D0000000800000A3000EF90978C2E8C29#1183013784147#/System/Server/Deployment##com.sap.engine.services.tcxblxdeploy_controller#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Info#1#com.sap.engine.services.tcxblxdeploy_controller#Plain###Error Handling Action: 'UndeploymentAction', Error Handling Strategy: 'OnErrorStop'.
Error Handling Action: 'DeploymentAction', Error Handling Strategy: 'OnErrorStop'.
Error Handling Action: 'PrerequisitesCheckAction', Error Handling Strategy: 'OnErrorStop'.
Version Handling Rule: 'UpdateAllVersions'.
Deployment Strategy: 'normal deploy strategy'.
Life Cycle Deployment Strategy: 'bulk deploy strategy'.
There are no batch filters specified.#
#1.5 #000C296B3F6A000D0000000900000A3000EF90978C2E8C29#1183013784194#/System/Server/Deployment##com.sap.engine.services.tcxblxdeploy_controller#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Info#1#com.sap.engine.services.tcxblxdeploy_controller#Plain###The batch for session id 14 will be executed with normal parallelism strategy.#
#1.5 #000C296B3F6A000D0000000A00000A3000EF90978C2E8C29#1183013784272#/System/Server/Services/Deploy##com.sap.engine.services.deploy#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Warning#1#com.sap.engine.services.deploy#Plain###A component loader with name sap.com/tcwddispwda doesn't exist, because is stopped or not deployed.#
#1.5 #000C296B3F6A000D0000000B00000A3000EF90978C2E8C29#1183013784272#/System/Server/Services/Deploy##com.sap.engine.services.deploy#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Warning#1#com.sap.engine.services.deploy#Plain###A component loader with name library:tcddicddicruntime doesn't exist, because is stopped or not deployed.#
#1.5 #000C296B3F6A000D0000000C00000A3000EF90978C2E8C29#1183013784272#/System/Server/Services/Deploy##com.sap.engine.services.deploy#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Warning#1#com.sap.engine.services.deploy#Plain###A component loader with name library:com.sap.aii.util.rb doesn't exist, because is stopped or not deployed.#
#1.5 #000C296B3F6A000D0000000D00000A3000EF90978C2E8C29#1183013784272#/System/Server/Services/Deploy##com.sap.engine.services.deploy#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Warning#1#com.sap.engine.services.deploy#Plain###A component loader with name library:com.sap.aii.util.xml doesn't exist, because is stopped or not deployed.#
#1.5 #000C296B3F6A000D0000000E00000A3000EF90978C2E8C29#1183013784272#/System/Server/Services/Deploy##com.sap.engine.services.deploy#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Warning#1#com.sap.engine.services.deploy#Plain###A component loader with name library:com.sap.aii.proxy.framework doesn't exist, because is stopped or not deployed.#
#1.5 #000C296B3F6A000D0000000F00000A3000EF90978C2E8C29#1183013784272#/System/Server/Services/Deploy##com.sap.engine.services.deploy#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Warning#1#com.sap.engine.services.deploy#Plain###A component loader with name library:tc~cmi doesn't exist, because is stopped or not deployed.#
#1.5 #000C296B3F6A000D0000001000000A3000EF90978C2E8C29#1183013784272#/System/Server/Services/Deploy##com.sap.engine.services.deploy#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Warning#1#com.sap.engine.services.deploy#Plain###A component loader with name library:com.sap.aii.util.misc doesn't exist, because is stopped or not deployed.#
#1.5 #000C296B3F6A000D0000001100000A3000EF90978C2E8C29#1183013784272#/System/Server/Services/Deploy##com.sap.engine.services.deploy#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Warning#1#com.sap.engine.services.deploy#Plain###A component loader with name library:tcddicddicservices doesn't exist, because is stopped or not deployed.#
#1.5 #000C296B3F6A000D0000001200000A3000EF90978C2E8C29#1183013784272#/System/Server/Services/Deploy##com.sap.engine.services.deploy#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Warning#1#com.sap.engine.services.deploy#Plain###A component loader with name library:tcgraphicsigs doesn't exist, because is stopped or not deployed.#
#1.5 #000C296B3F6A000D0000001300000A3000EF90978C2E8C29#1183013784366#/System/Server/Services/Deploy##com.sap.engine.services.deploy#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Warning#1#com.sap.engine.services.deploy#Plain###JLinEE validation of application local/Dashboard returned result
WARNINGS:
References Test: Count of deploy time references (described in META-INF/SAP_MANIFEST.MF) and runtime references (described in META-INF/application-j2ee-engine.xml) does not match., file: Dashboard.ear, column 0, line 0, severity: warning
References Test: There are no matching deploy time references (described in META-INF/SAP_MANIFEST.MF) for the following runtime references [sap.com/tcwddispwda, sap.com/com.sap.mw.jco, sap.com/tcddicddicruntime, sap.com/com.sap.aii.util.rb, sap.com/com.sap.aii.util.xml, sap.com/webservices_lib, sap.com/com.sap.aii.proxy.framework, sap.com/sapxmltoolkit, sap.com/tccmi, sap.com/com.sap.security.api.sda, sap.com/com.sap.util.monitor.jarm, sap.com/com.sap.aii.util.misc, sap.com/tcddicddicservices, sap.com/com.sap.lcr.api.cimclient, sap.com/tcgraphics~igs, sap.com/sld] (described in the META-INF/application-j2ee-engine.xml)., file: Dashboard.ear, column 0, line 0, severity: warning
#1.5 #000C296B3F6A000D0000001400000A3000EF90978C2E8C29#1183013784366#/System/Server/Services/Deploy##com.sap.engine.services.deploy#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Error#1#com.sap.engine.services.deploy#Plain#Exception while validating application local/Dashboard.
No one of the [] containers, which processed it, returned deployed component names.
The registered containers in this moment were [com.sap.security.ume, app_libraries_container, Cache Configuration Upload, servlet_jsp, dbcontentcontainer, connector, Cluster File System, JMSConnector, appclient, dbschemacontainer, orpersistence, JDBCConnector, EJBContainer, webservices_container, scheduler~container].
Possible reasons :
1.An AS Java service, which is providing a container, is stopped or not deployed.
2.The containers, which processed it, are not implemented correct. They deployed or started initially the application, but didn't return deployed components in the application deployment info.###
#1.5 #000C296B3F6A000D0000001700000A3000EF90978C2E8C29#1183013784366#/System/Server/Services/Deploy##com.sap.engine.services.deploy#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Error#1#com.sap.engine.services.deploy#Plain#Exception in operation deploy with application local/Dashboard.###
#1.5 #000C296B3F6A000D0000001B00000A3000EF90978C2E8C29#1183013784397#/System/Server##java.lang.Package#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Error#1#java.lang.Package#Java#error.action.filter#com/sap/engine/services/mngt_model/localization.properties#Exception thrown by Action Filter: com.sap.engine.services.mngt_model.spi.ActionFilteringException: com.sap.engine.services.deploy.server.utils.DSRemoteException: Application local/Dashboard is not deployed..Action will not be delivered to domain: connector. Action is: APPLICATION_DEPLOYED#3#com.sap.engine.services.mngt_model.plugins.ApplicationActionFilter@d46ed0#connector#APPLICATION_DEPLOYED#
#1.5 #000C296B3F6A000D0000001D00000A3000EF90978C2E8C29#1183013784397#/System/Server##java.lang.Package#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Error#1#java.lang.Package#Java#error.action.filter#com/sap/engine/services/mngt_model/localization.properties#Exception thrown by Action Filter: com.sap.engine.services.mngt_model.spi.ActionFilteringException: com.sap.engine.services.deploy.server.utils.DSRemoteException: Application local/Dashboard is not deployed..Action will not be delivered to domain: servlet_jsp. Action is: APPLICATION_DEPLOYED#3#com.sap.engine.services.mngt_model.plugins.ApplicationActionFilter@d46ed0#servlet_jsp#APPLICATION_DEPLOYED#
#1.5 #000C296B3F6A000D0000001F00000A3000EF90978C2E8C29#1183013784397#/System/Server##java.lang.Package#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Error#1#java.lang.Package#Java#error.action.filter#com/sap/engine/services/mngt_model/localization.properties#Exception thrown by Action Filter: com.sap.engine.services.mngt_model.spi.ActionFilteringException: com.sap.engine.services.deploy.server.utils.DSRemoteException: Application local/Dashboard is not deployed..Action will not be delivered to domain: appclient. Action is: APPLICATION_DEPLOYED#3#com.sap.engine.services.mngt_model.plugins.ApplicationActionFilter@d46ed0#appclient#APPLICATION_DEPLOYED#
#1.5 #000C296B3F6A000D0000002100000A3000EF90978C2E8C29#1183013784397#/System/Server##java.lang.Package#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Error#1#java.lang.Package#Java#error.action.filter#com/sap/engine/services/mngt_model/localization.properties#Exception thrown by Action Filter: com.sap.engine.services.mngt_model.spi.ActionFilteringException: com.sap.engine.services.deploy.server.utils.DSRemoteException: Application local/Dashboard is not deployed..Action will not be delivered to domain: dbpool. Action is: APPLICATION_DEPLOYED#3#com.sap.engine.services.mngt_model.plugins.ApplicationActionFilter@d46ed0#dbpool#APPLICATION_DEPLOYED#
#1.5 #000C296B3F6A000D0000002300000A3000EF90978C2E8C29#1183013784397#/System/Server##java.lang.Package#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Error#1#java.lang.Package#Java#error.action.filter#com/sap/engine/services/mngt_model/localization.properties#Exception thrown by Action Filter: com.sap.engine.services.mngt_model.spi.ActionFilteringException: com.sap.engine.services.deploy.server.utils.DSRemoteException: Application local/Dashboard is not deployed..Action will not be delivered to domain: jmsconnector. Action is: APPLICATION_DEPLOYED#3#com.sap.engine.services.mngt_model.plugins.ApplicationActionFilter@d46ed0#jmsconnector#APPLICATION_DEPLOYED#
#1.5 #000C296B3F6A000D0000002500000A3000EF90978C2E8C29#1183013784397#/System/Server/Services/Deploy##com.sap.engine.services.deploy#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Error#1#com.sap.engine.services.deploy#Plain#Exception while validating application local/Dashboard.
No one of the [] containers, which processed it, returned deployed component names.
The registered containers in this moment were [com.sap.security.ume, app_libraries_container, Cache Configuration Upload, servlet_jsp, dbcontentcontainer, connector, Cluster File System, JMSConnector, appclient, dbschemacontainer, orpersistence, JDBCConnector, EJBContainer, webservices_container, scheduler~container].
Possible reasons :
1.An AS Java service, which is providing a container, is stopped or not deployed.
2.The containers, which processed it, are not implemented correct. They deployed or started initially the application, but didn't return deployed components in the application deployment info.###
#1.5 #000C296B3F6A000D0000002800000A3000EF90978C2E8C29#1183013784397#/System/Server/Deployment##com.sap.engine.services.tcxblxdeploy_controller#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Error#1#com.sap.engine.services.tcxblxdeploy_controller#Plain#An error occurred while deploying the deployment item 'local_Dashboard'.###
#1.5 #000C296B3F6A000D0000002B00000A3000EF90978C2E8C29#1183013784428#/System/Server/Deployment##com.sap.engine.services.tcxblxdeploy_controller#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Info#1#com.sap.engine.services.tcxblxdeploy_controller#Plain###Unlocking the Deploy.#
#1.5 #000C296B3F6A000D0000002C00000A3000EF90978C2E8C29#1183013784428#/System/Server/Deployment##com.sap.engine.services.tcxblxdeploy_controller#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Error#1#com.sap.engine.services.tcxblxdeploy_controller#Plain#An error occurred while deploying the deployment item 'local_Dashboard'.; nested exception is:
java.rmi.RemoteException: class com.sap.engine.services.dc.gd.DeliveryException: An error occurred during deployment of sdu id: local_Dashboard
sdu file path: C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\tcbldeploy_controller\archives\14\Dashboard.ear
version status: NEW
deployment status: Admitted
description:
1. Error:
Error occurred while deploying ear file C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\tcbldeploy_controller\archives\14\Dashboard.ear.
Reason: Exception while validating application local/Dashboard.
No one of the [] containers, which processed it, returned deployed component names.
The registered containers in this moment were [com.sap.security.ume, app_libraries_container, Cache Configuration Upload, servlet_jsp, dbcontentcontainer, connector, Cluster File System, JMSConnector, appclient, dbschemacontainer, orpersistence, JDBCConnector, EJBContainer, webservices_container, scheduler~container].
Possible reasons :
1.An AS Java service, which is providing a container, is stopped or not deployed.
2.The containers, which processed it, are not implemented correct. They deployed or started initially the application, but didn't return deployed components in the application deployment info.
. Cannot deploy it.; nested exception is:
java.rmi.RemoteException: class com.sap.engine.services.deploy.server.utils.DSRemoteException: Error occurred while deploying ear file C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\tcbldeploy_controller\archives\14\Dashboard.ear.
Reason: Exception while validating application local/Dashboard.
No one of the [] containers, which processed it, returned deployed component names.
The registered containers in this moment were [com.sap.security.ume, app_libraries_container, Cache Configuration Upload, servlet_jsp, dbcontentcontainer, connector, Cluster File System, JMSConnector, appclient, dbschemacontainer, orpersistence, JDBCConnector, EJBContainer, webservices_container, scheduler~container].
Possible reasons :
1.An AS Java service, which is providing a container, is stopped or not deployed.
2.The containers, which processed it, are not implemented correct. They deployed or started initially the application, but didn't return deployed components in the application deployment info.###
#1.5 #000C296B3F6A000D0000002F00000A3000EF90978C2E8C29#1183013784428#/System/Server/Deployment##com.sap.engine.services.tcxblxdeploy_controller#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Info#1#com.sap.engine.services.tcxblxdeploy_controller#Plain###Deployment has finished#
Thanks,
MK
Maybe you are looking for
-
Has anyone else had this problem? My ipod has been working perfectly for years and all of a sudden i have gone through three sets of headphones at least in the last month, i have discovered that it is a problem with where the headphones go......no id
-
I am having trouble signing into the Creative Cloud. I try to sign in and it then tells me, "You've been signed out." Help please!!
-
How can i get ahold of an apple person
Hello, My name is wesley Stern and I can't find out how to get ahold of an Apple person to help me out. I just got locked out of buying apps because i exceeded the maximum amount of times I can answer a security question. Please Help.
-
Hello, I,m using an N95 8GB and am having problems using the songs transferred to my phone as ringtones. Anytime I try it keeps on telling me that the song exceeds 600KB. To be realistic all mp3s exceed 600KB. So pls I need help. Any advice??
-
Displaying Alternate Text if Column is Empty
Coming back to the brain trust for this one. I have a Date/Time Column in a list. The Column is not required nor for internal business practices can it be made to be required (Don't get me started). In my search result template, I'm using the followi