Friday, February 8, 2013

Error occurred in deployment step ‘retract solution’ cannot start service SPUserCodeV4 on this computer


Yesterday I was creating my first SharePoint 2010 Sand-boxed solution using Visual Studio 2010.  I have successfully built and deployed other SharePoint projects on the server but I always used Farm based solution due to the requirements.
When I built the Sand-boxed solution the project would build and package without any errors but when I tried to deploy it to the SharePoint site the following error occurred:
Error occurred in deployment step ‘Activate Features’: Cannot start service SPUserCodeV4 on computer ‘SERVERNAME'
The error can be easily resolved by starting the Microsoft SharePoint Foundation Sandboxed Code Service which can be accessed through the Central Administration site in SharePoint.   Open the Central Administration site and go to System Settings and click on Manage Service on server, as shown below



After starting the service try to deploy the snadoxed solution and the following erros wil be removed. 
"Error occurred in deployment step ‘retract solution’ cannot start service SPUserCodeV4 on this computer"


Thursday, February 7, 2013

This solution contains no resources scoped for a Web application and cannot be deployed to a particular Web application


Here is another SharePoint post for the deployment guys. I was deploying a SharePoint solution using SharePoint Admin utility i.e. Stsadm . I started facing error i.e. "This solution contains no resources scoped for a Web application and cannot be deployed to a particular Web application"

After analyzing the error message i.e. why I cannot deploy the solution to a web application. However if you do not like to deploy the solution to all the web applications and only like to deploy your solution to a specific application , you need to change the solution settings Assembly Deployment Target from GlobalAssemblyCache to WebApplication.



Change Assembly Deployment Target to Web-application, as shown below





After you change the Assembly Deployment Target and run the script again, you will have the solution deployed successfully. Happy deployment.


Sunday, February 3, 2013

SharePoint Hives Folders

SharePoint has hives folder for all the SharePoint major versions i.e 2007 has 12 hive, 2010 has 14 hive and now SharePoint 2013 has 15 hive folder. Let me elaborate the naming convention that why SharePoint has different hives folder name, then the SharePoint release name.

Basically Hive folder naming convention is development version of SharePoint. As SharePoint team is keep on working on different features of SharePoint all the team, so keep on creating different versions but Hive represent the production version which Microsoft release for SharePoint  I hope this post will help you in understanding why we have different Hive folder naming convention, then SharePoint.

Thank You.
Earn Money ! Affiliate Program
Open Directory Project at dmoz.org