February 2013 CU for SharePoint 2010 has been released

The KB articles for February CU

• KB 2760791 - SharePoint Foundation 2010
• KB 2767793 - SharePoint Server 2010
• KB 2767794 - SharePoint Server 2010 with Project Server
  As you see there is a separate Full Server Package for SharePoint Server 2010 with Project Server which simplifies patching of this common installation.

The Full Server Packages for February 2013 CU are available through the following links:

• Download SharePoint Foundation 2010 February 2013 CU
• Download SharePoint Server 2010 February 2013 CU
• Download SharePoint Server 2010 with Project Server February 2013 CU - 

After installing the fixes you need to run the SharePoint 2010 Products Configuration Wizard on each machine in the farm

March Public Update for SharePoint 2013 available and mandatory

The product group recently released the March 2013 Public Update (PU) for the SharePoint 2013 product family.

Important: Due to a change in the package configuration introduced after SharePoint 2013 RTM the March Public update is a mandatory requirement in order to install subsequent SharePoint 2013 Updates.

That means that in order to install future cumulative updates for SharePoint 2013 it will be mandatory to first install the March public update.

• KB 2768000 - SharePoint Foundation 2013
• KB 2767999 - SharePoint Server 2013
• KB 2768001 - Project Server 2013

The Full Server Packages for March 2013 PU are available through the following links:

• Download SharePoint Foundation 2013 March 2013 PU
• Download SharePoint Server 2013 March 2013 PU
• Download Project Server 2013 March 2013 PU
  After installing the fixes you need to run the SharePoint 2013 Products Configuration Wizard on each machine in the farm.

Be aware that the SharePoint Server 2013 PU contains the SharePoint Foundation PU. And the Project Server 2013 PU contains SharePoint Server PU and SharePoint Foundation PU.
That means only one package has to be installed for the SharePoint 2013 product family.

Thanks Stefan for this Information

http://blogs.technet.com/b/stefan_gossner/archive/2013/03/21/march-public-update-for-sharepoint-2013-available-and-mandatory.aspx

List tools tab was missing after Migration from 2007 to 2010

Hi some after Migration issues discussed . 

Issue : List tools tab was missing after Migration from 2007 to 2010

We found today that one of the User had a site collection with 5 lists . When he clicks on the first list the List tools tab at the top is available . 

However for one of the Lists we don't see the Tab . Thought the list has gone corrupt and was about to create a new list with the Template and move the contents .

But then while troubleshooting we found that if we click on one Item we see the List tools tab . Ahhhh But that is not a resolution . why is it working for others ?. 

It also looked like the permissions were gone but that was wrong. Permissions were correctly set and the user was logged on as an site collection admin.

Then some how we found the solution . 

Resolution : The user had added edited the page when they were on 2007 and added a Content Editor web part without any text on the top of the list as a web part 

Deleted the web part and there you go got the List tools back

Access Denied on the site collection after migrating form MOSS 2007 to SharePoint 2010.

We have recently migrated from the Moss 2007 to SharePoint Server 2010 and after migration we have several user complain about that they get access Denied error message on accessing parent site collection despite of they are having access on the site.

Error: Access Denied on the site collection level, though they have permissions. 

Background:

We user to activate a feature in the MOSS 2007 using stsadm -o activatefeature -name “Feature Name” -url  https://siteurl.net/sites/sites, after the site creation to have Branding enabled on it. 

After Migration, this feature is automatically activated on the web application level. Hence there is no need to activate it manually to apply standard branding on the newly created site. 

Troubleshooting:

-          Checked user permission on the group.

-          Added the user explicitly to the SharePoint group or individually.

-          Removed the user form the site collection and added again.

-          Added the user to site collection admin group. 

Note: We have seen Master page Gallery on the site collection level is using the unique permissions. Where as it has to be inherit from the site collection.

Resolution:

-          Added the NT Authority\Authenticated Users to the Master Page Gallery with Read permissions.

-          Change the permissions of the site to inherit form the site collection level.

-          Add the NT Authority\Authenticated Users to the style library with Read Permissions. 

Applied To:

SharePoint 2010. SharePoint Foundation 2010. SharePoint Server 2013.

The site collection could not be restored. If this problem persists, please make sure the content databases are available and have sufficient free space

Topology details:

-SharePoint Server 2010 with latest CU

-SQL Server 2008R2

-4 applications and 7 WFE’s

Problem Details:  Requirement comes up to replicate the production site collection to staging environment. We have taken the backup of the site by using PowerShell command without any issues.As soon as we started the restore command then it throws the following exception.

Error Message:

The site collection could not be restored. If this problem persists, please make sure the content databases are available and have sufficient free space.

Note:  One thing we need to understand that this is a very generic error message and does not have any correlation with the disk space available or not. If you have disk space available on the SQL Server as well as on the servers where SP is running then also you will face this error message. I think this is a BUG but not getting any documentation based on this to conclude the same. 

Troubleshooting done:

-Check the disk space on the SQL Server where LDF and MDF files are stored.

-Check the partition on the SQL SERVER in reference to data files

-Make sure the content database has enough space allocated.

-Make sure the databases does not have restrictive growth

-Make sure to check the disk space on the SP server where restore is running.  Approximately it should 2 times the DB size.

Resolution Applied:

-Go to “SQL Server Properties--Connections” and uncheck ‘Use query governor to prevent long-running queries’. Also, set “Remote query timeout” to 0.

-Stop and restart the "Windows SharePoint service Timer" 

-Restart IIS

If you have any queries/questions regarding the above mentioned information then please let me know.

I would be more than happy to help you as well as resolves your issues, thank you.