Deploying ESS through JSPM

Hi All,
I am deploying the ESS 10 through JSPM and was checking the error log. Found the following,
server.4.log
shows the following
Operation deploy over application sap.com/essinaddr finished successfully on server 101711350#
#1.5#00144FEC6FF000590000007B00005F63000456104F4F7033#1220527956914#/System/Server##com.sap.engine.services.deploy#J2EE_ADMIN#1337##sapdev_D
EV_101711350#Guest#2bda93107a7511ddc7e200144fec6ff0#SAPEngine_Application_Thread[impl:3]_2##0#0#Info#1#com.sap.engine.services.deploy#Plain#
Operation deploy on application sap.com/essinaddr finished in whole cluster for 1047 ms.#
#1.5#00144FEC6FF000520000032400005F63000456104F5D1163#1220527957793#/System/Server##com.sap.engine.services.deploy#J2EE_ADMIN#1338##sapdev_D
EV_101711350#Guest#2d0d1fa07a7511dd994c00144fec6ff0#SAPEngine_Application_Thread[impl:3]_26##0#0#Error#1#com.sap.engine.services.deploy#Java
#deploy_5005#com.sap.engine.services.deploy.DeployResourceBundle#Application is not deployed on cluster element and it is not possib
le to .#3#sap.com/ess~per#Server 0 10_17113#get its status#
#1.5#00144FEC6FF000520000032700005F63000456104F5D2A9F#1220527957813#/System/Server##com.sap.engine.services.deploy#J2EE_ADMIN#1338##sapdev_D
EV_101711350#Guest#2d0d1fa07a7511dd994c00144fec6ff0#SAPEngine_Application_Thread[impl:3]_26##0#0#Error#1#com.sap.engine.services.deploy#Java
#deploy_5030#com.sap.engine.services.deploy.DeployResourceBundle#Clusterwide exception: #1#Cannot get the status of application sap.com/e
ss~per#
#1.5#00144FEC6FF000520000032C00005F63000456104F5DD487#1220527957857#/System/Server##com.sap.engine.services.deploy#J2EE_ADMIN#1338##sapdev_D
EV_101711350#Guest#2d0d1fa07a7511dd994c00144fec6ff0#SAPEngine_Application_Thread[impl:3]_26##0#0#Error#1#com.sap.engine.services.deploy#Java
#deploy_5029#com.sap.engine.services.deploy.DeployResourceBundle#Exception in operation with application .#2#startApp#sap.com/essin
addr#
#1.5#00144FEC6FF000520000032F00005F63000456104F5ECF58#1220527957903#/System/Server##com.sap.engine.services.deploy#J2EE_ADMIN#1338##sapdev_D
EV_101711350#Guest#2d0d1fa07a7511dd994c00144fec6ff0#SAPEngine_Application_Thread[impl:3]_26##0#0#Error#1#com.sap.engine.services.deploy#Java
#deploy_5030#com.sap.engine.services.deploy.DeployResourceBundle#Clusterwide exception: #1#Failed to prepare application ''sap.com/ess~in
~addr'' for startup. Reason=
Clusterwide exception: Failed to start application ''sap.com/essinaddr'': The referenced application ''sap.com/ess~per'' can''t be started
. Check the causing exception for details. Hint: Is the referenced application deployed correctly on the server?#
#1.5#00144FEC6FF000520000033200005F63000456104F5F1D18#1220527957941#/System/Server##com.sap.engine.services.deploy#J2EE_ADMIN#1338##sapdev_D
EV_101711350#Guest#2d0d1fa07a7511dd994c00144fec6ff0#SAPEngine_Application_Thread[impl:3]_26##0#0#Error#1#com.sap.engine.services.deploy#Plai
n###
Operation startApp over application sap.com/essinaddr finished with errors on server 101711350. For more detailed information see traces o
f Deploy Service.#
#1.5#00144FEC6FF000520000033400005F63000456104F5F208B#1220527957942#/System/Server##com.sap.engine.services.deploy#J2EE_ADMIN#1338##sapdev_D
EV_101711350#Guest#2d0d1fa07a7511dd994c00144fec6ff0#SAPEngine_Application_Thread[impl:3]_26##0#0#Error#1#com.sap.engine.services.deploy#Plai
n###
Error occurred on server 101711350 during startApp sap.com/essinaddr : com.sap.engine.services.deploy.container.DeploymentException: Clust
erwide exception: Failed to prepare application ''sap.com/essinaddr'' for startup. Reason=
Clusterwide exception: Failed to start application ''sap.com/essinaddr'': The referenced application ''sap.com/ess~per'' can''t be started
. Check the causing exception for details. Hint: Is the referenced application deployed correctly on the server?
 at com.sap.engine.services.webdynpro.WebDynproContainer.prepareStart(WebDynproContainer.java:1490)
 at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
 at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:171)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:301
 at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:342)
 at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:126)
 at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:245)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4761)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4666)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4639)
 at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1163)
 at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
 at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
 at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListene
r.java:33)
 at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
