InfoBus applet deployment steps

It seemed that some "users" have had success with the deployment
of the InfoBus applet, can someone be kind enough to post the
steps / process, ie to share their success stories
thanks in advance
null

Make sure below :
1.Only contain the application's class files,XML file,and
connection.properties file in your .jar file.
2.Distribute .jar file with runtime libaries for Infobus applet:
class111.zip,connectionmanager.zip,dacf.zip,infobus.jar,
javax_ejb.zip,jbomt.zip,jboremote.zip,jndi.jar,
jdev-rt.zip,swingall.jar,xmlparser.jar
3.Try your applet with IE browser.
null

Similar Messages

FYI: Deploying Infobus Applet

This is a response to multiple posts on problems with deploying
the Infobus Applet tutorial.
When you create your applet.jar file, here are some explicit
steps to follow when using the Deployment wizard, followed by
some general notes on deploying applets:
1. Select Project->Deploy->New Profile from the menu.
2. Click Next to get past the Welcome page, then accept the
default 'Deploy to Simple Archive' and click Next.
3. On the Rules page, click << to shuttle all the rules back to
the left. We won't use the rules, but will explictly select
which source files to include from our project on the next page.
Click Next.
4. On the Sources page, select your HTML file, XML file, and
Applet java file and click > to shuttle them over to the right.
Click Next.
5. Here is where things get tricky in the deployment phase. For
this specific tutorial. You do NOT want to include dependency
classes in your archive since you will deploy those separately.
Therefore, you want to ADD the oracle.dacf, oracle.jbo and javax
packages to the list of packages to EXCLUDE from the archive:
a. Click the Exclude button to display a list of packages.
b. Expand the oracle node and select the dacf subnode.
c. Click OK. Notice that oracle.dacf is added to the list of
packages to exclude from your archive.
d. Repeate a-c for oracle.jbo and javax.
e. The exclusions list on the Dependencies page should now
include oracle.dacf, oracle.jbo and javax (in addition to the
original default values)
f. Click the Preview button to show what will be included in
your archive. It should ONLY show your .class, .xml and .html
files from your project, a connection.properties file and the
manifest.
6. Click Next.
7. Enter a name for your archive jar file and click Finish to
generate it. Click Yes when prompted if you want to deploy now.
Copy the .jar file and each of the .jar/zip files listed in the
tutorial to your webserver. If the .jars will reside in a
different directory than the HTML file that calls the applet,
then you need to set the CODEBASE tag accordingly (relative path
from the HTML file to the archives).
Most of the archives you need to deploy are in the redist
directory. The classes111.zip file you deploy depends on which
driver you used, but by default will be in jdbc/lib/oracle8.1.5.
Basically, you want your applet archive file to contain ONLY the
class and xml files for your applet, and you want to deploy all
other 'referenced' archives separately (and list each of them in
the ARCHIVE tag of your applet's HTML file). This provides a few
benefits:
* your applet archive is much smaller because it doesn't
include all referenced class files
* if you have multiple Infobus applets, you only have to deploy
the commonly referenced archives once, not package them with each
applet and deploy them over and over which takes up space on the
server
As a side affect of the above deployment strategy, you have to
explictly tell the deployment wizard to EXCLUDE these referenced
packages that it would normally try to include in your archive.
That is accomplished on the Dependencies page of the wizard as
described above.
The Preview button will show you what is included. From there,
you can determine which packages to Exlcude. Keep checking the
Preview list to make sure you have stripped it down to the bare
minimum.
Hope this helps some.
L
null

Hong,
Are you using an internationalized operating system and/or
Browser? This appears to be related to a Resource file which
contains translated strings.
L
Hong (guest) wrote:
: Hi,
: I did the same way as you mention below. I get this following
: error message. I guess it couldn't find this class. I don't
even
: know where I can find this class.
: Thanks
: Hong
: These are the error message:
: Opening
http://web/java/oracle/dacf/dataset/ResTable_en_US.class
: no proxy
: java.lang.ClassFormatError: oracle/dacf/dataset/ResTable_en_US
: (Bad magic number)
: at java.lang.ClassLoader.defineClass0(Native Method)
: at java.lang.ClassLoader.defineClass
: (ClassLoader.java:403)
: at java.security.SecureClassLoader.defineClass
: (SecureClassLoader.java:101)
: at sun.applet.AppletClassLoader.findClass
: (AppletClassLoader.java:144)
: at java.lang.ClassLoader.loadClass(Compiled Code)
: at sun.applet.AppletClassLoader.loadClass(Compiled Code)
: at java.lang.ClassLoader.loadClass(Compiled Code)
: at java.util.ResourceBundle.findBundle(Compiled Code)
: at java.util.ResourceBundle.getBundle(Compiled Code)
: at java.util.ResourceBundle.getBundle
: (ResourceBundle.java:334)
: at oracle.dacf.dataset.Res.<clinit>(Res.java:16)
: at oracle.dacf.dataset.SessionInfo.<clinit>
: (SessionInfo.java:59)
: at package1.Applet1.<init>(Applet1.java:207)
: at java.lang.Class.newInstance0(Native Method)
: at java.lang.Class.newInstance(Compiled Code)
: at sun.applet.AppletPanel.createApplet
: (AppletPanel.java:532)
: at sun.plugin.AppletViewer.createApplet
: (AppletViewer.java:759)
: at sun.applet.AppletPanel.runLoader(AppletPanel.java:468)
: at sun.applet.AppletPanel.run(Compiled Code)
: at java.lang.Thread.run(Thread.java:479)
: JDeveloper Team (guest) wrote:
: : This is a response to multiple posts on problems with
: deploying
: : the Infobus Applet tutorial.
: : When you create your applet.jar file, here are some explicit
: : steps to follow when using the Deployment wizard, followed by
: : some general notes on deploying applets:
: : 1. Select Project->Deploy->New Profile from the menu.
: : 2. Click Next to get past the Welcome page, then accept the
: : default 'Deploy to Simple Archive' and click Next.
: : 3. On the Rules page, click << to shuttle all the rules back
: to
: : the left. We won't use the rules, but will explictly select
: : which source files to include from our project on the next
: page.
: : Click Next.
: : 4. On the Sources page, select your HTML file, XML file, and
: : Applet java file and click > to shuttle them over to the
: right.
: : Click Next.
: : 5. Here is where things get tricky in the deployment phase.
: For
: : this specific tutorial. You do NOT want to include
dependency
: : classes in your archive since you will deploy those
: separately.
: : Therefore, you want to ADD the oracle.dacf, oracle.jbo and
: javax
: : packages to the list of packages to EXCLUDE from the archive:
: : a. Click the Exclude button to display a list of packages.
: : b. Expand the oracle node and select the dacf subnode.
: : c. Click OK. Notice that oracle.dacf is added to the list
: of
: : packages to exclude from your archive.
: : d. Repeate a-c for oracle.jbo and javax.
: : e. The exclusions list on the Dependencies page should now
: : include oracle.dacf, oracle.jbo and javax (in addition to the
: : original default values)
: : f. Click the Preview button to show what will be included
in
: : your archive. It should ONLY show your .class, .xml and
.html
: : files from your project, a connection.properties file and the
: : manifest.
: : 6. Click Next.
: : 7. Enter a name for your archive jar file and click Finish to
: : generate it. Click Yes when prompted if you want to deploy
: now.
: : Copy the .jar file and each of the .jar/zip files listed in
: the
: : tutorial to your webserver. If the .jars will reside in a
: : different directory than the HTML file that calls the applet,
: : then you need to set the CODEBASE tag accordingly (relative
: path
: : from the HTML file to the archives).
: : Most of the archives you need to deploy are in the redist
: : directory. The classes111.zip file you deploy depends on
: which
: : driver you used, but by default will be in
: jdbc/lib/oracle8.1.5.
: : Basically, you want your applet archive file to contain ONLY
: the
: : class and xml files for your applet, and you want to deploy
: all
: : other 'referenced' archives separately (and list each of them
: in
: : the ARCHIVE tag of your applet's HTML file). This provides a
: few
: : benefits:
: : * your applet archive is much smaller because it doesn't
: : include all referenced class files
: : * if you have multiple Infobus applets, you only have to
: deploy
: : the commonly referenced archives once, not package them with
: each
: : applet and deploy them over and over which takes up space on
: the
: : server
: : As a side affect of the above deployment strategy, you have
to
: : explictly tell the deployment wizard to EXCLUDE these
: referenced
: : packages that it would normally try to include in your
: archive.
: : That is accomplished on the Dependencies page of the wizard
as
: : described above.
: : The Preview button will show you what is included. From
: there,
: : you can determine which packages to Exlcude. Keep checking
: the
: : Preview list to make sure you have stripped it down to the
: bare
: : minimum.
: : Hope this helps some.
: : L
null

Deploy infobus applet--"Invalidating certificate principals"

Hi, lots of questions about deploying infobus applet had been
posted previously, but none of them is my case.
After finishing generating "package1.jar", I copy every *.jar,
*.zip file into my deploy directory "c:\temp" as well as the
package1.applet1.html. But while I open this html file in
Netscape 4.7, no applet appear. In the java console, the
following error message appear..
Invalidating certificate principals in [file:/C|/temp/try/,]
Can the applet be invoked without webserver?
I had tried to transfer the whole directory to the website(sun
webserver), the same error message appear( only change is the
path now is [155.69.60.117:88])
Can anyone tell me why?
thx
null

This is hardly an Advanced Language Topic, nor is it Java-related. And who uses Netscape? I'm just playing with you. No but seriously, nobody is gonna answer that here. This is a JAVA forum.

Problems deploying a simple Infobus Applet

Hi,
I am testing the infrastructure required to build an Infobus
Applet for our Web-based application using the Business Component
Framework in JDeveloper 3.0.
I have created a simple project based on the Scott schema, which
uses the Java Business Object framework to define Entity Objects,
Views, etc. for the Dept and Emp tables.
I have then created, using the Wizard, an Infobus Data Form to
create a master-detail Applet to display Employees within a
Department based on the above mentioned View Object. This works
fine when running within JDeveloper3.
However, when I try to deploy the applet to our Oracle
Application Server as a simple HTML file and JAR file (not using
EJB, etc. as we currently only have OAS 4.0.7.1 - waiting for OAS
4.0.8 to be available for download), the applet fails to start.
I have installed the Java Plug-in 1.2.2 from Sun as documented as
I'm using Swing controls.
After much frustration with the online 'Help', I managed to
create a deployment profile which included the appropriate
archives (See Packaging Source and Deployment Files in Help -
still refers to 'Rules' and 'Sources' pages ala JDeveloper 2 NOT
3.0).
Using the Console feature of the Java Plug-in, I was able to see
the progress of the Applets classes being loaded. It gets to the
point where it's trying to load the ResTable classes in
dacf.zip as found in the path:
oracle\dacf\control\swing\find
At this point, it just stops and nothing else happens.
Do I need to explicitly localize my Infobus Applet because I'm in
the United Kingdom and my PC has that as it's Regional Setting?
That is, do I need to define a ResTable_en_GB version of this
class?
Also, in attempting to create a localized version, I had errors
with JDeveloper stating that the text for the FIND_HELP_MESSAGE
exceeds the limit of JDeveloper (meaning that it's too long and I
needed to replace it with a shorter string). Could this be the
problem in the first place?
I have not been able to get the Applet to get beyond this point,
although I'm still trying the localization to Great Britain.
I know this is already a LONG email, but here is an extract from
the Java Console after which nothing else happens:
CacheHandler file name: null
Opening
http://dell_server.wsp.co.uk:4005/oracle/dacf/control/swing/find/
ResTable_en.properties no proxy
Opening
http://dell_server.wsp.co.uk:4005/oracle/dacf/control/swing/find/
ResTable_en.properties with cookie
"SITESERVER=ID=8e93834f82ef0710b78e5a4b087d6eed".
Regards
Gene Schneider
null

Parameter passing in EJB must implement Serializable. One way to solve this is:
1. Define a new class which implements
Serializable.
2. Place whatever you want to pass inside
this class.
3. Now use the new class as your parameter.
eg.
public class Params implements java.io.Serializable {
String p1;
XmlDocmuent xdoc;,
etc, etc
Your program now have to use the class Params for parameter passing.
Hope this helps.
Tam
null

Sealing violation deploying Infobus Applet

Hi:
I'm trying to deploy an Infobus Applet. The database I'm using
is Oracle 8.0.5, and I've installed the Java plug-in 1.2
The connection dialog appears fine, but when I click the open
button I get this exception
405: sealing violation...
I've read about sealing, and it seems to be a property in the
manifest file generated in the JAR. But when I open the JAR I
can't see the property referred in the documentation
Any idea about what could be the problem?
Thanks in advance
Jose Luis
null

This is the whole text of the exception I get
Jose Luis
java.lang.SecurityException: sealing violation
at java.net.URLClassLoader.defineClass(Compiled Code)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(Compiled Code)
at sun.applet.AppletClassLoader.findClass(Compiled Code)
at java.lang.ClassLoader.loadClass(Compiled Code)
at sun.applet.AppletClassLoader.loadClass(Compiled Code)
at java.lang.ClassLoader.loadClass(Compiled Code)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Compiled Code)
at
oracle.jbo.rt.jndi.JboInitialContextFactory.getInitialContext
(JboInitialContextF
actory.java:52)
at javax.naming.spi.NamingManager.getInitialContext
(NamingManager.java:783)
at javax.naming.InitialContext.getDefaultInitCtx
(InitialContext.java:165)
at javax.naming.InitialContext.<init>
(InitialContext.java:142)
at oracle.dacf.dataset.SessionInfo._createAppModule
(SessionInfo.java:1476)
at oracle.dacf.dataset.SessionInfo.connect
(SessionInfo.java:1186)
at oracle.dacf.dataset.DbAccessImpl.connect(Compiled Code)
at oracle.dacf.control.swing.LoginDlg._connectToDB
(LoginDlg.java:1641)
at oracle.dacf.control.swing.LoginDlg._okButtonClicked
(LoginDlg.java:1550)
at oracle.dacf.control.swing.LoginDlg.actionPerformed
(LoginDlg.java:1632)
at javax.swing.AbstractButton.fireActionPerformed(Compiled
Code)
at
javax.swing.AbstractButton$ForwardActionEvents.actionPerformed
(AbstractButton.ja
va:1101)
at javax.swing.DefaultButtonModel.fireActionPerformed
(Compiled Code)
at javax.swing.DefaultButtonModel.setPressed
(DefaultButtonModel.java:250)
at
javax.swing.plaf.basic.BasicButtonListener.mouseReleased
(BasicButtonListener.jav
a:217)
at java.awt.Component.processMouseEvent(Component.java:3126)
at java.awt.Component.processEvent(Compiled Code)
at java.awt.Container.processEvent(Compiled Code)
at java.awt.Component.dispatchEventImpl(Compiled Code)
at java.awt.Container.dispatchEventImpl(Compiled Code)
at java.awt.Component.dispatchEvent(Compiled Code)
at java.awt.LightweightDispatcher.retargetMouseEvent
(Compiled Code)
at java.awt.LightweightDispatcher.processMouseEvent(Compiled
Code)
at java.awt.LightweightDispatcher.dispatchEvent(Compiled
Code)
at java.awt.Container.dispatchEventImpl(Compiled Code)
at java.awt.Window.dispatchEventImpl(Compiled Code)
at java.awt.Component.dispatchEvent(Compiled Code)
at java.awt.EventQueue.dispatchEvent(Compiled Code)
at java.awt.EventDispatchThread.run(Compiled Code)
null

Infobus applet and temporary files

Hi,
I have made an infobus applet and deploy it with the OAS407.
Now I have seen, that each time I load the applet from the
OAS407 the applet create 15 files in my temp-folder with the
prefix jar_cache (for example: jar_cache40989.tmp).
There is no problem with creating but there is a problem with
deleting because there is no mechanism for automatic deleting.
So I have to delete these files manually but I think that this
is unuseable for end-user.
Does anybody know how to bypass this problem ?
Thanks.
Nils
null

<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Nils Buering ([email protected]):
I ran into the same problem when I built an applet that uses DAC and runs the app module in the downloaded applet. The Java plugin 1.2.2 is creating these files in TEMP and these files are equal in size to the support jar and zip files downloaded to the browser. You can easily verify this by comparing file sizes (use the Properties facility when you right click a Windows file sname to see its exact size in bytes). The plugin does not delete these files when you exit the browser and thus re-creates them every time you restart the browser and access the applet from the web server potentially filling the user's disk.
SUN has fixed this problem with the 1.3 plugin. Ater downloading and installing the 1.3 plugin, you must edit the applet's HTML file to add two new PARAM options: "cache_option" and "cache_archive". See http://java.sun.com/j2se/1.3/docs/guide/misc/appletcaching.html for instructions (a document titled "Applet caching in Java Plug-in") on doing this. This basically tells the plugin to use its own caching, instead of the browser's and doing this, the jar files created in the user's TEMP directory are deleted when you kill the browser.
However, since Jdeveloper is not certified with Java 2 v1.3, I ran into problems with code that works under the 1.2.2 plugin. The applet no longer runs once its been downloaded: I get a permissions error in jbo.logging.show and jbo.logging.trace; to wit: (java.lang.ExceptionInInitializerError: java.security.AccessControlException: access denied (java.sql.SQLPermission setLog). So switching to the 1.3 plugin will fix the buildup of jar files in TEMP problem; but your applets may no longer work! Best to wait until Jdeveloper is certified with 1.3 then you can run the 1.3 plugin successfully.
Hi,
I have made an infobus applet and deploy it with the OAS407.
Now I have seen, that each time I load the applet from the
OAS407 the applet create 15 files in my temp-folder with the
prefix jar_cache (for example: jar_cache40989.tmp).
There is no problem with creating but there is a problem with
deleting because there is no mechanism for automatic deleting.
So I have to delete these files manually but I think that this
is unuseable for end-user.
Does anybody know how to bypass this problem ?
Thanks.
Nils<HR></BLOCKQUOTE>
null

Error occurred in deployment step 'Add Solution': A timeout has occurred while invoking commands in SharePoint host process.

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 occurred in deployment step 'Activate Features': A timeout has occurred while invoking commands in SharePoint host process.

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

Error occurred in deployment step 'Add Solution': A feature with ID '' has already been installed in this farm. Use the force attribute to explicitly re-install the feature.

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 advance

If 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>

Error occurred in deployment step 'Uninstall app for SharePoint': The remote server returned an error: (502) Bad Gateway.

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
Arun

Hi 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

Deploying simple SharePoint 2013 feature causing error: "Error occurred in deployment step 'Add Solution': An unknown exception occurred while executing a sandboxed code solution request in the worker process."

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

"Error occurred in deployment step 'Retract Solution': The solution does not have a WSP file associated with it." occurs while deploying from Visual studio

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,
AM

Hi
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/

Sharepoint 2010 - Visual studio 2010 error - Error occurred in deployment step 'Add Solution': Failed to load receiver assembly

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é Rentes

I 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.

InfoBus applet deployment steps

Similar Messages

Maybe you are looking for