SocialListNotFound: The Social list does not exist in your personal site.

February 12, 2016 Leave a comment

Well, new blog post after a very long time.

I was recently getting the following error when I click on the follow button on a SharePoint 2013 site, this was a environment that was upgraded from SharePoint 2010.


Follow Error

Turns out for the follow feature to work, my MySite needs to have a list called “Social” and this list was missing in my MySite which was still in the 2010 look and feel mode. The fix for this issue was upgrading my MySite from the SharePoint 2010 look and feel mode to SharePoint 2013 and the issue was resolved. Pretty simple fix!


Categories: SharePoint

Office Web Apps Missing on one Server in a Farm

December 13, 2011 Leave a comment

During installation of Office Web Apps recently, I noticed something strange. After installing Office Web Apps on all the servers in the farm, I proceeded towards running the SharePoint Configuration wizard on one server and I was presented with the error below.

Office Web Apps Error

For some reason, SharePoint is thinking that Office Web Apps is missing on one server and wants me to install Office Web Apps on that particular server. This is not true as I ensured that I installed Office Web Apps on all the servers in the farm. Clicking refresh did not help!

I have seen similar error while installing SP1, in fact it was known issue while installing SP1 and the fix was running a PowerShell cmdlet which refreshes the list of installed SharePoint products. Here is what I did

Opened up SharePoint PowerShell Management Console and ran the following command

Get-SPProduct -Local

After running this command and clicking refresh, the SharePoint Config Wizard went through successfully.

Is your SharePoint 2010 Ribbon broken on IE 8?

February 14, 2011 1 comment

I noticed a strange thing on my SharePoint ribbon yesterday, it was all broken on IE 8. The tabs were squeezed, the text was truncated and It was not pretty anymore.

Notice there is no user information drop down, I was trying to “Sign in as Different User” but I could not the see the drop down for “Sign in as Different User”. I asked around to see if anybody else had the same issue and looked like it was only me and only on my machine.  This was only happening in IE 8 and It was working fine on Firefox or Safari. I tried restoring my browser to default,  but it did not help. After some digging on Bing, I found this KB article from Microsoft.

Looks like if you have IE zoomed out past 100%, the tabs will be break. The fix is pretty simple, click on View -> Zoom -> 100%. This fixed the issue for me.

The ribbon looks pretty again!



Categories: SharePoint 2010 Tags: ,

SharePoint 2010 Usage and Health Data Collection Service Application

December 8, 2010 3 comments

Usage and Health Data Collection Service Application collects Data about Usage and Health of your farm. This information is used for Health Monitoring and this is also required for running the Web Analytics Service. If you do not have a Usage and Health Data Collection Service Application or your Usage and Health Data Collection Proxy is stopped, you will not see any data in the Web Analytics Report. So, How do you create a Usage and Health Data Collection Service Application? Your natural instinct is you login to Central Admin -> Application Management -> Manage Service Application -> New

Guess What? You do not see a “New Usage and Health Data Collection Service Application”

So How do you do it? Well You can create it by following this Technet Article. You need to navigate to Monitoring, Click on Configure Usage and Health Data Collection, check the box for “, select the Events to Log, Put in the log file location, SQL information and you are done. Now you have Health Data Collection Service Application but if you navigate back to Manage Service Application Section, you see that the Usage and Health Data Collection Proxy is Stopped.  How do we start? I will get there in a Minute.

You can also create Usage and Health Data Collection Service Application by using Power Shell, here is the Syntax for it. I love Power Shell, so this is my preferred method.

New-SPUsageApplication -Name “UsageAppName” -DatabaseServer “DBServerName” -DatabaseName “DBName”

Even if you use Power Shell to create the Usage and Health Data Collection Service Application, if you navigate back to Manage Service Application, you see that the Usage and Health Data Collection Proxy is Stopped.

So to Start the Usage and Health Data Collection Proxy, use the Power Shell Command below

$Usage = Get-SPServiceApplicationProxy | where {$_.TypeName -eq “Usage and Health Data Collection Proxy”}


This should get your Usage and Health Data Collection Proxy started, hopefully you will find some peace!


New-SPUsageApplication -Name UsageName -DatabaseServer $databaseServerName -DatabaseName “UsageDB”

How to restart a query component in SharePoint 2010?

November 2, 2010 1 comment

Sometimes you might have seen this warning in event log

Event ID: 2587

The following conditions are currently affecting index propagation to this server for search service application ‘ Search Service’: 1. Query 0 has been disabled so that crawls can continue. It may be recovered via the Restart-SPEnterpriseSearchQueryComponent command in PowerShell.

It indicates that SharePoint 2010 Search Query Component has been disabled and it needs to be restarted, this might occur due to index corruption.  You might also see errors/warnings with Event ID 2581 and Event ID 74. When you get on to central admin and navigate to the Search administration screen, you might notice that the query component is disabled.

So How do you restart it? You can do it using the Restart-SPEnterpriseSearchQueryComponet, here it the power shell powershell script to do it

Add-PSSnapin Microsoft.SharePoint.Powershell

$S = Get-SPEnterpriseSearchServiceApplication -Identity ” Search Service Name”