#1.5#00144FEC6FF000520000033600005F63000456104F5F28F4#1220527957944#/System/Server##com.sap.engine.services.deploy#J2EE_ADMIN#1338##sapdev_D
EV_101711350#Guest#2d0d1fa07a7511dd994c00144fec6ff0#SAPEngine_Application_Thread[impl:3]_26##0#0#Info#1#com.sap.engine.services.deploy#Plain
Operation startApp on application sap.com/essinaddr finished in whole cluster for 160 ms.#
#1.5#00144FEC6FF000520000033700005F63000456104F5F54F8#1220527957955#/System/Server##com.sap.engine.services.deploy#J2EE_ADMIN#1338##sapdev_D
EV_101711350#Guest#2d0d1fa07a7511dd994c00144fec6ff0#SAPEngine_Application_Thread[impl:3]_26##0#0#Error#1#com.sap.engine.services.deploy#Java
#deploy_5030#com.sap.engine.services.deploy.DeployResourceBundle#Clusterwide exception: #1#server ID 101711350:com.sap.engine.services.de
ploy.container.DeploymentException: Clusterwide exception: Failed to prepare application ''sap.com/essinaddr'' for startup. Reason=
Clusterwide exception: Failed to start application ''sap.com/essinaddr'': The referenced application ''sap.com/ess~per'' can''t be started
. Check the causing exception for details. Hint: Is the referenced application deployed correctly on the server?
 at com.sap.engine.services.webdynpro.WebDynproContainer.prepareStart(WebDynproContainer.java:1490)
 at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
 at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:171)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:301
 at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:342)
 at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:126)
 at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:245)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4761)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4666)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4639)
 at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1163)
 at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
 at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
 at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListene
r.java:33)
 at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
