Are you ready for the Microsoft Private Cloud?

On February 21 & 22 there is a 2-day virtual training event to learn about the upcoming enhancements with the Creating & Managing a Private Cloud Event Agenda Day 1: Deployment & Configuration (Feb. 21)
•Part 1: Understanding the Microsoft Private Cloud
•Part 2: Deploying the Infrastructure Components
•Part 3: Deploying the Private Cloud Infrastructure
•Part 4: Deploying the Service Layer
•Part 5: Deploying the Applications & VMs Day 2: Management & Operations (Feb. 22)
•Part 6: Managing the Infrastructure Components
•Part 7: Managing the Private Cloud Infrastructure
•Part 8: Managing the Service Layer
•Part 9: Managing the Applications & VMs Register at:

SharePoint database is currently running in backwards compatible mode

The other day I saw an error on my SharePoint environment stating the following error
“SharePoint object [SPContentDatabase Name=SharePoint_AdminContent_c8de0fec-7405-48f2-9fef-ed15ae4b1125] is currently running in backwards compatible mode. Please fully upgrade it to ensure optimal performance from this object” So, what exactly is the message all about, let us understand. The “Backward compatibility Mode” has been newly introduced in SharePoint 2010.This is a new feature in SharePoint 2010 which allows you to defer the database upgrade even though the binaries on your server are upgraded. So what does that mean Following scenario depicts how you could enter a “Backward compatibility Mode” (either planned or accidental as in my case)

  1. You install a service pack in your SharePoint environment successfully
  2. But you do not run the “SharePoint Configuration Wizard” which is responsible to update the database or do not run psconfig (for advanced users)

The above steps leave your databases in a “backward compatibility mode”. i.e. When the database upgrade is deferred, the databases enter the “backwards compatibility mode” Pros:

  1. Defer update of database to later date/time to avoid immediate downtime and support high availability for users (The accepted duration of running in this mode would be few days or maybe a week but not more than that)


  1. Running for long durations in this mode could lead to undesired results

Catch: This mode works on a baseline as to what should be the minimum version of database you should be running (if you choose to upgrade the database at a later date). The backward compatibility mode is supposed to be re-based lined with each Service Pack releases, i.e. Service Packs should introduce a compatibility boundary. A compatibly boundary would mean that after a particular Service Pack deployment, we would not be able to upgrade binaries on the server and defer database upgrade. The supported baseline is N-1 range of binaries on servers to database backwards compatibility where N equals to Service Pack build. Example:

  1. You install SP1 for SharePoint but do not run “SharePoint Configuration Wizard” and hence you enter “backward compatibility mode”
  2. Should you need to install future SP (e.g. SP2) (N) then you must be at least running the database version SP1(N-1)

SharePoint Client Object Model: Read MultiLineText as Plain Text

While working with SharePoint Client Object Model there might be a need to retrieve value of a multiline rich text as “plain text. Let’s show you how

static void Main(string[] args)
string siteUrl = "http://yoursiteUrl";

ClientContext clientContext = new ClientContext(siteUrl);
var web = clientContext.Web;
var list = web.Lists.GetByTitle("MyList");

var itemId = "1";
var listItem = list.GetItemById(itemId);

//load listitem values as text
var itemFieldValues = listItem.FieldValuesAsText;


//retrieve the multiline field value as text
string multitextValue = itemFieldValues["MyMultiLineTextField"];


Azure Pricing Calculator

The other day while searching around for some information related to Windows Azure I came across the Azure pricing calculator.Very helpful!! Azure Pricing Calculator: Azure Pricing Calculator (Advanced):

“Cannot generate SSPI context" error message when you access SharePoint

If you try to Google for this issue you will get various resolutions including a Microsoft support article as well (which are valid for the issue resolution) However, when I received the same error the source of the error in my case was different. In my case the domain controller was not running and was the cause of the issue (I use virtual machine for my domain controller which stopped due to some error) So, next time if you get this error than one of the check points should be if the domain controller is up and running.