SDM deployment failed (DeployManagerException)
Dear programmers,
Since yesterday I'm trying to deploy an EAR file with NetWeaver Developer Studio. But, each time I get this error:
Apr 25, 2007 10:59:54... Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Apr 25, 2007 10:59:56... Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Apr 25, 2007 10:59:56... Error: Aborted: development component 'NewsEAR'/'sap.com'/'localhost'/'2007.04.24.11.16.39':
Caught exception while checking the login credentials for SAP J2EE Engine. Check whether the SAP J2EE Engine is up and running.
com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot connect to Host: [cp22383-a] with user name: [admin]
Check your login information.
Exception is:
com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Cannot authenticate the user.]
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.checkLoginCredentials.DMEXC)
Apr 25, 2007 11:00:33... Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
Apr 25, 2007 11:00:33... Error: -
At least one of the Deployments failed -
We did reset the SDM password in de Configtool and in the RemoteGui.bat. All processes seem to work, because they are green.
We appreciate your help.
Regards,
Adri
We found the solution while looking at my last question, which was almost the same. Thnx anyway
If you go to User Administration and change the password there, when next time you log in, in the portal you will get an notification that the password is expired. Change it to your liking and your problem is solved
Adri Kodde
Similar Messages
-
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 -
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 -
SDM Deployment Failed--SDM could not start the J2EE cluster on the DB Host
HI,
I am trying to deploy ESS packges in EP through SDM.But while deploying I am getting this error in SDM at the start itself:-
Error: An error occured while starting a cluster instance.
Oct 14, 2008 5:14:41 PM Error: There is no clutser control instance running on host SBPEPDB1 which is described in SecureStorage
Please check if there is an appropriate running cluster instances
SDM could not start the J2EE cluster on the host SBPEPDB1! The online deployment is terminated.
There is no clutser control instance running on host SBPEPDB1 which is described in SecureStorage
I am pasting the full LOG File details:-
Oct 14, 2008 6:32:00 PM Info: Starting cluster instance processes.
Oct 14, 2008 6:32:00 PM Error: An error occured while starting a cluster instance.
Oct 14, 2008 6:32:00 PM Error: There is no clutser control instance running on host SBPEPDB1 which is described in SecureStorage . The instances, returned by MessageServer [MS host: SBPEPCI1; MS port: 3900], are :
Name:JM_T1223989073901_0_CPCAPP109
Host:SBPEPCI1
State:5
HostAddress:172.17.131.38
Name:JC_CPCAPP109_EPP_01
Host:CPCAPP109
State:5
HostAddress:172.17.131.31
Please check if there is an appropriate running cluster instances.
Oct 14, 2008 6:32:00 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Oct 14, 2008 6:32:00 PM Error: Aborted: development component 'pcui_gp/isr/cfg'/'sap.com'/'MAIN_ERP05VAL_C'/'2515722'/'0', grouped by software component 'SAPPCUI_GP'/'sap.com'/'MAIN_ERP05VAL_C'/'1000.600.0.13.0.20080516101947''/'0':
SDM could not start the J2EE cluster on the host SBPEPDB1! The online deployment is terminated.
There is no clutser control instance running on host SBPEPDB1 which is described in SecureStorage .
The instances, returned by MessageServer [MS host: SBPEPCI1; MS port: 3900], are :
Name:JM_T1223989073901_0_CPCAPP109
Host:SBPEPCI1
State:5
HostAddress:172.17.131.38
Name:JC_CPCAPP109_EPP_01
Host:CPCAPP109
State:5
HostAddress:172.17.131.31
Please check if there is an appropriate running cluster instances.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).STARTUP_CLUSTER)
Oct 14, 2008 6:32:04 PM Info: Starting to save the repository
Oct 14, 2008 6:32:05 PM Info: Finished saving the repository
Oct 14, 2008 6:32:07 PM Info: Starting: Initial deployment: Selected software component 'SAPPCUI_GP'/'sap.com'/'MAIN_ERP05VAL_C'/'1000.600.0.13.0.20080516101947''/'0' will be deployed.
Oct 14, 2008 6:32:07 PM Error: Aborted: software component 'SAPPCUI_GP'/'sap.com'/'MAIN_ERP05VAL_C'/'1000.600.0.13.0.20080516101947''/'0':
Failed deployment of SDAs:
development component 'pcui_gp/isr/cfg'/'sap.com'/'MAIN_ERP05VAL_C'/'2515722'/'0' : aborted
Please, look at error logs above for more information!
I have checked the CONFIGTOOl and the properties seem to be OK.
I tried SHUTTING DOWN all APPLICATION servers & Restarting the DEPLOYMENT,but it still Failed
Pls suggest.
Regards,
Abhijeet
IHi George,
Thnx for your reply.
I have stopped all Application servers and kept only the CI-DB instances running.Retried deploying the ESS packages but still getting the same error.
Have checked the Visual admin,it is not in SAFE mode,it working normally.
Have alos checked the CLUSTER Manager Property Values in both Visual Admin & Config Tool,they are alright.
About the Cluster Resources,can you pls specify what exactly do you mean by "Cluster Resources are running or not".
I think if the application servers are stopped,then the Cluster resources shudnt come into play right?? Correct me if I am wrong.
Kindly suggest what other steps I shud take.
Regards,
Abhijeet -
Hi Experts
I am facing a strange issue when trying to deploy through NWDS. The EAR file does not deploy and the deployment hangs. Here the deployment simply hangs and no error is recieved. we tried restarting the SDM and deploying but even that failed.
When I rename the EAR file and deploy it works very fine. All other EAR files are deployed perfectly well.
Kindly advise as what could be the cause of the issue.
Thanks & Regards,
VijithHi,
If you have application with the same name, try to undeploy it first. If you had it in the past, check sdmrepository.xml and %SDM%/root and clean all references for your old application (with the same name). Once it's done, try to deploy the new application again,
Regards,
Mike -
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. -
J2ee Admin User locked on SDM Deployment - BI 7.0 and EP 7.0
Hi,
We had a recent issue on BI iview publishing from the BEX WAD 7.0 in our Production Portal server.
The BEX WAD had the error " Java communication error"
" An Error occured during communication with the BI Components of the J2ee engine"
We traced down to identify that the current stack NW 7.0 SP14 BI Components had issues and had to patch to the next level
However, during deployment of the patch using SDM, the components (all) failed posting the following error. The SDM deployment got struck and the J2ee Engine user j2ee_admin was locked.
Only a restart of the j2ee engine is allowing us to get the Visual Admin connected. But the SDM deployment again is failing and admin user gets locked. Is there any tested solution to solve this.
Kindly help asap.
Trace:
SDM:
Caught exception while checking the login credentials for SAP J2EE Engine. Check whether the SAP J2EE Engine is up and running.com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot connect to Host: [xxxx] with user name: [j2ee_admin]check your login information.
com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during getInitialContext operation. No server is running. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
J2ee Engine:
Error while connecting
com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is java.lang.SecurityException: com.sap.engine.services.security.exceptions.BaseSecurityException: This call must be performed from a system thread.
at com.sap.engine.services.security.login.SecuritySession.setExpirationPeriod(SecuritySession.java:479)
at com.sap.engine.services.security.login.TicketGenerator.getSecuritySession(TicketGenerator.java:180)
at com.sap.engine.services.security.login.SecurityContext.load(SecurityContext.java:313)
at com.sap.engine.services.rmi_p4.Message.loadContextObject(Message.java:345)
at com.sap.engine.services.rmi_p4.Message.parseMessage(Message.java:239)
at com.sap.engine.services.rmi_p4.Message.getByteArrayInputStream(Message.java:314)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:212)
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)Hi Anup,
The restart unlocks the j2ee engine admin user and i am able to login to Visual admin and SDM and not otherwise (SDM is hanged and doesnot allow another session and hence only restart helps me to get into SDM again)
Admin Pwds reset etc from config tool secure store and all possible solutions have been tried before restart.
However, after restart, when we try to deploy again, the deploy fails saying the same msg
Caught exception while checking the login credentials for SAP J2EE Engine. Check whether the SAP J2EE Engine is up and running.com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot connect to Host: [xxx] with user name: [j2ee_admin]check your login information.
com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during getInitialContext operation. No server is running. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
Any clues ?
Regards
Venkat. -
i am trying to deploy some missing components and get the following error. I have checked the j2ee_admin in the abap stack for client 001 and the password is the same for visual administrator and in secure store. any ideas?
===========================================================================
Deployment started Fri Feb 01 08:21:29 GMT 2008
===========================================================================
Starting Deployment of com.sap.ip.bi.broadcasting
Deployment of com.sap.ip.bi.broadcasting finished successfully (Duration 4781 ms)
Starting Deployment of com.sap.ip.bi.broadcasting.kmmimes
Deployment of com.sap.ip.bi.broadcasting.kmmimes finished successfully (Duration 4828 ms)
Starting Deployment of com.sap.ip.bi.portalheartbeat
Deployment of com.sap.ip.bi.portalheartbeat finished successfully (Duration 4594 ms)
Starting Deployment of com.sap.ip.bi.portallogger
Deployment of com.sap.ip.bi.portallogger finished successfully (Duration 4531 ms)
Starting Deployment of com.sap.ip.bi.portalnavigation
Deployment of com.sap.ip.bi.portalnavigation finished successfully (Duration 4515 ms)
Starting Deployment of com.sap.ip.bi.portalrfc
Deployment of com.sap.ip.bi.portalrfc finished successfully (Duration 4516 ms)
Starting Deployment of com.sap.ip.bi.portalrfctest
Deployment of com.sap.ip.bi.portalrfctest finished successfully (Duration 4484 ms)
Starting Deployment of com.sap.ip.bi.biloggingconfig
Aborted: development component 'com.sap.ip.bi.biloggingconfig'/'sap.com'/'SAP AG'/'7.0007.20060316173253.0000', grouped by software component 'BI-IBC'/'sap.com'/'SAP AG'/'1000.7.00.7.0.20060319093500':
Caught exception while checking the login credentials for SAP J2EE Engine. Check whether the SAP J2EE Engine is up and running.
com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot connect to Host: [OFCOMTOLS039] with user name: [J2EE_ADMIN] Check your login information. Exception is: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Cannot authenticate the user.]
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.checkLoginCredentials.DMEXC)
Deployment of com.sap.ip.bi.biloggingconfig finished with Error (Duration 6594 ms)
Starting Deployment of BI-IBC
Aborted: software component 'BI-IBC'/'sap.com'/'SAP AG'/'1000.7.00.7.0.20060319093500':
No further description found.
Deployment of BI-IBC finished with Error (Duration 3968 ms)Hello Mike,
Your issue is described in note 997810:
If deployment fails with the error:
Caught exception while checking the login credentials for SAP J2EE Engine. Check whether the SAP J2EE Engine is up and running.
com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot connect to Host: [sapmef1d] with user name: [Administrator] Check your login information.
Exception is:
com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext.
[Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Cannot create new RemoteLoginContext instance.]
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.checkLoginCredentials.DMEXC)
Either the connection details in Secure Store are incorrect, or the j2ee engine is not running at all. First check the admin/port/<SID>entry in Secure Store and make sure it corresponds to the p4 port on the dispatcher. If the j2ee engine is not running (no jlaunch processes on os level), check the std_<XXX> and dev_<XXX> files in the instance work folder, located on the same level as the j2ee one.
Regards,
Ventsi Tsachev
Technology Development Support (J2EE Engine)
SAP Labs, Palo Alto, Ca (USA) -
SDM deployment error during XI 3.0 installation
(nobody in the PI forum replied, so I'm reposting here)
I need to install a sandbox using this old version. Installation base is 6.40 WebAS plus Java addon SR1. System installs fine, however during final SDM deployment I get a problem during the J2EE engine restart:
errors:
service sld ================= ERROR =================
Cannot start service com.sap.aii.af.cpa.svc; it has hard reference to service sld which is not started.
and around 20 more services which have a dependency on sld
sld does not start because:
/Applications/SLD#sap.com/com.sap.lcr#com.sap.lcr.sagent.BuilderDirector#J2EE_
GUEST#328####e4cd3451819411dec19c001d72bd0666#SAPEngine_Application_Threadimpl:3_0##0#0#Error#1#com.sap.lcr.sagent.BuilderDirector#Plain###Can't access http store#
OR:
SAPEngine_System_Threadimpl:5_32##0#0#Error#1#com.sap.engine.core.service630.container.ServiceRunner#Plain###Service sld error. Nested exception is: com.sap.engine.frame.ServiceException: <--Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='sld_3012', A
rguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key sld_3012
at com.sap.sldserv.SldServerFrame.start(SldServerFrame.java:109)
at com.sap.sldserv.SldServerFrame.start(SldServerFrame.java:78) ...........
further suspicious warnings:
Aug 5, 2009 12:51:17 AM Info: No action: Selected development component 'com.sap.aii.af.ms.svc'/'sap.com'/'SAP AG'/'3.0.0920041027171222.0000' will not be deployed because containing software component 'SAP-XIAFC'/'sap.com'/'SAP AG'/'1000.3.0.9.1.20041028052722' will not be deployed.
and this for around 20 more components from comp.sap.aii*
What went wrong, and, what can I do to fix this? Redeploy sld ? I could not find how.
Java version is latest 1.4.2 x86_64 from IBM (1.4.2_13) for my architecture (x86_64 Linux RHEL5), DB is maxdb 7.6
Any help is appreciated, Thanks.
SanjayCan you please check thet if you have given a central SLD then that SLD is up and running as you are getting the message.
Cannot start service com.sap.aii.af.cpa.svc; it has hard reference to service sld which is not started.
Please check this note it will solve your issue.
Note 994433 - XI AF on J2EE Engine terminates with OutOfMemoryError
you can manually start th services.
Thanks Rishi Abrol -
<h5>Good Morning Gentleman,</h5>
<h5>"When i'm trying to import a transport order to our productive system the import fails in step SDM-deploy with the following error:</h5>
<h5>20120228122646 Info :Starting Step SDM-deploy at 2012-02-28 12:26:46.0143 +0:00
20120228122646 Info :start deployment of archives:http://sapsps.sonaesierra.com:50004
20120228122646 Fatal :caused by Exception:com.sap.cms.tcs.beans.exception.TCSDeployException_Communication: The user 'j2ee_admin' could not be connected to the specified host 'sapsps.sonaesierra.com'and port '50004'.:The user 'j2ee_admin' could not be connected to the specified host 'sapsps.sonaesierra.com'and port '50004'.
com.sap.cms.tcs.beans.exception.TCSDeployException_Communication: The user 'j2ee_admin' could not be connected to the specified host 'sapsps.sonaesierra.com'and port '50004'.
at com.sap.cms.tcs.beans.deployer.DeployConnector.openConnection(DeployConnector.java:160)
at com.sap.cms.tcs.beans.TCSDeployBean.performDirectDeployment(TCSDeployBean.java:194)
at com.sap.cms.tcs.beans.TCSDeployObjectImpl0_0.performDirectDeployment(TCSDeployObjectImpl0_0.java:1342)
at com.sap.cms.tcs.beans.TCSDeploy_Stub.performDirectDeployment(TCSDeploy_Stub.java:1296)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:331)
at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187)
at $Proxy225.performDirectDeployment(Unknown Source)
at com.sap.cms.tcs.core.SDMDeployTask.processImport(SDMDeployTask.java:302)
at com.sap.cms.tcs.core.SDMDeployTask.process(SDMDeployTask.java:366)
at com.sap.cms.tcs.process.ProcessStep.processStep(ProcessStep.java:77)
at com.sap.cms.tcs.process.ProcessStarter.process(ProcessStarter.java:206)
at com.sap.cms.tcs.core.TCSManager.importPropagationRequests(TCSManager.java:447)
at com.sap.cms.pcs.transport.importazione.ImportManager.importazione(ImportManager.java:176)
at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.execImport(ImportQueueHandler.java:500)
at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.startImport(ImportQueueHandler.java:113)
at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:648)
at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:620)
at com.sap.cms.pcs.transport.proxy.LocalCmsTransportProxyLocalObjectImpl0_0.startImport(LocalCmsTransportProxyLocalObjectImpl0_0.java:1640)
at com.sap.cms.ui.wl.Custom1.importQueue(Custom1.java:1637)
at com.sap.cms.ui.wl.wdp.InternalCustom1.importQueue(InternalCustom1.java:2817)
at com.sap.cms.ui.wl.Worklist.onActionImportQueue(Worklist.java:1042)
at com.sap.cms.ui.wl.wdp.InternalWorklist.wdInvokeEventHandler(InternalWorklist.java:2866)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:333)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:741)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:694)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1060)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
20120228122646 Info :Step SDM-deploy ended with result 'fatal error' ,stopping execution at 2012-02-28 12:26:46.0306 +0:00"</h5>
<h5>I'm new to NWDI and related subjects. I've already checked:</h5>
<h5>1. Port 50004 is available in the productive system</h5>
<h5>2. J2EE Visual Administrator in productive is accessible by j2ee_admin</h5>
<h5>3. j2ee_admin isn't locked in productive system</h5>
<h5>What more should i check? What could be the reason behind this error?</h5>
<h5>Thank you.</h5>
<h5>Best Regards,</h5>
<h5>Pedro Gaspar</h5>Good Morning Kumar,
If i tell you what happened you're going to laugh... But i'll tell you anyway.
After watching your post i went to the CMS Landscape Configurator in order to look into the configuration. I noticed that the Selected Tool for deployment in the Productive Runtime system was configured as Deploy Controller (this is a NW 7.01 and as far as i've read before... in this version it's advisable to configure it as you told me in your post - SDM Deploy, thanks for that).
So i tried to change it, but nothing happened, i've tried a second time, but the changes wouldn't take effect and no message was generated. I've spent a few hours trying to understand what was happening... So i told to myself, let me try it with another browser (was using Firefox 3.6.27, changed to IE 9.0.8112) and when trying to change the runtime system configuration a message outputs... "... More than one name server configured in SLD"
Immediately searched and got SAP note 1118009 - SLD name-server configuration error in CMS. After executing note steps i was able to change the runtime system tool for deployment, and i could finish the transport.
The difference a message and the browser version can do in your life
Thanks for your reply, which helped me solve the problem.
Best Regards,
Pedro Gaspar -
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 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
Maybe you are looking for
-
I accidentally clicked "restore" when I meant to "back up" on my iphone 5, is there anyway I can undo that and get back to what I had?
-
Look Up feature is not working properly.
Look Up feature will not work if another word is selected inside the Look Up display of the first word. The only solution was to the problem is to click on the word "Dictionary" (so that you will be using the Dictionary application instead) and then
-
Email hyperlink using %SI_VIEWER_URL% with JAVA SSO
Hi, I am attempting to email a Crystal report via email from within InfoView as link in the message body utilizing the %SI_VIEWER_URL% viewer hyperlink. The recipient receives the link but fails with the following error "An error has occurred: java.l
-
Keep focus in the same window after opening a new window per key-event
I have an application in which user can press on a specific key, and that opens a new window in a JFrame. User might want open a few of such windows in a row by changing the cursor position and pressing the same letter key. But the problem is that wi
-
Is the ADF API 11.1.1.2.0 latest?
Hi, Want to know if the API given @ http://www.oracle.com/technology/documentation/jdev/111110/apirefs.html the latest for ADF 11.1.1.2.0. When I click the links under the section 11.1.1.2.0 the API it opens still shows 11.1.1.1.