#1.5#00144FEC6FF000590000007C00005F63000456104F94BD5A#1220527961455#/System/Server##com.sap.engine.services.deploy#J2EE_ADMIN#1340##sapdev_D
EV_101711350#Guest#2f399c907a7511dd914b00144fec6ff0#SAPEngine_Application_Thread[impl:3]_2##0#0#Info#1#com.sap.engine.services.deploy#Plain#
##Display name of application is not correct [ess/in/addr/cfg]. It should not contain any of the following characters: /
: * ? " < > |. I
t should not end with '.' character. All incorrect occurrences will be replaced with '~'.#
#1.5#00144FEC6FF000590000007D00005F63000456104F94BF7F#1220527961456#/System/Server##com.sap.engine.services.deploy#J2EE_ADMIN#1340##sapdev_D
EV_101711350#Guest#2f399c907a7511dd914b00144fec6ff0#SAPEngine_Application_Thread[impl:3]_2##0#0#Warning#1#com.sap.engine.services.deploy#Pla
in###Warning! Application display name ess/in/addr/cfg was internally changed to essinaddr~cfg.#
#1.5#00144FEC6FF000590000007E00005F63000456104FC0F899#1220527964354#/System/Server##com.sap.engine.core.classload.impl0.LoadContextImpl.regi
sterReferenceInternal(String from, String to)#J2EE_ADMIN#1340##sapdev_DEV_101711350#Guest#2f399c907a7511dd914b00144fec6ff0#SAPEngine_Applica
tion_Thread[impl:3]_2##0#0#Warning#1#com.sap.engine.core.classload.impl0.LoadContextImpl#Java###Cannot find loader sap.com/essinaddr~cfg o
n the system, but will register reference for furture usage.#2#sap.com/essinaddr~cfg#common:service:http;service:servlet_jsp#
#1.5#00144FEC6FF000590000007F00005F63000456104FC19A7E#1220527964396#/System/Server##com.sap.engine.services.deploy#J2EE_ADMIN#1340##sapdev_D
EV_101711350#Guest#2f399c907a7511dd914b00144fec6ff0#SAPEngine_Application_Thread[impl:3]_2##0#0#Info#1#com.sap.engine.services.deploy#Plain#
Operation deploy over application sap.com/essinaddr~cfg finished successfully on server 101711350#
#1.5#00144FEC6FF000590000008000005F63000456104FC19C92#1220527964396#/System/Server##com.sap.engine.services.deploy#J2EE_ADMIN#1340##sapdev_D
EV_101711350#Guest#2f399c907a7511dd914b00144fec6ff0#SAPEngine_Application_Thread[impl:3]_2##0#0#Info#1#com.sap.engine.services.deploy#Plain#
Operation deploy on application sap.com/essinaddr~cfg finished in whole cluster for 2938 ms.#
#1.5#00144FEC6FF000520000033A00005F63000456104FD0016A#1220527965339#/System/Server##com.sap.engine.core.classload.impl0.LoadContextImpl.regi
sterReferenceInternal(String from, String to)#J2EE_ADMIN#1342##sapdev_DEV_101711350#Guest#31838c907a7511ddc7e500144fec6ff0#SAPEngine_Applica
tion_Thread[impl:3]_26##0#0#Warning#1#com.sap.engine.core.classload.impl0.LoadContextImpl#Java###Cannot find loader sap.com/essinaddr~cfg
on the system, but will register reference for furture usage.#2#sap.com/essinaddr~cfg#common:service:http;service:servlet_jsp#
#1.5#00144FEC6FF000520000033B00005F63000456104FD04295#1220527965356#/System/Server##com.sap.engine.services.deploy#J2EE_ADMIN#1342##sapdev_D
EV_101711350#Guest#31838c907a7511ddc7e500144fec6ff0#SAPEngine_Application_Thread[impl:3]_26##0#0#Info#1#com.sap.engine.services.deploy#Plain
Operation startApp over application sap.com/essinaddr~cfg finished successfully on server 101711350#
#1.5#00144FEC6FF000520000033C00005F63000456104FD04480#1220527965357#/System/Server##com.sap.engine.services.deploy#J2EE_ADMIN#1342##sapdev_D
EV_101711350#Guest#31838c907a7511ddc7e500144fec6ff0#SAPEngine_Application_Thread[impl:3]_26##0#0#Info#1#com.sap.engine.services.deploy#Plain
Operation startApp on application sap.com/essinaddr~cfg finished in whole cluster for 24 ms.#
#1.5#00144FEC6FF000590000008100005F63000456105005E58B#1220527968871#/System/Server##com.sap.engine.services.deploy#J2EE_ADMIN#1344##sapdev_D
EV_101711350#Guest#33a0a0307a7511ddbec400144fec6ff0#SAPEngine_Application_Thread[impl:3]_2##0#0#Info#1#com.sap.engine.services.deploy#Plain#
##Display name of application is not correct [ess/in/bank/cfg]. It should not contain any of the following characters: /
: * ? " < > |. I
t should not end with '.' character. All incorrect occurrences will be replaced with '~'.#
#1.5#00144FEC6FF000590000008200005F63000456105005E7B6#1220527968872#/System/Server##com.sap.engine.services.deploy#J2EE_ADMIN#1344##sapdev_D
EV_101711350#Guest#33a0a0307a7511ddbec400144fec6ff0#SAPEngine_Application_Thread[impl:3]_2##0#0#Warning#1#com.sap.engine.services.deploy#Pla
in###Warning! Application display name ess/in/bank/cfg was internally changed to essinbank~cfg.#
#1.5#00144FEC6FF000590000008300005F63000456105159B658#1220527991141#/System/Server##com.sap.engine.core.classload.impl0.LoadContextImpl.regi
sterReferenceInternal(String from, String to)#J2EE_ADMIN#1344##sapdev_DEV_101711350#Guest#33a0a0307a7511ddbec400144fec6ff0#SAPEngine_Applica
tion_Thread[impl:3]_2##0#0#Warning#1#com.sap.engine.core.classload.impl0.LoadContextImpl#Java###Cannot find loader sap.com/essinbank~cfg o
n the system, but will register reference for furture usage.#2#sap.com/essinbank~cfg#common:service:http;service:servlet_jsp#
#1.5#00144FEC6FF000590000008400005F6300045610515A7604#1220527991190#/System/Server##com.sap.engine.services.deploy#J2EE_ADMIN#1344##sapdev_D
EV_101711350#Guest#33a0a0307a7511ddbec400144fec6ff0#SAPEngine_Application_Thread[impl:3]_2##0#0#Info#1#com.sap.engine.services.deploy#Plain#
Operation deploy over application sap.com/essinbank~cfg finished successfully on server 101711350#
#1.5#00144FEC6FF000590000008500005F6300045610515A7815#1220527991191#/System/Server##com.sap.engine.services.deploy#J2EE_ADMIN#1344##sapdev_D
EV_101711350#Guest#33a0a0307a7511ddbec400144fec6ff0#SAPEngine_Application_Thread[impl:3]_2##0#0#Info#1#com.sap.engine.services.deploy#Plain#
Operation deploy on application sap.com/essinbank~cfg finished in whole cluster for 22317 ms.#
#1.5#00144FEC6FF000560000005A00005F6300045610516B08C0#1220527992277#/System/Server##com.sap.engine.core.classload.impl0.LoadContextImpl.regi
sterReferenceInternal(String from, String to)#J2EE_ADMIN#1347##sapdev_DEV_101711350#Guest#417df9007a7511ddbfa500144fec6ff0#SAPEngine_Applica
tion_Thread[impl:3]_16##0#0#Warning#1#com.sap.engine.core.classload.impl0.LoadContextImpl#Java###Cannot find loader sap.com/essinbank~cfg
on the system, but will register reference for furture usage.#2#sap.com/essinbank~cfg#common:service:http;service:servlet_jsp#
#1.5#00144FEC6FF000560000005B00005F6300045610516B4A2B#1220527992293#/System/Server##com.sap.engine.services.deploy#J2EE_ADMIN#1347##sapdev_D
EV_101711350#Guest#417df9007a7511ddbfa500144fec6ff0#SAPEngine_Application_Thread[impl:3]_16##0#0#Info#1#com.sap.engine.services.deploy#Plain
Operation startApp over application sap.com/essinbank~cfg finished successfully on server 101711350#
#1.5#00144FEC6FF000560000005C00005F6300045610516B4C15#1220527992294#/System/Server##com.sap.engine.services.deploy#J2EE_ADMIN#1347##sapdev_D
EV_101711350#Guest#417df9007a7511ddbfa500144fec6ff0#SAPEngine_Application_Thread[impl:3]_16##0#0#Info#1#com.sap.engine.services.deploy#Plain
Can anybody tell me what needs to be done now?

