Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Wednesday, March 30, 2011 2:03 PM | 1 vote
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
All replies (18)
Wednesday, March 30, 2011 2:22 PM ✅Answered
When you deploy the solution through visual studio, not only it deploys the solution but it activates the site level feature. If you are keep getting error, I would check what's causing site level feature activation throw an error..
Nik
Nik Patel
Slalom Consulting
Blog: http://nikspatel.wordpress.com/
Follow me at http://twitter.com/nikxpatel
Wednesday, March 30, 2011 2:45 PM ✅Answered
Sure!
Please refer below links for stsadm command
http://technet.microsoft.com/en-us/library/cc263231(office.12).aspx
EX:
1) stsadm -o Addsolution -filename <<yourWSP file>>
2) stsadm -o DeploySolution -name <<solution name>> -url <<site url>> -immediate
Pathik Rawal My Blog
Wednesday, March 30, 2011 3:08 PM ✅Answered
there was a feature in the solution called feature1
i deleted that and the solution now deploys :)
I cant see it anywhere tho sop i suppose that will require another thread?
Wednesday, March 30, 2011 2:15 PM
Hi,
Are you deploying this feature from visual studio? use STSADM command and see if you get same error.
Pathik Rawal My Blog
Wednesday, March 30, 2011 2:17 PM
yes from visual studio
use stsadm from the command prompt?
Wednesday, March 30, 2011 2:20 PM
Yeah,
Just try once from Command Prompt using STSADM, and see if you get same error?
Pathik Rawal My Blog
Wednesday, March 30, 2011 2:20 PM
I would go to the central admin and manually delete the solution if it's errored out. Central Admin -> Settings -> Manage Farm Solutions would provide the info if solution was errored out. Try manually deleting it and redeploy through visual studio.. It seems like you have feature receiver for the site level feature and it throws an error while deploying solution from visual studio..Nik Patel
Slalom Consulting
Blog: http://nikspatel.wordpress.com/
Follow me at http://twitter.com/nikxpatel
Wednesday, March 30, 2011 2:39 PM
i deleted it and deployed it again and i get the same error
Wednesday, March 30, 2011 2:40 PM
could you give me an example of the command i would use please
sorry very new to al this
Wednesday, March 30, 2011 2:56 PM
stsadm is not recognised
Saturday, December 3, 2011 5:52 AM
If you are getting the error at the time of deploying the solution through VS 2010, first retract the solution through VS 2010.
Then it will be retracted from farm level and site collection level.
Then again you can easily deploy the solution. This time it will deploy smoothly.
Thanks Shiva
Monday, December 5, 2011 4:28 AM
If you ever get the error, please run the Uninstall-SPFeature with Force on all the servers or boxes in the farm..
Retract and Deploy the solution and everything should be all right.. This happens whenever you install/deploy new solution on the environment where features are already installed/activated with previous version of deployed solution.. Proper retraction/deployment would help...
Nik Patel
Slalom Consulting
Blog: http://nikspatel.wordpress.com
Follow me at http://twitter.com/nikxpatel
Friday, December 9, 2011 4:12 PM
Just to build on what others have suggested...you can also just deploy the package with the -force attribute. Something like the following:
stsadm.exe -o deploysolution -name <wsp_name> -url <target_web_app_url> -immediate -force -allowgacdeployment
If you get "stsadm" is not recognized then you need to change directory to the <SharePointRoot>\bin subdirectory or add it to your path statement.
-Guy
Friday, May 24, 2013 10:49 AM | 2 votes
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
im new to all this by the way :)
thanks in advance
Old post but i can't see a direct answer to question 1.
Here it is :
Find the Feature with the given Id (in the output something like 57746904-90ae-4e73-8ad4-561a4df370e7) in the solution. Open the feature in Visual Studio.
From the Property tab (double click the feature), Change the property “Always force Install” to “True”. Deploy the solution again…
Saturday, May 25, 2013 6:03 AM
The same same solution and feature already installed in farm and site collection.
First remove solution from farm.
Open the feature in Visual Studio. From the Property tab, Change the property “Always force Install” to “True”. Deploy the solution again.
Thursday, July 11, 2013 8:52 AM | 2 votes
1. Go to your Features in your project.
2. Open the feature.template.xml file
add AlwaysForceInstall="TRUE" to the below tag
<Feature xmlns="http://schemas.microsoft.com/sharepoint/" AlwaysForceInstall="TRUE">
Now try to deploy the code.
Thanks
Suresh A
New User
Wednesday, September 11, 2013 8:12 PM
This solution worked like a charm!
Dodge
Thursday, September 4, 2014 2:35 AM
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>