Deployment failed in SDM ( SP8 to SP16)
hi
i am updating solman 4.0 SP8 to SP16, i have updated kernel and JSPM version to letest level.
i have copied all .SCA files and XML file to eps/in folder...i have started java update from JSPM..
java update failed in JSPM, so i have switched to safemode=NO and restarted java engine..
I tried this with SIDADM and Administrator also, but same error
after that from SDM i selected the all .SCA files...loading archives done with below error.
Summary:
========
There were 27 archives selected.
18 archives successfully loaded.
Loading of 9 archives failed.
Details:
========
1) Error loading archive
D:\usr\sap\trans\EPS\in\ADSSAP15_0-10003001.SCA
(server side name is: D:\usr\sap\trans\EPS\in\ADSSAP15_0-10003001.SCA)
There is already a component of the same type with identical name 'ADSSAP' and vendor 'sap.com' selected.
2) Error loading archive
D:\usr\sap\trans\EPS\in\CAF15_0-10003464.SCA
(server side name is: D:\usr\sap\trans\EPS\in\CAF15_0-10003464.SCA)
There is already a component of the same type with identical name 'CAF' and vendor 'sap.com' selected.
3) Error loading archive
D:\usr\sap\trans\EPS\in\CAFUM15_0-10003472.SCA
(server side name is: D:\usr\sap\trans\EPS\in\CAFUM15_0-10003472.SCA)
There is already a component of the same type with identical name 'CAF-UM' and vendor 'sap.com' selected.
4) Error loading archive
D:\usr\sap\trans\EPS\in\LMSERVICE15_0-20001429.SCA
(server side name is: D:\usr\sap\trans\EPS\in\LMSERVICE15_0-20001429.SCA)
There is already a component of the same type with identical name 'LM-SERVICE' and vendor 'sap.com' selected.
5) Error loading archive
D:\usr\sap\trans\EPS\in\SAPBUILDT15_0-10003479.SCA
(server side name is: D:\usr\sap\trans\EPS\in\SAPBUILDT15_0-10003479.SCA)
There is already a component of the same type with identical name 'SAP_BUILDT' and vendor 'sap.com' selected.
6) Error loading archive
D:\usr\sap\trans\EPS\in\SAPJEE15_0-10003469.SCA
(server side name is: D:\usr\sap\trans\EPS\in\SAPJEE15_0-10003469.SCA)
There is already a component of the same type with identical name 'SAP-JEE' and vendor 'sap.com' selected.
7) Error loading archive
D:\usr\sap\trans\EPS\in\SAPJEECOR15_0-10003466.SCA
(server side name is: D:\usr\sap\trans\EPS\in\SAPJEECOR15_0-10003466.SCA)
There is already a component of the same type with identical name 'SAP-JEECOR' and vendor 'sap.com' selected.
8) Error loading archive
D:\usr\sap\trans\EPS\in\SAPJTECHF15_0-10003468.SCA
(server side name is: D:\usr\sap\trans\EPS\in\SAPJTECHF15_0-10003468.SCA)
There is already a component of the same type with identical name 'SAP_JTECHF' and vendor 'sap.com' selected.
9) Error loading archive
D:\usr\sap\trans\EPS\in\SAPJTECHS15_0-10003467.SCA
(server side name is: D:\usr\sap\trans\EPS\in\SAPJTECHS15_0-10003467.SCA)
There is already a component of the same type with identical name 'SAP_JTECHS' and vendor 'sap.com' selected.
After that i have started deployment from SDM, but failed with below error.
=======================================================================
Log from SDM:
===========================================================================
Deployment started Tue Jan 08 15:29:23 GMT+05:30 2008
===========================================================================
Starting Deployment of tc/smd/cptdict
Finished successfully: development component 'tc/smd/cptdict'/'sap.com'/'SAP AG'/'7.0014.20080122064620.0000'/'0', grouped by
Deployment of tc/smd/cptdict finished successfully (Duration 8437 ms)
Starting Deployment of SAP_BUILDT
Finished successfully: software component 'SAP_BUILDT'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20071117141300''/'0'
Deployment of SAP_BUILDT finished successfully (Duration 5454 ms)
Starting Deployment of tc/smd/datamgmt/dict
Finished successfully: development component 'tc/smd/datamgmt/dict'/'sap.com'/'SAP AG'/'7.0014.20080122064620.0000'/'0', grouped by
Deployment of tc/smd/datamgmt/dict finished successfully (Duration 5891 ms)
Starting Deployment of tc/smd/server/service
The SDM will now stop SAP Web AS Java cluster instance(s) processes in order to perform offline deployment. After that the deployment will proceed.
It could take some time, so please be patient.
Finished successfully: development component 'tc/smd/server/service'/'sap.com'/'SAP AG'/'7.0014.20080122064620.0000'/'0', grouped by software component 'LM-SERVICE'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20080122073158''/'0'
Deployment of tc/smd/server/service finished successfully (Duration 20954 ms)
Starting Deployment of tc/webadministrator/ccrep/dict
Finished successfully: development component 'tc/webadministrator/ccrep/dict'/'sap.com'/'SAP AG'/'7.0014.20080122064620.0000'/'0', grouped by
Deployment of tc/webadministrator/ccrep/dict finished successfully (Duration 13625 ms)
Starting Deployment of tc/webadministrator/ewa/dict
Finished successfully: development component 'tc/webadministrator/ewa/dict'/'sap.com'/'SAP AG'/'7.0014.20080122064620.0000'/'0', grouped by
Deployment of tc/webadministrator/ewa/dict finished successfully (Duration 6703 ms)
Starting Deployment of tc/webadministrator/fvrep/dict
Finished successfully: development component 'tc/webadministrator/fvrep/dict'/'sap.com'/'SAP AG'/'7.0014.20080122064620.0000'/'0', grouped by software component 'LM-SERVICE'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20080122073158''/'0'
Deployment of tc/webadministrator/fvrep/dict finished successfully (Duration 6812 ms)
Starting Deployment of tc/webadministrator/httpanalysis/dict
Finished successfully: development component 'tc/webadministrator/httpanalysis/dict'/'sap.com'/'SAP AG'/'7.0014.20080122064620.0000'/'0', grouped by
Deployment of tc/webadministrator/httpanalysis/dict finished successfully (Duration 5734 ms)
Starting Deployment of tc/webadministrator/lib/dict
Finished successfully: development component 'tc/webadministrator/lib/dict'/'sap.com'/'SAP AG'/'7.0014.20080122064620.0000'/'0', grouped by
Deployment of tc/webadministrator/lib/dict finished successfully (Duration 5875 ms)
Starting Deployment of tc/webadministrator/lib/dbc
Finished successfully: development component 'tc/webadministrator/lib/dbc'/'sap.com'/'SAP AG'/'7.0014.20080122064620.0000'/'0', grouped by
Deployment of tc/webadministrator/lib/dbc finished successfully (Duration 5563 ms)
Starting Deployment of tc/webadministrator/logviewer/dict
Finished with warnings: development component 'tc/webadministrator/logviewer/dict'/'sap.com'/'SAP AG'/'7.0014.20080122064620.0000'/'0', grouped by :
No further description found.
Deployment of tc/webadministrator/logviewer/dict finished with Warning (Duration 6078 ms)
Starting Deployment of tc/webadministrator/navigation/dict
Finished successfully: development component 'tc/webadministrator/navigation/dict'/'sap.com'/'SAP AG'/'7.0014.20080122064620.0000'/'0', grouped by
Deployment of tc/webadministrator/navigation/dict finished successfully (Duration 7375 ms)
Starting Deployment of tc/webadministrator/navigation/dbc
Finished successfully: development component 'tc/webadministrator/navigation/dbc'/'sap.com'/'SAP AG'/'7.0014.20080122064620.0000'/'0', grouped by
Deployment of tc/webadministrator/navigation/dbc finished successfully (Duration 7671 ms)
Starting Deployment of tc/webadministrator/scheduler/dict
Finished successfully: development component 'tc/webadministrator/scheduler/dict'/'sap.com'/'SAP AG'/'7.0014.20080122064620.0000'/'0', grouped by software component 'LM-SERVICE'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20080122073158''/'0'
Deployment of tc/webadministrator/scheduler/dict finished successfully (Duration 6047 ms)
Starting Deployment of tc/webadministrator/screp/dict
Finished successfully: development component 'tc/webadministrator/screp/dict'/'sap.com'/'SAP AG'/'7.0014.20080122064620.0000'/'0', grouped by
Deployment of tc/webadministrator/screp/dict finished successfully (Duration 6485 ms)
Starting Deployment of tc/webadministrator/screp/dbc
Finished successfully: development component 'tc/webadministrator/screp/dbc'/'sap.com'/'SAP AG'/'7.0014.20080122064620.0000'/'0', grouped by software component 'LM-SERVICE'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20080122073158''/'0'
Deployment of tc/webadministrator/screp/dbc finished successfully (Duration 5562 ms)
Starting Deployment of tc/webadministrator/selfcheck/dict
Finished successfully: development component 'tc/webadministrator/selfcheck/dict'/'sap.com'/'SAP AG'/'7.0014.20080122064620.0000'/'0', grouped by
Deployment of tc/webadministrator/selfcheck/dict finished successfully (Duration 5968 ms)
Starting Deployment of tc/webadministrator/selfcheck/dbc
Finished successfully: development component 'tc/webadministrator/selfcheck/dbc'/'sap.com'/'SAP AG'/'7.0014.20080122064620.0000'/'0', grouped by software component 'LM-SERVICE'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20080122073158''/'0'
Deployment of tc/webadministrator/selfcheck/dbc finished successfully (Duration 5500 ms)
Starting Deployment of DocumentServicesLicenseManager
The SDM will now start SAP Web AS Java instance processes in order to perform online deployment. After that the deployment will proceed.
It could take some time, so please be patient.
Aborted: development component 'DocumentServicesLicenseManager'/'com.adobe'/'Adobe Systems'/'800.20070306123954.374077'/'2', grouped by software component 'ADSSAP'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20071118055147''/'0':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Only Administrators have the right to perform this operation.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of DocumentServicesLicenseManager finished with Error (Duration 323422 ms)
Starting Deployment of AdobeDocumentServices
Deployment of AdobeDocumentServices was skipped (Duration 5329 ms)
Starting Deployment of tc/ads/grmg
Aborted: development component 'tc/ads/grmg'/'sap.com'/'SAP AG'/'7.0010.20061002104728.0000'/'2', grouped by software component 'ADSSAP'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20071118055147''/'0':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Only Administrators have the right to perform this operation.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of tc/ads/grmg finished with Error (Duration 6047 ms)
Starting Deployment of ADSSAP
Aborted: software component 'ADSSAP'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20071118055147''/'0':
Failed deployment of SDAs:
development component 'AdobeDocumentServices'/'com.adobe'/'Adobe Systems'/'800.20070708051308.406522'/'2' : skipped
development component 'tc/ads/grmg'/'sap.com'/'SAP AG'/'7.0010.20061002104728.0000'/'2' : aborted
development component 'DocumentServicesLicenseManager'/'com.adobe'/'Adobe Systems'/'800.20070306123954.374077'/'2' : aborted
Please, look at error logs above for more information!
Deployment of ADSSAP finished with Error (Duration 5782 ms)
Starting Deployment of bi/mmr/browser_ea
Aborted: development component 'bi/mmr/browser_ea'/'sap.com'/'SAP AG'/'7.0011.20070124085018.0000'/'1', grouped by :
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Only Administrators have the right to perform this operation.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of bi/mmr/browser_ea finished with Error (Duration 6266 ms)
Starting Deployment of bi/mmr/cwm_1.0_source
Aborted: development component 'bi/mmr/cwm_1.0_source'/'sap.com'/'SAP AG'/'7.0015.20080131095802.0000'/'1', grouped by :
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Only Administrators have the right to perform this operation.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of bi/mmr/cwm_1.0_source finished with Error (Duration 7750 ms)
Starting Deployment of bi/mmr/miniMetaModel
Aborted: development component 'bi/mmr/miniMetaModel'/'sap.com'/'SAP AG'/'7.0015.20080131095802.0000'/'1', grouped by software component 'BI_MMR'/'sap.com'/'SAP AG'/'1000.7.00.15.0.20080216072334''/'1':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Only Administrators have the right to perform this operation.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of bi/mmr/miniMetaModel finished with Error (Duration 5860 ms)
Starting Deployment of bi/mmr/mini_md350
Aborted: development component 'bi/mmr/mini_md350'/'sap.com'/'SAP AG'/'7.0015.20080131095802.0000'/'1', grouped by software component 'BI_MMR'/'sap.com'/'SAP AG'/'1000.7.00.15.0.20080216072334''/'1':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Only Administrators have the right to perform this operation.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of bi/mmr/mini_md350 finished with Error (Duration 5750 ms)
Starting Deployment of BI_MMR
Aborted: software component 'BI_MMR'/'sap.com'/'SAP AG'/'1000.7.00.15.0.20080216072334''/'1':
Failed deployment of SDAs:
development component 'bi/mmr/mini_md350'/'sap.com'/'SAP AG'/'7.0015.20080131095802.0000'/'1' : aborted
development component 'bi/mmr/miniMetaModel'/'sap.com'/'SAP AG'/'7.0015.20080131095802.0000'/'1' : aborted
development component 'bi/mmr/browser_ea'/'sap.com'/'SAP AG'/'7.0011.20070124085018.0000'/'1' : aborted
development component 'bi/mmr/cwm_1.0_source'/'sap.com'/'SAP AG'/'7.0015.20080131095802.0000'/'1' : aborted
Please, look at error logs above for more information!
Deployment of BI_MMR finished with Error (Duration 5672 ms)
Starting Deployment of caf/um/metadata/actions
Aborted: development component 'caf/um/metadata/actions'/'sap.com'/'MAIN_APL70VAL_C'/'1077265'/'1', grouped by software component 'CAF-UM'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.14.0.20071117062847''/'0':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Only Administrators have the right to perform this operation.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of caf/um/metadata/actions finished with Error (Duration 6172 ms)
Starting Deployment of caf/um/metadata/content
Aborted: development component 'caf/um/metadata/content'/'sap.com'/'MAIN_APL70VAL_C'/'1497172'/'1', grouped by :
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Only Administrators have the right to perform this operation.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of caf/um/metadata/content finished with Error (Duration 5828 ms)
Starting Deployment of caf/um/metadata/example
Aborted: development component 'caf/um/metadata/example'/'sap.com'/'MAIN_APL70VAL_C'/'963657'/'1', grouped by software component 'CAF-UM'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.14.0.20071117062847''/'0':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Only Administrators have the right to perform this operation.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of caf/um/metadata/example finished with Error (Duration 5844 ms)
Starting Deployment of caf/um/metadata/testwd
Aborted: development component 'caf/um/metadata/testwd'/'sap.com'/'MAIN_APL70VAL_C'/'963659'/'1', grouped by :
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Only Administrators have the right to perform this operation.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of caf/um/metadata/testwd finished with Error (Duration 6078 ms)
Starting Deployment of caf/um/relgroups/admin
Aborted: development component 'caf/um/relgroups/admin'/'sap.com'/'MAIN_APL70VAL_C'/'963666'/'1', grouped by :
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Only Administrators have the right to perform this operation.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of caf/um/relgroups/admin finished with Error (Duration 5797 ms)
Starting Deployment of caf/um/relgroups/test
Aborted: development component 'caf/um/relgroups/test'/'sap.com'/'MAIN_APL70VAL_C'/'963945'/'1', grouped by :
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Only Administrators have the right to perform this operation.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of caf/um/relgroups/test finished with Error (Duration 5891 ms)
Starting Deployment of CAF-UM
Aborted: software component 'CAF-UM'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.14.0.20071117062847''/'0':
Failed deployment of SDAs:
development component 'caf/um/metadata/example'/'sap.com'/'MAIN_APL70VAL_C'/'963657'/'1' : aborted
development component 'caf/um/metadata/content'/'sap.com'/'MAIN_APL70VAL_C'/'1497172'/'1' : aborted
development component 'caf/um/metadata/testwd'/'sap.com'/'MAIN_APL70VAL_C'/'963659'/'1' : aborted
development component 'caf/um/metadata/actions'/'sap.com'/'MAIN_APL70VAL_C'/'1077265'/'1' : aborted
development component 'caf/um/relgroups/test'/'sap.com'/'MAIN_APL70VAL_C'/'963945'/'1' : aborted
development component 'caf/um/relgroups/admin'/'sap.com'/'MAIN_APL70VAL_C'/'963666'/'1' : aborted
Please, look at error logs above for more information!
Deployment of CAF-UM finished with Error (Duration 5718 ms)
Starting Deployment of tc/km_tc/kw
Aborted: development component 'tc/km_tc/kw'/'sap.com'/'SAP AG'/'7.0012.20070328121935.0000'/'0', grouped by software component 'KM-KW_JIKS'/'sap.com'/'SAP AG'/'1000.7.00.15.0.20080216072941''/'0':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Only Administrators have the right to perform this operation.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of tc/km_tc/kw finished with Error (Duration 6172 ms)
Starting Deployment of tc/km_tc/sapiks
Aborted: development component 'tc/km_tc/sapiks'/'sap.com'/'SAP AG'/'7.0012.20070328121935.0000'/'0', grouped by software component 'KM-KW_JIKS'/'sap.com'/'SAP AG'/'1000.7.00.15.0.20080216072941''/'0':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Only Administrators have the right to perform this operation.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of tc/km_tc/sapiks finished with Error (Duration 5859 ms)
Starting Deployment of tc/km_tc/sapirexthelp
Aborted: development component 'tc/km_tc/sapirexthelp'/'sap.com'/'SAP AG'/'7.0012.20070328121935.0000'/'0', grouped by software component 'KM-KW_JIKS'/'sap.com'/'SAP AG'/'1000.7.00.15.0.20080216072941''/'0':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Only Administrators have the right to perform this operation.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of tc/km_tc/sapirexthelp finished with Error (Duration 6110 ms)
Starting Deployment of tc/kw_tc
Aborted: development component 'tc/kw_tc'/'sap.com'/'SAP AG'/'7.0015.20080123135455.0000'/'0', grouped by software component 'KM-KW_JIKS'/'sap.com'/'SAP AG'/'1000.7.00.15.0.20080216072941''/'0':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Only Administrators have the right to perform this operation.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of tc/kw_tc finished with Error (Duration 6766 ms)
Starting Deployment of KM-KW_JIKS
Aborted: software component 'KM-KW_JIKS'/'sap.com'/'SAP AG'/'1000.7.00.15.0.20080216072941''/'0':
Failed deployment of SDAs:
development component 'tc/km_tc/kw'/'sap.com'/'SAP AG'/'7.0012.20070328121935.0000'/'0' : aborted
development component 'tc/km_tc/sapiks'/'sap.com'/'SAP AG'/'7.0012.20070328121935.0000'/'0' : aborted
development component 'tc/km_tc/sapirexthelp'/'sap.com'/'SAP AG'/'7.0012.20070328121935.0000'/'0' : aborted
development component 'tc/kw_tc'/'sap.com'/'SAP AG'/'7.0015.20080123135455.0000'/'0' : aborted
Please, look at error logs above for more information!
Deployment of KM-KW_JIKS finished with Error (Duration 5719 ms)
Starting Deployment of SQLTrace
Aborted: development component 'SQLTrace'/'sap.com'/'SAP AG'/'7.0013.20070703111935.0000'/'1', grouped by software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20071123073950''/'0':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Only Administrators have the right to perform this operation.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of SQLTrace finished with Error (Duration 6141 ms)
Starting Deployment of com.sap.aii.util.rb
Aborted: development component 'com.sap.aii.util.rb'/'sap.com'/'SAP AG'/'7.0012.20070328121059.0000'/'1', grouped by software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20071123073950''/'0':
Caught exception during library deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot perform action deploy on component library D:\usr\sap\ABA\DVEBMGS01\SDM\root\origin\sap.com\com.sap.aii.util.rb\SAP AG\1\7.0012.20070328121059.0000\aii_util_rb.sda. Reason: java.rmi.RemoteException: Only Administrators have the right to perform this operation.
at com.sap.engine.services.deploy.server.DeployServiceImpl.deployLibrary(DeployServiceImpl.java:1463)
at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:336)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Exception is: ; nested exception is: com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot perform action deploy on component library D:\usr\sap\ABA\DVEBMGS01\SDM\root\origin\sap.com\com.sap.aii.util.rb\SAP AG\1\7.0012.20070328121059.0000\aii_util_rb.sda. Reason: java.rmi.RemoteException: Only Administrators have the right to perform this operation.
at com.sap.engine.services.deploy.server.DeployServiceImpl.deployLibrary(DeployServiceImpl.java:1463)
at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:336)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Exception is:
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineCompOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of com.sap.aii.util.rb finished with Error (Duration 5922 ms)
Starting Deployment of com.sap.aii.util.misc
Deployment of com.sap.aii.util.misc was skipped (Duration 5359 ms)
Starting Deployment of com.sap.aii.util.xml
Deployment of com.sap.aii.util.xml was skipped (Duration 5547 ms)
Starting Deployment of com.sap.aii.ibtranslationclient
Deployment of com.sap.aii.ibtranslationclient was skipped (Duration 5218 ms)
Starting Deployment of com.sap.aii.ibtransportclient
Deployment of com.sap.aii.ibtransportclient was skipped (Duration 5266 ms)
Starting Deployment of com.sap.aii.proxy.framework
Deployment of com.sap.aii.proxy.framework was skipped (Duration 5266 ms)
Starting Deployment of com.sap.engine.class.download
Aborted: development component 'com.sap.engine.class.download'/'sap.com'/'SAP AG'/'7.0012.20070328121153.0000'/'1', grouped by :
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Only Administrators have the right to perform this operation.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of com.sap.engine.class.download finished with Error (Duration 6078 ms)
Starting Deployment of com.sap.engine.customizing.ccms
Aborted: development component 'com.sap.engine.customizing.ccms'/'sap.com'/'SAP AG'/'7.0014.20071029094615.0000'/'1', grouped by software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20071123073950''/'0':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Only Administrators have the right to perform this operation.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of com.sap.engine.customizing.ccms finished with Error (Duration 6016 ms)
Starting Deployment of com.sap.engine.docs.examples
Aborted: development component 'com.sap.engine.docs.examples'/'sap.com'/'SAP AG'/'7.0014.20071029094615.0000'/'0', grouped by :
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Only Administrators have the right to perform this operation.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of com.sap.engine.docs.examples finished with Error (Duration 9703 ms)
Starting Deployment of com.sap.engine.heartbeat
Aborted: development component 'com.sap.engine.heartbeat'/'sap.com'/'SAP AG'/'7.0012.20070328121153.0000'/'0', grouped by :
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot remove references from sap.com/com.sap.engine.heartbeat to library:sap.com/com.sap.mw.jco, library:sap.com/com.sap.util.monitor.grmg; java.rmi.RemoteException: Only Administrators have the right to perform this operation.; nested exception is: com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot remove references from sap.com/com.sap.engine.heartbeat to library:sap.com/com.sap.mw.jco, library:sap.com/com.sap.util.monitor.grmg; java.rmi.RemoteException: Only Administrators have the right to perform this operation.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of com.sap.engine.heartbeat finished with Error (Duration 6250 ms)
Starting Deployment of com.sap.jdo
Aborted: development component 'com.sap.jdo'/'sap.com'/'SAP AG'/'7.0013.20070703111940.0000'/'0', grouped by :
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Only Administrators have the right to perform this operation.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of com.sap.jdo finished with Error (Duration 6219 ms)
Starting Deployment of com.sap.lcr.namealloc
Aborted: development component 'com.sap.lcr.namealloc'/'sap.com'/'SAP AG'/'7.0013.20070703113613.0000'/'1', grouped by :
Caught exception during library deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot perform action deploy on component library D:\usr\sap\ABA\DVEBMGS01\SDM\root\origin\sap.com\com.sap.lcr.namealloc\SAP AG\1\7.0013.20070703113613.0000\namealloc.sda. Reason: java.rmi.RemoteException: Only Administrators have the right to perform this operation.
at com.sap.engine.services.deploy.server.DeployServiceImpl.deployLibrary(DeployServiceImpl.java:1463)
at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:336)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Exception is: ; nested exception is: com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot perform action deploy on component library D:\usr\sap\ABA\DVEBMGS01\SDM\root\origin\sap.com\com.sap.lcr.namealloc\SAP AG\1\7.0013.20070703113613.0000\namealloc.sda. Reason: java.rmi.RemoteException: Only Administrators have the right to perform this operation.
at com.sap.engine.services.deploy.server.DeployServiceImpl.deployLibrary(DeployServiceImpl.java:1463)
at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:336)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Exception is:
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineCompOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of com.sap.lcr.namealloc finished with Error (Duration 5703 ms)
Starting Deployment of com.sap.lcr.saprfc
Aborted: development component 'com.sap.lcr.saprfc'/'sap.com'/'SAP AG'/'7.0013.20070703113613.0000'/'1', grouped by :
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot remove references from sap.com/com.sap.lcr.saprfc to library:sap.com/com.sap.mw.jco, library:sap.com/com.sap.lcr.api.cimclient; java.rmi.RemoteException: Only Administrators have the right to perform this operation.; nested exception is: com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot remove references from sap.com/com.sap.lcr.saprfc to library:sap.com/com.sap.mw.jco, library:sap.com/com.sap.lcr.api.cimclient; java.rmi.RemoteException: Only Administrators have the right to perform this operation.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of com.sap.lcr.saprfc finished with Error (Duration 6187 ms)
Starting Deployment of com.sap.lcrabapapi
Aborted: development component 'com.sap.lcrabapapi'/'sap.com'/'SAP AG'/'7.0013.20070328121631.0000'/'1', grouped by :
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot remove references from sap.com/com.sap.lcrabapapi to library:sap.com/com.sap.mw.jco, library:sap.com/com.sap.lcr.api.cimclient; java.rmi.RemoteException: Only Administrators have the right to perform this operation.; nested exception is: com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot remove references from sap.com/com.sap.lcrabapapi to library:sap.com/com.sap.mw.jco, library:sap.com/com.sap.lcr.api.cimclient; java.rmi.RemoteException: Only Administrators have the right to perform this operation.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of com.sap.lcrabapapi finished with Error (Duration 5906 ms)
Starting Deployment of com.sap.mobile.clientinfo
Aborted: development component 'com.sap.mobile.clientinfo'/'sap.com'/'SAP AG'/'7.0013.20060719095239.0000'/'1', grouped by :
Caught exception during library deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot perform action deploy on component library D:\usr\sap\ABA\DVEBMGS01\SDM\program\.\temp\temp_dm\com.sap.mobile.clientinfo.jar. Reason: java.rmi.RemoteException: Only Administrators have the right to perform this operation.
at com.sap.engine.services.deploy.server.DeployServiceImpl.deployLibrary(DeployServiceImpl.java:1463)
at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:336)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Exception is: ; nested exception is: com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot perform action deploy on component library D:\usr\sap\ABA\DVEBMGS01\SDM\program\.\temp\temp_dm\com.sap.mobile.clientinfo.jar. Reason: java.rmi.RemoteException: Only Administrators have the right to perform this operation.
at com.sap.engine.services.deploy.server.DeployServiceImpl.deployLibrary(DeployServiceImpl.java:1463)
at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:336)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Exception is:
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineLib620OnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of com.sap.mobile.clientinfo finished with Error (Duration 5860 ms)
Starting Deployment of com.sap.pmi.adm
Aborted: development component 'com.sap.pmi.adm'/'sap.com'/'SAP AG'/'7.0014.20071029095144.0000'/'0', grouped by :
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Only Administrators have the right to perform this operation.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of com.sap.pmi.adm finished with Error (Duration 5765 ms)
Starting Deployment of com.sap.rprof.dbprofiles
Aborted: development component 'com.sap.rprof.dbprofiles'/'sap.com'/'SAP AG'/'7.0014.20070328121706.0000'/'0', grouped by software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20071123073950''/'0':
Caught exception during library deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot perform action deploy on component library D:\usr\sap\ABA\DVEBMGS01\SDM\root\origin\sap.com\com.sap.rprof.dbprofiles\SAP AG\0\7.0014.20070328121706.0000\dbprofiles.sda. Reason: java.rmi.RemoteException: Only Administrators have the right to perform this operation.
at com.sap.engine.services.deploy.server.DeployServiceImpl.deployLibrary(DeployServiceImpl.java:1463)
at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:336)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Exception is: ; nested exception is: com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot perform action deploy on component library D:\usr\sap\ABA\DVEBMGS01\SDM\root\origin\sap.com\com.sap.rprof.dbprofiles\SAP AG\0\7.0014.20070328121706.0000\dbprofiles.sda. Reason: java.rmi.RemoteException: Only Administrators have the right to perform this operation.
at com.sap.engine.services.deploy.server.DeployServiceImpl.deployLibrary(DeployServiceImpl.java:1463)
at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:336)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Exception is:
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineCompOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of com.sap.rprof.dbprofiles finished with Error (Duration 5734 ms)
Starting Deployment of com.sap.lcr
Deployment of com.sap.lcr was skipped (Duration 5297 ms)
Starting Deployment of com.sap.rprof.remoteProfile
Deployment of com.sap.rprof.remoteProfile was skipped (Duration 5266 ms)
Starting Deployment of com.sap.security.core.admin
Aborted: development component 'com.sap.security.core.admin'/'sap.com'/'SAP AG'/'7.0014.20071029094847.0000'/'0', grouped by :
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Only Administrators have the right to perform this operation.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of com.sap.security.core.admin finished with Error (Duration 7688 ms)
Starting Deployment of com.sap.util.monitor.jarm.ccms
Aborted: development component 'com.sap.util.monitor.jarm.ccms'/'sap.com'/'SAP AG'/'7.0013.20051128142456.0000'/'1', grouped by :
Caught exception during library deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot perform action deploy on component library D:\usr\sap\ABA\DVEBMGS01\SDM\program\.\temp\temp_dm\com.sap.util.monitor.jarm.ccms.jar. Reason: java.rmi.RemoteException: Only Administrators have the right to perform this operation.
at com.sap.engine.services.deploy.server.DeployServiceImpl.deployLibrary(DeployServiceImpl.java:1463)
at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:336)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Exception is: ; nested exception is: com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot perform action deploy on component library D:\usr\sap\ABA\DVEBMGS01\SDM\program\.\temp\temp_dm\com.sap.util.monitor.jarm.ccms.jar. Reason: java.rmi.RemoteException: Only Administrators have the right to perform this operation.
at com.sap.engine.services.deploy.server.DeployServiceImpl.deployLibrary(DeployServiceImpl.java:1463)
at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:336)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Exception is:
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineLib620OnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of com.sap.util.monitor.jarm.ccms finished with Error (Duration 5719 ms)
Starting Deployment of com.sap.util.monitor.jarm.j2ee
Aborted: development component 'com.sap.util.monitor.jarm.j2ee'/'sap.com'/'SAP AG'/'7.0013.20051128142456.0000'/'1', grouped by :
Caught exception during library deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot perform action deploy on component library D:\usr\sap\ABA\DVEBMGS01\SDM\program\.\temp\temp_dm\com.sap.util.monitor.jarm.j2ee.jar. Reason: java.rmi.RemoteException: Only Administrators have the right to perform this operation.
at com.sap.engine.services.deploy.server.DeployServiceImpl.deployLibrary(DeployServiceImpl.java:1463)
at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:336)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Exception is: ; nested exception is: com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot perform action deploy on component library D:\usr\sap\ABA\DVEBMGS01\SDM\program\.\temp\temp_dm\com.sap.util.monitor.jarm.j2ee.jar. Reason: java.rmi.RemoteException: Only Administrators have the right to perform this operation.
at com.sap.engine.services.deploy.server.DeployServiceImpl.deployLibrary(DeployServiceImpl.java:1463)
at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:336)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Exception is:
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineLib620OnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of com.sap.util.monitor.jarm.j2ee finished with Error (Duration 5953 ms)
Starting Deployment of com.sapmarkets.mesyncjco
Deployment of com.sapmarkets.mesyncjco was skipped (Duration 5547 ms)
Starting Deployment of com.sapportals.htmlb
Deployment of com.sapportals.htmlb was skipped (Duration 5281 ms)
Starting Deployment of com.sap.engine.services.webservices.tool
Deployment of com.sap.engine.services.webservices.tool was skipped (Duration 5469 ms)
Starting Deployment of com.sapportals.htmlb.ear
Deployment of com.sapportals.htmlb.ear was skipped (Duration 5234 ms)
Starting Deployment of sl.ut.content.nw
Aborted: development component 'sl.ut.content.nw'/'sap.com'/'SAP AG'/'7.0014.20071123054250.0000'/'1', grouped by software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20071123073950''/'0':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Only Administrators have the right to perform this operation.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of sl.ut.content.nw finished with Error (Duration 5704 ms)
Starting Deployment of sl.ut.infoprovider
Aborted: development component 'sl.ut.infoprovider'/'sap.com'/'SAP AG'/'7.0014.20071123054250.0000'/'1', grouped by software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20071123073950''/'0':
Caught exception during library deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot perform action deploy on component library D:\usr\sap\ABA\DVEBMGS01\SDM\root\origin\sap.com\sl.ut.infoprovider\SAP AG\1\7.0014.20071123054250.0000\sap.com~sl.ut.infoprovider.sda. Reason: java.rmi.RemoteException: Only Administrators have the right to perform this operation.
at com.sap.engine.services.deploy.server.DeployServiceImpl.deployLibrary(DeployServiceImpl.java:1463)
at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:336)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Exception is: ; nested exception is: com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot perform action deploy on component library D:\usr\sap\ABA\DVEBMGS01\SDM\root\origin\sap.com\sl.ut.infoprovider\SAP AG\1\7.0014.20071123054250.0000\sap.com~sl.ut.infoprovider.sda. Reason: java.rmi.RemoteException: Only Administrators have the right to perform this operation.
at com.sap.engine.services.deploy.server.DeployServiceImpl.deployLibrary(DeployServiceImpl.java:1463)
at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:336)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Exception is:
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineCompOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of sl.ut.infoprovider finished with Error (Duration 5828 ms)
Starting Deployment of sl/ut/info
Deployment of sl/ut/info was skipped (Duration 5297 ms)
Starting Deployment of tc/SL/CMS/Util
Aborted: development component 'tc/SL/CMS/Util'/'sap.com'/'SAP AG'/'7.0014.20071002095021.0000'/'0', grouped by software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20071123073950''/'0':
Caught exception during library deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot perform action deploy on component library D:\usr\sap\ABA\DVEBMGS01\SDM\root\origin\sap.com\tc\SL\CMS\Util\SAP AG\0\7.0014.20071002095021.0000\CMSutil.sda. Reason: java.rmi.RemoteException: Only Administrators have the right to perform this operation.
at com.sap.engine.services.deploy.server.DeployServiceImpl.deployLibrary(DeployServiceImpl.java:1463)
at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:336)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
Hi,
I think there are two sda files with adsap so just check in the eps/in directory.
Also just try to deploy the BI component individually using SDM.
Regards,
Vamshi.
Similar Messages
-
SDM Deployment fails - Dependency caf/core/ear missing
crosspost from: SDM Deployment fails - Dependency caf/core/ear missing
deploying a DC from NWDS into SDM the following Exception is thrown:
07.01.2008 16:20:38 /userOut/daView_category (eclipse.UserOutLocation) [ThreadDeploy Thread,5,main] INFO:
002Additional log information about the deployment
<!LOGHEADERSTART/>
<!HELPManual modification of the header may cause parsing problem!/>
<!LOGGINGVERSIONhttp://1.5.3.7185 - 630/>
<!NAME[/usr/sap/IT1/DVEBMGS00/SDM/program/log/sdmcl20080107151422.log]/>
<!PATTERNhttp://sdmcl20080107151422.log/>
<!FORMATTERcom.sap.tc.logging.TraceFormatter(%24d %s: %m)/>
<!ENCODINGUTF8/>
<!LOGHEADEREND/>
Jan 7, 2008 4:14:22 PM Info:
Starting deployment
Jan 7, 2008 4:14:22 PM Info: Error handling strategy: OnErrorStop
Jan 7, 2008 4:14:22 PM Info: Prerequisite error handling strategy: OnPrerequisiteErrorStop
Jan 7, 2008 4:14:22 PM Info: Update strategy: UpdateAllVersions
Jan 7, 2008 4:14:22 PM Info: Starting deployment prerequisites:
Jan 7, 2008 4:14:23 PM Info: Loading selected archives...
Jan 7, 2008 4:14:23 PM Info: Loading archive '/usr/sap/IT1/DVEBMGS00/SDM/program/temp/temp23425innobis.dewkbtmetadata.ear'
Jan 7, 2008 4:14:24 PM Info: Loading archive '/usr/sap/IT1/DVEBMGS00/SDM/program/temp/temp23426innobis.dewkbtear.ear'
Jan 7, 2008 4:14:24 PM Info: Loading archive '/usr/sap/IT1/DVEBMGS00/SDM/program/temp/temp23427innobis.dewkbtdictionary.sda'
Jan 7, 2008 4:14:25 PM Info: Loading archive '/usr/sap/IT1/DVEBMGS00/SDM/program/temp/temp23428innobis.dewkbtpermissions.ear'
Jan 7, 2008 4:14:26 PM Info: Selected archives successfully loaded.
Jan 7, 2008 4:14:26 PM Error: Unresolved dependencies found for the following SDAs:
1.: development component 'wkbt/ear'/'innobis.de'/'NetWeaver Developer Studio'/'20080107144202'/'0'
dependency:
name: 'caf/core/ear'
vendor: 'sap.com'
There is no component either in SDM repository or in Deployment batch that resolves the dependency.
Deployment will be aborted.
Jan 7, 2008 4:14:26 PM Error: Prerequisites were aborted.
Jan 7, 2008 4:14:27 PM Error: Error while creating deployment actions.
system:
sap.com/SAP-JEECOR 7.00 SP10 (1000.7.00.10.0.20061026144500)
sap.com/SAP-JEE 7.00 SP10 (1000.7.00.10.0.20061026144500)
I checked http://<srv>/sap/monitoring/ComponentInfo
the missing 'caf/core/ear' is not listed, however several other CAFs are:
sap.com caf/core null (964250) SAP AG MAIN_APL70VAL_C 20061212133926 sap.com/CAF
sap.com caf/core/dict null (964586) SAP AG MAIN_APL70VAL_C 20061212131613 sap.com/CAF
sap.com caf/core/gp/facade/backgroundco/ear null (964227) SAP AG MAIN_APL70VAL_C 20061212134201 sap.com/CAF
sap.com caf/core/metadata null (963689) SAP AG MAIN_APL70VAL_C 20061212133653 sap.com/CAF
etc....
Is it possible to deploy this missing caf-ear component supplementary?
I have the strange feelings caf/core/ear is something 7.1 CE only related....
thanks for any hint!
kaiKai, I didn't mean to offend you. But good forum practice is to avoid duplicate posts.
Regards,
\-- Vladimir -
Hello everybody i have a problem with my SAP ERP Installation the Error is :
An error occurred while processing service SAP ERP 6.0 Support Release 3 > SAP Systems > Oracle > Central System > Central System( Last error reported by the step :uncaught exception: nw.sdm.deploymentErrorWithLog: SDM deployment failed for at least one of the components to be deployed. SOLUTION: Check C:\Program Files/sapinst_instdir/ERP/SYSTEM/ORA/CENTRAL/AS/callSdmViaSapinst.log for more information. (in script unknown, line 0:
And here are my logfile , i hope you can help me for a solution. I have restart the SAP System and start it again and click retry but nothing happen, the same error comes again.
Jan 19, 2010 7:34:14 AM Info: Initial deployment: Selected development component 'tc/kmc/bc.uwl.ui/wd_pp'/'sap.com'/'SAP AG'/'7.0010.20061109164817.0000'/'1' will be deployed.
Jan 19, 2010 7:34:14 AM Info: No action: Selected development component 'com.sap.portal.nav.ws.NavigationWSEar'/'sap.com'/'SAP AG'/'7.0014.20071210113331.0000'/'2' will not be deployed because containing software component 'EP-PSERV'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20071210193159''/'2' will not be deployed.
Jan 19, 2010 7:34:14 AM Info: No action: Selected development component 'caf/eu/gp/ui/gpconf'/'sap.com'/'MAIN_APL70VAL_C'/'1534144'/'3' will not update currently deployed development component 'caf/eu/gp/ui/gpconf'/'sap.com'/'MAIN_APL70VAL_C'/'1534144'/'2'.
Jan 19, 2010 7:34:14 AM Info: No action: Selected development component 'caf/eu/gp/croom/content'/'sap.com'/'MAIN_APL70VAL_C'/'1498043'/'3' will not update currently deployed development component 'caf/eu/gp/croom/content'/'sap.com'/'MAIN_APL70VAL_C'/'1498043'/'1'.
Jan 19, 2010 7:34:14 AM Info: No action: Selected development component 'com.sap.prt.ws.container'/'sap.com'/'SAP AG'/'7.0010.20061109164817.0000'/'2' will not be deployed because containing software component 'EPBC2'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20071210152356''/'2' will not be deployed.
Jan 19, 2010 7:34:14 AM Info: Ending deployment prerequisites. All items are correct.
Jan 19, 2010 7:35:49 AM Info: Saved current Engine state.
Jan 19, 2010 7:35:49 AM Info: Starting: Initial deployment: Selected development component 'caf/eu/gp/ws/msosrv'/'sap.com'/'MAIN_APL70VAL_C'/'963790'/'3' will be deployed.
Jan 19, 2010 7:35:49 AM Info: SDA to be deployed: C:\usr\sap\DRC\DVEBMGS00\SDM\root\origin\sap.com\caf\eu\gp\ws\msosrv\MAIN_APL70VAL_C\3\963790\sap.com_cafeugpwsmsosrv.sda
Jan 19, 2010 7:35:49 AM Info: Software type of SDA: J2EE
Jan 19, 2010 7:35:49 AM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Jan 19, 2010 7:35:56 AM Info: Begin of log messages of the target system:
10/01/19 07:35:50 - ***********************************************************
10/01/19 07:35:51 - Start updating EAR file...
10/01/19 07:35:51 - start-up mode is lazy
10/01/19 07:35:51 - EAR file updated successfully for 47ms.
10/01/19 07:35:51 - Start deploying ...
10/01/19 07:35:51 - EAR file uploaded to server for 32ms.
10/01/19 07:35:56 - ERROR: NOT deployed. The Deploy Service returned the following error:
For detailed information see the log file of the Deploy Service.
Exception is:
com.sap.engine.services.rmi_p4.P4ConnectionException: Possible problem: no available running server node. Check your running servers.
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:700)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:688)
at com.sap.engine.services.rmi_p4.Parser.newRequest(Parser.java:180)
at com.sap.engine.services.rmi_p4.Connection.run(Connection.java:427)
at java.lang.Thread.run(Thread.java:534)
10/01/19 07:35:56 - ***********************************************************
Jan 19, 2010 7:35:56 AM Info: End of log messages of the target system.
Jan 19, 2010 7:35:56 AM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Jan 19, 2010 7:35:56 AM Error: Aborted: development component 'caf/eu/gp/ws/msosrv'/'sap.com'/'MAIN_APL70VAL_C'/'963790'/'3', grouped by software component 'SAP-EU'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.14.0.20071210153525''/'3':
Caught exception during application deployment from SAP J2EE Engine's deploy API:
com.sap.engine.deploy.manager.DeployManagerException: ERROR: NOT deployed. The Deploy Service returned the following error: com.sap.engine.services.rmi_p4.P4ConnectionException: Possible problem: no available running server node. Check your running servers.
Exception is:
com.sap.engine.services.rmi_p4.P4ConnectionException: Possible problem: no available running server node. Check your running servers.
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:700)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:688)
at com.sap.engine.services.rmi_p4.Parser.newRequest(Parser.java:180)
at com.sap.engine.services.rmi_p4.Connection.run(Connection.java:427)
at java.lang.Thread.run(Thread.java:534)
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).DMEXC)
Jan 19, 2010 7:35:56 AM Info: Starting to save the repository
Jan 19, 2010 7:35:57 AM Info: Finished saving the repositoryHi,
Check below thread:
/message/441671#441671 [original link is broken]
Thanks
Sunny -
Hi,
I started with WAS 6.40 and Eclipse. I made the tutorial with the calculator. I finished without errors, the only I had to make is to deploy. But then I got a lot of errors
30.11.2005 09:42:19 /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
[020]Deployment aborted
Settings
SDM host : sbrc30222
SDM port : 50018
URL to deploy : file:/c:/temp/temp31802CalculatorEar.ear
Result
=> deployment aborted : file:/c:/temp/temp31802CalculatorEar.ear
Aborted: development component 'CalculatorEar'/'sap.com'/'localhost'/'2005.11.30.09.31.44':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot deploy application sap.com/CalculatorEar.. Reason: Incorrect application sap.com/CalculatorEar:Error in the remote interface com.sap.examples.calculator.Calculator of bean CalculatorBean: No corresponding business method in the bean class com.sap.examples.calculator.CalculatorBean was found for method substract.Error in the local interface com.sap.examples.calculator.CalculatorLocal of bean CalculatorBean: No corresponding business method in the bean class was found for method substract.; nested exception is: com.sap.engine.services.deploy.container.DeploymentException: <--Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='com.sap.engine.services.ejb.exceptions.deployment.EJBDeploymentException: Incorrect application sap.com/CalculatorEar:Error in the remote interface com.sap.examples.calculator.Calculator of bean CalculatorBean: No corresponding business method in the bean class com.sap.examples.calculator.CalculatorBean was found for method substract.Error in the local interface com.sap.examples.calculator.CalculatorLocal of bean CalculatorBean: No corresponding business method in the bean class was found for method substract.
at com.sap.engine.services.ejb.deploy.verifier.Verifier.check(Verifier.java:66)
at com.sap.engine.services.ejb.deploy.DeployAdmin.generate(DeployAdmin.java:252)
at com.sap.engine.services.ejb.EJBAdmin.deploy(EJBAdmin.java:2118)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:594)
at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:379)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:296)
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.deploy(DeployServiceImpl.java:463)
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: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:37)
at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
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:94)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key com.sap.engine.services.ejb.exceptions.deployment.EJBDeploymentException: Incorrect application sap.com/CalculatorEar:Error in the remote interface com.sap.examples.calculator.Calculator of bean CalculatorBean: No corresponding business method in the bean class com.sap.examples.calculator.CalculatorBean was found for method substract.Error in the local interface com.sap.examples.calculator.CalculatorLocal of bean CalculatorBean: No corresponding business method in the bean class was found for method substract.
at com.sap.engine.services.ejb.deploy.verifier.Verifier.check(Verifier.java:66)
at com.sap.engine.services.ejb.deploy.DeployAdmin.generate(DeployAdmin.java:252)
at com.sap.engine.services.ejb.EJBAdmin.deploy(EJBAdmin.java:2118)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:594)
at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:379)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:296)
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.deploy(DeployServiceImpl.java:463)
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: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:37)
at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
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:94)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment exception : The deployment of at least one item aborted
I read a lot of posts about similar errors, but nothing has put me through this problem.thx, was a simple typing error.
deploy is done, but now I have the next problem.
show this error on ie
Application error occurs during processing the request.
Details: com.sap.engine.services.servlets_jsp.server.exceptions.WebIOException: Internal error while parsing JSP page C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/CalculatorEar/servlet_jsp/Calculator/root/Calculator.jsp.
at com.sap.engine.services.servlets_jsp.server.jsp.JSPParser.parse(JSPParser.java:117)
at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.getClassName(JSPServlet.java:238)
at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.compileAndGetClassName(JSPServlet.java:428)
at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:169)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:391)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:265)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:345)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:323)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:865)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:240)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
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:94)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
Caused by: com.sap.engine.services.servlets_jsp.lib.jspparser.exceptions.JspParseException: Expecting [ = ] instead of [ < ].
Error in file C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/CalculatorEar/servlet_jsp/Calculator/root/Calculator.jsp; line: 1; position: 0.
at com.sap.engine.services.servlets_jsp.lib.jspparser.syntax.Attribute.parse(Attribute.java:84)
at com.sap.engine.services.servlets_jsp.lib.jspparser.syntax.JspTag.readAttributes(JspTag.java:62)
at com.sap.engine.services.servlets_jsp.lib.jspparser.syntax.JspDirective.parse0(JspDirective.java:130)
at com.sap.engine.services.servlets_jsp.lib.jspparser.syntax.JspDirective.parse(JspDirective.java:96)
at com.sap.engine.services.servlets_jsp.lib.jspparser.syntax.ElementCollection.parse(ElementCollection.java:89)
at com.sap.engine.services.servlets_jsp.lib.jspparser.syntax.ParserImpl.parse(ParserImpl.java:525)
at com.sap.engine.services.servlets_jsp.server.jsp.JSPParser.initParser(JSPParser.java:339)
at com.sap.engine.services.servlets_jsp.server.jsp.JSPParser.parse(JSPParser.java:105)
... 18 more
is there a way to look the files on the server? -
Ess deployment failed with an error localization failed
Hi,
I'm trying to deploy the ess business packages but got the following error during the deployment:
Starting validation -
Info: Prerequisite error handling strategy: OnPrerequisiteErrorSkipDepending
Info: Update strategy: UpdateLowerOrChangedVersions
Info: Starting deployment prerequisites:
Info: Loading selected archives...
Info: Loading archive 'D:\usr\sap\NWP\JC00\SDM\program\temp\BPERP5ESS15_0-10003288.SCA'
Info: Loading archive 'D:\usr\sap\NWP\JC00\SDM\program\temp\SAPPCUIGP15P_1-20001215.SCA'
Info: Loading archive 'D:\usr\sap\NWP\JC00\SDM\program\temp\SAPESS15_0-20000512.SCA'
Info: Loading archive 'D:\usr\sap\NWP\JC00\SDM\program\temp\SAPMSS15_0-20000503.SCA'
Info: Loading archive 'D:\usr\sap\NWP\JC00\SDM\program\temp\SAPPSS15_0-20001217.SCA'
Info: Selected archives successfully loaded.
Info: Actions per selected component:
Info: Software type of SDA: J2EE
Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Info: Begin of log messages of the target system:
Start updating EAR file...
start-up mode is lazy
EAR file updated successfully for 1094ms.
Start deploying ...
EAR file uploaded to server for 1485ms.
ERROR: Not deployed. Deploy Service returned ERROR: java.rmi.RemoteException: Cannot deploy application sap.com/ess~bp_ess..
Reason: <--Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='Exception during deploy: Failed to deploy archive
D:\usr\sap\NWP\JC00\j2ee\cluster\server0\.\temp\deploy\work\deploying\reader1245916977968\sap.comessbp_ess.epa
and I tried to find the reader1245916977968 but it was not created in the path above.
Thanks,
Niranjan.Hi,
Kindly paste error from sdm logs and dev_jrfc, dev_dispatcher. for more details.
Shailesh -
Hi Friends,
I created a new webdynpro App and added it to the DC (which I created on the Track). The track also has dependend ESS SC's like SAP_JEE, SAP_BUILDT.. When I try to deploy this DC I get the following error saying "Deployment failed".
I cant understand how to check this hint part. Any help is appreciated.
Hint: Are all referenced components deployed and available on the engine?
Oct 22, 2008 5:01:57 PM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy
Thread,5,main]] INFO:
[003]Additional log information about the deployment
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7185 - 630]/>
<!NAME[C:\usr\sap\XPS\JC01\SDM\program\log\sdmcl20081022210212.log]/>
<!PATTERN[sdmcl20081022210212.log]/>
<!FORMATTER[com.sap.tc.logging.TraceFormatter(%24d %s: %m)]/>
<!ENCODING[UTF8]/>
<!LOGHEADER[END]/>
Oct 22, 2008 5:02:12 PM Info: -
Starting deployment -
Oct 22, 2008 5:02:12 PM Info: Error handling strategy: OnErrorStop
Oct 22, 2008 5:02:12 PM Info: Prerequisite error handling strategy: OnPrerequisiteErrorStop
Oct 22, 2008 5:02:12 PM Info: Update strategy: UpdateAllVersions
Oct 22, 2008 5:02:12 PM Info: Starting deployment prerequisites:
Oct 22, 2008 5:02:13 PM Info: Loading selected archives...
Oct 22, 2008 5:02:13 PM Info: Loading archive 'C:\usr\sap\XPS\JC01
\SDM\program\temp\temp42155bwd.combbccustomessperdata.ear'
Oct 22, 2008 5:02:15 PM Info: Selected archives successfully loaded.
Oct 22, 2008 5:02:15 PM Info: Actions per selected component:
Oct 22, 2008 5:02:15 PM Info: Initial deployment: Selected development component
'bbc/custom/ess/perdata'/'bwd.com'/'LOKAL'/'0.2008.10.22.17.01.37'/'0' will be deployed.
Oct 22, 2008 5:02:15 PM Info: Ending deployment prerequisites. All items are correct.
Oct 22, 2008 5:02:15 PM Info: Saved current Engine state.
Oct 22, 2008 5:02:15 PM Info: Starting: Initial deployment: Selected development component
'bbc/custom/ess/perdata'/'bwd.com'/'LOKAL'/'0.2008.10.22.17.01.37'/'0' will be deployed.
Oct 22, 2008 5:02:15 PM Info: SDA to be deployed: C:\usr\sap\XPS\JC01
\SDM\root\origin\bwd.com\bbc\custom\ess\perdata\LOKAL\0\0.2008.10.22.17.01.37
\temp42155bwd.combbccustomessperdata.ear
Oct 22, 2008 5:02:15 PM Info: Software type of SDA: J2EE
Oct 22, 2008 5:02:15 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Oct 22, 2008 5:02:16 PM Info: Begin of log messages of the target system:
08/10/22 17:02:15 - ***********************************************************
08/10/22 17:02:15 - Start updating EAR file...
08/10/22 17:02:15 - start-up mode is lazy
08/10/22 17:02:15 - EAR file updated successfully for 94ms.
08/10/22 17:02:15 - Start deploying ...
08/10/22 17:02:15 - EAR file uploaded to server for 47ms.
08/10/22 17:02:16 - ERROR: Not deployed. Deploy Service returned ERROR:
java.rmi.RemoteException: Cannot deploy application bwd.com/bbccustomess~perdata..
Reason: Clusterwide exception: Failed to deploy application bwd.com/bbccustomess~perdata.
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 bwd.com/bbccustomess~perdata. 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:569)
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:319)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request
(P4SessionProcessor.java:136)
at
com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process
(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Caused by: com.sap.engine.services.deploy.container.DeploymentException: Clusterwide
exception: Failed to deploy application bwd.com/bbccustomess~perdata. Check causing exception for details (trace
file). Hint: Are all referenced components deployed and available on the engine?
at com.sap.engine.services.webdynpro.WebDynproContainer.deploy
(WebDynproContainer.java:1050)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents
(DeploymentTransaction.java:606)
at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin
(DeployUtilTransaction.java:321)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin
(DeploymentTransaction.java:307)
at
com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer
(ApplicationTransaction.java:292)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases
(ApplicationTransaction.java:326)
at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction
(DeployServiceImpl.java:3186)
at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy
(DeployServiceImpl.java:554)
... 10 more
For detailed information see the log file of the Deploy Service.
08/10/22 17:02:16 - ***********************************************************
Oct 22, 2008 5:02:16 PM Info: End of log messages of the target system.
Oct 22, 2008 5:02:16 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Oct 22, 2008 5:02:16 PM Error: Aborted: development component
'bbc/custom/ess/perdata'/'bwd.com'/'LOKAL'/'0.2008.10.22.17.01.37'/'0':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot deploy application bwd.com/bbccustomess~perdata..
Reason: Clusterwide exception: Failed to deploy application bwd.com/bbccustomess~perdata. 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 bwd.com/bbccustomess~perdata. 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)
Oct 22, 2008 5:02:16 PM Info: Starting to save the repository
Oct 22, 2008 5:02:17 PM Info: Finished saving the repository
Oct 22, 2008 5:02:17 PM Info: J2EE Engine is in same state (online/offline) as it has been before this deployment
process.
Oct 22, 2008 5:02:17 PM Error: -
At least one of the Deployments failed -
Thanks,
PSBHi,
You can check, all the SCAs that have got deployed on the server, in the location ..
"C:\usr\sap\J9A\JC00\j2ee\cluster\server0\apps\sap.com"
As usual "C:\", "J9A", "JC00" have to be replaced with the one specific to your scenario.
Just check whether all your used DCs have been deployed there.
regards,
amar s -
Error while deploying ESS through SDM
Hi,
While deploying ESS through SDM i got following error for one of the files:
Starting Deployment of tc/sl.ut.content.erp.xss
Aborted: development component 'tc/sl.ut.content.erp.xss'/'sap.com'/'MAIN_ERP53PAT_C'/'2433758'/'0', grouped by software component 'SAP_ESS'/'sap.com'/'MAIN_ERP53PAT_C'/'1000.603.0.0.1.20080207103154''/'0':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Error occurred while deploying ear file ./temp/deploy/work/deploying/tc_sl.ut.content.erp.xss.ear. Reason: None of the available containers recognized the components of application sap.com/tc~sl.ut.content.erp.xss; it is not possible to make deploy.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of tc/sl.ut.content.erp.xss finished with Error (Duration 13250 ms)
Can anyone please tell what exactly the issue could be because of which that particular file is not recognized.
Thanks & regards,
AnupreetHi,
Its always advisable to use JSPM for the installation. Copy all the installable files in the JSPM temp folder and the instalation will be taken care and you don't have to worry about dependencies.
If you are using SDM make sure that you deploy PCUI_GP component FIRST, then the other components in any order.
Regards
Deb -
Error while deploying BPEL Process(Error during deployment: Deployment Fail
Hi,
when i try to deploying 11.1.1.3 - bpel project with thirdpartyparty adapter from jdeveloper to weblogic server, I got the following error.
[04:53:50 PM] Error deploying archive sca_TPASOAProject_rev1.0.jar to partition "default" on server soa_server1 [10.150.67.195:8001]
[04:53:50 PM] HTTP error code returned [500]
[04:53:50 PM] Error message from server:
Error during deployment: Deployment Failed: [JCABinding] [TPASOAProject.Service1/1.0]Unable to complete load due to: Generic error.
Generic error.
Cause: Unable to find suitable outbound binding.
Please create a Service Request with Oracle Support.
: Generic error.
Generic error.
Cause: Unable to find suitable outbound binding.
Please create a Service Request with Oracle Support.
[04:53:50 PM] Check server log for more details.
[04:53:50 PM] Error deploying archive sca_TPASOAProject_rev1.0.jar to partition "default" on server soa_server1 [10.150.67.195:8001]
[04:53:50 PM] #### Deployment incomplete. ####
[04:53:50 PM] Error deploying archive file:/C:/JDeveloper/mywork/Application16/TPASOAProject/deploy/sca_TPASOAProject_rev1.0.jar
(oracle.tip.tools.ide.fabric.deploy.common.SOARemoteDeployer)
Please, any one can tell solution for this.
Thanks In advance
Amar.
Edited by: 897448 on Dec 13, 2011 8:48 PMHi,
when i try to deploying 11.1.1.3 - bpel project with thirdpartyparty adapter from jdeveloper to weblogic server, I got the following error.
[04:53:50 PM] Error deploying archive sca_TPASOAProject_rev1.0.jar to partition "default" on server soa_server1 [10.150.67.195:8001]
[04:53:50 PM] HTTP error code returned [500]
[04:53:50 PM] Error message from server:
Error during deployment: Deployment Failed: [JCABinding] [TPASOAProject.Service1/1.0]Unable to complete load due to: Generic error.
Generic error.
Cause: Unable to find suitable outbound binding.
Please create a Service Request with Oracle Support.
: Generic error.
Generic error.
Cause: Unable to find suitable outbound binding.
Please create a Service Request with Oracle Support.
[04:53:50 PM] Check server log for more details.
[04:53:50 PM] Error deploying archive sca_TPASOAProject_rev1.0.jar to partition "default" on server soa_server1 [10.150.67.195:8001]
[04:53:50 PM] #### Deployment incomplete. ####
[04:53:50 PM] Error deploying archive file:/C:/JDeveloper/mywork/Application16/TPASOAProject/deploy/sca_TPASOAProject_rev1.0.jar
(oracle.tip.tools.ide.fabric.deploy.common.SOARemoteDeployer)
Please, any one can tell solution for this.
Thanks In advance
Amar.
Edited by: 897448 on Dec 13, 2011 8:48 PM -
Error deploying the composite on soa_server1: Deployment Failed ..
Hi,
I am trying to access external webservice from my BPEL Process; imported the external system's wsdl with xsd into my local & change all the reference of the xsd in my wsdl ,which now pointing to local xsd etc.
I am getting the following error while deploying to EM console from my J Developer; but in Make/Rebuild from jdevloper is working fine, no error. In the deployment from JDeveloper 11.1.1.5.0 I got this below error.
[01:36:45 PM] Error deploying archive sca_TG7_rev1.0.0.jar to partition "default" on server soa_server1
[01:36:45 PM] HTTP error code returned [500]
[01:36:45 PM] Error message from server:
There was an error deploying the composite on soa_server1: Deployment Failed: Unable to register service..
[01:36:45 PM] Check server log for more details.
[01:36:45 PM] Error deploying archive sca_TG7_rev1.0.0.jar to partition "default" on server soa_server1 [01:36:45 PM] #### Deployment incomplete. ####
[01:36:45 PM] Error deploying archive file:/C:/JDeveloper/mywork/TG7/deploy/sca_TG7_rev1.0.0.jar
(oracle.tip.tools.ide.fabric.deploy.common.SOARemoteDeployer)
========Log ==
<[ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <2db1df1f7258da77:342b4c64:1361c317b43:-8000-0000000000007504> <1331930173734> <BEA-000000> <Error during deployment
oracle.fabric.common.FabricException: Deployment Failed: Unable to register service.
at oracle.integration.platform.blocks.deploy.StandaloneCompositeDeploymentCoordinatorImpl.coordinateCompositeDeployment(StandaloneCompositeDeploymentCoordinatorImpl.java:62)
at oracle.integration.platform.blocks.deploy.servlet.BaseDeployProcessor.deployNewComposite(BaseDeployProcessor.java:378)
at oracle.integration.platform.blocks.deploy.servlet.BaseDeployProcessor.deploySARs(BaseDeployProcessor.java:226)
at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeployWork(DeployProcessor.java:160)
at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeployWork(DeployProcessor.java:109)
at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeploy(DeployProcessor.java:96)
at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.process(DeployProcessor.java:78)
at oracle.integration.platform.blocks.deploy.servlet.CompositeDeployerServlet.doPostInsideLoggingSession(CompositeDeployerServlet.java:221)
at oracle.integration.platform.blocks.deploy.servlet.CompositeDeployerServlet.doPost(CompositeDeployerServlet.java:124)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:111)
at java.security.AccessController.doPrivileged(Native Method)
at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413)
at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:94)
at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:161)
at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:111)
at java.security.AccessController.doPrivileged(Native Method)
at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413)
at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:94)
at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:161)
at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:136)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3715)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3681)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2277)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2183)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1454)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused By: oracle.fabric.common.FabricDeploymentException: Unable to register service. {rootCauses=[]}
at oracle.integration.platform.blocks.soap.WebServiceEntryBindingComponent.load(WebServiceEntryBindingComponent.java:226)
at oracle.integration.platform.blocks.soap.WebServiceEntryBindingComponent.load(WebServiceEntryBindingComponent.java:97)
at oracle.integration.platform.blocks.deploy.CompositeDeploymentConnection.deployServices(CompositeDeploymentConnection.java:160)
at oracle.integration.platform.blocks.deploy.CompositeDeploymentConnection.deploy(CompositeDeploymentConnection.java:91)
at oracle.integration.platform.blocks.deploy.CompositeDeploymentManagerImpl.initDeployment(CompositeDeploymentManagerImpl.java:149)
at oracle.integration.platform.blocks.deploy.CompositeDeploymentManagerImpl.load(CompositeDeploymentManagerImpl.java:62)
at sun.reflect.GeneratedMethodAccessor1622.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
at oracle.integration.platform.blocks.deploy.DeploymentEventPublisher.invoke(DeploymentEventPublisher.java:68)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at $Proxy306.load(Unknown Source)
at oracle.integration.platform.blocks.deploy.StandaloneCompositeDeploymentCoordinatorImpl.coordinateCompositeDeployment(StandaloneCompositeDeploymentCoordinatorImpl.java:57)
at oracle.integration.platform.blocks.deploy.servlet.BaseDeployProcessor.deployNewComposite(BaseDeployProcessor.java:378)
at oracle.integration.platform.blocks.deploy.servlet.BaseDeployProcessor.deploySARs(BaseDeployProcessor.java:226)
at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeployWork(DeployProcessor.java:160)
at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeployWork(DeployProcessor.java:109)
at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeploy(DeployProcessor.java:96)
at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.process(DeployProcessor.java:78)
at oracle.integration.platform.blocks.deploy.servlet.CompositeDeployerServlet.doPostInsideLoggingSession(CompositeDeployerServlet.java:221)
at oracle.integration.platform.blocks.deploy.servlet.CompositeDeployerServlet.doPost(CompositeDeployerServlet.java:124)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:111)
at java.security.AccessController.doPrivileged(Native Method)
at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413)
at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:94)
at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:161)
at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:111)
at java.security.AccessController.doPrivileged(Native Method)
at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413)
at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:94)
at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:161)
at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:136)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3715)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3681)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2277)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2183)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1454)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
An help will be much .Hi There...
Oracle explains:
The cause of the problem:
While defining an Exposed Service for your composite you used the option Generate WSDL from schemas and selected elements or types from one of more XML schema (.xsd) files to define the various message parts for input or outputs to the service. One of these message parts was defined by selecting from a schema an element or type that is not associated with an XML namespace.
Therefore at deployment time, if the WSDL file for the exposed service defines a default namespace, all elements must belong to either the default namespace or any namespace explicitly defined for each element or type. Since there is no XML namespace associated with the "no namespace" XML element or type in question there is no namespace prefix that can be used to identify the relevant XML namespace.
Solution:
1. Ensure all elements and types use an XML namespace.
Adjust the original XSD so that the offending "no namespace" elements/types are associated with a namespace.
2. Modify the WSDL for the service to allow No Namespace elements/types to be used
Whilst is is not possible to give a fixed sequence of steps to achieve this, essentially:
ensure the definitions element in the WSDL document does not use an xmlns="xxxx" attribute to set a default namespace
without a default namespace, ensure all other elements in the document that are expected to be associated with the previous default namespace have an explicit
namespace declaration
Riko -
Windows 7 Image Deployment Failed in HP model D530 using MDT 2012 and ADK 8.0
Hi,
I need your help to sort out the following issue.
I have installed MDT 2012 +ADK 8.0 and created Windows 7 32 bit OS from CD in the deployment share and tried deploying the raw OS from Deployment Share in to a reference machine (HP D530) ,the deployment failed also couldn't able to capture
Image from the machine,even the sysprep failed. This is the error
Your PC needs to restart.
Please hold down the power button.
Error Code:0x0000005D
Parameters:
0x030F0209
0x746E6547
0X49656E69
0X6C65746E
So tried the same in another HP machine ,the deployment was success and also was able to capture the refrence machine.
Need your help to find why this error occurred in this specific HP model D530 alone. Is it the reason that ADK was not supported in that specific model.
D530 is the maximum available HW model in client environment so your help will be much appreciated.
Thanks in Advance!!I have never seen that error before (see identical post). I did a quick internet search and found the following:
http://optimizewindows8.wordpress.com/2013/03/26/how-to-fix-error-code-0x0000005d/
Either:
1) Upgrade your machines with modern processors that support the ADK.
or
2) Downgrade to the WAIK
http://www.microsoft.com/en-us/download/details.aspx?id=5753 and stick with Windows 7.
Keith Garner - keithga.wordpress.com -
Merchandising Deployment Fails w/ Table does not exist error
Very intermittently, our Merchandising Deployments fail.
After successfully inserting records into a target table (e.g. dcs_sku), it suddenly fails and the logs show an Oracle error about said table missing.
The table exists. It's there. We realize this is very strange.
Has anybody else encountered this? The stacktrace is below:
09:29:24,077 ERROR [ProductCatalog_staging] SQL Statement Failed: [++SQLInsert++]
INSERT INTO dcs_sku(sku_id,version,creation_date,start_date,end_date,display_name,description,sku_type,fulfiller,nonreturnable)
VALUES(?,?,?,?,?,?,?,?,?,?)
-- Parameters --
p[1] = {pd} sku12345 (java.lang.String)
p[2] = {pd: version} 1 (java.lang.Integer)
p[3] = {pd: creationDate} 2011-08-08 11:54:59.0 (java.sql.Timestamp)
p[4] = {pd: startDate} null
p[5] = {pd: endDate} null
p[6] = {pd: displayName} Sku Description (java.lang.String)p[7] = {pd: description} null
p[8] = {pd: type} 0 (java.lang.Integer)
p[9] = {pd: fulfiller} 0 (java.lang.Integer)
p[10] = {pd: nonreturnable} false (java.lang.Boolean)
[--SQLInsert--]
09:29:24,197 ERROR [DeploymentManager] item = repositoryMarker:mark2455397 cause = CONTAINER:atg.deployment.DistributedDeploymentException; SOURCE:CONTAINER:atg.repository.RepositoryException; SOURCE:java.sql.SQLException
: ORA-00604: error occurred at recursive SQL level 1
ORA-00942: table or view does not exist
at atg.deployment.repository.RepositoryWorkerThread.processMarkerForAddUpdatePhase(RepositoryWorkerThread.java:245)
at atg.deployment.DeploymentWorkerThread.processMarkerPhase(DeploymentWorkerThread.java:521)
at atg.deployment.DeploymentWorkerThread.run(DeploymentWorkerThread.java:300)
message = Deployment Failed time = Fri Aug 12 09:29:24 PDT 2011 atg.deployment.DeploymentFailure@3d938aa9
CAUGHT AT:
CONTAINER:atg.deployment.DistributedDeploymentException; SOURCE:CONTAINER:atg.repository.RepositoryException; SOURCE:java.sql.SQLException: ORA-00604: error occurred at recursive SQL level 1
ORA-00942: table or view does not exist
at atg.deployment.repository.RepositoryWorkerThread.processMarkerForAddUpdatePhase(RepositoryWorkerThread.java:245)
at atg.deployment.DeploymentWorkerThread.processMarkerPhase(DeploymentWorkerThread.java:521)
at atg.deployment.DeploymentWorkerThread.run(DeploymentWorkerThread.java:300)
Caused by: CONTAINER:atg.repository.RepositoryException; SOURCE:java.sql.SQLException: ORA-00604: error occurred at recursive SQL level 1
ORA-00942: table or view does not exist
at atg.adapter.gsa.GSAItemDescriptor.addItem(GSAItemDescriptor.java:6416)
at atg.adapter.gsa.GSARepository.addItem(GSARepository.java:1010)
at atg.deployment.repository.RepositoryWorkerThread.deployItem(RepositoryWorkerThread.java:1071)
at atg.deployment.repository.RepositoryWorkerThread.processMarkerForAddUpdatePhase(RepositoryWorkerThread.java:233)
... 2 more
Caused by: java.sql.SQLException: ORA-00604: error occurred at recursive SQL level 1
ORA-00942: table or view does not exist
at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:70)
at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:131)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:204)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:455)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:413)
at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:1034)
at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:194)
at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:953)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1222)
at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3387)
at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:3468)
at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeUpdate(OraclePreparedStatementWrapper.java:1062)
at org.jboss.resource.adapter.jdbc.WrappedPreparedStatement.executeUpdate(WrappedPreparedStatement.java:278)
at atg.adapter.gsa.SQLStatement.executeUpdate(SQLStatement.java:725)
at atg.adapter.gsa.Table.insert(Table.java:1378)
at atg.adapter.gsa.GSAItemDescriptor.addItem(GSAItemDescriptor.java:6339)
... 5 more
thanks!
JoeWe ran into a similar ORA-00942 issue when statements hitting the same table with the same SQL worked fine before and after. This was happening to us in production, and flushing the shared pool made them go away immediately.
Research led to this link that has a patch that you can try to apply: http://www.freelists.org/post/oracle-l/Not-as-straightforward-as-it-would-appear-exec-java-javasqlSQLException-ORA00942-table-or-view-does-not-exist,3 -
Sun java studio enterprise 8 - Deployment FAILED error
could anyone please help?
When I try to Deploy a EJB module and webservice I get Deployment failed:
run-deploy:
Starting server Sun Java System Application Server 8.1
/app/sun/jstudio_ent8/AppServ8.1UR2/bin/asadmin start-domain --domaindir /app/sun/jstudio_ent8/AppServ8.1UR2/domains/ domain1
Distributing /vfat/Roe/DevProject/Implementation/EJBModuleOnlineRegistration/dist/EJBModuleOnlineRegistration.jar to [localhost:4848_server]
Start registering the project's server resources
Finished registering server resources
No archivist is able to handle the archive /vfat/Roe/DevProject/Implementation/EJBModuleOnlineRegistration/dist/EJBModuleOnlineRegistration.jar
Deployment FAILED: No archivist is able to handle the archive /vfat/Roe/DevProject/Implementation/EJBModuleOnlineRegistration/dist/EJBModuleOnlineRegistration.jarYour porblem has been developed by another user:
Does the MSQL database have a primary key, the CMP wizard determines the primary key based on the primary key setup on the database. The primary key which is selected can be detemined using the database browser Runtime->Database, this displays meta data information from the specified databases.
John
http://websearch.money.cnn.com/websearch/search?magazine=websearch&query=media-press-release.com
http://websearch.money.cnn.com/websearch/search?magazine=websearch&query=hostcube.co.uk -
MDT2012 - Deployment failed, the system cannot find the file specified
Hi everybody.
First, excuse me for my english, i think it's not the best thing I'm able to do, but now, I REALLY need help.
I encounter issues with my MDT 2012 Update 1 platform.
I have 5 systems to capture. All systems have 3 partitions (System, softwares, data). Capture is working fine for all parts.
In my Task Sequence, to deploy these images (C, D and E parts), I use a script after the "Install Operating System" which runs imagex to deploy the WIM images for D: and E:.
The script is the following :
"%DeployRoot%\Tools\x64\imagex" /apply "%DeployRoot%\Operating Systems\D_Drive\D_Drive.wim" 1 %DDrive%"
But, for some images, the task fails on the "D" drive deployement. The wizard shows the following error :
Litetouch deployment dailed, return code = -214767259 0x80004005
Failed to run the action: InstallD (ie : the script above)
The system cannot find the file specified. (Error: 00000002; Source: Windows)
The error is on my task which uses imagex to deploy my D and E WIM.
So I looked to see if the file's path was the good one.
And it is !!!
Wizard says that the file couldn't be find, but the file is existing, and in the good path.
For your information, there is no problem when I don't use multicast. Everything is working fine on unicast, not on multicast.
I even encounter this issue if I use my MDT server and my computers on the same switch.
Any help would be gratefull, my client gives me the week to resolve the issue.
ThanksBDD.LOG
<![LOG[Microsoft Deployment Toolkit version: 6.1.2373.0]LOG]!><time="16:53:56.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[The task sequencer log is located at X:\WINDOWS\TEMP\SMSTSLog\SMSTS.LOG. For task sequence failures, please consult this log.]LOG]!><time="16:53:56.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Write all logging text to \\192.168.36.208\Logs$]LOG]!><time="16:53:56.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Validating connection to \\192.168.36.208\Logs$]LOG]!><time="16:53:56.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Already connected to server 192.168.36.208 as that is where this script is running from.]LOG]!><time="16:53:56.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Will boot into Windows PE architecture x64 to match OS being deployed.]LOG]!><time="16:53:56.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[OSDTargetDriveCache was determined earlier : V:]LOG]!><time="16:53:56.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Property OSDTargetDriveCache is now = V:]LOG]!><time="16:53:56.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Property OSDisk is now = V:]LOG]!><time="16:53:56.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Open Control File: OperatingSystems]LOG]!><time="16:53:56.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[------ Applying Windows image using ImageX.exe ------]LOG]!><time="16:53:56.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[LTI applying image \\192.168.36.208\MDT$\Operating Systems\Master 3 avec Sysprep\CAPT.wim using ImageX]LOG]!><time="16:53:56.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Event 41023 sent: LTI applying image \\192.168.36.208\MDT$\Operating Systems\Master 3 avec Sysprep\CAPT.wim using ImageX]LOG]!><time="16:53:56.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Property SourcePath is now = \\192.168.36.208\MDT$\Operating Systems\Master 3 avec Sysprep]LOG]!><time="16:53:56.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Multicast transfer to directory: C:\MININT\Operating Systems\Master 3 avec Sysprep]LOG]!><time="16:53:56.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[<Message containing password has been suppressed>]LOG]!><time="16:53:56.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Command has been started (process ID 1348)]LOG]!><time="16:53:56.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ZTI Heartbeat: command has been running for 0 minutes (process ID 1348)]LOG]!><time="16:53:57.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Event 41003 sent: ZTI Heartbeat: command has been running for 0 minutes (process ID 1348)]LOG]!><time="16:53:57.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console >
]LOG]!><time="16:53:57.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > Transfer Started.
]LOG]!><time="16:53:57.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ZTI Heartbeat: command has been running for 5 minutes (process ID 1348)]LOG]!><time="16:58:01.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Event 41003 sent: ZTI Heartbeat: command has been running for 5 minutes (process ID 1348)]LOG]!><time="16:58:01.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console >
]LOG]!><time="17:00:43.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > Transfer Complete [0x0].]LOG]!><time="17:00:43.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Return code from command = 0]LOG]!><time="17:00:43.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Multicast transfer of "\\192.168.36.208\MDT$\Operating Systems\Master 3 avec Sysprep\CAPT.wim" to "C:\MININT\Operating Systems\Master 3 avec Sysprep\CAPT.wim" completed successfully.]LOG]!><time="17:00:43.000+000" date="02-19-2014" component="LTIApply"
context="" type="1" thread="" file="LTIApply">
<![LOG[Cleaning off old operating system]LOG]!><time="17:00:43.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Skipping V:\Drivers]LOG]!><time="17:00:43.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[New ZTIDiskPartition : \\MININT-1H9O4H6\root\cimv2:Win32_LogicalDisk.DeviceID="V:" \\MININT-1H9O4H6\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #0"]LOG]!><time="17:00:43.000+000" date="02-19-2014" component="LTIApply"
context="" type="1" thread="" file="LTIApply">
<![LOG[Enabling 8dot3 name support on volume V:]LOG]!><time="17:00:43.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[About to run command: "\\192.168.36.208\MDT$\Tools\X64\imagex.exe" /apply "C:\MININT\Operating Systems\Master 3 avec Sysprep\CAPT.wim" 1 V:]LOG]!><time="17:00:43.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread=""
file="LTIApply">
<![LOG[Command has been started (process ID 536)]LOG]!><time="17:00:43.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > ImageX Tool for Windows]LOG]!><time="17:00:43.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > Copyright (C) Microsoft Corp. All rights reserved.]LOG]!><time="17:00:43.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > Version: 6.1.7600.16385]LOG]!><time="17:00:43.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > [ 0% ] Applying progress ]LOG]!><time="17:00:43.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > [ 0% ] Applying progress ]LOG]!><time="17:00:49.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > [ 1% ] Applying progress ]LOG]!><time="17:00:49.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > [ 2% ] Applying progress ]LOG]!><time="17:00:55.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > [ 3% ] Applying progress ]LOG]!><time="17:00:58.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > [ 4% ] Applying progress: 5:28 mins remaining ]LOG]!><time="17:01:03.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > [ 5% ] Applying progress: 5:33 mins remaining ]LOG]!><time="17:01:07.000+000"
<![LOG[ Console > [ 99% ] Applying progress: 3 secs remaining ]LOG]!><time="17:06:43.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > [ 100% ] Applying progress ]LOG]!><time="17:06:50.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > Successfully applied image.]LOG]!><time="17:06:51.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > Total elapsed time: 6 min 7 sec]LOG]!><time="17:06:51.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Return code from command = 0]LOG]!><time="17:06:51.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Property LTIDirtyOS is now = TRUE]LOG]!><time="17:06:51.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[The image C:\MININT\Operating Systems\Master 3 avec Sysprep\CAPT.wim was applied successfully.]LOG]!><time="17:06:51.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Event 5625 sent: The image C:\MININT\Operating Systems\Master 3 avec Sysprep\CAPT.wim was applied successfully.]LOG]!><time="17:06:51.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[About to run command: "\\192.168.36.208\MDT$\Tools\X64\bootsect.exe" /nt60 V:]LOG]!><time="17:06:52.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Command has been started (process ID 1252)]LOG]!><time="17:06:52.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > Target volumes will be updated with BOOTMGR compatible bootcode.
]LOG]!><time="17:06:54.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console >
]LOG]!><time="17:06:54.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > V: (\\?\Volume{2ab15dec-99c9-19e3-baf6-94de80bab573})
]LOG]!><time="17:06:54.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console >
]LOG]!><time="17:06:54.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > Successfully updated NTFS filesystem bootcode.
]LOG]!><time="17:06:54.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console >
]LOG]!><time="17:06:54.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > Bootcode was successfully updated on all targeted volumes.
]LOG]!><time="17:06:54.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Return code from command = 0]LOG]!><time="17:06:54.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Find the boot drive (if any) [True] [6.1.7601.18229] [False]]LOG]!><time="17:06:54.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[New ZTIDiskPartition : \\MININT-1H9O4H6\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #0" \\MININT-1H9O4H6\root\cimv2:Win32_LogicalDisk.DeviceID="V:"]LOG]!><time="17:06:54.000+000" date="02-19-2014" component="LTIApply"
context="" type="1" thread="" file="LTIApply">
<![LOG[New ZTIDisk : \\MININT-1H9O4H6\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"]LOG]!><time="17:06:54.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Found bootable drive (No Boot File Test) [ V: ]: \\MININT-1H9O4H6\root\cimv2:Win32_LogicalDisk.DeviceID="V:"]LOG]!><time="17:06:54.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Ready to Prepare boot partition: V:]LOG]!><time="17:06:54.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[About to run command: cscript.exe //nologo "\\192.168.36.208\MDT$\Scripts\ztiRunCommandHidden.wsf" ""\\192.168.36.208\MDT$\Tools\X64\BCDBoot.exe" V:\windows /l fr-fr /s V:"]LOG]!><time="17:06:54.000+000" date="02-19-2014" component="LTIApply"
context="" type="1" thread="" file="LTIApply">
<![LOG[Microsoft Deployment Toolkit version: 6.1.2373.0]LOG]!><time="17:06:54.000+000" date="02-19-2014" component="ztiRunCommandHidden" context="" type="1" thread="" file="ztiRunCommandHidden">
<![LOG[The task sequencer log is located at X:\WINDOWS\TEMP\SMSTSLog\SMSTS.LOG. For task sequence failures, please consult this log.]LOG]!><time="17:06:54.000+000" date="02-19-2014" component="ztiRunCommandHidden" context="" type="1" thread=""
file="ztiRunCommandHidden">
<![LOG[Write all logging text to \\192.168.36.208\Logs$]LOG]!><time="17:06:54.000+000" date="02-19-2014" component="ztiRunCommandHidden" context="" type="1" thread="" file="ztiRunCommandHidden">
<![LOG[Validating connection to \\192.168.36.208\Logs$]LOG]!><time="17:06:54.000+000" date="02-19-2014" component="ztiRunCommandHidden" context="" type="1" thread="" file="ztiRunCommandHidden">
<![LOG[Already connected to server 192.168.36.208 as that is where this script is running from.]LOG]!><time="17:06:54.000+000" date="02-19-2014" component="ztiRunCommandHidden" context="" type="1" thread="" file="ztiRunCommandHidden">
<![LOG[About to run command: \\192.168.36.208\MDT$\Tools\X64\BCDBoot.exe V:\windows /l fr-fr /s V:]LOG]!><time="17:06:54.000+000" date="02-19-2014" component="ztiRunCommandHidden" context="" type="1" thread="" file="ztiRunCommandHidden">
<![LOG[Command has been started (process ID 1984)]LOG]!><time="17:06:54.000+000" date="02-19-2014" component="ztiRunCommandHidden" context="" type="1" thread="" file="ztiRunCommandHidden">
<![LOG[ Console > Boot files successfully created.]LOG]!><time="17:06:55.000+000" date="02-19-2014" component="ztiRunCommandHidden" context="" type="1" thread="" file="ztiRunCommandHidden">
<![LOG[Return code from command = 0]LOG]!><time="17:06:55.000+000" date="02-19-2014" component="ztiRunCommandHidden" context="" type="1" thread="" file="ztiRunCommandHidden">
<![LOG[Command has returned: 0]LOG]!><time="17:06:55.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Run Command: X:\WINDOWS\SYSTEM32\bcdedit.exe /Store "V:\boot\bcd" /timeout 0]LOG]!><time="17:06:55.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[BCD> The operation completed successfully.]LOG]!><time="17:06:55.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[BCDEdit returned ErrorLevel = 0]LOG]!><time="17:06:55.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Created scratch folder.]LOG]!><time="17:06:55.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Copy File: C:\MININT\unattend.xml to V:\Windows\Panther\Unattend.xml]LOG]!><time="17:06:55.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Copied unattend.xml to V:\Windows\Panther for image apply.]LOG]!><time="17:06:55.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[About to run command: dism.exe /Image:V:\ /Apply-Unattend:V:\Windows\Panther\Unattend.xml /ScratchDir:C:\MININT\Scratch]LOG]!><time="17:06:55.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Command has been started (process ID 1516)]LOG]!><time="17:06:55.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > Deployment Image Servicing and Management tool]LOG]!><time="17:06:55.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > Version: 6.1.7600.16385]LOG]!><time="17:06:55.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > Image Version: 6.1.7600.16385]LOG]!><time="17:06:56.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > The operation completed successfully.]LOG]!><time="17:06:57.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Return code from command = 0]LOG]!><time="17:06:57.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[LTIApply processing completed successfully.]LOG]!><time="17:06:57.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Event 41001 sent: LTIApply processing completed successfully.]LOG]!><time="17:06:57.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Command completed, return code = -2147467259]LOG]!><time="17:10:54.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Litetouch deployment failed, Return Code = -2147467259 0x80004005]LOG]!><time="17:10:54.000+000" date="02-19-2014" component="LiteTouch" context="" type="3" thread="" file="LiteTouch">
<![LOG[Event 41014 sent: Litetouch deployment failed, Return Code = -2147467259 0x80004005]LOG]!><time="17:10:54.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[For more information, consult the task sequencer log ...\SMSTS.LOG.]LOG]!><time="17:10:54.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property RetVal is now = -2147467259]LOG]!><time="17:10:54.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Validating connection to \\192.168.36.208\Logs$]LOG]!><time="17:10:54.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Already connected to server 192.168.36.208]LOG]!><time="17:10:54.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[OSDTargetDriveCache was determined earlier : V:]LOG]!><time="17:10:54.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property OSDTargetDriveCache is now = V:]LOG]!><time="17:10:54.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property OSDisk is now = V:]LOG]!><time="17:10:54.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying C:\MININT\SMSOSD\OSDLOGS\LiteTouch.log to \\192.168.36.208\Logs$\MININT-1H9O4H6\LiteTouch.log]LOG]!><time="17:10:54.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying C:\MININT\SMSOSD\OSDLOGS\LTIApply.log to \\192.168.36.208\Logs$\MININT-1H9O4H6\LTIApply.log]LOG]!><time="17:10:54.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying C:\MININT\SMSOSD\OSDLOGS\LTICopyScripts.log to \\192.168.36.208\Logs$\MININT-1H9O4H6\LTICopyScripts.log]LOG]!><time="17:10:54.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying C:\MININT\SMSOSD\OSDLOGS\PnpEnum.xml to \\192.168.36.208\Logs$\MININT-1H9O4H6\PnpEnum.xml]LOG]!><time="17:10:54.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying C:\MININT\SMSOSD\OSDLOGS\Wizard.log to \\192.168.36.208\Logs$\MININT-1H9O4H6\Wizard.log]LOG]!><time="17:10:54.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying C:\MININT\SMSOSD\OSDLOGS\ZTIBDE.log to \\192.168.36.208\Logs$\MININT-1H9O4H6\ZTIBDE.log]LOG]!><time="17:10:54.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying C:\MININT\SMSOSD\OSDLOGS\ZTIConfigure.log to \\192.168.36.208\Logs$\MININT-1H9O4H6\ZTIConfigure.log]LOG]!><time="17:10:55.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying C:\MININT\SMSOSD\OSDLOGS\ZTIDiskpart.log to \\192.168.36.208\Logs$\MININT-1H9O4H6\ZTIDiskpart.log]LOG]!><time="17:10:55.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying C:\MININT\SMSOSD\OSDLOGS\ZTIDrivers.log to \\192.168.36.208\Logs$\MININT-1H9O4H6\ZTIDrivers.log]LOG]!><time="17:10:55.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying C:\MININT\SMSOSD\OSDLOGS\ZTIGather.log to \\192.168.36.208\Logs$\MININT-1H9O4H6\ZTIGather.log]LOG]!><time="17:10:55.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying C:\MININT\SMSOSD\OSDLOGS\ZTINextPhase.log to \\192.168.36.208\Logs$\MININT-1H9O4H6\ZTINextPhase.log]LOG]!><time="17:10:55.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying C:\MININT\SMSOSD\OSDLOGS\ZTIPatches.log to \\192.168.36.208\Logs$\MININT-1H9O4H6\ZTIPatches.log]LOG]!><time="17:10:55.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying C:\MININT\SMSOSD\OSDLOGS\ztiRunCommandHidden.log to \\192.168.36.208\Logs$\MININT-1H9O4H6\ztiRunCommandHidden.log]LOG]!><time="17:10:55.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying C:\MININT\SMSOSD\OSDLOGS\ZTIValidate.log to \\192.168.36.208\Logs$\MININT-1H9O4H6\ZTIValidate.log]LOG]!><time="17:10:55.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying X:\WINDOWS\TEMP\SMSTSLog\SMSTS.LOG to \\192.168.36.208\Logs$\MININT-1H9O4H6\SMSTS.LOG]LOG]!><time="17:10:55.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying X:\WINDOWS\Debug\Netsetup.log to \\192.168.36.208\Logs$\MININT-1H9O4H6\]LOG]!><time="17:10:55.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying X:\WINDOWS\System32\wpeinit.log to \\192.168.36.208\Logs$\MININT-1H9O4H6\]LOG]!><time="17:10:55.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying log C:\MININT\SMSOSD\OSDLOGS\BDD.log contents to \\192.168.36.208\Logs$\MININT-1H9O4H6\BDD.LOG]LOG]!><time="17:10:55.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch"> -
Bpel deployment fails for all processes that have revision other than 1.0.
Using: Release *10.1.3.3.1*
Hello All,
Bpel deployment fails for all processes that have revision other than *1.0*.
We have been attempting to deploy several BPEL projects via ANT script to a target environment and are encountering failures to deploy for every project which isn’t a (revision 1.0). We are getting the following error whenever we try to deploy a process with a revision other than 1.0:
D:\TJ_AutoDeploy\BPEL_AutoDeploy_BETA\build.xml:65: BPEL archive doesnt exist in directory "{0}"
at com.collaxa.cube.ant.taskdefs.DeployRemote.getJarFile(DeployRemote.java:254)
at com.collaxa.cube.ant.taskdefs.DeployRemote.deployProcess(DeployRemote.java:409)
at com.collaxa.cube.ant.taskdefs.DeployRemote.execute(DeployRemote.java:211)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
at org.apache.tools.ant.Task.perform(Task.java:364)
at org.apache.tools.ant.Target.execute(Target.java:341)
at org.apache.tools.ant.Target.performTasks(Target.java:369)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40)
at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
at org.apache.tools.ant.Main.runBuild(Main.java:668)
at org.apache.tools.ant.Main.startAnt(Main.java:187)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67)
The structure of our automated deployment script is as follows:
First, a batch script calls (Jdeveloper_BPEL_Prompt.bat) in order to set all necessary environment variables i.e. ORACLE_HOME, BPEL_HOME, ANT_HOME, etc for ant.
Next, the script lists every .jar file within the directory to an .ini file called BPEL_List.ini. Furthermore, BPEL_DIR, ADMIN_USER and ADMIN_PSWD variables are set and initialized respectively to:
- “.” – point to directory where script is running from because all the BPEL processes are located here
- “oc4jadmin”
- “*********” (whatever the password for out environment is)
We’ve developed a method to have the script prompt the user to select the target environment to deploy to. Once the user selects the appropriate environment, the script goes through the BPEL_List.ini files and a loop tells it that for every BPEL process listed:
DO ant
-Dprocess.name=%%b
-Drev= !Rev!
-Dpath=%BPEL_DIR%
-Ddomain=default
-Dadmin.user=%ADMIN_USER%
-Dadmin.password=%ADMIN_PWD%
-Dhttp.hostname=%HOST%
-Dhttp.port=%PORT%
-Dverbose=true
(What’s happening is that the variables in the batch file are being passed on to the ANT script where *%%b* is the process name, !rev! is revision #, and so on…)
The loop goes through each line in the BPEL_List.ini and tokenizes the BPEL process into 3 parts *(%%a, %%b, and %%c)* but we only extract 2 parts: *%%b* (process name) and *%%c* which becomes !Rev! (revision number).
Example:
Sample BPEL process:
bpel_ThisIsProcess1_1.0.jar
bpel_ThisIsProcess2_SOAv2.19.0.001B.jar
After tokenizing:
%%a %%b %%c
bpel ThisIsProcess1 1.0.jar
bpel ThisIsProcess2 SOAv2.19.0.001B.jar
*!Rev!* and not *%%c* because *%%c* will return whatever the revision number is + the “.jar” file extension as illustrated above. So to circumvent this, we parse *%%c* so that the last 4 characters are stripped. Such is done like this:
set RevN=%%c
set RevN=!RevN:~0,-4!
Hence, the usage of !Rev!.
Below is a screenshot post of the ANT build.xml that goes with our script:
<!--<?xml version="1.0"?>-->
<!--BUILD.XML-->
<project name="bpel.deploy" default="deployProcess" basedir=".">
<!--
This ant build file was generated by JDev to deploy the BPEL process.
DONOT EDIT THIS JDEV GENERATED FILE. Any customization should be done
in default target in user created pre-build.xml or post-build.xml
-->
<property name="process.dir" value="${basedir}" />
<!-- Set BPEL process name -->
<!--
<xmlproperty file="${process.dir}/bpel/bpel.xml"/>
<property name="process.name" value="${BPELSuitcase.BPELProcess(id)}"/>
<property name="rev" value="${BPELSuitcase(rev)}"/>
-->
<property environment="env"/>
<!-- Set bpel.home from developer prompt's environment variable BPEL_HOME -->
<condition property="bpel.home" value="${env.BPEL_HOME}">
<available file="${env.BPEL_HOME}/utilities/ant-orabpel.xml" />
</condition>
<!-- show that both bpel and oracle.home are located (TESTING purposes ONLY) -->
<!-- <echo>HERE:${env.BPEL_HOME} ${env.ORACLE_HOME}</echo> -->
<!-- END TESTING -->
<!--If bpel.home is not yet using env.BPEL_HOME, set it for JDev -->
<property name="oracle.home" value="${env.ORACLE_HOME}" />
<property name="bpel.home" value="${oracle.home}/bpel" />
<!--First override from build.properties in process.dir, if available-->
<property file="${process.dir}/build.properties"/>
<!--import custom ant tasks for the BPEL PM-->
<import file="${bpel.home}/utilities/ant-orabpel.xml" />
<!--Use deployment related default properties-->
<property file="${bpel.home}/utilities/ant-orabpel.properties" />
<!-- *************************************************************************************** -->
<target name="deployProcess">
<tstamp>
<format property="timestamp" pattern="MM-dd-yyyy HH:mm:ss" />
</tstamp>
<!-- WRITE TO LOG FILE #tjas -->
<record name="build_verbose.log" loglevel="verbose" append="true" />
<record name="build_debug.log" loglevel="debug" append="true" />
<echo></echo>
<echo>####################################################################</echo>
<echo>BPEL_AutoDeploy initiated @ ${timestamp}</echo>
<echo>--------------------------------------------------------------------</echo>
<echo>Deploying ${process.name} on ${http.hostname} port ${http.port} </echo>
<echo>--------------------------------------------------------------------</echo>
<deployProcess
user="${admin.user}"
password="${admin.password}"
domain="${domain}"
process="${process.name}"
rev="${rev}"
dir="${process.dir}/${path}"
hostname="${http.hostname}"
httpport="${http.port}"
verbose="${verbose}" />
<sleep seconds="30" />
<!--<echo message="${process.name} deployment logged to ${build_verbose.log}"/>
<echo message="${process.name} deployment logged to ${build.log}"/> -->
</target>
<!-- *************************************************************************************** -->
</project>
SUMMARY OF ISSUE AT HAND:
~ Every bpel process w/ 1.0 revision deploys with no problems
~ At first I would get an invalid character error most likely due to the “!” preceding “Rev”, but then I decided to set rev=”false” in the build.xml file. That didn’t work quite well. In another attempt, I decided to leave the –Drev= attribute within the batch script blank. That still led to 1.0s going through. My next thought was deploying something other than a 1.0, such as 1.2 or 2.0 and that’s when I realized that if it wasn’t a 1.0, it refused to go through.
QUESTIONS:
1. IS THERE A WAY TO HAVE ANT LOOK INTO THE BPEL PROCESS AND PULL THE REVISION ID?
2. WHAT ARE WE DOING WRONG? ARE WE MISSING ANYTHING?
3. DID WE GO TOO FAR? MEANING, IS THERE A MUCH EASIER WAY WE OVERLOOKED/FORGOT/OR DON’T KNOW ABOUT THAT EXISTS?
Edited by: 793292 on Jul 28, 2011 12:38 PMOnly thing i can think of is instead of using a MAC ACL , u cud jus use the default class
Policy Map Test
class class-default
police 56000 8000 exceed-action drop
Class Map match-any class-default (id 0)
Match any
You would be saving a MAC-ACL ;-). -
MDT 2012 Litetocuh Deployment Failed, Return Code = -2147467259 0x0004005
Here is what I have tried. I have tried recreating the DeploymentShare. Moved my Deployment Test Share to the standard 2008 Server running MDT 2012. I have setup a Win7 x64 box as the Deployment Manager. I am still getting the following error:
Litetouch deployment failed, Return Code = -2147467259 0x80004005
Failed to run the action: Copy OEM files.
Incorrect function, (Error: 00000001; Source: Windows)
The execution of the group (Install has failed and the execution has been aborted. An action failed.
Operation abourted (Error: 80004004; Source Windows)
Failed to run the last action: Copy OEM files, Execution of task sequence failed.
Incorrect funtion. (Error: 00000001; Source: Windows)
Task Sequence Engine failed! Code: enExecutionFail
Task sequence execution failed with error code 80004005
Error Task Sequence Manager failed to execute task sequence. Code 0x80004005
Recreated the Image, Task Sequences, CS.ini and Boot.ini) Incorporated all OOB Drivers, Packages. Using
a USB 16Gb flash drive with LiteTouchx86.
List last time we tried to create a separate deployment share. Copy all the preexisting data from a working known good deployment share with images, task
sequence, cs.ini and all image files. Still getting the same issue.
Finally checked some of the Google, technet and forums for any assistance but non seem to do the trick.
I'm new to the process but have been working with a fellow tech who has been working with MDT for six months and he can not find the issue either.
Thanks for all your help up front.Can you post your log files?
IT Support " Scripting Noob "
Maybe you are looking for
-
Please Help, Issues when batch processing Multi Frame images in Fireworks
I hope someone will know how to do this and tell me where I am going wrong. Objective 1 I have a large number of images that all have the exact same number of frames (4) and are all exactly the same size that I want to get resized, cropped and water
-
Language and Region Date Preferences not working
Date set up is for UK (day/month/year), whichever format I use for cells in Numbers, it's aways MM leading. I tried everything on 2 separate machines and it's not working on both. What am I doing wrong ?
-
Is there a way to send an email in an automator workflow without sendingthe previous actions content? I'd like to notify some people in my group that I've added a file to a folder, but not send them the file, I don't want to fill up their inbox with
-
Different icons on home screen for each email account?
Good Morning, I have searched and searched to no avail for an answer to this (simple) question: Is there any way to have separate mail icons on your home screen for each of your mail accounts? I have my work/exchange email (knee-jerk response require
-
How do I downgrade to iMovie 9.0.1 or 9.0.0?
Back in January I upgraded to iMovie 9.0.2 and I have been working on a project ever since. Just to check on it, because my computer goes slow and I cant view how it will really play in the Full screen Theater, I export it from time to time to see ho