Not answered

Similar Messages

Error while deploying ESS through SDM

Hi,
While deploying ESS through SDM i got following error for one of the files:
Starting Deployment of tc/sl.ut.content.erp.xss
Aborted: development component 'tc/sl.ut.content.erp.xss'/'sap.com'/'MAIN_ERP53PAT_C'/'2433758'/'0', grouped by software component 'SAP_ESS'/'sap.com'/'MAIN_ERP53PAT_C'/'1000.603.0.0.1.20080207103154''/'0':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Error occurred while deploying ear file ./temp/deploy/work/deploying/tc_sl.ut.content.erp.xss.ear. Reason: None of the available containers recognized the components of application sap.com/tc~sl.ut.content.erp.xss; it is not possible to make deploy.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of tc/sl.ut.content.erp.xss finished with Error (Duration 13250 ms)
Can anyone please tell what exactly the issue could be because of which that particular file is not recognized.
Thanks & regards,
Anupreet

Hi,
Its always advisable to use JSPM for the installation. Copy all the installable files in the JSPM temp folder and the instalation will be taken care and you don't have to worry about dependencies.
If you are using SDM make sure that you deploy PCUI_GP component FIRST, then the other components in any order.
Regards
Deb

MDM Business Package deployment - through JSPM

Hi,
I am getting the following error while deploying the MDM Business package through JSPM at the check stage.
com.sap.sdt.jspm.phases.PhaseTypeJSPM
com.sap.sdt.util.diag.JavaException
java.lang.NullPointerException: null
JSPM_MAIN,JSPMPhases,NetWeaver Upgrade,
SAPJup
Java Upgrade
Can anyone let me know what can be the reason .
Best Regards
Sid

Hi,
Try to add more memory to your database server in start up parameter. Like 512 or 1G. Bacause there me be insufficient memory. After this restart your db server.
or
It may be problem with downloaded business package. Try to check the size and compare.
Also try to check this note # 891983
Regards,
Padman

Errror while deploying ESS Business Package.

Hi,
I'am deploying ESS SP11 Business Package and while deploying it in SDM it is giving me an error in the intial stage,when i press Start Deploymet option it is giving the error "None of the available containers recognized the components of application sap.com/tc~sl.ut.content.erp.xss; it is not possible to make deploy."
Please guide me in this issue
Thanks and Regards
Pradeep.B

Hi Mahipal,
I would request you to go for ESS 10 or 11.
Why you required ESS 13. Even I faced the same issue, but then undeployed everything and deployed ESS 10 and BPERP5ESS 10. Let your PCUI be 11 or 12 that does not matter.
Also when I deployed through SDM it took the hell lot of time. So the best option is to go through JSPM.
Copy your .zip file in /usr/sap/trans/EPS/in folder and open JSPM ( /usr/sap/SID/j2ee/JSPM/go.sh) and give your SDM password and then select the first option( support pack).
But ensure that you undeploy the ESS/BPERP5ESS 13 from SDM and then deploy through JSPM.
Everything will be all right.
Take care

Deployed ESS in upgraded EP7.0, but content not found

Hi,
We upgraded our EP6 SP14 system to EP7 SP12. Then, deployed ESS Business Package through JSPM. It deployed with success. However, I am unable to locate the content.
I know from another system that the content should be located in Content Administration -> Portal Content -> Content Provided by SAP -> End User Content -> Employee Self-Service. However, the Employee Self-Service area is not there. Also, none of the ESS roles can be found.
Any ideas? Thanks!
Regards,
Rick

Hi Markus,
I see the following line close to the to the top.
sap.com SAP_ESS 600 SP8 (1000.600.0.8.0.20070320033846) SAP AG MAIN_ERP05VAL_C 20070713083600
Then, I see several lines closer to the bottom. The below list is just a sample. I don't see anything like "BP_ERP5ESS" though.
sap.com ess/ar/addr null (1182885) SAP AG MAIN_ERP05VAL_C 20070713082319 sap.com/SAP_ESS
sap.com ess/ar/addr/cfg null (1182169) SAP AG MAIN_ERP05VAL_C 20070713081004 sap.com/SAP_ESS
sap.com ess/ar/bank null (1183028) SAP AG MAIN_ERP05VAL_C 20070713083422 sap.com/SAP_ESS
sap.com ess/ar/bank/cfg null (1182170) SAP AG MAIN_ERP05VAL_C 20070713081007 sap.com/SAP_ESS
sap.com ess/ar/emergency null (1182888) SAP AG MAIN_ERP05VAL_C 20070713082321 sap.com/SAP_ESS
sap.com ess/ar/emergency/cfg null (1182173) SAP AG MAIN_ERP05VAL_C 20070713081009 sap.com/SAP_ESS
Any ideas?
Thanks for your help!
Rick

