How to enable site pages document library in SharePoint 2010

In one of the SharePoint 2010 site I don't see 'Site Pages' document library, after some research I have found that we have to activate "Wiki Page Home Page" feature to see site pages library into SharePoint 2010 site.

Features\ExcelServerSite\Microsoft.Office.Excel.WebUI.dwp is referenced in the database, but is not installed on the current farm

I was getting above error while migrating contents from 2007 to 2010, as per this MSDN links we can ignore this error while migration.

http://social.technet.microsoft.com/Forums/en-US/sharepoint2010setup/thread/539c4086-0bfe-4c87-9b0a-c4d65642340f/

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"

Access denied error while installing feature

I was getting “Access denied” in command prompt when I tried to execute below command

Stsadm –o installfeature –name “featurename” –force

Solution:

1. Log in user was not added into Central Admin Database security group into SQL Server.

2. Log in user has to be in farm administrator/site collection users group in SharePoint site.

By adding my current Log in users into above two parts, I was able to successfully install feature.