Error 300 in deployment
hi, excuseme my english isn´t very good, i expect could understand me.....
well,
I have a applications in jdeveloper, and my aplication server is in weblogic...
well
i have one pc with windows Vista Bussines Edition with Service Pack 1
and the other is a Laltop with Windows Vista Home Premium Edition Service Pack 1
in the pc (with Bussines Edition ) when i try do deploy to the aplication it´s says the next error
---- Deployment started. ---- 7/01/2009 07:22:56 PM
Target platform is WebLogic Server 9.x (WebLogic).
Checking weblogic.xml for completeness...
Wrote WAR file to C:\Users\Dirección General\Desktop\prueba\ViewController\deploy\warPrueba.war
Checking weblogic-ejb-jar.xml for completeness...
Wrote EJB JAR file to C:\Users\Dirección General\Desktop\prueba\Model\deploy\ejbPrueba.jar
Generating WebLogic EJB container classes...
C:\jdevstudio10133wJDK\jdk\jre\bin\javaw.exe -classpath C:\bea\wlserver_10.3\server\lib\weblogic.jar;C:\jdevstudio10133wJDK\jdk\jre\lib\rt.jar;C:\jdevstudio10133wJDK\jdk\jre\lib\i18n.jar;C:\jdevstudio10133wJDK\jdk\jre\lib\sunrsasign.jar;C:\jdevstudio10133wJDK\jdk\jre\lib\jsse.jar;C:\jdevstudio10133wJDK\jdk\jre\lib\jce.jar;C:\jdevstudio10133wJDK\jdk\jre\lib\charsets.jar;C:\jdevstudio10133wJDK\jdk\jre\classes;C:\jdevstudio10133wJDK\j2ee\home\lib\ejb30.jar;C:\jdevstudio10133wJDK\toplink\jlib\toplink-essentials.jar;C:\jdevstudio10133wJDK\j2ee\home\lib\activation.jar;C:\jdevstudio10133wJDK\j2ee\home\lib\ejb.jar;C:\jdevstudio10133wJDK\j2ee\home\lib\jms.jar;C:\jdevstudio10133wJDK\j2ee\home\lib\jta.jar;C:\jdevstudio10133wJDK\j2ee\home\lib\mail.jar;C:\jdevstudio10133wJDK\j2ee\home\lib\servlet.jar;C:\jdevstudio10133wJDK\BC4J\lib\adfshare.jar;C:\jdevstudio10133wJDK\BC4J\lib\adfm.jar;C:\jdevstudio10133wJDK\BC4J\lib\collections.jar;C:\jdevstudio10133wJDK\BC4J\jlib\adfui.jar;C:\jdevstudio10133wJDK\BC4J\lib\adfbinding.jar;C:\jdevstudio10133wJDK\BC4J\jlib\adfmtl.jar weblogic.appc -nowarn -compiler C:\jdevstudio10133wJDK\jdev\bin\ojc.exe "C:\Users\Dirección General\Desktop\prueba\Model\deploy\ejbPrueba.jar"
C:\Users\DIRECC~1\AppData\Local\Temp\appcgen_1231356178263_ejbPrueba.jar\mmp\usa\ejb\PublicPruebaFacade_ba20y0_PublicPruebaFacadeLocalImpl.java:17: error #300: PublicPruebaFacadeLocal not found in class mmp.usa.ejb.PublicPruebaFacade_ba20y0_PublicPruebaFacadeLocalImpl
implements mmp.usa.ejb.PublicPruebaFacadeLocal, weblogic.utils.PlatformConstants,
^
C:\Users\DIRECC~1\AppData\Local\Temp\appcgen_1231356178263_ejbPrueba.jar\mmp\usa\ejb\PublicPruebaFacade_ba20y0_PublicPruebaFacadeLocalImpl.java:191: error #300: SuCatCol not found in class mmp.usa.ejb.PublicPruebaFacade_ba20y0_PublicPruebaFacadeLocalImpl
public java.util.List<mmp.usa.ejb.SuCatCol> querySuCatColFindAll(java.lang.Integer arg0)
^
C:\Users\DIRECC~1\AppData\Local\Temp\appcgen_1231356178263_ejbPrueba.jar\mmp\usa\ejb\PublicPruebaFacade_ba20y0_Impl.java:17: error #454: class mmp.usa.ejb.PublicPruebaFacade_ba20y0_Impl should be declared abstract; it does not define method persistEntity(java.lang.Object) of interface mmp.usa.ejb.PublicPruebaFacade_ba20y0_Intf
public final class PublicPruebaFacade_ba20y0_Impl
^
C:\Users\DIRECC~1\AppData\Local\Temp\appcgen_1231356178263_ejbPrueba.jar\mmp\usa\ejb\PublicPruebaFacade_ba20y0_Impl.java:17: error #454: class mmp.usa.ejb.PublicPruebaFacade_ba20y0_Impl should be declared abstract; it does not define method mergeEntity(java.lang.Object) of interface mmp.usa.ejb.PublicPruebaFacade_ba20y0_Intf
public final class PublicPruebaFacade_ba20y0_Impl
^
C:\Users\DIRECC~1\AppData\Local\Temp\appcgen_1231356178263_ejbPrueba.jar\mmp\usa\ejb\PublicPruebaFacade_ba20y0_Impl.java:18: error #300: PublicPruebaFacadeBean not found in class mmp.usa.ejb.PublicPruebaFacade_ba20y0_Impl
extends PublicPruebaFacadeBean
^
C:\Users\DIRECC~1\AppData\Local\Temp\appcgen_1231356178263_ejbPrueba.jar\mmp\usa\ejb\PublicPruebaFacade_ba20y0_PublicPruebaFacadeImpl.java:21: error #300: PublicPruebaFacade not found in class mmp.usa.ejb.PublicPruebaFacade_ba20y0_PublicPruebaFacadeImpl
private final Class bIClass = mmp.usa.ejb.PublicPruebaFacade.class;
^
Exec failed .. exiting
**** weblogic.ejbc returned with a non-zero exit status:
Elapsed time for deployment: 9 seconds
#### Deployment incomplete. #### 7/01/2009 07:23:06 PM
but when i do deployment in the lapTop (with Windows Vista Home Premium), is succesfull, and all is fine.....
then, i don't know what is the problem, i feel that when i do deployment it´s don't create some files or some like that
well i expect you can help me, thatk you and see you later.... bye bye
Hi Dhinesh,
Technically we cannot deploy the app on any site. It has to be a site created from developer site template..Here are some useful information for you.
http://blogs.msdn.com/b/officeapps/archive/2013/12/10/enable-app-sideloading-in-your-non-developer-site-collection.aspx
https://curah.microsoft.com/248050/side-loading-of-apps-is-not-enabled-on-this-site-error-while-installing-app-in-sharepoint-2013
Regards,
Partha
Regards, Partha Avepoint Please mark the response as "Answer" if it answers your response If this response takes you closer to your solution mark it as a "helpful post"
Similar Messages
-
Hi,
I am deplyoing a solution which has custom web parts- vwp- appln pages, event receivers.
It was working fine till last week. I was able to deploy the solution and able to see the web parts and func. was working.
But now from the last 2 days onwards, when I tried to depoy this soution, I am getting the error
"Error occurred in deployment step 'Add Solution': A timeout has occurred while invoking commands in SharePoint host process "
may i know why am getting this error.
note: my dev machine- Win Srvr 2012 - VS 2012- SP 2013 - SP D 2013 was having soem issues with the space in C drive.
once i have done the index reset few months back and i started getting space in C:\ Drive is 0 bytes.
so what my infra. team has done is , increased the space in drive to 150 GB[ it was a VM ].
help is appreciated !What is current disk space on your drives
Delete ULS logs and other log files from server id not needed
could be related to ChannelOperationTimeout
http://msdn.microsoft.com/en-us/library/ee471440(v=vs.100).aspx
Also, don't forget to restart Visual Studio
Goto the following regustry key: HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\10.0\SharePointTools
Add the following as a DWORD (wont be there by default)
ChannelOperationTimeout
REG_DWORD that specifies the time, in seconds, that Visual Studio waits for a SharePoint command to execute. If the command does not execute in time, a SharePointConnectionException is thrown.
The default is 120 seconds.
http://social.technet.microsoft.com/wiki/contents/articles/21052.como-resolver-o-erro-error-occurred-in-deployment-step-activate-features-a-timeout-has-occurred-while-invoking-commands-in-sharepoint-host-process-pt-br.aspx
If this helped you resolve your issue, please mark it Answered -
Error 1 Error occurred in deployment step 'Activate Features': A timeout has occurred while invoking commands in SharePoint host process.
0 0 myProjectAssetsLists
am getting the above error when i deploy my farm solution which is actually a "farm solution import package" template.
i am deploying this to a new site collection and once its features are activated this will provision few doc libs and splists in the targeted site.
any help is appreciated.try below link:
http://msdn.microsoft.com/en-us/library/ee471440.aspx
http://sujeetrec.blogspot.in/2013/12/sharepoint-2010-deployment-timing-out.html
Increase the timeout that Visual Studio waits for SharePoint to deploy a feature:
Create: [HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\10.0\SharePointTools] ChannelOperationTimeout DWORD
The value is a timeout in seconds. The default is 120 (2 minutes).
Full details on this switch and others are here:
http://msdn.microsoft.com/en-us/library/ee471440.aspx -
Hi I am getting the error
Error occurred in deployment step 'Add Solution': A feature with ID 10495515-2482-41fd-98eb-3c87f739f54b has already been installed in this farm. Use the force attribute to explicitly re-install the feature.
when trying to deploy web parts
question 1 - how do i use the force attribute when deploying from visual studio
question 2 - am i deplying it to the right place, if i deply it to the
url:port that points to my central admin tool it deploys but i cant seem to see it in any of my webs in my site collection, if i deploy it to the
url:port that points to my site collection I get this error.
im new to all this by the way :)
thanks in advanceIf you are deploying from Visual Studio then please follow this post:
http://sharepointfordeveloper.blogspot.com/2014/03/solved-visual-studio-issue-error.html
Open the visual Studio and navigate to the feature XML file and add the bellow attribute.
AlwaysForceInstall="TRUE"
The <FeatureName>.Template.Xml output would be some think link this.
<?xml
version="1.0"
encoding="utf-8"
?><Feature
xmlns="http://schemas.microsoft.com/sharepoint/"
AlwaysForceInstall="TRUE"></Feature> -
Installed SP 2013 Foundation in my Hyper-V machine
Created and done all the steps mentioned here http://blogs.msdn.com/b/shariq/archive/2013/05/07/how-to-set-up-high-trust-apps-for-sharepoint-2013-amp-troubleshooting-tips.aspx && http://msdn.microsoft.com/en-us/library/office/fp179901%28v=office.15%29.aspx
for self signed certificate
copied those two certificates in my local machine(base machine) D drive
(D:\Cert)
Both VM and base machine are in same domain
Installed VS 2013 in my base machine and create a Provided hosted app with the copied certificates, (For creation i followed the above mentioned URL)
Just created and hit F5 to run in my base machine, but getting this error
Error occurred in deployment step 'Uninstall app for SharePoint': The remote server returned an error: (502) Bad Gateway.
Please help me to resolve this issue, trying to figure out from last 2 days
Thanks in Advance
ArunHi Harminder,
This happens because an app has already been deployed and you are deploying it again using the same version.
Resolution:
Open the AppManifest.xml file and change the version.
Vivek Jagga - MCTS SharePoint
SharePointExcellence -
Error during application deployment in cluster
Hi All,
I am seeing a weird error when I deploy my application in 2 node cluster. Few months back, the same cluster worked perfectly alright. The error relates to lookup at localhost:7001 which is no where in the configuration as admin server url is http://srai-xp:7001. I created a new domain and see the same problem.
Any pointers are greatly appreciated.
Thanks
--shashi
Here is the error log:
D:\apps\bea\user_projects\domains\nclusterdomain>startManagedWebLogic.cmd NodeSR http://srai-xp:7001
D:\apps\bea\user_projects\domains\nclusterdomain>echo off
CLASSPATH=CR190380_81sp3.jar;D:\apps\bea\user_projects\domains\nclusterdomain\lib\jax-qname.jar;;D:\apps\bea\user_projects\domains\nclusterdomain\li
jsafe.jar;;D:\apps\bea\user_projects\domains\nclusterdomain\lib\jsafejce.jar;;D:\apps\bea\user_projects\domains\nclusterdomain\lib\asn1.jar;;C:\j2sd
.4.2_04\lib\tools.jar;d:\apps\bea\WEBLOG~1\server\lib\weblogic_sp.jar;d:\apps\bea\WEBLOG~1\server\lib\weblogic.jar;d:\apps\bea\WEBLOG~1\common\eval\
intbase\lib\pbserver44.jar;d:\apps\bea\WEBLOG~1\common\eval\pointbase\lib\pbclient44.jar;C:\j2sdk1.4.2_04\jre\lib\rt.jar;d:\apps\bea\WEBLOG~1\server\lib\webservices.jar;D:\apps\bea\user_projects\domains\nclusterdomain\lib;;D:\apps\bea\user_projects\domains\nclusterdomain\lib\jcsi_base.jar;;D:\apps\bea\user_projects\domains\nclusterdomain\lib\jcsi_jce.jar;;D:\apps\bea\user_projects\domains\nclusterdomain\lib\jcsi_krb.jar;;D:\apps\bea\user_projects\domains\nclusterdomain\lib\jcsi_krb_jaas.jar;;D:\apps\bea\user_projects\domains\nclusterdomain\lib\jcsi_license.jar;;D:\apps\bea\user_projects\domains\nclusterdomain\lib\jcsi_provider.jar;D:\apps\bea\user_projects\domains\nclusterdomain\lib\mysql-connector-java.jar;;D:\apps\bea\user_projects\domains\nclusterdomain\lib\nls_charset12.jar;;D:\apps\bea\user_projects\domains\nclusterdomain\lib\ojdbc14.jar;
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http://[hostname]:[port]/console *
<Mar 17, 2005 4:19:27 PM PST> <Info> <Security> <BEA-090065> <Getting boot identity from user.>
Enter username to boot WebLogic server:weblogic
Enter password to boot WebLogic server:
<Mar 17, 2005 4:21:22 PM PST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Server VM Version 1.4.2_04-b05 fr
Sun Microsystems Inc.>
<Mar 17, 2005 4:21:22 PM PST> <Info> <Management> <BEA-141140> <The managed server is going to contact the admin server at http://srai-xp:7001 to ch
k if there exists a running admin server at this URL.>
<Mar 17, 2005 4:21:22 PM PST> <Info> <Configuration Management> <BEA-150017> <This server is being started as a dependent managed server.>
<Mar 17, 2005 4:21:22 PM PST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973
WebLogic XMLX Module 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973 >
<Mar 17, 2005 4:21:22 PM PST> <Info> <Configuration Management> <BEA-150015> <Connecting to the administration server http://srai-xp:7001 to retriev
the initial configuration.>
<Mar 17, 2005 4:21:25 PM PST> <Notice> <Log Management> <BEA-170019> <The server log file D:\apps\bea\user_projects\domains\nclusterdomain\NodeSR\No
SR.log is opened. All server side log events will be written to this file.>
<Mar 17, 2005 4:21:30 PM PST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Mar 17, 2005 4:21:30 PM PST> <Notice> <WebLogicServer> <BEA-000328> <Starting WebLogic Managed Server "NodeSR" for domain "nclusterdomain">
<Mar 17, 2005 4:21:35 PM PST> <Notice> <Cluster> <BEA-000138> <Listening for announcements from cluster XCluster on 237.0.0.101:8050.>
<Mar 17, 2005 4:21:35 PM PST> <Notice> <Cluster> <BEA-000133> <Waiting to synchronize with other running members of XCluster.>
<Mar 17, 2005 4:22:08 PM PST> <Notice> <WebLogicServer> <BEA-000355> <Thread "ListenThread.Default" listening on port 8001, ip address 153.32.158.12
<Mar 17, 2005 4:22:08 PM PST> <Notice> <Cluster> <BEA-000102> <Joining cluster XCluster on 237.0.0.101:8050>
<Mar 17, 2005 4:22:08 PM PST> <Notice> <WebLogicServer> <BEA-000330> <Started WebLogic Managed Server "NodeSR" for domain "nclusterdomain" running i
Production Mode>
<Mar 17, 2005 4:22:08 PM PST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
<Mar 17, 2005 4:23:33 PM PST> <Warning> <HTTP> <BEA-101247> <Application: 'C:\Temp\edc-server.ear', Module: 'help_de': Public ID references the old
rsion of the Servlet DTD. You must change the public ID in web.xml file to "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN".>
<Mar 17, 2005 4:23:33 PM PST> <Warning> <HTTP> <BEA-101247> <Application: 'C:\Temp\edc-server.ear', Module: 'help_fr': Public ID references the old
rsion of the Servlet DTD. You must change the public ID in web.xml file to "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN".>
<Mar 17, 2005 4:23:33 PM PST> <Warning> <HTTP> <BEA-101247> <Application: 'C:\Temp\edc-server.ear', Module: 'help_ja': Public ID references the old
rsion of the Servlet DTD. You must change the public ID in web.xml file to "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN".>
<Mar 17, 2005 4:23:35 PM PST> <Warning> <J2EE> <BEA-160081> <The JMS connection factory resource EDCEventQCF declared in the EJB "EventManagerBean"
part of application "edc-server" does not support XA. It cannot be used inside a transaction context.>
javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested exception is:
java.net.ConnectException: Connection refused: connect; No available router to destination]
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:47)
at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:618)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:306)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:239)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:135)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:175)
at weblogic.deployment.EnvironmentBuilder.findObject(EnvironmentBuilder.java:768)
at weblogic.deployment.EnvironmentBuilder.findObjectOrCreateLinkRef(EnvironmentBuilder.java:759)
at weblogic.deployment.EnvironmentBuilder.addUserTransaction(EnvironmentBuilder.java:555)
at weblogic.deployment.EnvironmentBuilder.<init>(EnvironmentBuilder.java:94)
at weblogic.servlet.internal.CompEnv.<init>(CompEnv.java:80)
at weblogic.servlet.internal.WebAppServletContext.init(WebAppServletContext.java:565)
at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:489)
at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:634)
at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:632)
at weblogic.j2ee.J2EEApplicationContainer.prepareWebModule(J2EEApplicationContainer.java:3150)
at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1558)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1208)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1051)
at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2444)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2394)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2310)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:866)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:594)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:508)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
Caused by: java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested exception is:
java.net.ConnectException: Connection refused: connect; No available router to destination
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:199)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:125)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:296)
... 28 more
--------------- nested within: ------------------
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Unable to create InitialContext ] - with nested exception:
[javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested exception is
java.net.ConnectException: Connection refused: connect; No available router to destination]]
at weblogic.deployment.EnvironmentBuilder.findObject(EnvironmentBuilder.java:770)
at weblogic.deployment.EnvironmentBuilder.findObjectOrCreateLinkRef(EnvironmentBuilder.java:759)
at weblogic.deployment.EnvironmentBuilder.addUserTransaction(EnvironmentBuilder.java:555)
at weblogic.deployment.EnvironmentBuilder.<init>(EnvironmentBuilder.java:94)
at weblogic.servlet.internal.CompEnv.<init>(CompEnv.java:80)
at weblogic.servlet.internal.WebAppServletContext.init(WebAppServletContext.java:565)
at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:489)
at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:634)
at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:632)
at weblogic.j2ee.J2EEApplicationContainer.prepareWebModule(J2EEApplicationContainer.java:3150)
at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1558)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1208)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1051)
at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2444)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2394)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2310)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:866)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:594)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:508)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
<Mar 17, 2005 4:23:40 PM PST> <Error> <Deployer> <BEA-149201> <Failed to complete the deployment task with ID 0 for the application edc-server.
java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested exception is:
java.net.ConnectException: Connection refused: connect; No available router to destination
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:199)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:125)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:296)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:239)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:135)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:175)
at weblogic.deployment.EnvironmentBuilder.findObject(EnvironmentBuilder.java:768)
at weblogic.deployment.EnvironmentBuilder.findObjectOrCreateLinkRef(EnvironmentBuilder.java:759)
at weblogic.deployment.EnvironmentBuilder.addUserTransaction(EnvironmentBuilder.java:555)
at weblogic.deployment.EnvironmentBuilder.<init>(EnvironmentBuilder.java:94)
at weblogic.servlet.internal.CompEnv.<init>(CompEnv.java:80)
at weblogic.servlet.internal.WebAppServletContext.init(WebAppServletContext.java:565)
at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:489)
at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:634)
at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:632)
at weblogic.j2ee.J2EEApplicationContainer.prepareWebModule(J2EEApplicationContainer.java:3150)
at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1558)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1208)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1051)
at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2444)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2394)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2310)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:866)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:594)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:508)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
--------------- nested within: ------------------
weblogic.management.ManagementException: - with nested exception:
[java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested exception is:
java.net.ConnectException: Connection refused: connect; No available router to destination]
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2327)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:866)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:594)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:508)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
>I checked all deployment descriptions and there are no references to t3://localhost:7001. Few months back, I had the complete clustering setup working on 2 machines and now when I deploy my application on same configuration, it fails with t3://localhost:7001 unreachable error. I created a new cluster configuration on one machine with 2 managed server and it deploys fine. Can not figure out what has changed ?
-
Error occurred while deploying ear file
Hello experts,
I am using NWDS (NW Version: 7.0.18). For a particular java file I am getting this error:
ERROR: Not deployed. Deploy Service returned ERROR:
20110728174758 Info : java.rmi.RemoteException: Error occurred while deploying ear file ./temp/deploy/work/deploying/WSPiloto.ear.
20110728174758 Info : Reason: None of the available containers recognized the components of application sap.com.avn/WSPiloto; it is not possible to make deploy. Most commonly used containers do not recognize the content of the application. Please contact the application vendor for details.
Appreciate your help to fix the issue.
Thanks in advance,
Guillermo,
devHi,
can you please check if the following note helps?
#1270242 -- None of the available containers recognized the components
(http://service.sap.com/sap/support/notes/1270242)
Best Regards,
Ervin -
Error when I deployed the java EAR application in NWDS 7.1
HI All,
I got the error when I deployed the java EAR application in NWDS 7.1 version..help me out...........................................
com.sap.ide.eclipse.deployer.api.APIException: DeployException,cause=[ERROR CODE DPL.DCAPI.1023] AuthorizationException.
Reason: , An error occurred during the deployer retrieval. Cause =[ERROR CODE DPL.DC.3151] The user LJ4PJW could not be authorized, because doesn't own the (com.sap.engine.interfaces.security.ServiceAccessPermission dc) permission for deploy controller. at com.sap.ide.eclipse.deployer.dc.ComponentManagerImpl.getDeployProcessor(ComponentManagerImpl.java:62)
Thanks
CostaThe user LJ4PJW could not be authorized, *because doesn't own the* (com.sap.engine.interfaces.security.ServiceAccessPermission dc) *permission for deploy controller. a*t com.sap.ide.eclipse.deployer.dc.ComponentManagerImpl.getDeployProcessor(ComponentManagerImpl.java:62)
The user is not have proper authorizations. Use some other administrators user id which has all admin roles and authorizations assigned and try to deploy.
Regards,
Ravi -
When trying to deploy a sandboxed solution containing only a feature with a simple associated event receiver from VS 2013, I'm getting the following error:
Error occurred in deployment step 'Add Solution': An unknown exception occurred while executing a sandboxed code solution request in the worker process.\r\n|0
I'm working in Visual Studio 2013, deploying to SharePoint 2013.
The SharePoint project is very basic. I've only added a feature and an associated event receiver. It works without the event receiver. Then after I simply add the event receiver I get the error.
I've tried deploying directly from VS 2013 as well as publishing to a .WSP and uploading via web interface. Same error reported using both methods. I'm doing this using an Administrator account that I've confirmed is a site collection administrator.
Additionally, I've found that if I change Sandboxed Solution to False, deploy it, retract it, then change Sandboxed Solution back to True, then I can successfully deploy it. But this doesn't seem to be a permanent solution as the error will resurface a day
or two later...Hi Steve,
Are you running your SharePoint 2013 on domain controller?
http://www.learningsharepoint.com/2013/08/09/sharepoint-2013-error-an-unknown-exception-occurred-while-executing-a-sandboxed-code-solution-request-in-the-worker-process-rn0/
http://social.technet.microsoft.com/Forums/sharepoint/en-US/b7408608-c21b-45d9-bc16-e6afff510cd2/installed-sharepoint-2013-foundation-on-window-2010-server-issues-activating-sandbox-solutions?forum=sharepointadmin
My Blog- http://www.sharepoint-journey.com|
If a post answers your question, please click Mark As Answer on that post and Vote as Helpful -
HI,
I get this error "Error occurred in deployment step 'Retract Solution': The solution does not have a WSP file associated with it. " when deploying my project from visual studio 2010 to
SharePoint 2010 site. I tried restarting IIS, but it didn't help. This application used to work fine until the server crashed during the deployment process. All the other applications on the same server works fine also. Any ideas how to fix this issue?
Thanks in advance,
AMHi
AM ,
Thank you for your posting!
According to your error message, it says your solution does not have a WSP file associated with it. Take a look at the file system. After you Right Click -> Deploy Solution on the VS Solution, there
should be a .wsp file at <Solution Directory>\bin\<debug|release>.
Also the error can be occurring when the developer try to deploy solutions over pre-existing solutions with material changed in the solution. Go to your Central Administration Site and then
Operations and then Solution Management. Make sure that there not already a solution with the same name deployed or installed there. If there is, remove it and try deploying again.
And you could look in logs and find if there is a below error in ULS log (C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS).
Thank you for your understanding and support.
Best Regards,
Eric
Eric Tao
TechNet Community Support -
Error occurred in deployment step 'Add Solution': Attempted to perform an unauthorized operation.
Hello,
I'm new to SharePoint development. I just created a empty sharepoing app in VS2010, added a webpart and in .cs file of this webpart, add hello inside RenderContents. Its compiling fine. but giving following error while deploying
Error occurred in deployment step 'Add Solution': Attempted to perform an unauthorized operation.
My VS 2010 is running under Administrator privileges & I'm admin to this machine.
Comments?Hi, just had the same problem (on a 2013 enviroment) and was able to solve it partly by this post.
Also experience a problem with dublicate ports, see here: http://technicaltrix.blogspot.dk/2014/11/error-occurred-in-deployment-step-add.html
http://technicaltrix.blogspot.dk/ -
Hello,
I get the following error when trying to attach an event reciver ->
Error occurred in deployment step 'Add Solution': Failed to load receiver assembly . The system cannot find the file specified.
This happens only when i try to change the deployment target from "GlobalAssemblyCache" to "WebApplication".
Steps to reproduce->
1. Create a new feature and add an event receiver. Deploy the solution. Everything works fine.(Since deployment target is GlobalAssemblyCache). If you now change the deployment target to "WebApplication" , it works too.
2. Now, restart visual studio. Change Deployment target to "WebApplication" without deploying the solution. And you get the above error.
3. Every time you restart your visual studio with deployment target as "WebApplication", you will receive this error.
Any idea?? Manual deployment of the solution works fine too.
When i go to virutal path bin directory, the dll is missing because of which the error occurs. Dont know why, it doesnt copy the dll to bin?
Thanks in advance,Hi,
Feature receivers must be deployed in the GAC & cannot be deployed to private bin of the WebApplication.
Link: http://msdn.microsoft.com/en-us/library/ms469501.aspx
HTH !!!
AnjaliCH-MSFT -
Error occurred in deployment step 'Add Solution': Failed to load receiver assembly
Guys,
I've created a VS2010 sharepoint project and added a feature event receiver to my site definition. When I try to deploy it show me the error bellow:
Error 1 Error occurred in deployment step 'Add Solution': Failed to load receiver assembly "SiteDefinitionProject2, Version=1.0.0.0, Culture=neutral, PublicKeyToken=a693a58979940483" for feature "SiteDefinitionProject2_Feature1" (ID: 9dce3ed9-5eb0-4bea-b42d-4dad84559a36).:
System.IO.FileNotFoundException: Could not load file or assembly 'SiteDefinitionProject2, Version=1.0.0.0, Culture=neutral, PublicKeyToken=a693a58979940483' or one of its dependencies. The system cannot find the file specified.
File name: 'SiteDefinitionProject2, Version=1.0.0.0, Culture=neutral, PublicKeyToken=a693a58979940483'
at System.Reflection.Assembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection)
at System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
at System.Reflection.Assembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
at System.Reflection.Assembly.Load(String assemblyString)
at Microsoft.SharePoint.Administration.SPFeatureDefinition.get_ReceiverObject()
WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
0 0 SiteDefinitionProject2
9dce3ed9-5eb0-4bea-b42d-4dad84559a36
Someone can hepl!?
André RentesI also just encountered this error while trying to deploy my feature from Visual Studio 2010. I found the solution for my situation. Perhaps it may help others as well.
To see if your problem has the same cause as I encountered, open up the 14 hive and go to 14/template/features/<your-project-name_your-feature-name>. In this folder you will find a file Feature.xml. Open it up with notepad. On the second line
you will find the XML node Feature. Scroll to the right untill you see the XML attribute ReceiverClass. This
should show you a namespace, i.e. KoenZomers.MyProject.Branding.Features.Web.BrandingEventReceiver. In my situation it didn't show a namespace, but instead the following: $SharePoint.Type.<some-guid>.FullName$. If this is the same for
you, read on as this might be the solution to your problem. If it does already show a namespace, this probably won't help you.
This problem is caused because of a bug in Visual Studio 2010. It should replace the guid to match the guid found above the class declaration of your event receiver. For example:
[Guid("ff9717e0-05c4-4e7e-9349-3f31d3919b9c")]
public
class
BrandingEventReceiver
: SPFeatureReceiver
Probably because I recreated the event receiver class, it did generate a new Guid tag with a new Guid above my class declaration, but it did not update the feature file to reference this new guid. To do this manually, open up the folder on your development
machine where your Visual Studio project files reside. In it you will find a subfolder named Features. Open it. In that folder you fill find subfolders with the names of your features as given in Visual Studio. Open up the one containing the non functional
event receiver. In that folder you will find a file called <feature-name>.feature. Right click on it and choose Open with. Select to open it with notepad. On the second line you will find the XML node feature. Scroll to the right until you see the XML
attribute receiverClass in the same line. Make sure the value of this XML node is built up using the following syntax: $SharePoint.Type.<guid-from-event-receiver-class-declaration>.FullName$. So in the above example it would be $SharePoint.Type.ff9717e0-05c4-4e7e-9349-3f31d3919b9c.FullName$.
Save the file, close notepad. Close the solution in Visual Studio. Once closed, reopen the solution. Do a deploy of your solution. It should work this time. If you check the feature.xml file in the 14 hive now, it does display a namespace. This
made it work for me. -
Error occurred in deployment step 'add solution' value cannot be null Parameter name: g
Hi!
I have a SharePoint Server 2013 with latest updates. Worflow Manager 1.0 installed and configured correctly. The server has a website, site temblate is Reacods Center. This site is default. On the site I created a blank Document library "TestLib"
If I create workflow in SharePoint Designer 2013, workflow works normally. Workflow set Title of element to "MyCustomTitle" and Write to History string "Done!".
If I create Empty Solution in Visual Studio 2013, insert into solution Workflow and make same actions, my solution at deployment step fails with error:
"error occurred in deployment step 'add solution' value cannot be null Parameter name: g"
Please, help me to resolve this problem?
Thanks!Hi,
What if stop this service, then start it again, perform an iisreset? It will make the change applied to the whole farm.
Also, you can check the ULS logs to see if there is any unexpected error occurs when deploying this solution.
About how to check the ULS logs:
http://blogs.technet.com/b/fesiro/archive/2013/11/11/sharepoint-logging-and-troubleshooting-using-ulsviewer.aspx
Thanks
Patrick Liang
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected] -
Hi,
When i am trying to deploy sharepoint 2010 application in VS 2010, i am getting the below error:
"Error occurred in deployment step 'Add Solution': The definition specifies a claim provider with a name already in use."
How to fix this?
Thank youYou can use:
$provider = Get-SPClaimProvider | where {$_.DisplayName -eq "Provider DisplayName"}
$mgr = Get-SPClaimProviderManager
$mgr.ClaimProviders.Remove($prov)
$mgr.Update()
Trevor Seward
Follow or contact me at...
  
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.
Maybe you are looking for
-
Hi, How to define a background jobs in Sm37. Give me the steps. Rgds, Shradha
-
Analytical function in OWB 10.2.0.4.0
Dear - I am trying to implement analytical function in OWB but not sure how to do it. Can anyone help me? My SQL query looks like select sum (aamtorg), sum(sum(aamtorg)) over (order by cbssuntgbk, caccgbk, caccroo, ccrytrngbk, creftrl, cmgmint, cbase
-
I just bought a new Samsung 22" monitor. The text resolution is really bad. After talking to Samsung, I found that the needed resolution is higher then what my Mini-Mac shows available. Can this be fixed or do I return the monitor?
-
My computer went to sleep and never woke up!
twin g4 867 MDD went to sleep at its scheduled time (2AM) The next day it would not wake from sleep as far as i could tell. Unplugged it, plugged it back in and i get startup tones but no video feed. HD's and fans are spinning. anyone have any ideas?
-
Reinstall Display Driver to enable 3D
Currently using Photoshop CS6 Extended on Windows XP. When I go to enable UGP in Preferences the message I get is "photoshop detected an error in your display driver. Update or reinstall the driver and check UGP to retry". Have reinstalled Phot