Deploy wsp through Power Shell- start stop SP admin service and run execadmsvcjobs command using power shell

Hi,
Can anyone pls point me any link/ src code for deplyoing wsp using power shell. I know I can deploy it through Add-spsolution and install-spsolution, the issue is that, it will give "status - stuck in deploying scheduled..."
and i need to restart the sharepoint services - services.msc --> SP administration and timer services - and then i need to run the exceadmsvcjobs command to deploy / update the wsp successfully in solution store.
i mean, whats the power shell equivalent of these tasks. or anyone has already scripted these.
if i elaborate little bit, would like to know how to automatically Retract, Remove, Add and Deploy SharePoint 2010 WSP Solution Files with PowerShell

ok, i have found the same :
here its : hope this will help someone.
function wait4timer($solutionName)
$solutionName ="TestingWSP.wsp"
$solution = Get-SPSolution | where-object {$_.Name -eq $solutionName}
if ($solution -ne $null)
Write-Host "Waiting to finish soultion timer job" -ForegroundColor Green
while ($solution.JobExists -eq $true )
Write-Host "Please wait...Either a Retraction/Deployment is happening" -ForegroundColor DarkYellow
sleep 5
Write-Host "Finished the solution timer job" -ForegroundColor Green
try
# Get the WebApplicationURL
$MyWebApplicationUrl = "http://srvr:21778/";
# Get the Solution Name
$MywspName = "TestingWSP.wsp"
# Get the Path of the Solution
$MywspFullPath = "D:\myWorkspace\TestingWSP.wsp"
# Try to get the Installed Solutions on the Farm.
$MyInstalledSolution = Get-SPSolution | Where-Object Name -eq $MywspName
# Verify whether the Solution is installed on the Target Web Application
if($MyInstalledSolution -ne $null)
if($MyInstalledSolution.DeployedWebApplications.Count -gt 0)
wait4timer($MywspName)
# Solution is installed in atleast one WebApplication. Hence, uninstall from all the web applications.
# We need to unInstall from all the WebApplicaiton. If not, it will throw error while Removing the solution
Uninstall-SPSolution $MywspName -AllWebApplications:$true -confirm:$false
# Wait till the Timer jobs to Complete
wait4timer($MywspName)
Write-Host "Remove the Solution from the Farm" -ForegroundColor Green
# Remove the Solution from the Farm
Remove-SPSolution $MywspName -Confirm:$false
sleep 5
else
wait4timer($MywspName)
# Solution not deployed on any of the Web Application. Go ahead and Remove the Solution from the Farm
Remove-SPSolution $MywspName -Confirm:$false
sleep 3
wait4timer($MywspName)
# Add Solution to the Farm
Add-SPSolution -LiteralPath "$MywspFullPath"
# Install Solution to the WebApplication
#Install-SPSolution -Identity <SolutionName> -WebApplication <URLName> [-GACDeployment] [-CASPolicies]
install-spsolution -Identity $MywspName -WebApplication $MyWebApplicationUrl -GACDeployment #-FullTrustBinDeployment:$true -GACDeployment:$false -Force:$true
# Let the Timer Jobs get finishes
wait4timer($MywspName)
Write-Host "Successfully Deployed to the WebApplication" -ForegroundColor Green
catch
Write-Host "Exception Occuerd on DeployWSP : " $Error[0].Exception.Message -ForegroundColor Red
ref :
http://www.sharepointpals.com/post/How-to-Deploy-a-SharePoint-2013-Solution-(WSP)-in-the-Farm-using-PowerShell

The error when I deploy ess application with SDM

SOS!!!when I deploy ess application with SDM(ESS05P_1-10002965.sca), It failed.please help me.
The trace file:
#1.5#00145ED221BE00F7000000B90011A07C0004421B32EEBBA8#1198584492898#com.sap.engine.services.webdynpro.WebDynproContainer##com.sap.engine.services.webdynpro.WebDynproContainer#J2EE_ADMIN#15220####0f7fa990b2e211dca62200145ed221be#SAPEngine_Application_Thread[impl:3]_173##0#0#Error#1#/System/UserInterface#Java###Failed to deploy application '''' for deployment state listener ''''.
[EXCEPTION]
#3#sap.com/essauaddr#com.sap.tc.webdynpro.serverimpl.wdc.repository.RepositoryContainerHook#com.sap.tc.webdynpro.repository.RepositoryRuntimeException: Failed to deploy the file '/usr/sap/EP1/DVEBMGS02/j2ee/cluster/server0/./temp/webdynpro/public/sap.com/essauaddr/webdynpro/Applications/com.sap.xss.hr.per.au.address.Per_Address_AU/Per_Address_AU.xml' into the database. Reason: Development Object 'sap.com/ess~au' contains already same repository content. Hint: fully qualified name of the repository VMO must be globally unique.
     at com.sap.tc.webdynpro.repository.deploy.RepositoryUpdateManager.checkVMOsExistInOtherDC(RepositoryUpdateManager.java:504)
     at com.sap.tc.webdynpro.repository.deploy.RepositoryUpdateManager.deployRepositoryContent(RepositoryUpdateManager.java:98)
     at com.sap.tc.webdynpro.serverimpl.wdc.repository.RepositoryContainerHook.onDeploy(RepositoryContainerHook.java:232)
     at com.sap.engine.services.webdynpro.WebDynproContainer.deploy(WebDynproContainer.java:1007)
     at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)
     at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:321)
     at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:307)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3184)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:552)
     at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1555)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
     at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(AccessController.java:215)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
