Saturday, March 19, 2011 10:05 AM
I just made one sample Form Project and deployed I got this below error. Not sure how to continue
Error 1 Error occurred in deployment step 'Activate Features': Feature with Id '4413517c-0022-4bf0-88af-5690a35a8e6b' is not installed in this farm, and cannot be added to this scope.
0 0 FarmProject
- Moved by Mike Walsh FIN Saturday, March 19, 2011 11:51 AM deployment (From:SharePoint - Setup, Upgrade, Administration and Operation (pre-SharePoint 2010))
Sunday, March 20, 2011 4:51 AM
You are not giving enough detail for a person to answer for sure what the problem is. Sometimes you get the "cannot be added to this scope" if you are trying to deploy something to web vrs site. There are 4 scopes to deploying features with in a WSP file. The four scopes are Farm, Web Application, Site and Web. Most of the time its due to being deployed to the web when it should be deployed to the site level. If you are in Visual Studio 2010 you can open your project and double click the feature and this will open and you can see the scope of your feature.
Gary Newman MCSE, MCT, CCNA MCDBA, MCAD, MCSA MCTS SharePoint 2007 Dev & Admin MCPD SharePoint 2010 Development
Sunday, March 20, 2011 9:55 AM
check SCOPE AND ALLOWED FEATURES
Mai Omar | Senior Solutions Developer | ITEgyptCorp | Email: maio@ITegyptCorp.com | Blog: http://maiomar.itegyptcorp.com
Moderator Note: NEVER propose your own posts as answers. The "Propose as Answer" function is there so that people can propose the good answers of other people. It is not there for self-proposing.
- Proposed As Answer by Mai Omar Desouki Sunday, March 20, 2011 9:55 AM
- Unproposed As Answer by Mike Walsh FIN Sunday, March 20, 2011 2:57 PM
- Edited by Mike Walsh FIN Sunday, March 20, 2011 2:59 PM Moderator Note about never proposing own posts as answers added (again)
- Marked As Answer by Leoyi Sun Friday, April 01, 2011 2:17 AM
Monday, May 02, 2011 9:03 PMHi, Could be that the web.config file is either corrupted or just not there anymore...I was doing some clean up on the IIS sites on the server and I took away by mistake the folder in the "virtual directories" corresponding to the web application I was trying to deploy to.Of course I didnt realized that while I was trying to deploy the solution, I was just getting your error even though when I was able to go to the site itself and execute the actual custom code anyway...I end up going to "manage farm solutions" a saw an error on the particular solution that I was trying to deploy from VS and it was very clearHopes this helps