SDM upgrade
folks
i'm trying to upgrade the sdm on my 1841 via the update tool in the sdm but when trying to load onto the router the upload failed after it had removed the old sdm so now i can't get onto the router
anyone any suggestions how i can recover this?
thanks
Ok, so I'm really hoping you're able to access this device via ssh, or even telnet. If so, you'll be able to take care of this issue.
This is your how-to right here. There are several steps in the process, so take your time if you're not familiar with doing this.
http://www.cisco.com/en/US/products/sw/secursw/ps5318/prod_installation_guide09186a00803e4727.html
Similar Messages
-
AE Deployment Errors in SDM - Upgrading from 5.1 to 5.2
Hello-
I'm in the process of upgrading Access enforcer on a Java standalone system from version 5.1 to 5.2.
Documentation provides a short list of project files that must be deployed in order - I have successfully deployed all others but am now facing the last require file - AEEAR4WS.ear.
Errors logs are below - Any advice or insight is greatly appreciated.
===========================================================================
Deployment started Mon Dec 01 16:22:04 EST 2008
===========================================================================
Starting Deployment of AEEAR4WS
Aborted: development component 'AEEAR4WS'/'sap.com'/'localhost'/'2007.12.08.00.49.25':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot deploy application sap.com/AEEAR4WS.. Reason: Error while reading [default web.xml] while deploying [AESelectSystemService_5_2/Config1] web application.; nested exception is: com.sap.engine.services.deploy.container.DeploymentException: <--Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='com.sap.engine.services.servlets_jsp.server.exceptions.WebDeploymentException: Error while reading [default web.xml] while deploying [AESelectSystemService_5_2/Config1] web application.
at com.sap.engine.services.servlets_jsp.server.container.WebContainerHelper.initXmls(WebContainerHelper.java:570)
at com.sap.engine.services.servlets_jsp.server.container.WebContainerHelper.deploy(WebContainerHelper.java:143)
at com.sap.engine.services.servlets_jsp.server.container.DeployAction.deploy(DeployAction.java:140)
at com.sap.engine.services.servlets_jsp.server.container.WebContainer.deploy(WebContainer.java:104)
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: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)
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.frame.ServiceException: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='ERROR:java.io.IOException: Access is denied', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key ERROR:java.io.IOException: Access is denied
at com.sap.engine.core.service630.container.PersistentHelper._getPersistentEntryFile(PersistentHelper.java:98)
at com.sap.engine.core.service630.container.PersistentHelper._getPersistentEntryStream(PersistentHelper.java:44)
at com.sap.engine.core.service630.container.PersistentHelperWrapper.getPersistentEntryStream(PersistentHelperWrapper.java:20)
at com.sap.engine.services.servlets_jsp.server.container.WebContainerHelper.initXmls(WebContainerHelper.java:566)
... 20 more
Caused by: java.io.IOException: Access is denied
at java.io.WinNTFileSystem.createFileExclusively(Native Method)
at java.io.File.createNewFile(File.java:828)
at com.sap.engine.core.service630.container.PersistentHelper._getPersistentEntryFile(PersistentHelper.java:55)
... 23 more
', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key com.sap.engine.services.servlets_jsp.server.exceptions.WebDeploymentException: Error while reading [default web.xml] while deploying [AESelectSystemService_5_2/Config1] web application.
at com.sap.engine.services.servlets_jsp.server.container.WebContainerHelper.initXmls(WebContainerHelper.java:570)
at com.sap.engine.services.servlets_jsp.server.container.WebContainerHelper.deploy(WebContainerHelper.java:143)
at com.sap.engine.services.servlets_jsp.server.container.DeployAction.deploy(DeployAction.java:140)
at com.sap.engine.services.servlets_jsp.server.container.WebContainer.deploy(WebContainer.java:104)
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: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)
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.frame.ServiceException: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='ERROR:java.io.IOException: Access is denied', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key ERROR:java.io.IOException: Access is denied
at com.sap.engine.core.service630.container.PersistentHelper._getPersistentEntryFile(PersistentHelper.java:98)
at com.sap.engine.core.service630.container.PersistentHelper._getPersistentEntryStream(PersistentHelper.java:44)
at com.sap.engine.core.service630.container.PersistentHelperWrapper.getPersistentEntryStream(PersistentHelperWrapper.java:20)
at com.sap.engine.services.servlets_jsp.server.container.WebContainerHelper.initXmls(WebContainerHelper.java:566)
... 20 more
Caused by: java.io.IOException: Access is denied
at java.io.WinNTFileSystem.createFileExclusively(Native Method)
at java.io.File.createNewFile(File.java:828)
at com.sap.engine.core.service630.container.PersistentHelper._getPersistentEntryFile(PersistentHelper.java:55)
... 23 more
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of AEEAR4WS finished with Error (Duration 31437 ms)Hi Christof,
The VB codes used in the excel sheets are only excel dependent. I don't think Microsoft has any backward compatability issue with 2003 to 2007. Similarly the VB commands from 5.1 is maintained in 7 so you should not face any major issues there too.
Badrish -
Error when Upgrading BI_UDI SP-9 to BI_UDI SP-20 from SDM
Hi Experts.
can any one solve my problem its urgent.
I am trying to upgrade BI_UDI SP-9 to BI_UDI SP-20,but it is giving me the error.
The below is the entire log of the Error.
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7186 - 630]/>
<!NAME[D:\usr\sap\BW3\DVEBMGS00\SDM\program\log\sdmlog20070730.log]/>
<!PATTERN[sdmlog20070730.log]/>
<!FORMATTER[com.sap.tc.logging.TraceFormatter(%24d %s: %m)]/>
<!ENCODING[UTF8]/>
<!LOGHEADER[END]/>
Jul 30, 2007 2:34:23 PM Info:
Jul 30, 2007 2:34:24 PM Info: ============================================
Jul 30, 2007 2:34:24 PM Info: = Starting to execute command 'server' =
Jul 30, 2007 2:34:24 PM Info: ============================================
Jul 30, 2007 2:34:24 PM Info: Starting SDM - Software Deployment Manager...
Jul 30, 2007 2:34:25 PM Info: tc/SL/SDM/SDM/sap.com/SAP AG/6.4020.00.0000.20070308110902.0000
Jul 30, 2007 2:34:27 PM Info: SDM operation mode successfully set to: Integrated
Jul 30, 2007 2:34:28 PM Info: JStartupFramework is requesting to start the SDM Server.
Jul 30, 2007 2:34:28 PM Info: Start the SDM Server integrated in the JStartupFramework.
Jul 30, 2007 2:34:28 PM Info: Initializing Network Manager (50017)
Jul 30, 2007 2:34:28 PM Info: Starting SDM Server listening on port 50018
Jul 30, 2007 2:34:28 PM Info: SDM started successfully.
Jul 31, 2007 9:11:50 AM Info: Opened client connection to HostName (IP address HostName/192.158.3.36, remote port 4072)
Jul 31, 2007 9:11:50 AM Info: Request for Logon as admin accepted
Jul 31, 2007 9:12:26 AM Info: Loading archive 'E:\sap-download\downloads\javasp20\BIUDI20_0-20000143.SCA'
Jul 31, 2007 9:12:34 AM Info: Actions per selected component:
Jul 31, 2007 9:12:34 AM Info: Update: Selected development component 'com.sap.ip.bi.sdk.dac.connector.xmla'/'sap.com'/'SAP AG'/'350.20070308111013.0000'/'1' updates currently deployed development component 'com.sap.ip.bi.sdk.dac.connector.xmla'/'sap.com'/'SAP AG'/'350.20041022092304.0000'/'0'.
Jul 31, 2007 9:12:34 AM Info: No action: Selected development component 'com.sap.ip.bi.sdk.dac.connector.odbo'/'sap.com'/'SAP AG'/'350.20061110093918.0000'/'1' will not update currently deployed development component 'com.sap.ip.bi.sdk.dac.connector.odbo'/'sap.com'/'SAP AG'/'350.20061110093918.0000'/'0'.
Jul 31, 2007 9:12:34 AM Info: Update: Selected development component 'com.sap.ip.bi.sdk.monitoring'/'sap.com'/'SAP AG'/'350.20061110093918.0000'/'1' updates currently deployed development component 'com.sap.ip.bi.sdk.monitoring'/'sap.com'/'SAP AG'/'350.20041022092304.0000'/'0'.
Jul 31, 2007 9:12:34 AM Info: Update: Selected software component 'BI_UDI'/'sap.com'/'SAP AG'/'1000.350.0.20.0.20070322073220''/'1' updates currently deployed software component 'BI_UDI'/'sap.com'/'SAP AG'/'1000.350.0.9.0.20041025073430''/'0'.
Jul 31, 2007 9:12:34 AM Info: Update: Selected development component 'com.sap.ip.bi.sdk.datasource.sys'/'sap.com'/'SAP AG'/'350.20061110093918.0000'/'1' updates currently deployed development component 'com.sap.ip.bi.sdk.datasource.sys'/'sap.com'/'SAP AG'/'350.20041022092304.0000'/'0'.
Jul 31, 2007 9:12:34 AM Info: No action: Selected development component 'com.sap.ip.bi.sdk'/'sap.com'/'SAP AG'/'350.20070308111013.0000'/'1' will not update currently deployed development component 'com.sap.ip.bi.sdk'/'sap.com'/'SAP AG'/'350.20070308111013.0000'/'0'.
Jul 31, 2007 9:12:34 AM Info: No action: Selected development component 'bi/mmr/browser_ea'/'sap.com'/'MAIN_BIMMRVAL_D'/'1183786'/'1' will not update currently deployed development component 'bi/mmr/browser_ea'/'sap.com'/'MAIN_BIMMRVAL_D'/'1183786'/'0'.
Jul 31, 2007 9:12:34 AM Info: Update: Selected development component 'com.sap.ip.bi.sdk.dac.connector.checkxmla'/'sap.com'/'SAP AG'/'350.20061110093918.0000'/'1' updates currently deployed development component 'com.sap.ip.bi.sdk.dac.connector.checkxmla'/'sap.com'/'SAP AG'/'350.20041022092304.0000'/'0'.
Jul 31, 2007 9:12:34 AM Info: No action: Selected development component 'bi/mmr/cwm_1.0_source'/'sap.com'/'SAP AG'/'350.1183777.000'/'1' will not update currently deployed development component 'bi/mmr/cwm_1.0_source'/'sap.com'/'SAP AG'/'350.1183777.000'/'0'.
Jul 31, 2007 9:12:34 AM Info: Update: Selected development component 'com.sap.ip.bi.sdk.dac.olap'/'sap.com'/'SAP AG'/'350.20070308111013.0000'/'1' updates currently deployed development component 'com.sap.ip.bi.sdk.dac.olap'/'sap.com'/'SAP AG'/'350.20041022092304.0000'/'0'.
Jul 31, 2007 9:12:34 AM Info: Update: Selected development component 'com.sap.ip.bi.sdk.datasource.sync'/'sap.com'/'SAP AG'/'350.20061110093918.0000'/'1' updates currently deployed development component 'com.sap.ip.bi.sdk.datasource.sync'/'sap.com'/'SAP AG'/'350.20041022092304.0000'/'0'.
Jul 31, 2007 9:12:34 AM Info: No action: Selected development component 'com.sap.ip.bi.sdk.dac.connector.checksapq'/'sap.com'/'SAP AG'/'350.20061110093918.0000'/'1' will not update currently deployed development component 'com.sap.ip.bi.sdk.dac.connector.checksapq'/'sap.com'/'SAP AG'/'350.20061110093918.0000'/'0'.
Jul 31, 2007 9:12:34 AM Info: No action: Selected development component 'com.sap.ip.bi.sdk.dac.connector.jdbc'/'sap.com'/'SAP AG'/'350.20061110093918.0000'/'1' will not update currently deployed development component 'com.sap.ip.bi.sdk.dac.connector.jdbc'/'sap.com'/'SAP AG'/'350.20061110093918.0000'/'0'.
Jul 31, 2007 9:12:34 AM Info: Update: Selected development component 'com.sap.ip.bi.sdk.datasource.ds'/'sap.com'/'SAP AG'/'350.20061110093918.0000'/'1' updates currently deployed development component 'com.sap.ip.bi.sdk.datasource.ds'/'sap.com'/'SAP AG'/'350.20041022092304.0000'/'0'.
Jul 31, 2007 9:12:34 AM Info: Initial deployment: Selected development component 'com.sap.ip.bi.sdk.dac.connector.xmla.proxy.ws'/'sap.com'/'SAP AG'/'350.20061110093918.0000'/'1' will be deployed.
Jul 31, 2007 9:12:34 AM Info: Update: Selected development component 'com.sap.ip.bi.sdk.datasource.fields'/'sap.com'/'SAP AG'/'350.20061110093918.0000'/'1' updates currently deployed development component 'com.sap.ip.bi.sdk.datasource.fields'/'sap.com'/'SAP AG'/'350.20041022092304.0000'/'0'.
Jul 31, 2007 9:12:34 AM Info: No action: Selected development component 'com.sap.ip.bi.sdk.dac.connector.checkjdbc'/'sap.com'/'SAP AG'/'350.20061110093918.0000'/'1' will not update currently deployed development component 'com.sap.ip.bi.sdk.dac.connector.checkjdbc'/'sap.com'/'SAP AG'/'350.20061110093918.0000'/'0'.
Jul 31, 2007 9:12:34 AM Info: No action: Selected development component 'com.sap.ip.bi.sdk.dac.connector.checkodbo'/'sap.com'/'SAP AG'/'350.20061110093918.0000'/'1' will not update currently deployed development component 'com.sap.ip.bi.sdk.dac.connector.checkodbo'/'sap.com'/'SAP AG'/'350.20061110093918.0000'/'0'.
Jul 31, 2007 9:12:34 AM Info: No action: Selected development component 'com.sap.ip.bi.sdk.dac.connector.sapq'/'sap.com'/'SAP AG'/'350.20061110093918.0000'/'1' will not update currently deployed development component 'com.sap.ip.bi.sdk.dac.connector.sapq'/'sap.com'/'SAP AG'/'350.20061110093918.0000'/'0'.
Jul 31, 2007 9:12:34 AM Info: No action: Selected development component 'bi/mmr/bi_4.0'/'sap.com'/'SAP AG'/'350.1183781.000'/'1' will not update currently deployed development component 'bi/mmr/bi_4.0'/'sap.com'/'SAP AG'/'350.1183781.000'/'0'.
Jul 31, 2007 9:12:43 AM Info: Saved current Engine state.
Jul 31, 2007 9:12:44 AM Info: Starting: Update: Selected development component 'com.sap.ip.bi.sdk.dac.connector.xmla'/'sap.com'/'SAP AG'/'350.20070308111013.0000'/'1' updates currently deployed development component 'com.sap.ip.bi.sdk.dac.connector.xmla'/'sap.com'/'SAP AG'/'350.20041022092304.0000'/'0'.
Jul 31, 2007 9:12:44 AM Info: SDA to be deployed: D:\usr\sap\BW3\DVEBMGS00\SDM\root\origin\sap.com\com.sap.ip.bi.sdk.dac.connector.xmla\SAP AG\1\350.20070308111013.0000\bi_sdk_xmla.rar
Jul 31, 2007 9:12:44 AM Info: Software type of SDA: single-module
Jul 31, 2007 9:12:45 AM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Module) *****
Jul 31, 2007 9:18:24 AM Info: Begin of log messages of the target system:
07/07/31 09:14:05 - ***********************************************************
07/07/31 09:14:05 - Start updating archive file...
07/07/31 09:14:06 - Archive file updated successfully for 47ms.
07/07/31 09:14:06 - Start updating...
07/07/31 09:14:21 - Archive file uploaded to server for 94ms.
07/07/31 09:18:24 - ERROR: Not updated. Deploy Service returned ERROR:
java.rmi.RemoteException: Cannot deploy application sap.com/com.sap.ip.bi.sdk.dac.connector.xmla..
Reason: Cannot access methods of instance of class "com.sap.ip.bi.sdk.dac.connector.xmla.XmlaManagedConnectionFactory". Possible reasons: the class is not public and is in another package, the current method does not have access to the appropriate zero-argument constructor or there is no such method.; nested exception is:
com.sap.engine.services.deploy.container.DeploymentException: <--Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='com.sap.engine.services.connector.exceptions.BaseDeploymentException: Cannot access methods of instance of class "com.sap.ip.bi.sdk.dac.connector.xmla.XmlaManagedConnectionFactory". Possible reasons: the class is not public and is in another package, the current method does not have access to the appropriate zero-argument constructor or there is no such method.
at com.sap.engine.services.connector.jca.deploy.DeployAdmin.instantiateMCF(DeployAdmin.java:1077)
at com.sap.engine.services.connector.jca.deploy.ContainerImpl.makeUpdate(ContainerImpl.java:913)
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:321)
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)
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.update(DeployServiceImpl.java:774)
at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:926)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:312)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:199)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Caused by: java.lang.NoSuchMethodException: com.sap.ip.bi.sdk.dac.connector.xmla.XmlaManagedConnectionFactory.setLogonmethod(java.lang.String)
at java.lang.Class.getMethod(Class.java:986)
at com.sap.engine.services.connector.jca.deploy.DeployAdmin.instantiateMCF(DeployAdmin.java:1057)
... 18 more
', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key com.sap.engine.services.connector.exceptions.BaseDeploymentException: Cannot access methods of instance of class "com.sap.ip.bi.sdk.dac.connector.xmla.XmlaManagedConnectionFactory". Possible reasons: the class is not public and is in another package, the current method does not have access to the appropriate zero-argument constructor or there is no such method.
at com.sap.engine.services.connector.jca.deploy.DeployAdmin.instantiateMCF(DeployAdmin.java:1077)
at com.sap.engine.services.connector.jca.deploy.ContainerImpl.makeUpdate(ContainerImpl.java:913)
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:321)
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)
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.update(DeployServiceImpl.java:774)
at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:926)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:312)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:199)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Caused by: java.lang.NoSuchMethodException: com.sap.ip.bi.sdk.dac.connector.xmla.XmlaManagedConnectionFactory.setLogonmethod(java.lang.String)
at java.lang.Class.getMethod(Class.java:986)
at com.sap.engine.services.connector.jca.deploy.DeployAdmin.instantiateMCF(DeployAdmin.java:1057)
... 18 more
at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:789)
at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:926)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:312)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:199)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Caused by: com.sap.engine.services.deploy.container.DeploymentException: <--Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='com.sap.engine.services.connector.exceptions.BaseDeploymentException: Cannot access methods of instance of class "com.sap.ip.bi.sdk.dac.connector.xmla.XmlaManagedConnectionFactory". Possible reasons: the class is not public and is in another package, the current method does not have access to the appropriate zero-argument constructor or there is no such method.
at com.sap.engine.services.connector.jca.deploy.DeployAdmin.instantiateMCF(DeployAdmin.java:1077)
at com.sap.engine.services.connector.jca.deploy.ContainerImpl.makeUpdate(ContainerImpl.java:913)
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:321)
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)
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.update(DeployServiceImpl.java:774)
at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:926)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:312)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:199)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Caused by: java.lang.NoSuchMethodException: com.sap.ip.bi.sdk.dac.connector.xmla.XmlaManagedConnectionFactory.setLogonmethod(java.lang.String)
at java.lang.Class.getMethod(Class.java:986)
at com.sap.engine.services.connector.jca.deploy.DeployAdmin.instantiateMCF(DeployAdmin.java:1057)
... 18 more
', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key com.sap.engine.services.connector.exceptions.BaseDeploymentException: Cannot access methods of instance of class "com.sap.ip.bi.sdk.dac.connector.xmla.XmlaManagedConnectionFactory". Possible reasons: the class is not public and is in another package, the current method does not have access to the appropriate zero-argument constructor or there is no such method.
at com.sap.engine.services.connector.jca.deploy.DeployAdmin.instantiateMCF(DeployAdmin.java:1077)
at com.sap.engine.services.connector.jca.deploy.ContainerImpl.makeUpdate(ContainerImpl.java:913)
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:321)
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)
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.update(DeployServiceImpl.java:774)
at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:926)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:312)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:199)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Caused by: java.lang.NoSuchMethodException: com.sap.ip.bi.sdk.dac.connector.xmla.XmlaManagedConnectionFactory.setLogonmethod(java.lang.String)
at java.lang.Class.getMethod(Class.java:986)
at com.sap.engine.services.connector.jca.deploy.DeployAdmin.instantiateMCF(DeployAdmin.java:1057)
... 18 more
at com.sap.engine.services.connector.exceptions.BaseDeploymentException.writeReplace(BaseDeploymentException.java:46)
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.defaultWriteFields(ObjectOutputStream.java:1332)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
at com.sap.engine.services.rmi_p4.DispatchImpl.throwException(DispatchImpl.java:145)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:314)
... 8 more
For detailed information see the log file of the Deploy Service.
07/07/31 09:18:24 - ***********************************************************
Jul 31, 2007 9:18:24 AM Info: End of log messages of the target system.
Jul 31, 2007 9:18:24 AM Info: ***** End of SAP J2EE Engine Deployment (J2EE Module) *****
Jul 31, 2007 9:18:25 AM Error: Aborted: development component 'com.sap.ip.bi.sdk.dac.connector.xmla'/'sap.com'/'SAP AG'/'350.20070308111013.0000'/'1', grouped by software component 'BI_UDI'/'sap.com'/'SAP AG'/'1000.350.0.20.0.20070322073220''/'1':
Caught exception during module deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot deploy application sap.com/com.sap.ip.bi.sdk.dac.connector.xmla..
Reason: Cannot access methods of instance of class "com.sap.ip.bi.sdk.dac.connector.xmla.XmlaManagedConnectionFactory". Possible reasons: the class is not public and is in another package, the current method does not have access to the appropriate zero-argument constructor or there is no such method.; nested exception is:
com.sap.engine.services.deploy.container.DeploymentException: <--Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='com.sap.engine.services.connector.exceptions.BaseDeploymentException: Cannot access methods of instance of class "com.sap.ip.bi.sdk.dac.connector.xmla.XmlaManagedConnectionFactory". Possible reasons: the class is not public and is in another package, the current method does not have access to the appropriate zero-argument constructor or there is no such method.
at com.sap.engine.services.connector.jca.deploy.DeployAdmin.instantiateMCF(DeployAdmin.java:1077)
at com.sap.engine.services.connector.jca.deploy.ContainerImpl.makeUpdate(ContainerImpl.java:913)
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:321)
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)
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.update(DeployServiceImpl.java:774)
at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:926)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:312)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:199)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Caused by: java.lang.NoSuchMethodException: com.sap.ip.bi.sdk.dac.connector.xmla.XmlaManagedConnectionFactory.setLogonmethod(java.lang.String)
at java.lang.Class.getMethod(Class.java:986)
at com.sap.engine.services.connector.jca.deploy.DeployAdmin.instantiateMCF(DeployAdmin.java:1057)
... 18 more
', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key com.sap.engine.services.connector.exceptions.BaseDeploymentException: Cannot access methods of instance of class "com.sap.ip.bi.sdk.dac.connector.xmla.XmlaManagedConnectionFactory". Possible reasons: the class is not public and is in another package, the current method does not have access to the appropriate zero-argument constructor or there is no such method.
at com.sap.engine.services.connector.jca.deploy.DeployAdmin.instantiateMCF(DeployAdmin.java:1077)
at com.sap.engine.services.connector.jca.deploy.ContainerImpl.makeUpdate(ContainerImpl.java:913)
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:321)
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)
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.update(DeployServiceImpl.java:774)
at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:926)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:312)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:199)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Caused by: java.lang.NoSuchMethodException: com.sap.ip.bi.sdk.dac.connector.xmla.XmlaManagedConnectionFactory.setLogonmethod(java.lang.String)
at java.lang.Class.getMethod(Class.java:986)
at com.sap.engine.services.connector.jca.deploy.DeployAdmin.instantiateMCF(DeployAdmin.java:1057)
... 18 more
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineSingleModuleOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Jul 31, 2007 9:18:25 AM Info: Starting to save the repository
Jul 31, 2007 9:18:25 AM Info: Finished saving the repository
Jul 31, 2007 9:18:26 AM Info: Starting: Update: Selected software component 'BI_UDI'/'sap.com'/'SAP AG'/'1000.350.0.20.0.20070322073220''/'1' updates currently deployed software component 'BI_UDI'/'sap.com'/'SAP AG'/'1000.350.0.9.0.20041025073430''/'0'.
Jul 31, 2007 9:18:26 AM Error: Aborted: software component 'BI_UDI'/'sap.com'/'SAP AG'/'1000.350.0.20.0.20070322073220''/'1':
Failed deployment of SDAs:
development component 'com.sap.ip.bi.sdk.dac.connector.xmla'/'sap.com'/'SAP AG'/'350.20070308111013.0000'/'1' : aborted
Please, look at error logs above for more information!
Jul 31, 2007 9:18:26 AM Info: Starting to save the repository
Jul 31, 2007 9:18:26 AM Info: Finished saving the repository
Jul 31, 2007 9:18:27 AM Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
Thanks in Advance
regards
KenI have just solved this problem. The symptom is the "No server is running"
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.
The cause for my case is that the server contains more than one NIC. P4 can't bind to correct NIC.
The solution is to follow SAP Notes 609603 to configure the "bindHost" property of p4 services using config tool. -
SDM not working after upgrade to SP12
I have just upgraded my Netweaver from SP9 to SP12. After doing the upgrade, SDM no longer runs and attempting to manually start it also fails.
A colleague of mine who also installed SP12 has the same problem.
Any suggestions?
WalterThe SDM isn't crashing.. it just seems to start, and then immediately stop itself.
Here is the Developer Trace:
trc file: "C:usrsapA2IJC00workdev_sdm", trc level: 1, release: "640"
node name : sdm
pid : 5420
system name : A2I
system nr. : 00
started at : Mon Aug 15 17:08:05 2005
arguments :
arg[00] : C:usrsapA2IJC00/j2ee/os_libs/jlaunch.exe
arg[01] : pf=C:usrsapA2ISYSprofileA2I_JC00_p030629
arg[02] : -DSAPINFO=A2I_00_sdm
arg[03] : pf=C:usrsapA2ISYSprofileA2I_JC00_p030629
JStartupReadInstanceProperties: read instance properties [C:usrsapA2IJC00SDMprogramconfigsdm_jstartup.properties]
-> ms host :
-> ms port :
-> OS libs : C:usrsapA2IJC00j2eeos_libs
-> Admin URL :
-> run mode : NORMAL
-> run action : NONE
-> enabled : yes
Used property files
-> files [00] : C:usrsapA2IJC00SDMprogramconfigsdm_jstartup.properties
Instance properties
-> ms host :
-> ms port :
-> os libs : C:usrsapA2IJC00j2eeos_libs
-> admin URL :
-> run mode : NORMAL
-> run action : NONE
-> enabled : yes
Bootstrap nodes
Worker nodes
-> [00] sdm : C:usrsapA2IJC00SDMprogramconfigsdm_jstartup.properties
[Thr 4724] Mon Aug 15 17:08:05 2005
[Thr 4724] JLaunchRequestQueueInit: create named pipe for ipc
[Thr 4724] JLaunchRequestQueueInit: create pipe listener thread
[Thr 5440] JLaunchRequestFunc: Thread 5440 started as listener thread for np messages.
[Thr 5612] WaitSyncSemThread: Thread 5612 started as semaphore monitor thread.
[Thr 4724] NiInit2: NI already initialized; param 'maxHandles' ignored
[Thr 4724] [Node: SDM] java home is set by profile parameter
Java Home: C:j2sdk1.4.2_08
JStartupIReadSection: read node properties [sdm]
-> node name : SDM
-> node type : sdm
-> java path : C:j2sdk1.4.2_08
-> java parameters :
-> java vm version : 1.4.2_08-b03
-> java vm vendor : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
-> java vm type : server
-> java vm cpu : x86
-> heap size : 128M
-> root path : C:usrsapA2IJC00SDMprogram
-> class path : C:usrsapA2IJC00SDMprogrambinSDM.jar
-> OS libs path : C:usrsapA2IJC00j2eeos_libs
-> main class : SDMInternal
-> framework class : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path : C:usrsapA2IJC00j2eeos_libsjstartup.jar
-> shutdown class : com.sap.sdm.jstartup.shutdown.InternalShutDown
-> parameters : server sdmhome=C:usrsap/A2I/JC00/SDM/program
-> debuggable : yes
-> debug mode : no
-> debug port : 50002
-> shutdown timeout: 120000
[Thr 4724] JLaunchISetDebugMode: set debug mode [no]
[Thr 4288] JLaunchIStartFunc: Thread 4288 started as Java VM thread.
JHVM_LoadJavaVM: VM Arguments of node [SDM]
-> stack : 262144 Bytes
-> arg[ 0]: exit
-> arg[ 1]: abort
-> arg[ 2]: -Dsys.global.dir=C:usrsapA2ISYSglobal
-> arg[ 3]: -Dapplication.home=C:usrsapA2IJC00j2eeos_libs
-> arg[ 4]: -Djava.class.path=C:usrsapA2IJC00j2eeos_libsjstartup.jar;C:usrsapA2IJC00SDMprogrambinSDM.jar
-> arg[ 5]: -Djava.library.path=C:j2sdk1.4.2_08jrebinserver;C:j2sdk1.4.2_08jrebin;C:j2sdk1.4.2_08bin;C:usrsapA2IJC00j2eeos_libs;c:sapdbprogramsbin;c:sapdbprogramspgm;C:PROGRA~1SECUDESECUDE~1;C:WINDOWSsystem32;C:WINDOWS;C:WINDOWSSystem32Wbem;C:Program FilesSymantecpcAnywhere;C:Program FilesMicrosoft SQL Server80ToolsBinn;C:Program FilesPerforce;C:Program FilesZipGenius 5;C:Program FilesCommon FilesOpSessionShared;C:Program FilesCommon FilesOpSessionViewer Shared;C:usrsapA2ISCS01exe;C:usrsapA2IJC00exe;C:usrsapA2ISYSexerun
-> arg[ 6]: -Dmemory.manager=128M
-> arg[ 7]: -Xmx128M
-> arg[ 8]: -DLoadBalanceRestricted=no
-> arg[ 9]: -Djstartup.mode=JCONTROL
-> arg[ 10]: -Djstartup.ownProcessId=5420
-> arg[ 11]: -Djstartup.ownHardwareId=A0497202134
-> arg[ 12]: -Djstartup.whoami=sdm
-> arg[ 13]: -Djstartup.debuggable=yes
-> arg[ 14]: -DSAPINFO=A2I_00_sdm
-> arg[ 15]: -DSAPSTARTUP=1
-> arg[ 16]: -DSAPSYSTEM=00
-> arg[ 17]: -DSAPSYSTEMNAME=A2I
-> arg[ 18]: -DSAPMYNAME=p030629_A2I_00
-> arg[ 19]: -DSAPDBHOST=
-> arg[ 20]: -Dj2ee.dbhost=p030629
[Thr 4288] JHVM_LoadJavaVM: Java VM created OK.
JHVM_BuildArgumentList: main method arguments of node [SDM]
-> arg[ 0]: server
-> arg[ 1]: sdmhome=C:usrsap/A2I/JC00/SDM/program
[Thr 5440] Mon Aug 15 17:08:12 2005
[Thr 5440] JLaunchRequestFunc: receive command:17, argument:0 from pid:4508
[Thr 5440] JLaunchIShutdownInvoke: set shutdown interval (stop:1124114892/end:1124115012/TO:120)
[Thr 5440] JLaunchProcessCommand: Invoke VM Shutdown
[Thr 5440] JHVM_FrameworkShutdownDirect: invoke direct shutdown
[Thr 5440] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
[Thr 5440] JLaunchISetState: change state from [Initial (0)] to [Stopping (5)]
[Thr 1552] JLaunchIExitJava: exit hook is called (rc=0)
[Thr 1552] JLaunchCloseProgram: good bye (exitcode=0)
Thanks to everyone who has helped so far.
Walter -
Patching Web AS Java, upgrading SDM results in version conflict
Hi,
We are currently patching Web AS Java for our XI 3.0 system which is based on Netweaver 2004 system. Since patching Java with this Netweaver version is implemented through SDM only, unlike for Netweaver 2004s which uses JSPM, we are having problems while upgrading SDM which is a requirement for patching web AS Java. Please see the error below:
SpecVersion of new SDM is older than installed SDM:(location of SDM)
SDM terminated with errors: Exit code: 4
What is the best thing do with this? Shall we continue upgrading using our SDM version? Or shall we have to find another SDM version. Also, how can we determine the patch level of SDM?
Thanks and God Bless!
Regards,
Jennahgot to you java home page:
http://system.fqdn:5<SYSNO>00/index.html
Goto system information.
Select all components:
search for SDM;
sap.com tc_SL_SDM_Client null (7.0010.20061019070020.0000) SAP AG SAP AG 20070505222412 null/null
sap.com tc_SL_SDM_Util null (7.0010.20061019070020.0000) SAP AG SAP AG 20070505222418 null/null
http://help.sap.com/saphelp_nw04/helpdata/en/76/fb72ec091f4bf8a2d8ba321bb7e8d9/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/22/a7663bb3808c1fe10000000a114084/frameset.htm -
Upgrade EP6 SP11 to EP6 SP13 - SDM Return Code: 4
Hi,
We are installing EP6 Sp13 on our existing Ep6 SP11 and we are getting the below error during the installation phase "Deploy via SDM/J2EE". Error is as shown in the
callSdmViaSapinst.log :
05/09/29 14:14:10 - ***********************************************************
05/09/29 14:14:11 - Start updating EAR file...
05/09/29 14:14:11 - start-up mode is lazy
05/09/29 14:14:11 - EAR file updated successfully for 218ms.
05/09/29 14:14:11 - Start updating...
05/09/29 14:14:11 - EAR file uploaded to server for 110ms.
05/09/29 14:14:13 - ERROR: Not updated. Deploy Service returned ERROR:
java.rmi.RemoteException: Cannot deploy application sap.com/com.sapportals.connectors.sap..
Reason: Exception during generation of components of application sap.com/com.sapportals.connectors.sap in container connector.; nested exception is:
com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application sap.com/com.sapportals.connectors.sap in container connector.
at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:592)
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:294)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:119)
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:95)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:159)
Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application sap.com/com.sapportals.connectors.sap in container connector.
at com.sap.engine.services.deploy.server.application.UpdateTransaction.makeComponents(UpdateTransaction.java:382)
at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:379)
at com.sap.engine.services.deploy.server.application.UpdateTransaction.begin(UpdateTransaction.java:148)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:290)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:323)
at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3033)
at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:580)
... 10 more
Caused by: java.lang.NullPointerException
at com.sap.engine.services.connector.jca.deploy.DeployAdmin.mergeDescriptorsConfigProps(DeployAdmin.java:3068)
at com.sap.engine.services.connector.jca.deploy.DeployAdmin.mergeDescriptors(DeployAdmin.java:2976)
at com.sap.engine.services.connector.jca.deploy.ContainerImpl.makeUpdate(ContainerImpl.java:736)
at com.sap.engine.services.deploy.server.application.UpdateTransaction.makeComponents(UpdateTransaction.java:376)
... 16 more
For detailed information see the log file of the Deploy Service.
Thanks.
regards,
MikeHi Mike,
I would first try to stop the installation and start again to see if it continues for where it stopped.
If this do not works, I would try to stop the patch upgrade,
start the SDM and undeploy the com.sapportals.connectors.sap.sda, stop again the SDM and then restart the upgrade.
You also might like to check the SAP Notes 841299, 751175, 750360, 710966 as your problem seems to be related to the sap connectors.
Hope this helps,
Robert -
HI, we have upgraded EP6.0 SP9 to EP 7.0 Sp7. when i check in the System information page i am able to see all the applications are running. But in SDM I am unable to see SDM port number. Its givig SDM port : null. can you please tell me why SDM port number is not displayed in the system information page.
Regards,
KrishnamYou developed your application with Java 1.5 while the run time system is on Java 1.4, which wont work. As per SAP note [718946|https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_bc_wd/~form/handler%7b5f4150503d3030323030363832353030303030303031393732265f4556454e543d444953504c4159265f4e4e554d3d373138393439%7d], your IDE should never be on a higher version than your Web AS.
-
Upgrading from EP6 SPS09 to EP6 SPS13 - SDM returncode 4
Hi SDN,
I tried to patch my portal EP6SPS09 to EP6SPS13 . After reaching the installation step "Deploy EAR File" the update procedure stops at the seventh step "Deploy via SDM" with the error message SDM could not start returncode 4.
I have seen this problem in serveral updates (SP11, SP12) before and I was always able to fix this issue, but not in this case.
So I investigated this problem and found the following error in callviaSDM.log
05/08/06 14:49:03 - ***********************************************************
05/08/06 14:49:05 - Start updating EAR file...
05/08/06 14:49:05 - start-up mode is lazy
05/08/06 14:49:08 - EAR file updated successfully for 3765ms.
05/08/06 14:49:08 - Start updating...
05/08/06 14:49:09 - EAR file uploaded to server for 621ms.
05/08/06 14:59:09 - ERROR: Not updated. Deploy Service returned ERROR:
java.rmi.RemoteException: Already started operation with application sap.com/irj in the cluster. No other operation with this application is allowed at the moment..
Reason: Cannot lock [2005080614452393400000sgisbruap33t...............205004850, DEPLOY_LOCK_AREA, sap.com/irj, X]; it is in use by the same owner.; nested exception is:
com.sap.engine.frame.core.locking.LockException: Cannot lock [2005080614452393400000sgisbruap33t...............205004850, DEPLOY_LOCK_AREA, sap.com/irj, X]; it is in use by the same owner.
at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:592)
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:294)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:119)
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:95)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:159)
Caused by: com.sap.engine.frame.core.locking.LockException: Cannot lock [2005080614452393400000sgisbruap33t...............205004850, DEPLOY_LOCK_AREA, sap.com/irj, X]; it is in use by the same owner.
at com.sap.engine.core.locking.impl3.LockingManagerImpl.lockInternal(LockingManagerImpl.java:160)
at com.sap.engine.core.locking.AbstractLockingManagerImpl.lock(AbstractLockingManagerImpl.java:420)
at com.sap.engine.core.locking.AbstractLockingManagerImpl.lock(AbstractLockingManagerImpl.java:1090)
at com.sap.engine.services.deploy.server.TransactionManager.lockApplication(TransactionManager.java:127)
at com.sap.engine.services.deploy.server.TransactionManager.registerTransactionWithLock(TransactionManager.java:89)
at com.sap.engine.services.deploy.server.DeployServiceImpl.registerTransactionWithLock(DeployServiceImpl.java:1847)
at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3031)
at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:580)
... 10 more
For detailed information see the log file of the Deploy Service.
05/08/06 14:59:09 - ***********************************************************
Aug 6, 2005 2:59:09 PM Info: End of log messages of the target system.
So I looked for a regarding note and found the sap note: 710966 DEPLOY_LOCK error during upgrade . I check the lock status of my sap.com/irj application.
The sap.com/irj is not running properly or the sap.com/irj is not installed.
So I reistalled the whole system EP6 SR1 and repeated the upgrade. The Upgrade of the WAS runs successfully, but the EP upgrade crashes again. I do not have a cluster version. I tried to upgrade my portal with the safe mode and without safe mode.
Has anyone of you installed EP6 SPS13 successfully?
My system:
1 CPU
Oracle DB
JVM 1.4.2_07
OS Win2000
Please help.
Best Regards,
Olaf Reiss
Message was edited by: Olaf ReissIn addition:
The last log entry in my default trace shows the lock (see the log below).
#1.5#00A0D1B98E97003F0000003700000ABC0003FDCE40F58480#1123487225039#com.sap.portal.pcd.Gl.Admin#sap.com/irj#com.sap.portal.pcd.Gl.Admin#Guest#108####9627f24107e011da8c3d00a0d1b98e97#SAPEngine_Application_Thread[impl:3]_13##0#0#Info#1#/System/Server#Plain###[Pcd.getServiceUser] Found service user#
#1.5#00A0D1B98E97003F0000004C00000ABC0003FDCE41B1C36F#1123487237376#com.sap.portal.prt.runtime#sap.com/irj#com.sap.portal.prt.runtime#Guest#108####9627f24107e011da8c3d00a0d1b98e97#SAPEngine_Application_Thread[impl:3]_13##0#0#Error#1#/System/Server#Plain###[LoggerManager] Logger appr_logger - definition not found! All mesagges will be send to the location com.sap.portal.portal. Please define the locationName in logger.xml. Method call stack - see trace message in com.sap.portal.runtime#
#1.5#00A0D1B98E9700400000000100000ABC0003FDCFC6423603#1123493756583#com.sap.engine.services.deploy##com.sap.engine.services.deploy#Administrator#243####6bc3dce007ee11da8eff00a0d1b98e97#SAPEngine_Application_Thread[impl:3]_31##0#0#Error#1#/System/Server#Java#deploy_5070##Already started operation with application sap.com/irj in the cluster. No other operation with this application is allowed at the moment.#1#sap.com/irj#
#1.5#00A0D1B98E9700400000000200000ABC0003FDCFC642384A#1123493756583#com.sap.engine.services.deploy##com.sap.engine.services.deploy#Administrator#243####6bc3dce007ee11da8eff00a0d1b98e97#SAPEngine_Application_Thread[impl:3]_31##0#0#Error#1#/System/Audit#Java###Exception #1#com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Already started operation with application sap.com/irj in the cluster. No other operation with this application is allowed at the moment.
at com.sap.engine.services.deploy.server.TransactionManager.lockApplication(TransactionManager.java:138)
at com.sap.engine.services.deploy.server.TransactionManager.registerTransactionWithLock(TransactionManager.java:89)
at com.sap.engine.services.deploy.server.DeployServiceImpl.registerTransactionWithLock(DeployServiceImpl.java:1847)
at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3031)
at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:580)
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:294)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:119)
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:95)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:159)
Caused by: com.sap.engine.frame.core.locking.LockException: Cannot lock [2005080809460049600000sgisbruap33t...............205004850, DEPLOY_LOCK_AREA, sap.com/irj, X]; it is in use by the same owner.
at com.sap.engine.core.locking.impl3.LockingManagerImpl.lockInternal(LockingManagerImpl.java:160)
at com.sap.engine.core.locking.AbstractLockingManagerImpl.lock(AbstractLockingManagerImpl.java:420)
at com.sap.engine.core.locking.AbstractLockingManagerImpl.lock(AbstractLockingManagerImpl.java:1090)
at com.sap.engine.services.deploy.server.TransactionManager.lockApplication(TransactionManager.java:127)
... 14 more
#1.5#00A0D1B98E9700410000000100000ABC0003FDD02BBCE425#1123495458931#com.sap.engine.services.deploy##com.sap.engine.services.deploy#Administrator#244####c8de4c3007f311daa13f00a0d1b98e97#3 Telnet 172.28.138.95 Mon Aug 08 12:03:48 CEST 2005##0#0#Error#1#/System/Server#Java#deploy_5005##Application com.sap/irj is not deployed on cluster element Server 0 20_50048 and it is not possible to get its status.#3#com.sap/irj#Server 0 20_50048#get its status#
#1.5#00A0D1B98E9700410000000200000ABC0003FDD02BBCE60C#1123495458931#com.sap.engine.services.deploy##com.sap.engine.services.deploy#Administrator#244####c8de4c3007f311daa13f00a0d1b98e97#3 Telnet 172.28.138.95 Mon Aug 08 12:03:48 CEST 2005##0#0#Error#1#/System/Audit#Java###Exception #1#com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Application com.sap/irj is not deployed on cluster element Server 0 20_50048 and it is not possible to get its status.
at com.sap.engine.services.deploy.server.DeployServiceImpl.getStatus(DeployServiceImpl.java:3712)
at com.sap.engine.services.deploy.server.DeployServiceImpl.getApplicationStatus(DeployServiceImpl.java:1256)
at com.sap.engine.services.deploy.command.GetStatusCommand.exec(GetStatusCommand.java:104)
at com.sap.engine.services.shell.processor.environment.CommandBase.exec(CommandBase.java:132)
at com.sap.engine.services.shell.processor.Interpreter.applyLineCommand(Interpreter.java:391)
at com.sap.engine.services.shell.processor.Interpreter.apply(Interpreter.java:150)
at com.sap.engine.services.shell.processor.Shell.work(Shell.java:142)
at com.sap.engine.services.shell.processor.managers.ShellProcessThread.run(ShellProcessThread.java:113) -
Error in MAIN_NEWBAS/STARTSAP_NBAS Upgrade EHP1
Hi
We have errors in this downtime phase of our BI upgrade. It looks like the KERNEL hasn't updated correctly ?
When I run R3INLPGM the environment variables do not show.
The SCS 00 instance started o.k. and Instance 01 is partially up with DISPATCHER JCONTROL SDM SERVER0
WATCHDOG only running.
I've followed all recommendations of note 1165462.
The error I see on the SDT tool is below together with the errors I see when I try to STOPSAP for manual intervention on 00 or 01
I forced an end of the subsystem to do a manual APYSAP of kernel 69 but this has the same results.
Please advise thanks
David
SDT error
Checks after phase MAIN_NEWBAS/STARTSAP_NBAS were negative!
Last error code set: RFC call to subst_get_uvers failed with key RFC_ERROR_COMMUNICATION (open): SAP_CMINIT3 : rc=20 > Connect to SAP gateway failed
Connect_PM DEST=BID, GWHOST=SATURN, GWSERV=sapgw03, SYSNR=03
LOCATION CPIC (TCP/IP) on local host with Unicode
ERROR partner 'SATURN.NFOODS.NET:3303' not reached
TIME Wed Jun 23 21:49:08 201
RELEASE 710
COMPONENT NI (network interface)
VERSION 39
RC -10
MODULE nixxi.cpp
LINE 2779
DETAIL NiPConnect: 10.222.40.91:3303
SYSTEM CALL connect
ERRNO 79
ERRNO TEXT Connection refused
COUNTER 78
System start failed
STOPSAP Errors
stopsap bid 01
Ownership of object GETOBJINF in QTEMP type *USRSPC changed.
Ownership of object GETOBJINF in QTEMP type *USRSPC changed.
Checking input parameters...
Ownership of object GETOBJINF in QTEMP type *USRSPC changed.
Ownership of object GETOBJINF in QTEMP type *USRSPC changed.
Ownership of object GETOBJINF in QTEMP type *USRSPC changed.
collectSystemInfo: found central instance DVEBMGS03 on host SATURN but
central instance already exists as DVEBMGS01 on host SATURN.
StopInstance: Stopping instance 01 of system BID on host SATURN is not
possible. System configuration can not be retrieved.
O4STPSAP: Stopping instance 01 of system BID on host SATURN failed.
Errors occurred in command.
Errors occurred in command.
CausedHi Miguel,
her wanted to say, that either the shadow during uptime or later the real instance during downtime restarts SAP several times and ALWAYS start saposcol as well. If this fails - which is a really crazy behviour - SAP shuts down again !
=> The easiest - especially during an upgrade - is to just comment the saposcol start in the start profile
Then you have repeat the upgrade after shutting down the instance completey with killing all proceeses and it should work fine ...
Regards
Volker Gueldenpfennig, consolut international ag
http://www.consolut.com http://www.4soi.de http://www.easymarketplace.de -
SDM agent is not registered with SDM server of Solution Manager server
Hi,
We are in process of configuring EWA report for JAVA stack of SAP system along with ABAP stack. For ABAP stack the EWA report generation is straight forward and it is working fine. We are facing the problem while configuring EWA report for JAVA stack. Pls. find below the steps that we have followed and currently where we are stuck,
1) Installation of Willy introscope on Solman server.
2) Define JAVA component for each SAP system in SMSY
3) Installation of SDM Agent on all managed systems
4) Trying to attach SDM Agent to SDM server(solman) with the use of smdsetup.bat (managingconf & sldconf ).still we are getting error in smd agent log file as given below:
===============
Nov 24, 2011 6:16:09 PM [Thread[Connector,5,main]] Info [p4://xxxx.xxxx.int:8103] Checking server availability...
Nov 24, 2011 6:16:39 PM [Thread[Connector,5,main]] Error Failed to connect to SMD server - user: SMD_ADMIN
Nov 24, 2011 6:16:39 PM [Thread[Connector,5,main]] Warning Connecting to SMD server p4://xxx.xxx..int:8103 failed - error counter: 0 - com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is com.sap.engine.interfaces.cross.DestinationException: cannot establish connection with any of the available instances
* Nested exceptions are:*
* com.sap.engine.services.rmi_p4.P4IOException: Cannot open connection on host: xx.xx.xx.xx and port: 8103*=================
5) The solman_setup t-code execution is successful in Solman server.
6) Trying to configure Technical system for JAVA system type through solman_setup : At this time we are getting another error as shown below:
========
The Managed System does not fulfil the Diagnostics prerequisites
Software with prerequisite are incorrect: Found SAP J2EE ENGINE 7.00 with sp level 0, minimum sp level required is 9: Please install or upgrade the required software component.========
I have gone through the SAP note: 1274287 : My solman system is already on the required patch level for LMservice and St 400 SP. Also, the managing systems Java patch level is more then sp06 which is minimum level required.
I need your help to know, why i am getting this SAP J2EE ENGINE 7.00 patch level error although my Java stack is up to date with the required patches.
Waiting for your reply friends.
Regards,Hi,
please let us know your solman version.
check and apply the sap note
[Note 1277258 - Diagnostics prerequisite check failure|https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1277258]
Thanks,
Jansi -
Upgrade from NW 7.0 EHP1 to NW 7.3
Hi All,
I am upgrading NW 7.0 EHP1 to NW 7.3 and reached the downtime phase.
I got halted by an error in UNDEPLOY_THE_OLD_DB_CONTENT phase of downtime step.
The logs are as follows :
UNDEPLOY_THE_OLD_DB_CONTENT_UTO_01.LOG
Aug 31, 2011 5:47:16 AM Info: com.sap.sdt.j710.db.DBContentUtilImpl [Threadmain,5,main]: T
he /usr/sap/EHD/JC00/SDM/root/origin/sap.com/tc/TechSrv/XML_DAS_Init/SAP AG/0/7.0103.20081105085233.0000/XML_DAS_Init.sda sda archive will be undeploy.
Aug 31, 2011 5:47:16 AM Error: com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:883) [Threadmain,5,main]:
Exception has occurred during the execution of the phase.
Aug 31, 2011 5:47:16 AM Error: com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:884) [Threadmain,5,main]:
java.io.FileNotFoundException: testconn.log (No such file or directory)
Aug 31, 2011 5:47:16 AM Error: com.sap.sdt.j710.db.DBContentUtilImpl.undeploySDAContent(DBContentUtilImpl.java:131) [Threadmain,5,main]:
java.io.FileNotFoundException: testconn.log (No such file or directory)
Aug 31, 2011 5:47:16 AM Error: com.sap.sdt.j2ee.phases.PhaseTypeUndeployDBContent.execute(PhaseTypeUndeployDBContent.java:79) [Threadmain,5,main]:
Error during undeployment of DB content. Details:java.io.FileNotFoundException: testconn.log (No such file or directory)
java.io.FileNotFoundException: testconn.log (No such file or directory)
Aug 31, 2011 5:47:16 AM Info: com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:925) [Threadmain,5,main]: P
hase UPGRADE/OFFLINE_MIGRATION/UNDEPLOY_THE_OLD_DB_CONTENT has been completed.
I suppose that it is not able to find testconn.log (No such file or directory) but not sure where it will be.
Please provide a solution or workaround.
ThanksHi,
The log files are ideally created in the upgrade folder - log subdirectory:
/usr/sap/<SID>/upg/java/log/
Please check in this folder if the file exists. Also check if the read/write permissions to this folder are fine for user <sid>adm. It could be that the file is getting created due to lack of permissions.
Regards,
Srikishan -
Error while upgrading NW04s to sp5
I installed NW04s in my machine. I am trying to upgrade it to sp5. I could upgrade the ABAP stack to sp5 without any problem. When i am doing java stack, i could update all other support packages except the one 'CAF05_0-10003464.SCA'. When this package is on progress, the process gets almost completed and gives the status also 'deployed'. But after that it throws the following error and the status also changed to 'not deployed'.
ERROR: Not updated. Deploy Service returned ERROR:
java.rmi.RemoteException: Exception in operation update with application sap.com/caf~tc..
Reason: com/sap/caf/metamodel/ApplicationInterface; nested exception is:
java.lang.NoClassDefFoundError: com/sap/caf/metamodel/ApplicationInterface
at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:682)
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: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: java.lang.NoClassDefFoundError: com/sap/caf/metamodel/ApplicationInterface
at java.lang.Class.getDeclaredMethods0(Native Method)
at java.lang.Class.privateGetDeclaredMethods(Class.java:1655)
at java.lang.Class.privateGetPublicMethods(Class.java:1778)
at java.lang.Class.privateGetPublicMethods(Class.java:1788)
at java.lang.Class.getMethods(Class.java:832)
at com.sap.engine.services.ejb.deploy.xml.MethodsExtractor.getWithNotSpecifiedMethodInterface(MethodsExtractor.java:156)
at com.sap.engine.services.ejb.deploy.xml.MethodsExtractor.getAllMethodsInBean(MethodsExtractor.java:103)
at com.sap.engine.services.ejb.deploy.xml.EJBJarParser.getMethodXml(EJBJarParser.java:1168)
at com.sap.engine.services.ejb.deploy.xml.EJBJarParser.processContainerTransaction(EJBJarParser.java:1023)
at com.sap.engine.services.ejb.deploy.xml.EJBJarParser.processAssemblyDescriptor(EJBJarParser.java:924)
at com.sap.engine.services.ejb.deploy.xml.EJBJarParser.parseXml(EJBJarParser.java:156)
at com.sap.engine.services.ejb.deploy.xml.EJBJarParser.parseXml(EJBJarParser.java:97)
at com.sap.engine.services.ejb.deploy.DeployAdmin.parseSingleJar(DeployAdmin.java:298)
at com.sap.engine.services.ejb.EJBAdmin.buildAppDescriptorBeforeUpdate(EJBAdmin.java:408)
at com.sap.engine.services.ejb.EJBAdmin.needUpdate(EJBAdmin.java:341)
at com.sap.engine.services.deploy.server.application.UpdateTransaction.getContainersWhichNeedUpdate(UpdateTransaction.java:537)
at com.sap.engine.services.deploy.server.application.UpdateTransaction.getConcernedContainers(UpdateTransaction.java:493)
at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:263)
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)
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.update(DeployServiceImpl.java:670)
... 10 more
For detailed information see the log file of the Deploy Service.
06/11/29 12:14:54 - ***********************************************************
Nov 29, 2006 12:14:54... Info: End of log messages of the target system.
Nov 29, 2006 12:14:54... Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Nov 29, 2006 12:14:54... Error: Aborted: development component 'caf/tc'/'sap.com'/'MAIN_APL70VAL_C'/'644873':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Exception in operation update with application sap.com/caf~tc..
Reason: com/sap/caf/metamodel/ApplicationInterface; nested exception is:
java.lang.NoClassDefFoundError: com/sap/caf/metamodel/ApplicationInterface
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Nov 29, 2006 12:14:55... Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
Can anyone help me to sort out this problem?Symptom
JSPM hangs by upgrade from SP4 to SP5 with the following message into the log file:
ERROR: Not updated. Deploy Service returned ERROR: java.rmi.RemoteException: Exception in operation
update with application sap.com/caf~tc..
Reason: com/sap/caf/rt/exception/CAFDeleteException; nested exception is: ,,java.lang.NoClassDefFoundError:
JUP fails by NW04 SP14 -> NW04s SP5 upgrade with the message into log file:
ERROR: Not updated. Deploy Service returned ERROR: java.rmi.RemoteException: Exception in operation
update with application sap.com/caf~tc..
Reason: com/sap/caf/rt/exception/CAFDeleteException; nested exception is: ,,java.lang.NoClassDefFoundError:
Reason and Prerequisites
Deployment of CAF component sap.com/caf~tc failed by deployment scenario of type:
1. The application is deployed with a reference to Lib1, where Class A
is included.
2. Then class A is moved from Lib1 to Lib2 (removed from Lib1);
3. Then the new version of the application which has references to both
libraries Lib1 and Lib2 is deployed via SDM;
4. The deployment fails with NoClassDefFoundError: class A.
For patricular case we have the situation:
The class com/sap/caf/rt/exception/CAFDeleteException was moved from
caf/runtime/ear to caf/runtime/api/lib between the SPs.
Solution
Please follow the steps:
1. Close JSPM application
2. Start <device>:\usr\sap\<sid>\JC<instance number>\SDM\program\RemoteGui.bat
3. From the menu invoke "SDM Gui" -> "Login" and enter your SDM password
4. Navigate to tab "Undeployment" and select CAF component caf~tc, press button "Select" and "Start Undeployment" and complete undeployment confirming it.
5. Navigate to tab "Deployment" and select CAF component using plus button and select option "Update deployed SDA/SCAs that have any version" into Deployment configuration options below and complete deployment confirming it.
6. Close "SDM Gui" application.
7. Restart JSPM and on the step "Select package type" select option "Single support packages" in order to update all other components, which left not deployed.
8. On step "Specify Queue" select all not deployed components and complete their deployment.
An alternative way is:
1. If there is a problem with CAF deployment do not stop the upgrade application.
2. Open command prompt and go to SDM\program directory
3. Execute: sdm jstartup "mode=integrated"
4. Execute: startserver
5. After that start the SDM remote GUI application
6. From the menu invoke "SDM Gui" -> "Login" and enter your SDM password
7. Navigate to tab "Undeployment" and select CAF component caf~tc, press button "Select" and "Start Undeployment" and complete undeployment confirming it.
8. Logout and close "SDM Gui" application.
9. In the command prompt execute: stopserver
10. In the command prompt execute: sdm jstartup "mode=standalone"
11. Go to the Upgrade application and restart the process from the point of failure
Best Regards,
Barry. -
Error while executing SDM process phase with action DEPLOY_SLOT
Hi,
I am upgrading CRM 2007 to CRM 7.0 and got an error in Java side.
Following is DEPLOY_SLOT_1_DON_01.LOG
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7185 - 630]/>
<!NAME[C:\usr\sap\jupgrade\log\DEPLOY_SLOT_1__DON_01.LOG]/>
<!PATTERN[DEPLOY_SLOT_1__DON_01.LOG]/>
<!FORMATTER[com.sap.tc.logging.TraceFormatter(%24d %s: %m)]/>
<!ENCODING[UTF8]/>
<!LOGHEADER[END]/>
May 20, 2009 4:15:48 AM Info:
May 20, 2009 4:15:48 AM Info: ============================================
May 20, 2009 4:15:48 AM Info: = Starting to execute command 'deploy' =
May 20, 2009 4:15:48 AM Info: ============================================
May 20, 2009 4:15:48 AM Info: Starting SDM - Software Deployment Manager...
May 20, 2009 4:15:49 AM Info: tc/SL/SDM/SDM/sap.com/SAP AG/7.0103.20081105085605.0000
May 20, 2009 4:15:51 AM Info: SDM operation mode successfully set to: Standalone
May 20, 2009 4:15:52 AM Info: Initializing Network Manager (50017)
May 20, 2009 4:15:52 AM Info: Checking if another SDM is running on port 50018
May 20, 2009 4:15:53 AM Info: -
Starting deployment -
May 20, 2009 4:15:53 AM Info: Error handling strategy: OnErrorSkipDepending
May 20, 2009 4:15:53 AM Info: Prerequisite error handling strategy: OnPrerequisiteErrorStop
May 20, 2009 4:15:53 AM Info: Update strategy: UpdateLowerVersions
May 20, 2009 4:15:53 AM Info: Starting deployment prerequisites:
May 20, 2009 4:15:55 AM Info: Loading selected archives...
May 20, 2009 4:15:55 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\ADSSAP03_0.SCA'
May 20, 2009 4:16:43 AM Info: Loading archive '
nbg-dev-cd1\sapmnt\trans\EPS\in\BIBASES16_0-10003477.SCA'
May 20, 2009 4:16:48 AM Info: Loading archive '
nbg-dev-cd1\sapmnt\trans\EPS\in\BIIBC16_0-10003495.SCA'
May 20, 2009 4:16:50 AM Info: Loading archive '
nbg-dev-cd1\sapmnt\trans\EPS\in\BIREPPLAN16_0-10002878.SCA'
May 20, 2009 4:17:00 AM Info: Loading archive '
nbg-dev-cd1\sapmnt\trans\EPS\in\BIWDALV16_0-10003475.SCA'
May 20, 2009 4:17:02 AM Info: Loading archive '
nbg-dev-cd1\sapmnt\trans\EPS\in\BIWEBAPP16_0-10003476.SCA'
May 20, 2009 4:17:13 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\BIMMR03_0.SCA'
May 20, 2009 4:17:24 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\BIUDI03_0.SCA'
May 20, 2009 4:17:31 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\BPCRMAPP02_0.SCA'
May 20, 2009 4:17:35 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\BPCRMFND02_0.SCA'
May 20, 2009 4:17:37 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\CAF03_0.SCA'
May 20, 2009 4:18:02 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\CAFKM03_0.SCA'
May 20, 2009 4:18:04 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\CAFUM03_0.SCA'
May 20, 2009 4:18:08 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\CRMAPP02_0.SCA'
May 20, 2009 4:18:09 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\CRMFND02_1.SCA'
May 20, 2009 4:18:10 AM Info: Loading archive '
nbg-dev-cd1\sapmnt\trans\EPS\in\DICBS16_0-10003500.SCA'
May 20, 2009 4:18:13 AM Info: Loading archive '
nbg-dev-cd1\sapmnt\trans\EPS\in\DICMS16_0-10003499.SCA'
May 20, 2009 4:18:20 AM Info: Loading archive '
nbg-dev-cd1\sapmnt\trans\EPS\in\DIDTR16_0-10003501.SCA'
May 20, 2009 4:18:26 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\EPPSERV03_0.SCA'
May 20, 2009 4:18:43 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\EPWDC03_0.SCA'
May 20, 2009 4:18:45 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\EPBC203_0.SCA'
May 20, 2009 4:18:50 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\KMKWJIKS03_0.SCA'
May 20, 2009 4:18:51 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\KMCBC03_0.SCA'
May 20, 2009 4:18:56 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\KMCCM03_0.SCA'
May 20, 2009 4:19:03 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\KMCCOLL03_0.SCA'
May 20, 2009 4:19:10 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\LMPORTAL03_0.SCA'
May 20, 2009 4:19:12 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\LMTOOLS03_01.SCA'
May 20, 2009 4:19:43 AM Error: There is already a component of the same type with identical name 'tc/cts/appl' and vendor 'sap.com' selected.
May 20, 2009 4:19:43 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\NETPDK03_0.SCA'
May 20, 2009 4:19:45 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\RTC03_0.SCA'
May 20, 2009 4:19:48 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\RTCSTREAM03_0.SCA'
May 20, 2009 4:19:49 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\SAPCRMAPP02_1.SCA'
May 20, 2009 4:20:55 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\SAPCRMDIC02_0.SCA'
May 20, 2009 4:21:00 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\SAPEU03_0.SCA'
May 20, 2009 4:21:39 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\SAPSHRAPP02_0.SCA'
May 20, 2009 4:23:18 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\SWLIFECYCL03_0.SCA'
May 20, 2009 4:23:24 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\UMEADMIN03_0.SCA'
May 20, 2009 4:23:27 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\UWLJWF03_0.SCA'
May 20, 2009 4:23:33 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\VCBASE03_0.SCA'
May 20, 2009 4:23:37 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\VCFLEX03_0.SCA'
May 20, 2009 4:23:54 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\VCFRAMEWORK03_0.SCA'
May 20, 2009 4:23:58 AM Info: Loading archive '
nbg-dev-cd1\sapmnt\trans\EPS\in\VCKITBI16_0-10003603.SCA'
May 20, 2009 4:23:59 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\VCKITGP03_0.SCA'
May 20, 2009 4:24:00 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\VCKITXX03_0.SCA'
May 20, 2009 4:24:02 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\WDEXTENSIONS03_0.SCA'
May 20, 2009 4:24:05 AM Error: Error while loading selected archives.
May 20, 2009 4:24:05 AM Error: Prerequisites were aborted.
May 20, 2009 4:24:13 AM Error: Error while loading selected archives.
May 20, 2009 4:24:13 AM Info: Summarizing the deployment results:
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\ADSSAP03_0.SCA
May 20, 2009 4:24:13 AM Error: Initial:
nbg-dev-cd1\sapmnt\trans\EPS\in\BIBASES16_0-10003477.SCA
May 20, 2009 4:24:13 AM Error: Initial:
nbg-dev-cd1\sapmnt\trans\EPS\in\BIIBC16_0-10003495.SCA
May 20, 2009 4:24:13 AM Error: Initial:
nbg-dev-cd1\sapmnt\trans\EPS\in\BIREPPLAN16_0-10002878.SCA
May 20, 2009 4:24:13 AM Error: Initial:
nbg-dev-cd1\sapmnt\trans\EPS\in\BIWDALV16_0-10003475.SCA
May 20, 2009 4:24:13 AM Error: Initial:
nbg-dev-cd1\sapmnt\trans\EPS\in\BIWEBAPP16_0-10003476.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\BIMMR03_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\BIUDI03_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\BPCRMAPP02_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\BPCRMFND02_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\CAF03_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\CAFKM03_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\CAFUM03_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\CRMAPP02_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\CRMFND02_1.SCA
May 20, 2009 4:24:13 AM Error: Initial:
nbg-dev-cd1\sapmnt\trans\EPS\in\DICBS16_0-10003500.SCA
May 20, 2009 4:24:13 AM Error: Initial:
nbg-dev-cd1\sapmnt\trans\EPS\in\DICMS16_0-10003499.SCA
May 20, 2009 4:24:13 AM Error: Initial:
nbg-dev-cd1\sapmnt\trans\EPS\in\DIDTR16_0-10003501.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\EPPSERV03_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\EPWDC03_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\EPBC203_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\KMKWJIKS03_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\KMCBC03_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\KMCCM03_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\KMCCOLL03_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\LMPORTAL03_0.SCA
May 20, 2009 4:24:13 AM Error: Precondition violated: C:\usr\sap\jupgrade\data\archives\LMTOOLS03_01.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\NETPDK03_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\RTC03_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\RTCSTREAM03_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\SAPCRMAPP02_1.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\SAPCRMDIC02_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\SAPEU03_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\SAPSHRAPP02_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\SWLIFECYCL03_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\UMEADMIN03_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\UWLJWF03_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\VCBASE03_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\VCFLEX03_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\VCFRAMEWORK03_0.SCA
May 20, 2009 4:24:13 AM Error: Initial:
nbg-dev-cd1\sapmnt\trans\EPS\in\VCKITBI16_0-10003603.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\VCKITGP03_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\VCKITXX03_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\WDEXTENSIONS03_0.SCA
May 20, 2009 4:24:13 AM Error: Processing error. Return code: 4
It appears to me that somehow there is a component conflict:
May 20, 2009 4:19:12 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\LMTOOLS03_01.SCA'
May 20, 2009 4:19:43 AM Error: There is already a component of the same type with identical name 'tc/cts/appl' and vendor 'sap.com' selected.
May 20, 2009 4:19:43 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\NETPDK03_0.SCA'
Is it advisable at all to manually delete the above LMTOOLS03_01.SCA from the location and try again or this will lead to more errors?
Please help ASAP, thanks a lot,
ShivalFollowing is the trouble ticket information:
Trouble Ticket Report
Upgrade to Enhancement Package 1 SR1 for SAP NetWeaver/ SAP Business Suite 7 SR1
SID................: CD1
Hostname...........: nbg-dev-cd1
Install directory..: c:/usr/sap/CD1
Upgrade directory..: C:\usr\sap\jupgrade
Database...........: SAP DB
Operating System...: NT
JDK version........: 1.4.2_15 Sun Microsystems Inc.
SAPJup version.....: 1.5.6
Source release.....: 700
Target release.....: 700
Current usages.....: AS;EP;EPC;BP-CRM;JCRM;AAS
ABAP stack present.: true
The execution of UPGRADE/UPGRADE/DEPLOY_ONLINE ended in error.
Error while executing SDM process phase with action DEPLOY_SLOT. See C:\usr\sap\jupgrade\log\DEPLOY_SLOT_1__DON_01.LOG for details.
Cannot execute Java process for deployList with parameters C:/usr/sap/jupgrade/tmp/SLOT.DEPLOY.LST.
Return code condition success evaluated to false for process java.exe for action ACTION_DEPLOY_LIST.
More information can be found in the log file C:\usr\sap\jupgrade\log\DEPLOY_ONLINE_DON_01.LOG.
Use the information provided to trouble-shoot the problem. There might be an OSS note providing a solution to this problem. Search for OSS notes with the following search terms:
com.sap.sdt.j2ee.phases.PhaseTypeSDMProcess
com.sap.sdt.ucp.phases.PhaseException
Error while executing SDM process phase with action DEPLOY_SLOT. See C:\usr\sap\jupgrade\log\DEPLOY_SLOT_1__DON_01.LOG for details.
DEPLOY_ONLINE
UPGRADE
NetWeaver Upgrade
SAPJup
Java Upgrade -
Problem with the UPGRADE in the PHASE - DEPLOY_ONLINE
Hello Expert,
I have a problem when a try to execute the upgrade in the phase
DEPLOY_ONLINE,
<<<<<<<<<<<BEGIN TROUBLE TICKET >>>>>>>>>>>>>>>>>>>>>>
Trouble Ticket Report
Upgrade to SAP NetWeaver'04s
SID................: J2E
Hostname...........: sapepd
Install directory..: d:/usr/sap/J2E
Upgrade directory..: D:\SAPEPD\saploc\jupgrade
Database...........: Microsoft SQL Server
Operating System...: NT
JDK version........: 1.4.2_11 Sun Microsystems Inc.
SAPJup version.....: 1.1.101
Source release.....: 630
Target release.....: 700
Current usages.....: EP;AS;DI
ABAP stack present.: false
The execution of UPGRADE/UPGRADE/DEPLOY_ONLINE ended in error.
Error while executing SDM process phase with action DEPLOY_SLOT. See
D:\SAPEPD\saploc\jupgrade\log\DEPLOY_SLOT_0__DON_01.LOG for details.
Cannot execute Java process for deployList with parameters
D:/SAPEPD/saploc/jupgrade/tmp/SLOT.DEPLOY.PRE.01.LST.
Return code condition success evaluated to false for process java.exe
for action ACTION_DEPLOY_LIST.
More information can be found in the log file
D:\SAPEPD\saploc\jupgrade\log\DEPLOY_ONLINE_DON_01.LOG.
Use the information provided to trouble-shoot the problem. There might
be an OSS note providing a solution to this problem. Search for OSS
notes with the following search terms:
com.sap.sdt.j2ee.phases.PhaseTypeSDMProcess
com.sap.sdt.ucp.phases.PhaseException
Error while executing SDM process phase with action DEPLOY_SLOT. See
D:\SAPEPD\saploc\jupgrade\log\DEPLOY_SLOT_0__DON_01.LOG for details.
DEPLOY_ONLINE
UPGRADE
NetWeaver Upgrade
SAPJup
Java Upgrade
<<<<<<<<<<< END OF TROUBLE TICKET >>>>>>>>>>>>>>>>>>>>>>>>>
THE FILE: DEPLOY_ONLINE_DON_01.LOG
BEGIN DEPLOY_ONLINE_DON_01.LOG----
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7185 - 630]/>
<!NAME[D:\SAPEPD\saploc\jupgrade\log\DEPLOY_ONLINE_DON_01.LOG]/>
<!PATTERN[DEPLOY_ONLINE_DON_01.LOG]/>
<!FORMATTER[com.sap.tc.logging.ListFormatter]/>
<!ENCODING[Cp1252]/>
<!LOGHEADER[END]/>
#1.5#C000AC10C807000000000B1D010BC49D0004358E71467A38#1184785808915#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:720)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:720)#Java###Phase has been started.#1#UPGRADE/UPGRADE/DEPLOY_ONLINE#
#1.5#C000AC10C807000000000B1E010BC49D0004358E71467A38#1184785808915#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:721)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:721)#Java###Phase type is .#1#com.sap.sdt.j2ee.phases.PhaseTypeSDMProcess#
#1.5#C000AC10C807000000000B1F010BC49D0004358E71467A38#1184785808915#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:345)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:345)#Java### Parameter =#2#action#DEPLOY_SLOT#
#1.5#C000AC10C807000000000B20010BC49D0004358E71467A38#1184785808915#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:345)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:345)#Java### Parameter =#2#connect#standard#
#1.5#C000AC10C807000000000B21010BC49D0004358E71467A38#1184785808915#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.j2ee.phases.PhaseTypeSDMProcess.checkParameters(PhaseTypeSDMProcess.java:755)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j2ee.phases.PhaseTypeSDMProcess.checkParameters(PhaseTypeSDMProcess.java:755)#Java###Checking phase parameters .#1#action, connect#
#1.5#C000AC10C807000000000B22010BC49D0004358E71467A38#1184785808915#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.j2ee.phases.PhaseTypeSDMProcess.checkParameters(PhaseTypeSDMProcess.java:764)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j2ee.phases.PhaseTypeSDMProcess.checkParameters(PhaseTypeSDMProcess.java:764)#Java###Phase parameters have been checked. All required phase parameters have been set.#1#1#
#1.5#C000AC10C807000000000B23010BC49D0004358E71467A38#1184785808915#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.j2ee.phases.PhaseTypeSDMProcess.createSlotDeployLists(PhaseTypeSDMProcess.java:1216)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j2ee.phases.PhaseTypeSDMProcess.createSlotDeployLists(PhaseTypeSDMProcess.java:1216)#Java###Temporary file has been created.#1#D:/SAPEPD/saploc/jupgrade/tmp/SLOT.DEPLOY.LST#
#1.5#C000AC10C807000000000B24010BC49D0004358E7146B8B8#1184785808931#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:46)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:46)#Java###Java process ID has been started.#1#249#
#1.5#C000AC10C807000000000B25010BC49D0004358E7146B8B8#1184785808931#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:54)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:54)#Java###Command line: #2# #C:
j2sdk
jre
bin
java.exe -Xmx256M -Djava.ext.dir=d:/usr/sap/J2E/JC00/SDM/program/lib -cp . -jar d:
usr
sap
J2E
JC00
SDM
program
bin
SDM.jar deploy onerror=skipdepending updateversions=all list=D:/SAPEPD/saploc/jupgrade/tmp/SLOT.DEPLOY.PRE.01.LST sdmHome=d:/usr/sap/J2E/JC00/SDM/program logfile=D:
SAPEPD
saploc
jupgrade
log
DEPLOY_SLOT_0__DON_01.LOG#
#1.5#C000AC10C807000000000B26010BC49D0004358E7146B8B8#1184785808931#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:55)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:55)#Java###Standard out: #2# #D:
SAPEPD
saploc
jupgrade
log
DEPLOY_SLOT_0__DON_01.OUT#
#1.5#C000AC10C807000000000B27010BC49D0004358E7146F350#1184785808946#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:126)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:126)#Java###Process ID has been started.#1#249#
#1.5#C000AC10C807000000000B28010BC49D0004358E7146F350#1184785808946#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:182)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:182)#Java###Waiting for process ID , name to finish.#2#249#java.exe#
#1.5#C000AC10C807000000000B29010BC49D0004358E90915390#1184786333914#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:215)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:215)#Java###Process ID , name has been finished, exit code .#3#249#java.exe#4#
#1.5#C000AC10C807000000000B2A010BC49D0004358E90918E28#1184786333929#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:748)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:748)#Java###Exception has occurred during the execution of the phase.##
#1.5#C000AC10C807000000000B2B010BC49D0004358E90918E28#1184786333929#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.tools.procx.DefaultProcessAdapter.checkReturnCode(DefaultProcessAdapter.java:513)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.tools.procx.DefaultProcessAdapter.checkReturnCode(DefaultProcessAdapter.java:513)#Java###Return code condition success evaluated to false for process java.exe for action ACTION_DEPLOY_LIST.##
#1.5#C000AC10C807000000000B2C010BC49D0004358E90918E28#1184786333929#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.j2ee.tools.sdmprocess.AbstractSDMProcessCall.deployList(AbstractSDMProcessCall.java:722)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.j2ee.tools.sdmprocess.AbstractSDMProcessCall.deployList(AbstractSDMProcessCall.java:722)#Java###Cannot execute Java process for deployList with parameters D:/SAPEPD/saploc/jupgrade/tmp/SLOT.DEPLOY.PRE.01.LST.##
#1.5#C000AC10C807000000000B2D010BC49D0004358E9091CCA8#1184786333945#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.j2ee.phases.PhaseTypeSDMProcess.execute(PhaseTypeSDMProcess.java:735)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.j2ee.phases.PhaseTypeSDMProcess.execute(PhaseTypeSDMProcess.java:735)#Java###Error while executing SDM process phase with action DEPLOY_SLOT. See D:
SAPEPD
saploc
jupgrade
log
DEPLOY_SLOT_0__DON_01.LOG for details.##
#1.5#C000AC10C807000000000B2E010BC49D0004358E9091CCA8#1184786333945#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:792)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:792)#Java###Phase has been completed.#1#UPGRADE/UPGRADE/DEPLOY_ONLINE#
#1.5#C000AC10C807000000000B2F010BC49D0004358E9091CCA8#1184786333945#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:793)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:793)#Java###Start time: .#1#2007/07/18 15:10:08#
#1.5#C000AC10C807000000000B30010BC49D0004358E9091CCA8#1184786333945#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:794)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:794)#Java###End time: .#1#2007/07/18 15:18:53#
#1.5#C000AC10C807000000000B31010BC49D0004358E9091CCA8#1184786333945#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:795)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:795)#Java###Duration: .#1#0:08:45.030#
#1.5#C000AC10C807000000000B32010BC49D0004358E9091CCA8#1184786333945#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:796)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:796)#Java###Phase status is .#1#error#
*************END DEPLOY_ONLINE_DON_01.LOG*******************
FILE ************** DEPLOY_SLOT_0__DON_01.LOG
BEGIN DEPLOY_SLOT_0__DON_01.LOG----
The application start is forbidden, because of the server mode and action.
Jul 18, 2007 3:18:33 PM Info: Starting to save the repository
Jul 18, 2007 3:18:33 PM Info: Finished saving the repository
Jul 18, 2007 3:18:33 PM Info: Starting: Initial deployment: Selected development component 'tc/wd/samples/testsuite/uuie'/'sap.com'/'SAP AG'/'7.0010.20061002110342.0000'/'0' will be deployed.
Jul 18, 2007 3:18:33 PM Info: SDA to be deployed: D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc\wd\samples\testsuite\uuie\SAP AG\0\7.0010.20061002110342.0000\TestSuiteUUIE.sda
Jul 18, 2007 3:18:33 PM Info: Software type of SDA: J2EE
Jul 18, 2007 3:18:33 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Jul 18, 2007 3:18:36 PM Info: Begin of log messages of the target system:
07/07/18 15:18:33 - ***********************************************************
07/07/18 15:18:34 - Start updating EAR file...
07/07/18 15:18:34 - start-up mode is lazy
07/07/18 15:18:34 - EAR file updated successfully for 172ms.
07/07/18 15:18:34 - Start deploying ...
07/07/18 15:18:34 - EAR file uploaded to server for 500ms.
07/07/18 15:18:36 - ERROR: Not deployed. Deploy Service returned ERROR:
java.rmi.RemoteException: Cannot deploy application sap.com/tcwdsamplestestsuiteuuie..
Reason: Clusterwide exception: Failed to deploy application sap.com/tcwdsamplestestsuiteuuie. 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/tcwdsamplestestsuiteuuie. 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/tcwdsamplestestsuiteuuie. 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/07/18 15:18:36 - ***********************************************************
Jul 18, 2007 3:18:36 PM Info: End of log messages of the target system.
Jul 18, 2007 3:18:36 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Jul 18, 2007 3:18:36 PM Error: Aborted: development component 'tc/wd/samples/testsuite/uuie'/'sap.com'/'SAP AG'/'7.0010.20061002110342.0000'/'0', grouped by software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.11.0.20070201154800''/'0':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot deploy application sap.com/tcwdsamplestestsuiteuuie..
Reason: Clusterwide exception: Failed to deploy application sap.com/tcwdsamplestestsuiteuuie. 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/tcwdsamplestestsuiteuuie. 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)
Jul 18, 2007 3:18:36 PM Info: Starting to save the repository
Jul 18, 2007 3:18:36 PM Info: Finished saving the repository
Jul 18, 2007 3:18:36 PM Info: Starting: Update: Selected development component 'tc/wd/tools'/'sap.com'/'SAP AG'/'7.0011.20061227101805.0000'/'0' updates currently deployed development component 'tc/wd/tools'/'sap.com'/'SAP AG'/'6.4020.00.0000.20070308112146.0000'/'0'.
Jul 18, 2007 3:18:36 PM Info: SDA to be deployed: D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc\wd\tools\SAP AG\0\7.0011.20061227101805.0000\WebDynproTools.sda
Jul 18, 2007 3:18:36 PM Info: Software type of SDA: J2EE
Jul 18, 2007 3:18:36 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Jul 18, 2007 3:18:39 PM Info: Begin of log messages of the target system:
07/07/18 15:18:36 - ***********************************************************
07/07/18 15:18:36 - Start updating EAR file...
07/07/18 15:18:36 - start-up mode is lazy
07/07/18 15:18:37 - EAR file updated successfully for 375ms.
07/07/18 15:18:37 - Start updating...
07/07/18 15:18:37 - EAR file uploaded to server for 422ms.
07/07/18 15:18:39 - Successfully updated. Update took 1641ms.
07/07/18 15:18:39 - Deploy Service status:
07/07/18 15:18:39 - Application : sap.com/tcwdtools
07/07/18 15:18:39 -
07/07/18 15:18:39 - sap.com/tcwdtools - WEBDYNPRO
07/07/18 15:18:39 - sap.com/tcwdtools monitoring configuration - MONITORING CONFIGURATION
07/07/18 15:18:39 - ***********************************************************
Jul 18, 2007 3:18:39 PM Info: End of log messages of the target system.
Jul 18, 2007 3:18:39 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Jul 18, 2007 3:18:39 PM Info: Finished successfully: development component 'tc/wd/tools'/'sap.com'/'SAP AG'/'7.0011.20061227101805.0000'/'0', grouped by :
The application start is forbidden, because of the server mode and action.
Jul 18, 2007 3:18:39 PM Info: Starting to save the repository
Jul 18, 2007 3:18:40 PM Info: Finished saving the repository
Jul 18, 2007 3:18:40 PM Info: Starting: Update: Selected development component 'tc/wd/wslib'/'sap.com'/'SAP AG'/'7.0011.20070125102926.0000'/'0' updates currently deployed development component 'tc/wd/wslib'/'sap.com'/'SAP AG'/'6.4020.00.0000.20070308112008.0000'/'0'.
Jul 18, 2007 3:18:40 PM Info: SDA to be deployed: D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc\wd\wslib\SAP AG\0\7.0011.20070125102926.0000\WebDynproWsLib.sda
Jul 18, 2007 3:18:40 PM Info: Software type of SDA: library
Jul 18, 2007 3:18:40 PM Info: ***** Begin of SAP J2EE Engine Deployment (Library component of SAP J2EE Engine) *****
Jul 18, 2007 3:18:40 PM Info: Begin of log messages of the target system:
07/07/18 15:18:40 - ***********************************************************
07/07/18 15:18:40 - Start deploying library JAR D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc\wd\wslib\SAP AG\0\7.0011.20070125102926.0000\WebDynproWsLib.sda...
07/07/18 15:18:40 - Library D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc\wd\wslib\SAP AG\0\7.0011.20070125102926.0000\WebDynproWsLib.sda successfully deployed on the server.
Jul 18, 2007 3:18:40 PM Info: End of log messages of the target system.
Jul 18, 2007 3:18:40 PM Info: ***** End of SAP J2EE Engine Deployment (Library component of SAP J2EE Engine) *****
Jul 18, 2007 3:18:40 PM Info: Finished successfully: development component 'tc/wd/wslib'/'sap.com'/'SAP AG'/'7.0011.20070125102926.0000'/'0', grouped by
Jul 18, 2007 3:18:40 PM Info: Starting to save the repository
Jul 18, 2007 3:18:41 PM Info: Finished saving the repository
Jul 18, 2007 3:18:41 PM Info: Starting: Initial deployment: Selected development component 'tc/workflowmodeler'/'sap.com'/'SAP AG'/'7.0011.20050509144048.0000'/'0' will be deployed.
Jul 18, 2007 3:18:41 PM Info: SDA to be deployed: D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc\workflowmodeler\SAP AG\0\7.0011.20050509144048.0000\Modeler.sda
Jul 18, 2007 3:18:41 PM Info: Software type of SDA: J2EE
Jul 18, 2007 3:18:41 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Jul 18, 2007 3:18:49 PM Info: Begin of log messages of the target system:
07/07/18 15:18:41 - ***********************************************************
07/07/18 15:18:41 - Start updating EAR file...
07/07/18 15:18:41 - start-up mode is lazy
07/07/18 15:18:42 - EAR file updated successfully for 1000ms.
07/07/18 15:18:42 - Start deploying ...
07/07/18 15:18:43 - EAR file uploaded to server for 891ms.
07/07/18 15:18:48 - Successfully deployed. Deployment took 5375ms.
07/07/18 15:18:48 - Application : sap.com/tc~workflowmodeler
07/07/18 15:18:48 -
07/07/18 15:18:48 - /Application/WorkflowModeler - LOGGING CONFIGURATION
07/07/18 15:18:48 - com.sap.workflowmodeler.modeler - LOGGING CONFIGURATION
07/07/18 15:18:48 - workflowBean - EJB
07/07/18 15:18:48 - WorkflowConnection - EJB
07/07/18 15:18:48 - Modeler - WEB
07/07/18 15:18:48 - sap.com/tc~workflowmodeler monitoring configuration - MONITORING CONFIGURATION
07/07/18 15:18:48 - ***********************************************************
Jul 18, 2007 3:18:49 PM Info: End of log messages of the target system.
Jul 18, 2007 3:18:49 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Jul 18, 2007 3:18:49 PM Info: Finished successfully: development component 'tc/workflowmodeler'/'sap.com'/'SAP AG'/'7.0011.20050509144048.0000'/'0', grouped by software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.11.0.20070201154800''/'0':
The application start is forbidden, because of the server mode and action.
Jul 18, 2007 3:18:49 PM Info: Starting to save the repository
Jul 18, 2007 3:18:49 PM Info: Finished saving the repository
Jul 18, 2007 3:18:49 PM Info: Starting: Update: Selected development component 'tc_SL_SDM_Client'/'sap.com'/'SAP AG'/'7.0011.20061227100346.0000'/'0' updates currently deployed development component 'tc_SL_SDM_Client'/'sap.com'/'SAP AG'/'6.4014.00.0000.20050818153711.0000'/'0'.
Jul 18, 2007 3:18:49 PM Info: SDA to be deployed: D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc_SL_SDM_Client\SAP AG\0\7.0011.20061227100346.0000\SDMClient.sda
Jul 18, 2007 3:18:49 PM Info: Software type of SDA: library
Jul 18, 2007 3:18:49 PM Info: ***** Begin of SAP J2EE Engine Deployment (Library component of SAP J2EE Engine) *****
Jul 18, 2007 3:18:49 PM Info: Begin of log messages of the target system:
07/07/18 15:18:49 - ***********************************************************
07/07/18 15:18:49 - Start deploying library JAR D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc_SL_SDM_Client\SAP AG\0\7.0011.20061227100346.0000\SDMClient.sda...
07/07/18 15:18:49 - Library D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc_SL_SDM_Client\SAP AG\0\7.0011.20061227100346.0000\SDMClient.sda successfully deployed on the server.
Jul 18, 2007 3:18:49 PM Info: End of log messages of the target system.
Jul 18, 2007 3:18:49 PM Info: ***** End of SAP J2EE Engine Deployment (Library component of SAP J2EE Engine) *****
Jul 18, 2007 3:18:50 PM Info: Finished successfully: development component 'tc_SL_SDM_Client'/'sap.com'/'SAP AG'/'7.0011.20061227100346.0000'/'0', grouped by
Jul 18, 2007 3:18:50 PM Info: Starting to save the repository
Jul 18, 2007 3:18:50 PM Info: Finished saving the repository
Jul 18, 2007 3:18:50 PM Info: Starting: Update: Selected development component 'tc_SL_SDM_Util'/'sap.com'/'SAP AG'/'7.0010.20061019070020.0000'/'0' updates currently deployed development component 'tc_SL_SDM_Util'/'sap.com'/'SAP AG'/'6.4014.00.0000.20050818153711.0000'/'0'.
Jul 18, 2007 3:18:50 PM Info: SDA to be deployed: D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc_SL_SDM_Util\SAP AG\0\7.0010.20061019070020.0000\SDMutil.sda
Jul 18, 2007 3:18:50 PM Info: Software type of SDA: library
Jul 18, 2007 3:18:50 PM Info: ***** Begin of SAP J2EE Engine Deployment (Library component of SAP J2EE Engine) *****
Jul 18, 2007 3:18:50 PM Info: Begin of log messages of the target system:
07/07/18 15:18:50 - ***********************************************************
07/07/18 15:18:50 - Start deploying library JAR D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc_SL_SDM_Util\SAP AG\0\7.0010.20061019070020.0000\SDMutil.sda...
07/07/18 15:18:50 - Library D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc_SL_SDM_Util\SAP AG\0\7.0010.20061019070020.0000\SDMutil.sda successfully deployed on the server.
Jul 18, 2007 3:18:50 PM Info: End of log messages of the target system.
Jul 18, 2007 3:18:50 PM Info: ***** End of SAP J2EE Engine Deployment (Library component of SAP J2EE Engine) *****
Jul 18, 2007 3:18:50 PM Info: Finished successfully: development component 'tc_SL_SDM_Util'/'sap.com'/'SAP AG'/'7.0010.20061019070020.0000'/'0', grouped by
Jul 18, 2007 3:18:50 PM Info: Starting to save the repository
Jul 18, 2007 3:18:51 PM Info: Finished saving the repository
Jul 18, 2007 3:18:51 PM Info: Starting: Initial deployment: Selected development component 'tc/sdt/cvl'/'sap.com'/'SAP AG'/'7.0010.20060210160258.0000'/'0' will be deployed.
Jul 18, 2007 3:18:51 PM Info: SDA to be deployed: D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc\sdt\cvl\SAP AG\0\7.0010.20060210160258.0000\sap.comtcsdt~cvl.sda
Jul 18, 2007 3:18:51 PM Info: Software type of SDA: library
Jul 18, 2007 3:18:51 PM Info: ***** Begin of SAP J2EE Engine Deployment (Library component of SAP J2EE Engine) *****
Jul 18, 2007 3:18:52 PM Info: Begin of log messages of the target system:
07/07/18 15:18:51 - ***********************************************************
07/07/18 15:18:51 - Start deploying library JAR D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc\sdt\cvl\SAP AG\0\7.0010.20060210160258.0000\sap.comtcsdt~cvl.sda...
07/07/18 15:18:52 - Library D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc\sdt\cvl\SAP AG\0\7.0010.20060210160258.0000\sap.comtcsdt~cvl.sda successfully deployed on the server.
Jul 18, 2007 3:18:52 PM Info: End of log messages of the target system.
Jul 18, 2007 3:18:52 PM Info: ***** End of SAP J2EE Engine Deployment (Library component of SAP J2EE Engine) *****
Jul 18, 2007 3:18:52 PM Info: Finished successfully: development component 'tc/sdt/cvl'/'sap.com'/'SAP AG'/'7.0010.20060210160258.0000'/'0', grouped by software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.11.0.20070201154800''/'0'
Jul 18, 2007 3:18:52 PM Info: Starting to save the repository
Jul 18, 2007 3:18:52 PM Info: Finished saving the repository
Jul 18, 2007 3:18:52 PM Info: Starting: Initial deployment: Selected software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.11.0.20070201154800''/'0' will be deployed.
Jul 18, 2007 3:18:52 PM Error: Aborted: software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.11.0.20070201154800''/'0':
Failed deployment of SDAs:
development component 'tc/wd/samples/testsuite/uuie'/'sap.com'/'SAP AG'/'7.0010.20061002110342.0000'/'0' : aborted
Please, look at error logs above for more information!
Jul 18, 2007 3:18:52 PM Info: Starting to save the repository
Jul 18, 2007 3:18:52 PM Info: Finished saving the repository
Jul 18, 2007 3:18:52 PM Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
Jul 18, 2007 3:18:52 PM Error: -
At least one of the Deployments failed -
Jul 18, 2007 3:18:53 PM Info: Summarizing the deployment results:
Jul 18, 2007 3:18:53 PM Info: OK: D:\SAPEPD\saploc\jupgrade\data\archives\EPBC11_0-10003473.SCA
Jul 18, 2007 3:18:53 PM Error: Aborted: D:\SAPEPD\saploc\jupgrade\data\archives\SAPJTECHS11_0-10003467.SCA
Jul 18, 2007 3:18:53 PM Error: Processing error. Return code: 4
END DEPLOY_SLOT_0__DON_01.LOG----
I SAW the SDN forum and talk about the question
Nw2004s Upgrade: Error in phase DEPLOY_ONLINE
but this one doesnu00B4t work
best regards
Luis MorenoHi
I resolved the issue by undeploying the TestSuiteUUIE component using SDM.
Thanks
Naresh P. -
Error during upgrade EP 6.0 on netweaver 2004 to EP7.0 netweaver 2004s
Hi
We are upgrading our EP system from EP6 Netweaver 2004 SP19 to EP7
Netweaver 2004s SP11 using SAPJUP and get stuck at deploy_online phase.
And the Failed deployment of SDAs:
component 'caf/eu/gp/content'/'sap.com'/'MAIN_APL70VAL_C'/'1078319'/'20' : aborted
OS: AIX 5.2
DB: Oracle 10.2.0.2.0
And in the log, it says ORA-00001 error.
Please find the details in the log.
Pls help.
Thanks
Stanley
07/03/12 20:06:08 - ***********************************************************
07/03/12 20:06:08 - Start deploying library JAR /usr/sap/EPS/JC00/SDM/root/origin/sap.com/caf/eu/gp/bpel/MAIN_APL70VAL_C/20/1077649/sap.com_cafeugp~bpel.sda...
07/03/12 20:06:11 - Library /usr/sap/EPS/JC00/SDM/root/origin/sap.com/caf/eu/gp/bpel/MAIN_APL70VAL_C/20/1077649/sap.com_cafeugp~bpel.sda successfully deployed on the server.
Mar 12, 2007 8:06:11 PM Info: End of log messages of the target system.
Mar 12, 2007 8:06:11 PM Info: ***** End of SAP J2EE Engine Deployment (Library component of SAP J2EE Engine) *****
Mar 12, 2007 8:06:11 PM Info: Finished successfully: development component 'caf/eu/gp/bpel'/'sap.com'/'MAIN_APL70VAL_C'/'1077649'/'20', grouped by
Mar 12, 2007 8:06:11 PM Info: Starting to save the repository
Mar 12, 2007 8:06:12 PM Info: Finished saving the repository
Mar 12, 2007 8:06:12 PM Info: Starting: Initial deployment: Selected development component 'caf/eu/gp/content'/'sap.com'/'MAIN_APL70VAL_C'/'1078319'/'20' will be deployed.
Mar 12, 2007 8:06:12 PM Info: SDA to be deployed: /usr/sap/EPS/JC00/SDM/root/origin/sap.com/caf/eu/gp/content/MAIN_APL70VAL_C/20/1078319/sap.com_cafeugp~content.sda
Mar 12, 2007 8:06:12 PM Info: Software type of SDA: J2EE
Mar 12, 2007 8:06:12 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Mar 12, 2007 8:06:26 PM Info: Begin of log messages of the target system:
07/03/12 20:06:12 - ***********************************************************
07/03/12 20:06:13 - Start updating EAR file...
07/03/12 20:06:13 - start-up mode is lazy
07/03/12 20:06:13 - EAR file updated successfully for 84ms.
07/03/12 20:06:13 - Start deploying ...
07/03/12 20:06:16 - EAR file uploaded to server for 1366ms.
07/03/12 20:06:26 - ERROR: Not deployed. Deploy Service returned ERROR:
java.rmi.RemoteException: Cannot deploy application sap.com/cafeugp~content..
Reason: <--Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='ORA-00001: unique constraint (SAPEPPDB.SYS_C005673) violated
', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key ORA-00001: unique constraint (SAPEPPDB.SYS_C005673) violated
; nested exception is:
com.sap.engine.services.deploy.container.DeploymentException: <--Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='ORA-00001: unique constraint (SAPEPPDB.SYS_C005673) violated
', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key ORA-00001: unique constraint (SAPEPPDB.SYS_C005673) violated
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(Compiled Code))
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java(Inlined Compiled Code))
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java(Compiled Code))
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java(Compiled Code))
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java(Compiled Code))
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java(Compiled Code))
at java.security.AccessController.doPrivileged1(Native Method)
at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code))
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java(Compiled Code))
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java(Compiled Code))
Caused by: com.sap.engine.services.deploy.container.DeploymentException: <--Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='ORA-00001: unique constraint (SAPEPPDB.SYS_C005673) violated
', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key ORA-00001: unique constraint (SAPEPPDB.SYS_C005673) violated
at com.sap.caf.eu.gp.model.fnd.transport.impl.DeployContainerImpl.reportException(DeployContainerImpl.java:729)
at com.sap.caf.eu.gp.model.fnd.transport.impl.DeployContainerImpl.deploy(DeployContainerImpl.java:143)
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(Compiled Code))
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)
... 11 more
For detailed information see the log file of the Deploy Service.
07/03/12 20:06:26 - ***********************************************************
Mar 12, 2007 8:06:26 PM Info: End of log messages of the target system.
Mar 12, 2007 8:06:26 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Mar 12, 2007 8:06:26 PM Error: Aborted: development component 'caf/eu/gp/content'/'sap.com'/'MAIN_APL70VAL_C'/'1078319'/'20', grouped by software component 'SAP-EU'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.11.0.20070202075922''/'20':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot deploy application sap.com/cafeugp~content..
Reason: <--Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='ORA-00001: unique constraint (SAPEPPDB.SYS_C005673) violated
', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key ORA-00001: unique constraint (SAPEPPDB.SYS_C005673) violated
; nested exception is:
com.sap.engine.services.deploy.container.DeploymentException: <--Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='ORA-00001: unique constraint (SAPEPPDB.SYS_C005673) violated
', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key ORA-00001: unique constraint (SAPEPPDB.SYS_C005673) violated
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Mar 12, 2007 8:06:26 PM Info: Starting to save the repository
Mar 12, 2007 8:06:27 PM Info: Finished saving the repository
Mar 12, 2007 8:06:27 PM Info: Starting: Update: Selected development component 'caf/eu/gp/content/portal'/'sap.com'/'MAIN_APL70VAL_C'/'1077400'/'20' updates currently deployed development component 'caf/eu/gp/content/portal'/'sap.com'/'MAIN_APL70VAL_C'/'1077400'/'18'.
Mar 12, 2007 8:06:27 PM Info: SDA to be deployed: /usr/sap/EPS/JC00/SDM/root/origin/sap.com/caf/eu/gp/content/portal/MAIN_APL70VAL_C/20/1077400/sap.com_cafeugpcontentportal.sda
Mar 12, 2007 8:06:27 PM Info: Software type of SDA: J2EE
Mar 12, 2007 8:06:27 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Mar 12, 2007 8:06:32 PM Info: Begin of log messages of the target system:
07/03/12 20:06:27 - ***********************************************************
07/03/12 20:06:28 - Start updating EAR file...
07/03/12 20:06:28 - start-up mode is lazy
07/03/12 20:06:28 - EAR file updated successfully for 76ms.
07/03/12 20:06:28 - Start updating...
07/03/12 20:06:31 - EAR file uploaded to server for 1289ms.
07/03/12 20:06:31 - Successfully updated. Update took 95ms.
07/03/12 20:06:31 - Deploy Service status:
07/03/12 20:06:31 - Application : sap.com/cafeugpcontentportal
07/03/12 20:06:31 -
07/03/12 20:06:31 - sap.comcafeugpcontent~portal.epa - EP
07/03/12 20:06:31 - ***********************************************************
Mar 12, 2007 8:06:32 PM Info: End of log messages of the target system.
Mar 12, 2007 8:06:32 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Mar 12, 2007 8:06:32 PM Info: Finished successfully: development component 'caf/eu/gp/content/portal'/'sap.com'/'MAIN_APL70VAL_C'/'1077400'/'20', grouped by :
The application start is forbidden, because of the server mode and action.
Mar 12, 2007 8:06:32 PM Info: Starting to save the repository
Mar 12, 2007 8:06:34 PM Info: Finished saving the repository
Mar 12, 2007 8:06:34 PM Info: Starting: Update: Selected development component 'caf/eu/gp/croom/api'/'sap.com'/'MAIN_APL70VAL_C'/'1077440'/'20' updates currently deployed development component 'caf/eu/gp/croom/api'/'sap.com'/'MAIN_APL70VAL_C'/'1077440'/'18'.
Mar 12, 2007 8:06:34 PM Info: SDA to be deployed: /usr/sap/EPS/JC00/SDM/root/origin/sap.com/caf/eu/gp/croom/api/MAIN_APL70VAL_C/20/1077440/sap.com_cafeugpcroomapi.sda
Mar 12, 2007 8:06:34 PM Info: Software type of SDA: library
Mar 12, 2007 8:06:34 PM Info: ***** Begin of SAP J2EE Engine Deployment (Library component of SAP J2EE Engine) *****
Mar 12, 2007 8:06:37 PM Info: Begin of log messages of the target system:
07/03/12 20:06:34 - ***********************************************************
07/03/12 20:06:34 - Start deploying library JAR /usr/sap/EPS/JC00/SDM/root/origin/sap.com/caf/eu/gp/croom/api/MAIN_APL70VAL_C/20/1077440/sap.com_cafeugpcroomapi.sda...
07/03/12 20:06:37 - Library /usr/sap/EPS/JC00/SDM/root/origin/sap.com/caf/eu/gp/croom/api/MAIN_APL70VAL_C/20/1077440/sap.com_cafeugpcroomapi.sda successfully deployed on the server.
Mar 12, 2007 8:06:37 PM Info: End of log messages of the target system.
Mar 12, 2007 8:06:37 PM Info: ***** End of SAP J2EE Engine Deployment (Library component of SAP J2EE Engine) *****
Mar 12, 2007 8:06:37 PM Info: Finished successfully: development component 'caf/eu/gp/croom/api'/'sap.com'/'MAIN_APL70VAL_C'/'1077440'/'20', grouped by
Mar 12, 2007 8:06:37 PM Info: Starting to save the repository
Mar 12, 2007 8:06:38 PM Info: Finished saving the repository
Mar 12, 2007 8:06:38 PM Info: Starting: Update: Selected development component 'caf/eu/gp/croom/bg'/'sap.com'/'MAIN_APL70VAL_C'/'1078197'/'20' updates currently deployed development component 'caf/eu/gp/croom/bg'/'sap.com'/'MAIN_APL70VAL_C'/'1078197'/'18'.
Mar 12, 2007 8:06:38 PM Info: SDA to be deployed: /usr/sap/EPS/JC00/SDM/root/origin/sap.com/caf/eu/gp/croom/bg/MAIN_APL70VAL_C/20/1078197/sap.com_cafeugpcroombg.sda
Mar 12, 2007 8:06:38 PM Info: Software type of SDA: library
Mar 12, 2007 8:06:38 PM Info: ***** Begin of SAP J2EE Engine Deployment (Library component of SAP J2EE Engine) *****
Mar 12, 2007 8:06:42 PM Info: Begin of log messages of the target system:
07/03/12 20:06:39 - ***********************************************************
07/03/12 20:06:39 - Start deploying library JAR /usr/sap/EPS/JC00/SDM/root/origin/sap.com/caf/eu/gp/croom/bg/MAIN_APL70VAL_C/20/1078197/sap.com_cafeugpcroombg.sda...
07/03/12 20:06:42 - Library /usr/sap/EPS/JC00/SDM/root/origin/sap.com/caf/eu/gp/croom/bg/MAIN_APL70VAL_C/20/1078197/sap.com_cafeugpcroombg.sda successfully deployed on the server.
Mar 12, 2007 8:06:42 PM Info: End of log messages of the target system.
Mar 12, 2007 8:06:42 PM Info: ***** End of SAP J2EE Engine Deployment (Library component of SAP J2EE Engine) *****
Mar 12, 2007 8:06:42 PM Info: Finished successfully: development component 'caf/eu/gp/croom/bg'/'sap.com'/'MAIN_APL70VAL_C'/'1078197'/'20', grouped by
Mar 12, 2007 8:06:42 PM Info: Starting to save the repository
Mar 12, 2007 8:06:43 PM Info: Finished saving the repository
Mar 12, 2007 8:06:43 PM Info: Starting: Update: Selected development component 'caf/eu/gp/croom/content'/'sap.com'/'MAIN_APL70VAL_C'/'1078328'/'20' updates currently deployed development component 'caf/eu/gp/croom/content'/'sap.com'/'MAIN_APL70VAL_C'/'1078328'/'18'.
Mar 12, 2007 8:06:43 PM Info: SDA to be deployed: /usr/sap/EPS/JC00/SDM/root/origin/sap.com/caf/eu/gp/croom/content/MAIN_APL70VAL_C/20/1078328/sap.com_cafeugpcroomcontent.sda
Mar 12, 2007 8:06:43 PM Info: Software type of SDA: J2EE
Mar 12, 2007 8:06:43 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Mar 12, 2007 8:07:01 PM Info: Begin of log messages of the target system:
07/03/12 20:06:43 - ***********************************************************
07/03/12 20:06:44 - Start updating EAR file...
07/03/12 20:06:44 - start-up mode is lazy
07/03/12 20:06:44 - EAR file updated successfully for 136ms.
07/03/12 20:06:44 - Start updating...
07/03/12 20:06:47 - EAR file uploaded to server for 2450ms.
07/03/12 20:07:00 - Successfully updated. Update took 12031ms.
07/03/12 20:07:00 - Deploy Service status:
07/03/12 20:07:00 - Application : sap.com/cafeugpcroomcontent
07/03/12 20:07:00 -
07/03/12 20:07:00 - sap.comcafeugpcroom~content.gpa - SAP-EU-GP
07/03/12 20:07:00 - ***********************************************************
Mar 12, 2007 8:07:01 PM Info: End of log messages of the target system.
Mar 12, 2007 8:07:01 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Mar 12, 2007 8:07:01 PM Info: Finished successfully: development component 'caf/eu/gp/croom/content'/'sap.com'/'MAIN_APL70VAL_C'/'1078328'/'20', grouped by :
The application start is forbidden, because of the server mode and action.
Mar 12, 2007 8:07:01 PM Info: Starting to save the repository
Mar 12, 2007 8:07:02 PM Info: Finished saving the repository
Mar 12, 2007 8:07:02 PM Info: Starting: Update: Selected development component 'caf/eu/gp/croom/service'/'sap.com'/'MAIN_APL70VAL_C'/'1077658'/'20' updates currently deployed development component 'caf/eu/gp/croom/service'/'sap.com'/'MAIN_APL70VAL_C'/'1077658'/'18'.
Mar 12, 2007 8:07:02 PM Info: SDA to be deployed: /usr/sap/EPS/JC00/SDM/root/origin/sap.com/caf/eu/gp/croom/service/MAIN_APL70VAL_C/20/1077658/sap.com_cafeugpcroomservice.sda
Mar 12, 2007 8:07:02 PM Info: Software type of SDA: J2EE
Mar 12, 2007 8:07:02 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Mar 12, 2007 8:07:06 PM Info: Begin of log messages of the target system:
07/03/12 20:07:02 - ***********************************************************
07/03/12 20:07:03 - Start updating EAR file...
07/03/12 20:07:03 - start-up mode is lazy
07/03/12 20:07:03 - EAR file updated successfully for 17ms.
07/03/12 20:07:03 - Start updating...
07/03/12 20:07:05 - EAR file uploaded to server for 806ms.
07/03/12 20:07:05 - Successfully updated. Update took 69ms.
07/03/12 20:07:05 - Deploy Service status:
07/03/12 20:07:05 - Application : sap.com/cafeugpcroomservice
07/03/12 20:07:05 -
07/03/12 20:07:05 - caf.eu.gp.croom.service.par - EP
07/03/12 20:07:05 - ***********************************************************
Mar 12, 2007 8:07:06 PM Info: End of log messages of the target system.
Mar 12, 2007 8:07:06 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Mar 12, 2007 8:07:07 PM Info: Finished successfully: development component 'caf/eu/gp/croom/service'/'sap.com'/'MAIN_APL70VAL_C'/'1077658'/'20', grouped by :
The application start is forbidden, because of the server mode and action.
Mar 12, 2007 8:07:07 PM Info: Starting to save the repository
Mar 12, 2007 8:07:08 PM Info: Finished saving the repository
Mar 12, 2007 8:07:08 PM Info: Starting: Update: Selected development component 'caf/eu/gp/croom/wd'/'sap.com'/'MAIN_APL70VAL_C'/'964691'/'20' updates currently deployed development component 'caf/eu/gp/croom/wd'/'sap.com'/'MAIN_APL70VAL_C'/'964691'/'18'.
Mar 12, 2007 8:07:08 PM Info: SDA to be deployed: /usr/sap/EPS/JC00/SDM/root/origin/sap.com/caf/eu/gp/croom/wd/MAIN_APL70VAL_C/20/964691/sap.com_cafeugpcroomwd.sda
Mar 12, 2007 8:07:08 PM Info: Software type of SDA: J2EE
Mar 12, 2007 8:07:08 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Mar 12, 2007 8:07:14 PM Info: Begin of log messages of the target system:
07/03/12 20:07:08 - ***********************************************************
07/03/12 20:07:09 - Start updating EAR file...
07/03/12 20:07:09 - start-up mode is lazy
07/03/12 20:07:09 - EAR file updated successfully for 55ms.
07/03/12 20:07:09 - Start updating...
07/03/12 20:07:12 - EAR file uploaded to server for 1676ms.
07/03/12 20:07:13 - Successfully updated. Update took 438ms.
07/03/12 20:07:13 - Deploy Service status:
07/03/12 20:07:13 - Application : sap.com/cafeugpcroomwd
07/03/12 20:07:13 -
07/03/12 20:07:13 - sap.com/cafeugpcroomwd - WEBDYNPRO
07/03/12 20:07:13 - ***********************************************************
Mar 12, 2007 8:07:14 PM Info: End of log messages of the target system.
Mar 12, 2007 8:07:14 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Mar 12, 2007 8:07:14 PM Info: Finished successfully: development component 'caf/eu/gp/croom/wd'/'sap.com'/'MAIN_APL70VAL_C'/'964691'/'20', grouped by :
The application start is forbidden, because of the server mode and action.
Mar 12, 2007 8:07:14 PM Info: Starting to save the repository
Mar 12, 2007 8:07:15 PM Info: Finished saving the repository
Mar 12, 2007 8:07:15 PM Info: Starting: Update: Selected development component 'caf/eu/gp/example/ordermat/def'/'sap.com'/'MAIN_APL70VAL_C'/'1078326'/'20' updates currently deployed development component 'caf/eu/gp/example/ordermat/def'/'sap.com'/'MAIN_APL70VAL_C'/'1078326'/'18'.
Mar 12, 2007 8:07:15 PM Info: SDA to be deployed: /usr/sap/EPS/JC00/SDM/root/origin/sap.com/caf/eu/gp/example/ordermat/def/MAIN_APL70VAL_C/20/1078326/sap.com_cafeugpexampleordermat~def.sda
Mar 12, 2007 8:07:15 PM Info: Software type of SDA: J2EE
Mar 12, 2007 8:07:15 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Mar 12, 2007 8:07:35 PM Info: Begin of log messages of the target system:
07/03/12 20:07:15 - ***********************************************************
07/03/12 20:07:16 - Start updating EAR file...
07/03/12 20:07:16 - start-up mode is lazy
07/03/12 20:07:16 - EAR file updated successfully for 148ms.
07/03/12 20:07:16 - Start updating...
07/03/12 20:07:20 - EAR file uploaded to server for 2976ms.
07/03/12 20:07:34 - Successfully updated. Update took 13320ms.
07/03/12 20:07:34 - Deploy Service status:
07/03/12 20:07:34 - Application : sap.com/cafeugpexampleordermat~def
07/03/12 20:07:34 -
07/03/12 20:07:34 - sap.comcafeugpexampleordermatdef.gpa - SAP-EU-GP
07/03/12 20:07:34 - ***********************************************************
Mar 12, 2007 8:07:35 PM Info: End of log messages of the target system.
Mar 12, 2007 8:07:35 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Mar 12, 2007 8:07:35 PM Info: Finished successfully: development component 'caf/eu/gp/example/ordermat/def'/'sap.com'/'MAIN_APL70VAL_C'/'1078326'/'20', grouped by :
The application start is forbidden, because of the server mode and action.
Mar 12, 2007 8:07:35 PM Info: Starting to save the repository
Mar 12, 2007 8:07:37 PM Info: Finished saving the repository
Mar 12, 2007 8:07:37 PM Info: Starting: Update: Selected development component 'caf/eu/gp/example/ordermat/wd'/'sap.com'/'MAIN_APL70VAL_C'/'964174'/'20' updates currently deployed development component 'caf/eu/gp/example/ordermat/wd'/'sap.com'/'MAIN_APL70VAL_C'/'964174'/'18'.
Mar 12, 2007 8:07:37 PM Info: SDA to be deployed: /usr/sap/EPS/JC00/SDM/root/origin/sap.com/caf/eu/gp/example/ordermat/wd/MAIN_APL70VAL_C/20/964174/sap.com_cafeugpexampleordermat~wd.sda
Mar 12, 2007 8:07:37 PM Info: Software type of SDA: J2EE
Mar 12, 2007 8:07:37 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Mar 12, 2007 8:07:42 PM Info: Begin of log messages of the target system:
07/03/12 20:07:37 - ***********************************************************
07/03/12 20:07:37 - Start updating EAR file...
07/03/12 20:07:37 - start-up mode is lazy
07/03/12 20:07:37 - EAR file updated successfully for 49ms.
07/03/12 20:07:37 - Start updating...
07/03/12 20:07:40 - EAR file uploaded to server for 1367ms.
07/03/12 20:07:41 - Successfully updated. Update took 309ms.
07/03/12 20:07:41 - Deploy Service status:
07/03/12 20:07:41 - Application : sap.com/cafeugpexampleordermat~wd
07/03/12 20:07:41 -
07/03/12 20:07:41 - sap.com/cafeugpexampleordermat~wd - WEBDYNPRO
07/03/12 20:07:41 - ***********************************************************
Mar 12, 2007 8:07:42 PM Info: End of log messages of the target system.
Mar 12, 2007 8:07:42 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Mar 12, 2007 8:07:42 PM Info: Finished successfully: development component 'caf/eu/gp/example/ordermat/wd'/'sap.com'/'MAIN_APL70VAL_C'/'964174'/'20', grouped by :
The application start is forbidden, because of the server mode and action.
Mar 12, 2007 8:07:42 PM Info: Starting to save the repository
Mar 12, 2007 8:07:43 PM Info: Finished saving the repository
Mar 12, 2007 8:07:43 PM Info: Starting: Update: Selected development component 'caf/eu/gp/example/timeoff/def'/'sap.com'/'MAIN_APL70VAL_C'/'1078320'/'20' updates currently deployed development component 'caf/eu/gp/example/timeoff/def'/'sap.com'/'MAIN_APL70VAL_C'/'1078320'/'18'.
Mar 12, 2007 8:07:43 PM Info: SDA to be deployed: /usr/sap/EPS/JC00/SDM/root/origin/sap.com/caf/eu/gp/example/timeoff/def/MAIN_APL70VAL_C/20/1078320/sap.com_cafeugpexampletimeoff~def.sda
Mar 12, 2007 8:07:43 PM Info: Software type of SDA: J2EE
Mar 12, 2007 8:07:43 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Mar 12, 2007 8:08:03 PM Info: Begin of log messages of the target system:
07/03/12 20:07:43 - ***********************************************************
07/03/12 20:07:44 - Start updating EAR file...
07/03/12 20:07:44 - start-up mode is lazy
07/03/12 20:07:44 - EAR file updated successfully for 97ms.
07/03/12 20:07:44 - Start updating...
07/03/12 20:07:48 - EAR file uploaded to server for 2573ms.
07/03/12 20:08:01 - Successfully updated. Update took 13402ms.
07/03/12 20:08:01 - Deploy Service status:
07/03/12 20:08:01 - Application : sap.com/cafeugpexampletimeoff~def
07/03/12 20:08:01 -
07/03/12 20:08:01 - sap.comcafeugpexampletimeoffdef.gpa - SAP-EU-GP
07/03/12 20:08:01 - ***********************************************************
Mar 12, 2007 8:08:03 PM Info: End of log messages of the target system.
Mar 12, 2007 8:08:03 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Mar 12, 2007 8:08:03 PM Info: Finished successfully: development component 'caf/eu/gp/example/timeoff/def'/'sap.com'/'MAIN_APL70VAL_C'/'1078320'/'20', grouped by :
The application start is forbidden, because of the server mode and action.
Mar 12, 2007 8:08:03 PM Info: Starting to save the repository
Mar 12, 2007 8:08:04 PM Info: Finished saving the repository
Mar 12, 2007 8:08:04 PM Info: Starting: Update: Selected development component 'caf/eu/gp/km/conn'/'sap.com'/'MAIN_APL70VAL_C'/'1077880'/'20' updates currently deployed development component 'caf/eu/gp/km/conn'/'sap.com'/'MAIN_APL70VAL_C'/'1077880'/'18'.
Mar 12, 2007 8:08:04 PM Info: SDA to be deployed: /usr/sap/EPS/JC00/SDM/root/origin/sap.com/caf/eu/gp/km/conn/MAIN_APL70VAL_C/20/1077880/sap.com_cafeugpkmconn.sda
Mar 12, 2007 8:08:04 PM Info: Software type of SDA: J2EE
Mar 12, 2007 8:08:04 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Mar 12, 2007 8:08:09 PM Info: Begin of log messages of the target system:
07/03/12 20:08:04 - ***********************************************************
07/03/12 20:08:05 - Start updating EAR file...
07/03/12 20:08:05 - start-up mode is lazy
07/03/12 20:08:05 - EAR file updated successfully for 35ms.
07/03/12 20:08:05 - Start updating...
07/03/12 20:08:07 - EAR file uploaded to server for 995ms.
07/03/12 20:08:07 - Successfully updated. Update took 86ms.
07/03/12 20:08:07 - Deploy Service status:
07/03/12 20:08:07 - Application : sap.com/cafeugpkmconn
07/03/12 20:08:07 -
07/03/12 20:08:07 - sap.comcafeugpkm~conn.par - EP
07/03/12 20:08:07 - ***********************************************************
Mar 12, 2007 8:08:09 PM Info: End of log messages of the target system.
Mar 12, 2007 8:08:09 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Mar 12, 2007 8:08:09 PM Info: Finished successfully: development component 'caf/eu/gp/km/conn'/'sap.com'/'MAIN_APL70VAL_C'/'1077880'/'20', grouped by :
The application start is forbidden, because of the server mode and action.
Mar 12, 2007 8:08:09 PM Info: Starting to save the repository
Mar 12, 2007 8:08:10 PM Info: Finished saving the repository
Mar 12, 2007 8:08:10 PM Info: Starting: Update: Selected development component 'caf/eu/gp/mail/ui'/'sap.com'/'MAIN_APL70VAL_C'/'963535'/'20' updates currently deployed development component 'caf/eu/gp/mail/ui'/'sap.com'/'MAIN_APL70VAL_C'/'963535'/'18'.
Mar 12, 2007 8:08:10 PM Info: SDA to be deployed: /usr/sap/EPS/JC00/SDM/root/origin/sap.com/caf/eu/gp/mail/ui/MAIN_APL70VAL_C/20/963535/sap.com_cafeugpmailui.sda
Mar 12, 2007 8:08:10 PM Info: Software type of SDA: J2EE
Mar 12, 2007 8:08:10 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Mar 12, 2007 8:08:15 PM Info: Begin of log messages of the target system:
07/03/12 20:08:10 - ***********************************************************
07/03/12 20:08:11 - Start updating EAR file...
07/03/12 20:08:11 - start-up mode is lazy
07/03/12 20:08:11 - EAR file updated successfully for 15ms.
07/03/12 20:08:11 - Start updating...
07/03/12 20:08:13 - EAR file uploaded to server for 877ms.
07/03/12 20:08:13 - Successfully updated. Update took 173ms.
07/03/12 20:08:13 - Deploy Service status:
07/03/12 20:08:13 - Application : sap.com/cafeugpmailui
07/03/12 20:08:13 -
07/03/12 20:08:13 - sap.com/cafeugpmailui - WEBDYNPRO
07/03/12 20:08:13 - ***********************************************************
Mar 12, 2007 8:08:15 PM Info: End of log messages of the target system.
Mar 12, 2007 8:08:15 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Mar 12, 2007 8:08:15 PM Info: Finished successfully: development component 'caf/eu/gp/mail/ui'/'sap.com'/'MAIN_APL70VAL_C'/'963535'/'20', grouped by :
The application start is forbidden, because of the server mode and action.
Mar 12, 2007 8:08:15 PM Info: Starting to save the repository
Mar 12, 2007 8:08:16 PM Info: Finished saving the repository
Mar 12, 2007 8:08:16 PM Info: Starting: Update: Selected development component 'caf/eu/gp/model/bwfbck/eap'/'sap.com'/'MAIN_APL70VAL_C'/'964048'/'20' updates currently deployed development component 'caf/eu/gp/model/bwfbck/eap'/'sap.com'/'MAIN_APL70VAL_C'/'964048'/'18'.
Mar 12, 2007 8:08:16 PM Info: SDA to be deployed: /usr/sap/EPS/JC00/SDM/root/origin/sap.com/caf/eu/gp/model/bwfbck/eap/MAIN_APL70VAL_C/20/964048/sap.com_cafeugpmodelbwfbck~eap.sda
Mar 12, 2007 8:08:16 PM Info: Software type of SDA: J2EE
Mar 12, 2007 8:08:16 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Mar 12, 2007 8:08:28 PM Info: Begin of log messages of the target system:
07/03/12 20:08:16 - ***********************************************************
07/03/12 20:08:17 - Start updating EAR file...
07/03/12 20:08:17 - start-up mode is lazy
07/03/12 20:08:17 - EAR file updated successfully for 33ms.
07/03/12 20:08:17 - Start updating...
07/03/12 20:08:19 - EAR file uploaded to server for 996ms.
07/03/12 20:08:25 - Successfully updated. Update took 6065ms.
07/03/12 20:08:25 - Deploy Service status:
07/03/12 20:08:25 - Application : sap.com/cafeugpmodelbwfbck~eap
07/03/12 20:08:25 -
07/03/12 20:08:25 - BackGroundActionProcessorBean - EJB
07/03/12 20:08:25 - SyncBackGroundActionProcessorBean - EJB
07/03/12 20:08:25 - AsynchBackgroundActionProcessorBean - EJB
07/03/12 20:08:25 - DueDateProcessingBean - EJB
07/03/12 20:08:25 - sap.com/cafeugpmodelbwfbck~eap - METAMODELREPOSITORY
07/03/12 20:08:25 - ***********************************************************
Mar 12, 2007 8:08:28 PM Info: End of log messages of the target system.
Mar 12, 2007 8:08:28 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Mar 12, 2007 8:08:28 PM Info: Finished successfully: development component 'caf/eu/gp/model/bwfbck/eap'/'sap.com'/'MAIN_APL70VAL_C'/'964048'/'20', grouped by :
The application start is forbidden, because of the server mode and action.
Mar 12, 2007 8:08:28 PM Info: Starting to save the repository
Mar 12, 2007 8:08:30 PM Info: Finished saving the repository
Mar 12, 2007 8:08:30 PM Info: Starting: Update: Selected development component 'caf/eu/gp/model/iforms/eap'/'sap.com'/'MAIN_APL70VAL_C'/'1078385'/'20' updates currently deployed development component 'caf/eu/gp/model/iforms/eap'/'sap.com'/'MAIN_APL70VAL_C'/'1078385'/'18'.
Mar 12, 2007 8:08:30 PM Info: SDA to be deployed: /usr/sap/EPS/JC00/SDM/root/origin/sap.com/caf/eu/gp/model/iforms/eap/MAIN_APL70VAL_C/20/1078385/sap.com_cafeugpmodeliforms~eap.sda
Mar 12, 2007 8:08:30 PM Info: Software type of SDA: J2EE
Mar 12, 2007 8:08:30 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Mar 12, 2007 8:08:39 PM Info: Begin of log messages of the target system:
07/03/12 20:08:30 - ***********************************************************
07/03/12 20:08:31 - Start updating EAR file...
07/03/12 20:08:31 - start-up mode is lazy
07/03/12 20:08:31 - EAR file updated successfully for 100ms.
07/03/12 20:08:31 - Start updating...
07/03/12 20:08:34 - EAR file uploaded to server for 1507ms.
07/03/12 20:08:38 - Successfully updated. Update took 4143ms.
07/03/12 20:08:38 - Deploy Service status:
07/03/12 20:08:38 - Application : sap.com/cafeugpmodeliforms~eap
07/03/12 20:08:38 -
07/03/12 20:08:38 - CreateFormByContextBean - EJB
07/03/12 20:08:38 - CreateFormBean - EJB
07/03/12 20:08:38 - ActivateChangesBean - EJB
07/03/12 20:08:38 - CancelChangesBean - EJB
07/03/12 20:08:38 - CreateFormByBusynessObjBean - EJB
07/03/12 20:08:38 - CreateNewVersionBean - EJB
07/03/12 20:08:38 - EnumeratePhysicalObjBean - EJB
07/03/12 20:08:38 - EnumerateTemplatesBean - EJB
07/03/12 20:08:38 - GeneratePublishUrlBean - EJB
07/03/12 20:08:38 - LockTemplateBean - EJB
07/03/12 20:08:38 - ReadTemplateConfigurationBean - EJB
07/03/12 20:08:38 - RetrievePhysicalObjByIdBean - EJB
07/03/12 20:08:38 - UpdatePhysicalObjByIdBean - EJB
07/03/12 20:08:38 - CreateXMLPrintBean - EJB
07/03/12 20:08:38 - CreateXMLPrintOnceBean - EJB
07/03/12 20:08:38 - GetAffectedTemplatesBean - EJB
07/03/12 20:08:38 - GetDesignTimeAppUrlBean - EJB
07/03/12 20:08:38 - InsertAttributesBean - EJB
07/03/12 20:08:38 - RemoveAttributesBean - EJB
07/03/12 20:08:38 - CreateFormByBODataBean - EJB
07/03/12 20:08:38 - ifcore - WEB
07/03/12 20:08:38 - sap.com/cafeugpmodeliforms~eap - METAMODELREPOSITORY
07/03/12 20:08:38 - ***********************************************************
Mar 12, 2007 8:08:39 PM Info: End of log messages of the target system.
Mar 12, 2007 8:08:39 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Mar 12, 2007 8:08:39 PM Info: Finished successfully: development component 'caf/eu/gp/model/iforms/eap'/'sap.com'/'MAIN_APL70VAL_C'/'1078385'/'20', grouped by :
The application start is forbidden, because of the server mode and action.
Mar 12, 2007 8:08:39 PM Info: Starting to save the repository
Mar 12, 2007 8:08:40 PM Info: Finished saving the repository
Mar 12, 2007 8:08:40 PM Info: Starting: Update: Selected development component 'caf/eu/gp/model/jmx'/'sap.com'/'MAIN_APL70VAL_C'/'1078191'/'20' updates currently deployed development component 'caf/eu/gp/model/jmx'/'sap.com'/'MAIN_APL70VAL_C'/'1078191'/'18'.
Mar 12, 2007 8:08:40 PM Info: SDA to be deployed: /usr/sap/EPS/JC00/SDM/root/origin/sap.com/caf/eu/gp/model/jmx/MAIN_APL70VAL_C/20/1078191/sap.com_cafeugpmodeljmx.sda
Mar 12, 2007 8:08:40 PM Info: Software type of SDA: library
Mar 12, 2007 8:08:40 PM Info: ***** Begin of SAP J2EE Engine Deployment (Library component of SAP J2EE Engine) *****
Mar 12, 2007 8:08:44 PM Info: Begin of log messages of the target system:
07/03/12 20:08:41 - ***********************************************************
07/03/12 20:08:41 - Start deploying library JAR /usr/sap/EPS/JC00/SDM/root/origin/sap.com/caf/eu/gp/model/jmx/MAIN_APL70VAL_C/20/1078191/sap.com_cafeugpmodeljmx.sda...
07/03/12 20:08:44 - Library /usr/sap/EPS/JC00/SDM/root/origin/sap.com/caf/eu/gp/model/jmx/MAIN_APL70VAL_C/20/1078191/sap.com_cafeugpmodeljmx.sda successfully deployed on the server.
Mar 12, 2007 8:08:44 PM Info: End of log messages of the target system.
Mar 12, 2007 8:08:44 PM Info: ***** End of SAP J2EE Engine Deployment (Library component of SAP J2EE Engine) *****
Mar 12, 2007 8:08:44 PM Info: Finished successfully: development component 'caf/eu/gp/model/jmx'/'sap.com'/'MAIN_APL70VAL_C'/'1078191'/'20', grouped by
Mar 12, 2007 8:08:44 PM Info: Starting to save the repository
Mar 12, 2007 8:08:45 PM Info: Finished saving the repository
Mar 12, 2007 8:08:45 PM Info: Starting: Update: Selected development component 'caf/eu/gp/model/jmx/eap'/'sap.com'/'MAIN_APL70VAL_C'/'1078258'/'20' updates currently deployed development component 'caf/eu/gp/model/jmx/eap'/'sap.com'/'MAIN_APL70VAL_C'/'1078258'/'18'.
Mar 12, 2007 8:08:45 PM Info: SDA to be deployed: /usr/sap/EPS/JC00/SDM/root/origin/sap.com/caf/eu/gp/model/jmx/eap/MAIN_APL70VAL_C/20/1078258/sap.com_cafeugpmodeljmx~eap.sda
Mar 12, 2007 8:08:45 PM Info: Software type of SDA: J2EE
Mar 12, 2007 8:08:45 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Mar 12, 2007 8:08:50 PM Info: Begin of log messages of the target system:
07/03/12 20:08:45 - ***********************************************************
07/03/12 20:08:46 - Start updating EAR file...
07/03/12 20:08:46 - start-up mode is lazy
07/03/12 20:08:46 - EAR file updated successfully for 30ms.
07/03/12 20:08:46 - Start updating...
07/03/12 20:08:48 - EAR file uploaded to server for 928ms.
07/03/12 20:08:48 - Successfully updated. Update took 270ms.
07/03/12 20:08:48 - Deploy Service status:
07/03/12 20:08:48 - Application : sap.com/cafeugpmodeljmx~eap
07/03/12 20:08:48 -
07/03/12 20:08:48 - gp_jmx_web - WEB
07/03/12 20:08:48 - sap.com/cafeugpmodeljmx~eap monitoring configuration - MONITORING CONFIGURATION
07/03/12 20:08:48 - ***********************************************************
Mar 12, 2007 8:08:50 PM Info: End of log messages of the target system.
Mar 12, 2007 8:08:50 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Mar 12, 2007 8:08:50 PM Info: Finished successfully: development component 'caf/eu/gp/model/jmx/eap'/'sap.com'/'MAIN_APL70VAL_C'/'1078258'/'20', grouped by :
The application start is forbidden, because of the server mode and action.
Mar 12, 2007 8:08:50 PM Info: Starting to save the repository
Mar 12, 2007 8:08:51 PM Info: Finished saving the repository
Mar 12, 2007 8:08:51 PM Info: Starting: Update: Selected development component 'caf/eu/gp/model/pwf/local/uwlconn'/'sap.com'/'MAIN_APL70VAL_C'/'1078002'/'20' updates currently deployed development component 'caf/eu/gp/model/pwf/local/uwlconn'/'sap.com'/'MAIN_APL70VAL_C'/'1078002'/'18'.
Mar 12, 2007 8:08:51 PM Info: SDA to be deployed: /usr/sap/EPS/JC00/SDM/root/origin/sap.com/caf/eu/gp/model/pwf/local/uwlconn/MAIN_APL70VAL_C/20/1078002/sap.com_cafeugpmodelpwflocaluwlconn.sda
Mar 12, 2007 8:08:51 PM Info: Software type of SDA: J2EE
Mar 12, 2007 8:08:51 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Mar 12, 2007 8:08:56 PM Info: Begin of log messages of the target system:
07/03/12 20:08:51 - ***********************************************************
07/03/12 20:08:52 - Start updating EAR file...
07/03/12 20:08:52 - start-up mode is lazy
07/03/12 20:08:52 - EAR file updated successfully for 18ms.
07/03/12 20:08:52 - Start updating...
07/03/12 20:08:54 - EAR file uploaded to server for 839ms.
07/03/12 20:08:54 - Successfully updated. Update took 73ms.
07/03/12 20:08:54 - Deploy Service status:
07/03/12 20:08:54 - Application : sap.com/cafeugpmodelpwflocaluwlconn
07/03/12 20:08:54 -
07/03/12 20:08:54 - caf.eu.gp.model.pwf.local.uwlconn.par - EP
07/03/12 20:08:54 - ***********************************************************
Mar 12, 2007 8:08:56 PM Info: End of log messages of the target system.
Mar 12, 2007 8:08:56 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Mar 12, 2007 8:08:56 PM Info: Finished successfully: development component 'caf/eu/gp/model/pwf/local/uwlconn'/'sap.com'/'MAIN_APL70VAL_C'/'1078002'/'20', grouped by software component 'SAP-EU'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.11.0.20070202075922''/'20':
The application start is forbidden, because of the server mode and action.
Mar 12, 2007 8:08:56 PM Info: Starting to save the repository
Mar 12, 2007 8:08:57 PM Info: Finished saving the repository
Mar 12, 2007 8:08:57 PM Info: Starting: Update: Selected development component 'caf/eu/gp/model/uwlproxy'/'sap.com'/'MAIN_APL70VAL_C'/'1077889'/'20' updates currently deployed development component 'caf/eu/gp/model/uwlproxy'/'sap.com'/'MAIN_APL70VAL_C'/'1077889'/'18'.
Mar 12, 2007 8:08:57 PM Info: SDA to be deployed: /usr/sap/EPS/JC00/SDM/root/origin/sap.com/caf/eu/gp/model/uwlproxy/MAIN_APL70VAL_C/20/1077889/sap.com_cafeugpmodeluwlproxy.sda
Mar 12, 2007 8:08:57 PM Info: Software type of SDA: J2EE
Mar 12, 2007 8:08:57 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Mar 12, 2007 8:09:03 PM Info: Begin of log messages of the target system:
07/03/12 20:08:57 - ***********************************************************
07/03/12 20:08:58 - Start updating EAR file...
07/03/12 20:08:58 - start-up mode is lazy
07/03/12 20:08:58 - EAR file updated successfully for 35ms.
07/03/12 20:08:58 - Start updating...
07/03/12 20:09:00 - EAR file uploaded to server for 1019ms.
07/03/12 20:09:01 - Successfully updated. Update took 1164ms.
07/03/12 20:09:01 - Deploy Service status:
07/03/12 20:09:01 - Application : sap.com/cafeugpmodeluwlproxy
07/03/12 20:09:01 -
07/03/12 20:09:01 - WS CLIENT: com.sap.caf.eu.gp.proxy.RuntimeFacadeWSProxy - WEBSERVICES
07/03/12 20:09:01 - WS CLIENT: com.sap.caf.eu.gp.uwl.proxy.facade - WEBSERVICES
07/03/12 20:09:01 - ***********************************************************
Mar 12, 2007 8:09:03 PM Info: End of log messages of the target system.
Mar 12, 2007 8:09:03 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Mar 12, 2007 8:09:03 PM Info: Finished successfully: development component 'caf/eu/gp/model/uwlproxy'/'sap.com'/'MAIN_APL70VAL_C'/'1077889'/'20', grouped by :
The application start is forbidden, because of the server mode and action.
Mar 12, 2007 8:09:03 PM Info: Starting to save the repository
Mar 12, 2007 8:09:04 PM Info: Finished saving the repository
Mar 12, 2007 8:09:04 PM Info: Starting: Update: Selected development component 'caf/eu/gp/smketest/eap'/'sap.com'/'MAIN_APL70VAL_C'/'964039'/'20' updates currently deployed development component 'caf/eu/gp/smketest/eap'/'sap.com'/'MAIN_APL70VAL_C'/'964039'/'18'.
Mar 12, 2007 8:09:04 PM Info: SDA to be deployed: /usr/sap/EPS/JC00/SDM/root/origin/sap.com/caf/eu/gp/smketest/eap/MAIN_APL70VAL_C/20/964039/sap.com_cafeugpsmketesteap.sda
Mar 12, 2007 8:09:04 PM Info: Software type of SDA: J2EE
Mar 12, 2007 8:09:04 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Mar 12, 2007 8:09:09 PM Info: Begin of log messages of the target system:
07/03/12 20:09:04 - ***********************************************************
07/03/12 20:09:05 - Start updating EAR file...
07/03/12 20:09:05 - start-up mode is lazy
07/03/12 20:09:05 - EAR file updated successfully for 30ms.
07/03/12 20:09:05 - Start updating...
07/03/12 20:09:07 - EAR file uploaded to server for 938ms.
07/03/12 20:09:07 - Successfully updated. Update took 226ms.
07/03/12 20:09:07 - Deploy Service status:
07/03/12 20:09:07 - Application : sap.com/cafeugpsmketesteap
07/03/12 20:09:07 -
07/03/12 20:09:07 - GPSmokeTest - WEB
07/03/12 20:09:07 - ***********************************************************
Mar 12, 2007 8:09:09 PM Info: End of log messages of the target system.
Mar 12, 2007 8:09:09 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Mar 12, 2007 8:09:09 PM Info: Finished successfully: development component 'caf/eu/gp/smketest/eap'/'sap.com'/'MAIN_APL70VAL_C'/'964039'/'20', grouped by software component 'SAP-EU'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.11.0.20070202075922''/'20':
The application start is forbidden, because of the server mode and action.
Mar 12, 2007 8:09:09 PM Info: Starting to save the repository
Mar 12, 2007 8:09:10 PM Info: Finished saving the repository
Mar 12, 2007 8:09:10 PM Info: Starting: Update: Selected development component 'caf/eu/gp/ui/co/base'/'sap.com'/'MAIN_APL70VAL_C'/'964634'/'20' updates currently deployed development component 'caf/eu/gp/ui/co/base'/'sap.com'/'MAIN_APL70VAL_C'/'964634'/'18'.
Mar 12, 2007 8:09:10 PM Info: SDA to be deployed: /usr/sap/EPS/JC00/SDM/root/origin/sap.com/caf/eu/gp/ui/co/base/MAIN_APL70VAL_C/20/964634/sap.com_cafeugpuico~base.sda
Mar 12, 2007 8:09:10 PM Info: Software type of SDA: J2EE
Mar 12, 2007 8:09:10 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Mar 12, 2007 8:09:15 PM Info: Begin of log messages of the target system:
07/03/12 20:09:10 - ***********************************************************
07/03/12 20:09:11 - Start updating EAR file...
07/03/12 20:09:11 - start-up mode is lazy
07/03/12 20:09:11 - EAR file updated successfully for 38ms.
07/03/12 20:09:11 - Start updating...
07/03/12 20:09:13 - EAR file uploaded to server for 915ms.
07/03/12 20:09:13 - Successfully updated. Update took 225ms.
07/03/12 20:09:13 - Deploy Service status:
07/03/12 20:09:13 - Application : sap.com/cafeugpuico~base
07/03/12 20:09:13 -
07/03/12 20:09:13 - sap.com/cafeugpuico~base - WEBDYNPRO
07/03/12 20:09:13 - ***********************************************************
Mar 12, 2007 8:09:15 PM Info: End of log messages of the target system.
Mar 12, 2007 8:09:15 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Mar 12, 2007 8:09:15 PM Info: Finished successfully: development component 'caf/eu/gp/ui/co/base'/'sap.com'/'MAIN_APL70VAL_C'/'964634'/'20', grouped by :
The application start is forbidden, because of the server mode and action.
Mar 12, 2007 8:09:15 PM Info: Starting to save the repository
Mar 12, 2007 8:09:16 PM Info: Finished saving the repository
Mar 12, 2007 8:09:16 PM Info: Starting: Update: Selected development component 'caf/eu/gp/ui/decision'/'sap.com'/'MAIN_APL70VAL_C'/'963501'/'20' updates currently deployed development component 'caf/eu/gp/ui/decision'/'sap.com'/'MAIN_APL70VAL_C'/'963501'/'18'.
Mar 12, 2007 8:09:16 PM Info: SDA to be deployed: /usr/sap/EPS/JC00/SDM/root/origin/sap.com/caf/eu/gp/ui/decision/MAIN_APL70VAL_C/20/963501/sap.com_cafeugpuidecision.sda
Mar 12, 2007 8:09:16 PM Info: Software type of SDA: J2EE
Mar 12, 2007 8:09:16 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Mar 12, 2007 8:09:20 PM Info: Begin of log messages of the target system:
07/03/12 20:09:16 - ***********************************************************
07/03/12 20:09:17 - Start updating EAR file...
07/03/12 20:09:17 - start-up mode is lazy
07/03/12 20:09:17 - EAR file updated successfully for 15ms.
07/03/12 20:09:17 - Start updating...
07/03/12 20:09:19 - EAR file uploaded to server for 815ms.
07/03/12 20:09:19 - Successfully updated. Update took 133ms.
07/03/12 20:09:19 - Deploy Service status:
07/03/12 20:09:19 - Application : sap.com/cafeugpuidecision
07/03/12 20:09:19 -
07/03/12 20:09:19 - sap.com/cafeugpuidecision - WEBDYNPRO
07/03/12 20:09:19 - ***********************************************************
Mar 12, 2007 8:09:20 PM Info: End of log messages of the target system.
Mar 12, 2007 8:09:20 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Mar 12, 2007 8:09:21 PM Info: Finished successfully: development component 'caf/eu/gp/ui/decision'/'sap.com'/'MAIN_APL70VAL_C'/'963501'/'20', grouped by :
The application start is forbidden, because of the server mode and action.
Mar 12, 2007 8:09:21 PM Info: Starting to save the repository
Mar 12, 2007 8:09:22 PM Info: Finished saving the repository
Mar 12, 2007 8:09:22 PM Info: Starting: Update: Selected development component 'caf/eu/gp/ui/iforms'/'sap.com'/'MAIN_APL70VAL_C'/'963541'/'20' updates currently deployed development component 'caf/eu/gp/ui/iforms'/'sap.com'/'MAIN_APL70VAL_C'/'963541'/'18'.
Mar 12, 2007 8:09:22 PM Info: SDA to be deployed: /usr/sap/EPS/JC00/SDM/root/origin/sap.com/caf/eu/gp/ui/iforms/MAIN_APL70VAL_C/20/963541/sap.com_cafeugpuiiforms.sda
Mar 12, 2007 8:09:22 PM Info: Software type of SDA: J2EE
Mar 12, 2007 8:09:22 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Mar 12, 2007 8:09:26 PM Info: Begin of log messages of the target system:
07/03/12 20:09:22 - ***********************************************************
07/03/12 20:09:22 - Start updating EAR file...
07/03/12 20:09:22 - start-up mode is lazy
07/03/12 20:09:22 - EAR file updated successfully for 16ms.
07/03/12 20:09:22 - Start updating...
07/03/12 20:09:25 - EAR file uploaded to server for 817ms.
07/03/12 20:09:25 - Successfully updated. Update took 92ms.
07/03/12 20:09:25 - Deploy Service status:
07/03/12 20:09:25 - Application : sap.com/cafeugpuiiforms
07/03/12 20:09:25 -
07/03/12 20:09:25 - sap.com/cafeugpuiiforms - WEBDYNPRO
07/03/12 20:09:25 - ***********************************************************
Mar 12, 2007 8:09:26 PM Info: End of log messages of the target system.
Mar 12, 2007 8:09:26 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Mar 12, 2007 8:09:26 PM Info: Finished successfully: development component 'caf/eu/gp/ui/iforms'/'sap.com'/'MAIN_APL70VAL_C'/'963541'/'20', grouped by :
The application start is forbidden, because of the server mode and action.
Mar 12, 2007 8:09:26 PM Info: Starting to save the repository
Mar 12, 2007 8:09:27 PM Info: Finished saving the repository
Mar 12, 2007 8:09:27 PM Info: Starting: Update: Selected development component 'caf/eu/gp/ui/migrate'/'sap.com'/'MAIN_APL70VAL_C'/'963783'/'20' updates currently deployed development component 'caf/eu/gp/ui/migrate'/'sap.com'/'MAIN_APL70VAL_C'/'963783'/'18'.
Mar 12, 2007 8:09:27 PM Info: SDA to be deployed: /usr/sap/EPS/JC00/SDM/root/origin/sap.com/caf/eu/gp/ui/migrate/MAIN_APL70VAL_C/20/963783/sap.com_cafeugpuimigrate.sda
Mar 12, 2007 8:09:27 PM Info: Software type of SDA: J2EE
Mar 12, 2007 8:09:27 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Mar 12, 2007 8:09:32 PM Info: Begin of log messages of the target system:
07/03/12 20:09:27 - ***********************************************************
07/03/12 20:09:28 - Start updating EAR file...
07/03/12 20:09:28 - start-up mode is lazy
07/03/12 20:09:28 - EAR file updated successfully for 19ms.
07/03/12 20:09:28 - Start updating...
07/03/12 20:09:31 - EAR file uploaded to server for 909ms.
07/03/12 20:09:31 - Successfully updated. Update took 167ms.
07/03/12 20:09:31 - Deploy Service status:
07/03/12 20:09:31 - Application : sap.com/cafeugpuimigrate
07/03/12 20:09:31 -
07/03/12 20:09:31 - sap.com/cafeugpuimigrate - WEBDYNPRO
07/03/12 20:09:31 - ***********************************************************
Mar 12, 2007 8:09:32 PM Info: End of log messages of the target system.
Mar 12, 2007 8:09:32 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Mar 12, 2007 8:09:32 PM Info: Finished successfully: development component 'caf/eu/gp/ui/migrate'/'sap.com'/'MAIN_APL70VAL_C'/'963783'/'20', grouped by software component 'SAP-EU'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.11.0.20070202075922''/'20':
The application start is forbidden, because of the server mode and action.
Mar 12, 2007 8:09:32 PM Info: Starting to save the repository
Mar 12, 2007 8:09:33 PM Info: Finished saving the repository
Mar 12, 2007 8:09:33 PM Info: Starting: Update: Selected development component 'caf/eu/gp/ui/mimes'/'sap.com'/'MAIN_APL70VAL_C'/'964623'/'20' updates currently deployed development component 'caf/eu/gp/ui/mimes'/'sap.com'/'MAIN_APL70VAL_C'/'964623'/'18'.
Mar 12, 2007 8:09:33 PM Info: SDA to be deployed: /usr/sap/EPS/JC00/SDM/root/origin/sap.com/caf/eu/gp/ui/mimes/MAIN_APL70VAL_C/20/964623/sap.com_cafeugpuimimes.sda
Mar 12, 2007 8:09:33 PM Info: Software type of SDA: J2EE
Mar 12, 2007 8:09:33 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Mar 12, 2007 8:09:39 PM Info: Begin of log messages of the target system:
07/03/12 20:09:33 - ***********************************************************
07/03/12 20:09:34 - Start updating EAR file...
07/03/12 20:09:34 - start-up mode is lazy
07/03/12 20:09:35 - EAR file updated successfully for 79ms.
07/03/12 20:09:35 - Start updating...
07/03/12 20:09:37 - EAR file uploaded to server for 1210ms.
07/03/12 20:09:37 - Successfully updated. Update took 232ms.
07/03/12 20:09:37 - Deploy Service status:
07/03/12 20:09:37 - Application : sap.com/cafeugpuimimes
07/03/12 20:09:37 -
07/03/12 20:09:37 - sap.com/cafeugpuimimes - WEBDYNPRO
07/03/12 20:09:37 - ***********************************************************
Mar 12, 2007 8:09:39 PM Info: End of log messages of the target system.
Mar 12, 2007 8:09:39 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Mar 12, 2007 8:09:39 PM Info: Finished successfully: development component 'caf/eu/gp/ui/mimes'/'sap.com'/'MAIN_APL70VAL_C'/'964623'/'20', grouped by :
The application start is forbidden, because of the server mode and action.
Mar 12, 2007 8:09:39 PM Info: Starting to save the repository
Mar 12, 2007 8:09:40 PM Info: Finished saving the repository
Mar 12, 2007 8:09:40 PM Info: Starting: Update: Selected development component 'caf/eu/gp/ui/notif'/'sap.com'/'MAIN_APL70VAL_C'/'964632'/'20' updates currently deployed development component 'caf/eu/gp/ui/notif'/'sap.com'/'MAIN_APL70VAL_C'/'964632'/'18'.
Mar 12, 2007 8:09:40 PM Info: SDA to be deployed: /usr/sap/EPS/JC00/SDM/root/origin/sap.com/caf/eu/gp/ui/notif/MAIN_APL70VAL_C/20/964632/sap.com_cafeugpuinotif.sda
Mar 12, 2007 8:09:40 PM Info: Software type of SDA: J2EE
Mar 12, 2007 8:09:40 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Mar 12, 2007 8:09:45 PM Info: Begin of log messages of the target system:
07/03/12 20:09:40 - ***********************************************************
07/03/12 20:09:41 - Start updating EAR file...
07/03/12 20:09:41 - start-up mode is lazy
07/03/12 20:09:41 - EAR file updated successfully for 37ms.
07/03/12 20:09:41 - Start updating...
07/03/12 20:09:43 - EAR file uploaded to server for 988ms.
07/03/12 20:09:43 - Successfully updated. Update took 263ms.
07/03/12 20:09:43 - Deploy Service status:
07/03/12 20:09:43 - Application : sap.com/cafeugpuinotif
07/03/12 20:09:43 -
07/03/12 20:09:43 - sap.com/cafeugpuinotif - WEBDYNPRO
07/03/12 20:09:43 - ***********************************************************
Mar 12, 2007 8:09:45 PM Info: End of log messages of the target system.
Mar 12, 2007 8:09:45 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Mar 12, 2007 8:09:45 PM Info: Finished successfully: development component 'caf/eu/gp/ui/notif'/'sap.com'/'MAIN_APL70VAL_C'/'964632'/'20', grouped by :
The application start is forbidden, because of the server mode and action.
Mar 12, 2007 8:09:45 PM Info: Starting to save the repository
Mar 12, 2007 8:09:46 PM Info: Finished saving the repository
Mar 12, 2007 8:09:46 PM Info: Starting: Update: Selected development component 'caf/eu/gp/ui/prt'/'sap.com'/'MAIN_APL70VAL_C'/'1077428'/'20' updates currently deployed development component 'caf/eu/gp/ui/prt'/'sap.com'/'MAIN_APL70VAL_C'/'1077428'/'18'.
Mar 12, 2007 8:09:46 PM Info: SDA to be deployed: /usr/sap/EPS/JC00/SDM/root/origin/sap.com/caf/eu/gp/ui/prt/MAIN_APL70VAL_C/20/1077428/sap.com_cafeugpuiprt.sda
Mar 12, 2007 8:09:46 PM Info: Software type of SDA: J2EE
Mar 12, 2007 8:09:46 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Mar 12, 2007 8:09:50 PM Info: Begin of log messages of the target system:
07/03/12 20:09:46 - ***********************************************************
07/03/12 20:09:47 - Start updating EAR file...
07/03/12 20:09:47 - start-up mode is lazy
07/03/12 20:09:47 - EAR file updated successfully for 17ms.
07/03/12 20:09:47 - Start updating...
07/03/12 20:09:49 - EAR file uploaded to server for 816ms.
07/03/12 20:09:49 - Successfully updated. Update took 63ms.
07/03/12 20:09:49 - Deploy Service status:
07/03/12 20:09:49 - Application : sap.com/cafeugpuiprt
07/03/12 20:09:49 -
07/03/12 20:09:49 - caf.eu.gp.ui.prt.par - EP
07/03/12 20:09:49 - ***********************************************************
Mar 12, 2007 8:09:50 PM Info: End of log messages of the target system.
Mar 12, 2007 8:09:50 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Mar 12, 2007 8:09:50 PM Info: Finished successfully: development component 'caf/eu/gp/ui/prt'/'sap.com'/'MAIN_APL70VAL_C'/'1077428'/'20', grouped by :
The application start is forbidden, because of the server mode and action.
Mar 12, 2007 8:09:50 PM Info: Starting to save the repository
Mar 12, 2007 8:09:52 PM Info: Finished saving the repository
Mar 12, 2007 8:09:52 PM Info: Starting: Update: Selected development component 'caf/eu/gp/ui/search'/'sap.com'/'MAIN_APL70VAL_C'/'964624'/'20' updates currently deployed development component 'caf/eu/gp/ui/search'/'sap.com'/'MAIN_APL70VAL_C'/'964624'/'18'.
Mar 12, 2007 8:09:52 PM Info: SDA to be deployed: /usr/sap/EPS/JC00/SDM/root/origin/sap.com/caf/eu/gp/ui/search/MAIN_APL70VAL_C/20/964624/sap.com_cafeugpuisearch.sda
Mar 12, 2007 8:09:52 PM Info: Software type of SDA: J2EE
Mar 12, 2007 8:09:52 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Mar 12, 2007 8:09:57 PM Info: Begin of log messages of the target system:
07/03/12 20:09:52 - ***********************************************************
07/03/12 20:09:52 - Start updating EAR file...
07/03/12 20:09:52 - start-up mode is lazy
07/03/12 20:09:52 - EAR file updated successfully for 56ms.
07/03/12 20:09:52 - Start updating...
07/03/12 20:09:55 - EAR file uploaded to server for 1144ms.
07/03/12 20:09:56 - Successfully updated. Update took 569ms.
07/03/12 20:09:56 - Deploy Service status:
07/03/12 20:09:56 - Application : sapHi Stanley,
double-verify that all needed files are there, specially the SP11 files.
You can stop the j2ee and start it again, then resume from point of failure, but I doubt it will help.
I suggest to open an oss with sap.
I too had a contraint violate with my upgrade, and they helped me to solve the problem.
Brad
Maybe you are looking for
-
How to call a window dynamically from a view
Dear forum experts, I am developing an application where i have 4 view controllers and 2 window controllers under one component.Some times on click of a button i have to give a provision to switch to another view from one view, which i did by firing
-
I deleted Ipod app by mistake, I just got iPad and didn't know I needed iPod to play music, as I have a droid I didn't think I needed it! I could not find it in App store! What can I do?
-
I cant find my ipod and i dont have the app
plzz help
-
I have checked with weblogic Server 8.1, supposing exposing Java Components as web services. I have checked with the examples.It is quite easily achievable. But what i want to know as what mentioned in http://www.javaworld.com/javaworld/jw-08-2004/jw
-
I have a comboBox that is populated by an XML file. Is there a way to set the selectedIndex to a variable within the XML file? For example, my XML data looks like this: <villa name="Villa 2" URL=" http://www.URL2.com" default_index="1"/> When someone