#1.5#00145ED221BE00F7000000BB0011A07C0004421B32EF7CEE#1198584492948#com.sap.engine.services.deploy##com.sap.engine.services.deploy#J2EE_ADMIN#15220####0f7fa990b2e211dca62200145ed221be#SAPEngine_Application_Thread[impl:3]_173##0#0#Error#1#/System/Server#Java#deploy_5029##Exception in operation deploy with application sap.com/essauaddr.#2#deploy#sap.com/essauaddr#
#1.5#00145ED221BE00F7000000BC0011A07C0004421B32EF7F24#1198584492949#com.sap.engine.services.deploy##com.sap.engine.services.deploy#J2EE_ADMIN#15220####0f7fa990b2e211dca62200145ed221be#SAPEngine_Application_Thread[impl:3]_173##0#0#Error#1#/System/Audit#Java###Exception #1#com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception in operation deploy with application sap.com/essauaddr.
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.rollbackPart(ApplicationTransaction.java:394)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:294)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3184)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:552)
     at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1555)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
     at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(AccessController.java:215)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Cannot deploy application sap.com/essauaddr.
     at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:330)
     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)
     ... 13 more
Caused by: com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application sap.com/essauaddr. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?
     at com.sap.engine.services.webdynpro.WebDynproContainer.deploy(WebDynproContainer.java:1016)
     at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)
     at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:321)
     ... 15 more

Check these below links
https://forums.sdn.sap.com/click.jspa?searchID=7622331&messageID=4611860
https://forums.sdn.sap.com/click.jspa?searchID=7622331&messageID=4562067
https://forums.sdn.sap.com/click.jspa?searchID=7622331&messageID=4258751
https://forums.sdn.sap.com/click.jspa?searchID=7622331&messageID=4474525
https://forums.sdn.sap.com/click.jspa?searchID=7622331&messageID=4543091
https://forums.sdn.sap.com/click.jspa?searchID=7622331&messageID=4368694
reward points if helpful

How to edit deployment plan through Administration Console in weblogic 9.0?

hi, 
I need to edit the deployment plan through console. But i'm not able to do so.Everytime i upload an ear file and tired to edit the environment variables or deployment plan through console it gives the message
"This module is defined with DTD based descriptors and cannot be edited using the console. " 
I have been manually editing the deployment plan file so far. 
In earlier versions of weblogic , there was an option to edit the environmental variables. Does weblogic 9.0 support the same? 
I'm not able to find a solution soo far. 
Please guide me. 
Thanks 
Smita

Hi.
I'm experiencing the same problem, using Weblogic 9.1.
I have an ear file that contains a war file.
Previously, the files were in servlet api 2.3 format (with a DTD). I used the DDConverter tool to update the files, and now I can use the console to change parameters for the web application, but I still can't change paramters for the main application: "This module is defined with DTD based descriptors and cannot be edited using the console.".
Here is the content of the META-INF/application.xml contained in mey ear file:
<?xml version='1.0' encoding='utf-8'?>
<application xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="1.4">
<description>Application xxx</description>
<display-name>xxx</display-name>
<module>
<web>
<web-uri>xxx.war</web-uri>
<context-root>xxx</context-root>
</web>
</module>
</application>
Thank you very much for your help.

Missing JCO files after deploying ESS

Hi
I deployed ESS BP.
I should get the below JCO destinations
u2022     SAP_R3_HumanResources
u2022     SAP_R3_HumanResources_MetaData
u2022     SAP_R3_Financials
u2022     SAP_R3_Financials_MetaData
u2022     SAP_R3_SelfServiceGenerics
u2022     SAP_R3_SelfServiceGenerics_MetaData
u2022     SAP_R3_Travel
u2022     SAP_R3_Travel_MetaData
But I missied the below JCO's.
I got only few.....
u2022     SAP_R3_Financials
u2022     SAP_R3_Financials_MetaData
u2022     SAP_R3_Travel
u2022     SAP_R3_Travel_MetaData
How to get back the above JCO's to configure completely my ESS
Thanks in advance
Renu

