Contents
What happens when you retract a solution from a file?
When a solution is retracted, all files for that solution are retracted, even if another solution points to the same file. This issue can be avoided by ensuring that each solution points to a unique set of files. It is possible to retract a solution from some web applications while leaving it deployed for others.
When to uninstall and retraction of a farm solution?
In a complete retraction, features are uninstalled first from front-end web servers in the farm. If the solution is web application–specific, solution global files (if any) are removed when the solution is retracted from the last web application to which it is deployed.
Which is the third step in the retraction process?
The third step, which applies only to Features, is always called activating, and its reversal is always called deactivating. Retracting a solution is the process of removing assemblies, files, resources, safe control entries, Features, and other solution components from computers to which they have been deployed.
Do you have to retract a solution deployed on a web app?
If you retract a solution deployed on a Web app basis, but that has been deployed to all Web app, you must retract it from all Web apps before uninstalling it. I have faced a similar issue couple of days back.
How are features removed in a retraction of a farm solution?
In a complete retraction, features are uninstalled first from front-end web servers in the farm. If the solution is web application–specific, solution global files (if any) are removed when the solution is retracted from the last web application to which it is deployed. Next, Features are uninstalled from databases.
Retraction and uninstallation can be done with either the Central Administration application or SharePoint Management Shell. See Technet for information about how to do these tasks.