Skip to main content

This solution contains no resources scoped for a web application and can not be retracted from a particular web application

While retracting/ deploying  sharepoint solution using visual studio or stsadm command you might have got following errors , such as

1.If you are using

 "'Retract Solution': C:\Windows\Temp\solution-b254f31c-6d03-41c0-869c-e0755c54a1e0\SOLUTION.wsp could not be created because the contents could not be found under id fc52e867-4f3f-4d65-a348-2406fd83635e in the configuration database."

2.If you are using stsadm command

"This solution  contains no resources scoped for a web application and can not be retracted from a particular web application"

 The above two errors are belonging to represent the same issue. This issue occurs because of improper activation of the feature. When you deployed the same solution or some other solution on the site, it might have given  you the message as 'deployed successfully', but might not have activated feature properly. In order to fix this issue use the following stsadm command and retract and remove those solution which cause the issue

stsadm -o retractsolution -name "SOLUTIONNAME.wsp" -local  
This will retract the solution . Remove the solution and start deploying your current solution.

Happy SharePointing


This may help some one
Cheers

Pradeepa achar

Comments

Post a Comment

Popular posts from this blog

The Fastest way to Export Schema of Sharepoint List

Many of my SharePoint Developer friends are struggling to get the Schema.xml file of a newly created list. The schema.xml file has the list's metadata information, by using the schema.xml, we can create the lis definition and paste this contents of Schema.xml to the Schema.xml file of the newly created List definition, so that you can deploy the list definition on another site. In order to do this, you guys might be following the procedure bu saving the site template and get the site definition solution. After this, you will open visual studio and import this solution and wait for few minutes. THIS IS A CRAPPY PROCEDURE..Why do you invest your time to get a schema of one or few list  by taking entire site definition?..If that site has lots of lists, then it will take lots of time. In my Research, i have found a the BEST  and quicker way to get schema.xml file of a particular list which you need Schema.xml. Follow the following procedure : Go to your site  click on the lis
Post a Comment
Continue »

How to avoid refreshing of page on clicking on BUTTON in jQuery?

Suppose you might have created a button on page.When you click on that button without page refresh some other custom things have to happen. But instead of that, on clicking on the button the page is getting refreshed. How to avoid this?.. Simple, The button click event has default event as refreshing the page. The solution is to "prevent the default event". $("#ButtonID").Click(function(e) {   e.preventDefault(); //Write your custom code here } ); Hope this may help Cheers Pradeepa Achar
Post a Comment
Continue »

This solution contains invalid markup or elements that cannot be deployed as part of a sandboxed solution. Solution manifest for solution 'cc218449-78b3-4430-b401-4884977560e2' failed validation, file manifest.xml, line 11, character 4: The element 'Solution' in namespace 'http://schemas.microsoft.com/sharepoint/' has invalid child element 'TemplateFiles' in namespace 'http://schemas.microsoft.com/sharepoint/'. List of possible elements expected: 'FeatureManifests, ActivationDependencies' in namespace 'http://schemas.microsoft.com/sharepoint/'. Troubleshoot issues with Microsoft SharePoint Foundation. Correlation ID: oplh6595a-a6hg-416f-a85f-a173bp03dda6 Date and Time: 30/10/2013 13:33:18

By looking at this bug you may get shocked and may not understand why this is happening. I can say, you have developed a wsp of farm solution, not the sandboxed solution  using visual studio and added some OOTB webparts such as visual webparts and trying to deploy the solution via solution gallery directly on to the sharepoint site. It is so simple.Understand that, when you create a .wsp file using visual studio, you deploy as farm solution. But when you try to deploy the same solution from site settings-> solution gallery, you deploy it as sand boxed solution. In this situation ,the "TemplateFiles" elements refers to the items that will be copied into the web servers. This is allowed only in farm solutions , not in sandboxed solutions. I suggest you guys to deploy the solution either using stsadm command or powershell command, so that it will work fine.If anyone wants to know about how to deploy using powershell command you can refer the   techNet  document for
Post a Comment
Continue »