Hi Renu,
Check this link for creating JCO destinations, and create the rest of the jco's
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/526bd490-0201-0010-038e-d3ff7eb1d16e
http://help.sap.com/erp2005_ehp_03/helpdata/EN/8c/cb3042366c0521e10000000a155106/frameset.htm
Regards,
Tilak.
Edited by: Tilak on Aug 11, 2008 6:54 AM

Deploying Reader through Group Policy

Hi,
I have applied for and been granted a deployment license, and am trying to follow the instructions to deploy reader through group policy to computers on my network.
The document adobe gives you says to put the computer name under security filtering in the OU GP that was created. I have done this but it's clear the policy isn't getting applied.
When I run group policy result, it's not even showing so I must have something wrong. The document that adobe gives has several of the pictures out of place and is covering some text (at least when I display it - and yes I am using most current version of reader).
Any ideas?
Thanks,
Allen

Unless I'm misunderstanding your last reply, the GPO is working as intended, when you change it back.
GPO = Applied to one specific OU
Security Filtering = 1 specific PC
Active Directory OU for intended GPO contains = 0 computers
The PC you're applying the security filtering to must exist in the Active Directory OU you created for the GPO.
E.G. I create a GPO called acc_sw for my Accounting dept called accounting. 3 PCs in accounting are called:
Ed_PC
Karen_PC
Thomas_PC
In the security filtering for the GPO I created, I have:
Ed_PC
Karen_PC
Thomas_PC
Now, in Active Directory Users & Computers, in the accounting OU I have 0 computers.
The end result is no acc_sw being processed for:
Ed_PC
Karen_PC
Thomas_PC
They must exist in the target OU, or a suboordinate OU of the target OU, for the GPO to work.

Deploying office through group policy

Hi people,
English is not my mother language so i'll hope you'll understand me.
I have a school project. Deploying office through group policy worked. But now my teacher has given me a command to give all OU's a different OFFICE packet when they logged in. So.. it will change the current installation when a different user from a different
OU logged in. I'm out of options. Please can anybody help me:(:(

No you don't misunderstand :p My teacher first did it wit Office 2003 and know i must do it in office2010.. and i also thought it was a stupid idea.. But who am i... i have not much knowledge in IT.. i'm still learning.
But i have 2 options
To confince him that this is not a good idea... (and i dont know with wich argument)
or find a way to do this...
Hmm, so, I think that kind of crazy was possible with very old versions of Office, which could be "advertised" via GPO to achieve per-user scenarios, but Office2007 and later versions, don't provide such different per-user options as part of setup.
Office2007 and later, uses the MSPfile etc for customization, and that is per-machine (common to all users of that machine).
You might be able to achieve something similar, by using AppLocker (e.g. AppLocker rules which deny excel.exe to be executed by GRP_Students).
But this doesn't address the matter nicely, because the Students can see the Excel shortcut/icon/program, but are forbidden to execute it.
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

What share and NTFS permissions must I give users to deploy software through SCCM?

What share and NTFS permissions must I give users to deploy software through SCCM? I have one folder with all of the applications and would like to know.
Thanks
James A+, Network+, MCP

That still doesn't help. We're not prying, we're trying to help but we honestly have no idea what you are talking about. The more and better details that you can provide, the better we can help.
"Because I want to know" adds no value and does not help us help you. We need technical details -- we can't see what you are seeing and we can't read your mind.
And, you didn't really answer any of my questions.
I'll take another wild-guess though: If you are talking about the source file locations referenced within packages and applications, users do not access those. The computer account for the systems hosting the SMS Provider needs read access to the location(s)
specified. Yes, this means both NTFS and share permissions assuming they are being referenced via a UNC.
Finally, there is no service account. If you've changed the account that the SMS_EXECUTIVE is running under, you're are now in a completely unsupported state that will have many issues. If instead you are talking about the Network Access Account, that is
*not* a service account and is *not* used to access content source files.
Once again though, we're simply guessing because no one has any idea what you're doing. Please provide actual, technical details.
Jason | http://blog.configmgrftw.com | @jasonsandys

Deploy capex through application library

Hi,
Can anyone experience the problem when deploying capex through application library 9.3.1?
The job progress kepts at 9% with detail:
"initialing product action...
product response:200..
waiting for status udpates...".
BTW, I
1) have already performed "validate" check for capex app. There is no error.
2) no error is captured in the shared service
3) SharedServices_Metadata.log shows
2008-02-11 02:59:17,324 [http-58080-Processor15] ERROR com.hyperion.eie.modelmgmt.stateless.action.GetProjectForAppAction - The resource '/files/Projects/capexp2.HP' was not found.
2008-02-11 02:59:17,324 [http-58080-Processor15] ERROR com.hyperion.eie.modelmgmt.stateless.action.GetProjectForAppAction - com.hyperion.eie.common.cms.ResourceNotFoundException: error.resourceNotFound
4) SharedServices_security.log shows several lines like this:
2008-02-11 03:00:53,252 [http-58080-Processor7] WARN com.hyperion.css.spi.impl.nv.XMLRoleRegDocumentModel.processRoleElement(Unknown Source) - The Product Version 'HP-9.3.1' in the Registration file does not match the application version '9.3.1'
Regards,
Kenneth

