Admin svc must be running in order to create deployment timer job SharePoint 2010

During solution package deployment, I have received above error and then I have figured out that “SharePoint 2010 Administrative” service was stopped in my server, once I started the service the package deployment worked good without any errors.

Reference solution links:

http://imak47.wordpress.com/2011/05/11/install-spsolution-admin-svc-must-be-running-in-order-to-create-deployment-timer-job/

http://blog.salamandersoft.co.uk/index.php/2011/03/error-admin-svc-must-be-running-in-order-to-create-deployment-timer-job/

How to deploy custom master page using solution package in SharePoint 2010

Microsoft provided many great features and functionality into Visual Studio 2010 for developing any solutions for SharePoint 2010, with Visual Studio 2010 we can create and mapped 14 HIVE folders very easily.

Microsoft provided very detailed and step by step guide for how to create and deploy any branding solutions using Visual Studio 2010 for SharePoint 2010.

http://msdn.microsoft.com/en-us/library/gg447066.aspx

One more good reference link: http://sharepointchick.com/archive/2010/03/26/deploying-a-custom-master-page-in-sharepoint-2010.aspx

ERROR: The file manifest.xml does not exist in the solution package

I was getting above error when solution package size becomes too big; I need to add below lines into cab.ddf file.

.Set CabinetFileCountThreshold=0

.Set FolderFileCountThreshold=0

.Set FolderSizeThreshold=0

.Set MaxCabinetSize=0

.Set MaxDiskFileCount=0

.Set MaxDiskSize=0

Reference Links:

http://andreasglaser.net/post/2009/03/13/SharePoint-and-the-file-manifestxml-does-not-exist-in-the-solution-package.aspx

http://ph-tom.blogspot.com/2008/04/file-manifestxml-does-not-exist-in.html

Object reference not set to an instance of an object. The Solution installation failed

I was getting error "Object reference not set to an instance of an object. The Solution installation failed" while adding and deploying my solution package from STSADM command, I have looked into my event log and SharePoint log to find out the exact error, I have found out that it’s related to Admin Content SQL database.  The current user who is executing the STSADM command must have full control access to this content database.

Then I run my solution package with service account and it ran well without any problem, here we can also add current user into content database and will give full control rights to current user to executing solution package.

Good Luck!

How to give intelligence into feature XML file

One day I was creating my feature file into solution package, at that time I saw that I didn’t get intelligence of all elements and attribute into my file and I have found that by adding below schema file, we will be having intelligence in any XML file. Though it’s very small things, but I thought to share with you.

Schema file:

"C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\XML\wss.xsd"

Error while deploying solution “This solution contains no resources scoped for a Web application and cannot be deployed to a particular Web application”

I was getting error while deploying solution through STSADM command, error was “This solution contains no resources scoped for a Web application and cannot be deployed to a particular Web application”

I have figured out that it’s giving me problem because of URL parameter into deploysolution STSADM command, after removing it from command, my solution package was working fine.

Reference Link:

http://snahta.blogspot.com/2008/08/this-solution-contains-no-resources.html

Error occurred while starting of workflow (Could not load file or assembly Load Workflow Assembly System.IO.FileNotFoundException)

I was so frustrated to resolved above workflow error, because when I deployed my visual studio workflow solution package and started the workflow (manually or item created) then I was getting error in workflow status as “Failed on Start (retrying)”, also I didn’t see much useful information into workflow history, after looking into SharePoint log file, I have found below error.

Error:

Could not load file or assembly Load Workflow Assembly: System.IO.FileNotFoundException: Could not load file or assembly ‘ABC.dll, Version=1.0.0.0, Culture=neutral, PublicKeyToken=xxxxxxxxxxx' or one of its dependencies.
I know that there was some problem into feature.xml or workflow.xml file into solution package, but after looking into details, I have found out that I made very silly mistake into workflow.xml file, there was one tag called “CodeBesideAssembly”, we need to write only assembly name like ABC into that tag, but I wrote ABC.dll into CodeBesideAssembly tag into workflow.xml file which caused the error while starting of workflow.

After removing extra DLL word from the file, my workflow was worked fine. So be careful while making workflow.xml file.

Keep Sharing…