$Q =$S.QueryTopologies

$C =Get-SPEnterpriseSearchQueryComponent -QueryTopology $Q.ActiveTopology

$C | fl Name,State

$C[0] |  Restart-SPEnterpriseSearchQueryComponent

Once you run the script, if you go back to central admin and search administration page, you would see the status of the query component change to recovering and eventually the status should change to online.

My Links missing in SharePoint 2010

October 21, 2010 1 comment

If you are running SharePoint 2010 and probably one of the first things that your users would notice is that there is no more MY LINKS shortcut on the top right corner. Also, you don’t see MY LINKS when you go to your My Site. Well, don’t worry and there are MY LINKS in SharePoint 2010, but sort of hidden.

With the introduction of tagging features in SharePoint 2010, Microsoft wants you to use this tagging feature rather than using the MY LINKS. So whenever you are on a page that you visit often, if you click on the Tags and Notes short cut on the top, this page link is added to Tags and Notes under My Site. Well this pretty cool but some users like the flexibility of having the MY LINKS shortcut on every page instead going to their My Site.

So, How do you get My Links back? Follow this post by Laura Rodgers and you should be able to access your MY LINKS. I followed the second method and I have a link to MY LINKS on the Top Bar in My Site.

In SharePoint 2007, MY LINKS are stored in the SSP Database not in My Site Content Database. So, If you upgraded to SharePoint 2010 using database attach to a new Environment and lost all your MY LINKS, here is post by Shane Young on how to retrieve them.

As always thanks to Laura Rodgers and Shane Young for their support to the SharePoint Community.

Fix Pre-Upgrade Check errors

July 30, 2010 4 comments

So before you upgrade to SharePoint 2010 from SharePoint 2007, it’s a written rule that you need to run Pre-Upgrade Checker which was introduced in SP2 and has been updated in October 09 Cumulative Update. You can read about the Pre-Upgrade Check here

The syntax for it is

STSADM -o preupgradecheck

When you run the Pre Upgrade Checker, you will get a report like this

There is a log file associated with the pre-upgrade check which you find at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Logs.

You can run the pre-upgrade check, any number of times and it will not make any changes to your farm. Even if you are not upgrading to SharePoint 2010, you should do this because it will give you nice report of your SharePoint including the size of farm,  any large lists etc. I think this is a great tool.

The report has all links to various KB  articles which will help you in troubleshooting a the various issues in the report.

So now, how to fix the errors shown in the pre-upgrade checker. Here we go

The first issue is the Missing server file or server configuration issue. You can read about this error here.

Part 1: Fixing Missing Web Part Issues

If you look at the first part of this issues, the pre-upgrade check is telling you that some web parts are being referenced but they are installed on the server. It should look something like this

The following web part(s) are referenced by the content, but they are not installed on the web server

  • Id = GUID, Type = Unknown, Reference = 2, Status = Missing

How to fix it? You got jump a few hoops to fix this issue.

First run this STSADM Command

stsadm.exe -o enumallwebs -includewebparts > N:\enumwebs.txt

Note: includefeatures, includesetupfiles, includewebparts, includeeventreceivers, and includecustomlistview were the new parameters for enumallwebs command included in the October 09 Cumulative Update

This would give you list of your webs in your farm and all the web parts installed.  Use CTRL F and search for MISSING which should show you the missing web part. It should look like this

The URL parameter next to web ID should lead you the web where this web part is missing.  Now to fix this web part, I followed the steps.

Go to the web part maintainance page, to do this add ?Contents=1 end the url.

For example: http://sitename/sites/site/default.aspx?contents=1

Thank You Shane Young for short cut, you can read more about the Maintenance here

You should see something like this

If you see the error, Select the error web part and delete it, this fixed one of my web part id error in pre upgrade check report.

If you don’t see the error, then you got a follow a longer way.

Consider my scenario, I have two farms; Farm A and Farm B.

We had a custom web part installed in Farm A but we never installed this web part in Farm B. We often move data from Farm A to Farm B using Export/Import, so I assumed that the data was referencing the custom web part in Farm even though we never installed this web part in Farm B. To prove my theory, I used few tricks.

Using the custom web part type name and assembly name we had on the Farm A, I was able to generate the GUID for the web part which matched with web part ID error on pre-upgrade check. To generate GUID I followed this blog.

Then installed the custom web part on the Farm B and this resolved one web part ID issue. To make sure, I ran the pre-upgrade check and this web part error was gone.

Part 2: How to Fix Missing Feature(s) Issue

If your data is referencing a feature and if the feature is not installed on the server, the pre-upgrade check will throw an error like below.

The following feature(s) are referenced by the content, but they are not installed on the web server

Name = Unknown, Feature id = GUID, Reference count = 43, Scope = Web, Status = Missing

These errors occur if you have faulty features in your Farm. You can delete these feature from the farm using Feature Admin Tool found here. This is a very handy tool, make sure you test before you remove these faulty features. Removing these features should fix most of the errors on the pre-upgrade check.

Hopefully this can help someone!

I am working on couple of upgrade projects and I will post any new findings.

Leave a comment if you have question.