Hi Kenneth,
Were you able to deploy the CAPEX plan? We are also stuck in deploying Workforce and CAPEX plan? If you could successfully, please share your inputs on the forum or through direct mail [email protected]
rgds
PM

Error in Applying Java support packages through JSPM

Hi All,
While Applying support packages, Package CAF 7.00 SP 13 is through an error
help required.
 For detailed information see the log file of the Deploy Service.
07/12/05 21:55:26 - ***********************************************************
Dec 5, 2007 9:55:26 PM Info: End of log messages of the target system.
Dec 5, 2007 9:55:26 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Dec 5, 2007 9:55:26 PM Error: Aborted: development component 'caf/UI/ptn/common'/'sap.com'/'MAIN_APL70VAL_C'/'1497914'/'0', grouped by software component 'CAF'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.13.0.20070809092315''/'0':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot deploy application sap.com/cafUIptn~common..
Reason: Clusterwide exception: Failed to deploy application sap.com/cafUIptn~common. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?; nested exception is:
 com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application sap.com/cafUIptn~common. 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)
Dec 5, 2007 9:55:26 PM Info: Starting to save the repository
Dec 5, 2007 9:55:28 PM Info: Finished saving the repository
Dec 5, 2007 9:55:28 PM Info: Starting: Update: Selected software component 'CAF'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.13.0.20070809092315''/'0' updates currently deployed software component 'CAF'/'sap.com'/'MAIN_APL70P06_C'/'1000.7.00.6.0.20060221161956''/'0'.
Dec 5, 2007 9:55:28 PM Error: Aborted: software component 'CAF'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.13.0.20070809092315''/'0':
Failed deployment of SDAs:
development component 'caf/UI/ptn/common'/'sap.com'/'MAIN_APL70VAL_C'/'1497914'/'0' : aborted
Please, look at error logs above for more information!
Dec 5, 2007 9:55:28 PM Info: Starting to save the repository
Dec 5, 2007 9:55:30 PM Info: Finished saving the repository
Dec 5, 2007 9:55:30 PM Info: Starting: Update: Selected software component 'LM-TOOLS'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.13.0.20070906104634''/'0' updates currently deployed software component 'LM-TOOLS'/'sap.com'/'MAIN_APL70P06_C'/'1000.7.00.6.1.20060302145618''/'0'.
Dec 5, 2007 9:55:30 PM Error: Aborted: software component 'LM-TOOLS'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.13.0.20070906104634''/'0':
No further description found.
Dec 5, 2007 9:55:30 PM Info: Starting to save the repository
Dec 5, 2007 9:55:32 PM Info: Finished saving the repository
Dec 5, 2007 9:55:32 PM Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
Dec 5, 2007 9:55:32 PM Error: -
At least one of the Deployments failed -
Regards,
Prashant.

Hello Prashant.
Check this supporting SAP note 1010640. It will solve your problem.
This is typical problem when you upgrade from < SP8 to higher version.
You need to Undeploy the CAF components from the system using SDM first and then reply the patches from JSPM.
It should go with out errors.
Let us know if this worked.
*Reward points for helpful answer.
Regards,
Prashant P.

Error while uploading ESS through SDM.

Hi all,
We are on EP7.0 SP13 .I am deploying the ESS business package through SDM.I deployed the PCUI_GP 600 SP06 through SDM.It went perfectly.Now I am deploying the
ESS 600 SP06.It is aborted in the middle by throwing an error like this.
starting Deployment of ess/au/addr
Aborted: development component 'ess/au/addr'/'sap.com'/'MAIN_ERP05VAL_C'/'788071'/'0', grouped by software component 'SAP_ESS'/'sap.com'/'MAIN_ERP05VAL_C'/'1000.600.0.6.0.20060920131656''/'0':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot deploy application sap.com/essauaddr.. Reason: Clusterwide exception: Failed to deploy application sap.com/essauaddr. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?; nested exception is: com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application sap.com/essauaddr. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of ess/au/addr finished with Error (Duration 3266 ms)
Starting Deployment of SAP_ESS
Aborted: software component 'SAP_ESS'/'sap.com'/'MAIN_ERP05VAL_C'/'1000.600.0.6.0.20060920131656''/'0':
Failed deployment of SDAs:
development component 'ess/au/addr'/'sap.com'/'MAIN_ERP05VAL_C'/'788071'/'0' : aborted
Please, look at error logs above for more information!
Deployment of SAP_ESS finished with Error (Duration 2375 ms).
Any clues please...
Thanx and Regards,
Rajesh.A

Hi,
please
- open configtool
- File > Config Tool Menu
- Webdynpro > sap.com > tcwddispwda > Propertysheet Default
There please change DuplicateNameCheckEnabled to false
first try after change, if still got problem,then restart cluster and then re-try

Deploying ESS through JSPM

Similar Messages

Maybe you are looking for