SSRS SharePoint 2013 Create Service Application error: Could not find SOFTWARE\Microsoft\Microsoft SQL Server\110 registry key Error

This post falls under the category, things to remember when installing the Reporting Services SharePoint add-in for SQL 2012

In order to get SSRS for SharePoint to work the RS Add-in must be installed on all app servers in the Farm, if you are averse to waiting for huge .iso files to copy from server to server, the pain of the SQL Installation and decide to download the SQL Server® 2012 SP1 Reporting Services Add-in for Microsoft® SharePoint don’t. This installer does not create the required registry setting on the app servers where you have not installed the full SSRS for SharePoint Integrated Instance. Use the SQL Server installation .iso select the RS Add-in for SharePoint from the feature selection and things start to work, more up front work, much less back end pain.


The user is not a farm administrator. Please address the validation failures and try again – PowerPivot Configuration Tool

I was installing PowerPivot for SharePoint on a new app server in a multi server farm and came across the following error, “The user is not a farm administrator. Please address the validation failures and try again.”, problem is the PowerPivot install account was the Farm Admin, the SharePoint install was done with the Farm Admin account, the Farm Admin had all access required. So after scouring the internet and trying everything that I could find

  • Install PowerPivot addin on all servers in the farm
  • Remove Farm Admin from admin group, re add Farm Admin to admin group
  • reinstall all components using SharePoint install account

I remembered that when I ran the SharePoint Configuration wizard to add the new app server to the existing Farm, I referenced the Farm to join with an IP rather than a Computer name, this led to the ultimate solution:

  • Uninstall everything (SharePoint and PowerPivot for SharePoint)
  • Install SharePoint
  • Run configuration wizard, be sure to reference the Farm by Name not IP
  • Install PowerPivot for SharePoint
  • Run the PowerPivot for SharePoint 2013 Config tool

Issue resolved, loud Arg, Sigh of relief

Remove Left Navigation Bar – SharePoint 2013

Little trick to hide only the Left Quick Launch bar in SharePoint 2013.

  • Place a content editor Web Part to your page
  • paste the following code into the HTML Editor

.ms-core-sideNavBox-removeLeftMargin{ DISPLAY: none }
#contentBox { margin-left: 20px }

watch it vanish.

If you want to hide both top and bottom quick launch bars see the post below

SQL 2012 – Exciting times

Just installed SQL 2012 and it was the most pleasant installation experience that I have had with SQL Server, no work arounds or config file modifications; double clicked setup.exe and clicked next until finished. Make sure you uninstall any Denali/2012 pre RTM instances including PowerPivot that you may have and remove old Denali/2012 PowerPivot and SSRS service applications in SharePoint Central Admin

SQL 2012 Release Candidate 0

Just installed SQL 2012 RC0 specifically to check out the new stuff in Power View, have a look at to see all cool new features, however there are few things that I would have loved to have seen included.

– Support for Hierarchies

– Cards or Tile region slicers, the addition of grid filters is cool, but if you are filtering cards within a region that contains a grid with related measures it does not get filtered.

– Font control within grids and cards

– Image size control

– Dimension attribute aliasing

– The abilty to publish documents that cannot be edited.


PPS Cascading Filters Save the Day

The Scenario:

Time Intelligence filter based on a typical date dimension filtering scorecard and Analytical reports, needed to add an Excel Services Report with a Parameter based on the Year attribute of the time dimension. I tried connecting the TI filter to year parameter available in the Excel Services report with a connection formula like: EXISTS([Date].[Years].members, <<UniqueName>>,”MeasureGroup”) expecting it to work, problem was that excel did not like it. Cascading filters to the rescue.

The Solution:

Created a Member Selection filter from the descendants of the Years Attributes, connected the TI filter to the Member Selection filter with the above connection formula, passed the member selection filter to the report, excel is happy again

The Gotchas:

– Cascading Filters filter Nulls, so if you need to return members that are in fact null you need to create a plug measures and set that as your filter measure

– Member Selection filters not based on a Function like Children or Descendants that you pass a connection formula into get created with a ‘With Set’ Expression and not the expected ‘strtoset’ expression and do not work very well (my experience anyway)

Will post a how to shortly.

Migrating Custom SharePoint Column nightmare

Well I had to migrate custom columns from one SharePoint 2010 environment to another, thanks to the following post, I was able to script it and migrate.

Easy right, not so fast, went to check my columns out and got this great error when accessing site columns under site settings

Field type  is not installed properly. Go to the list settings page to delete this field.

Turns out I made a typo and left a column type blank. after scouring the internet, i came across somebody brave enough to delete from the content database.

So I looked in the contenttypes table in the Content DB, found the offending record, deleted it and SharePoint started to work again.

I hope this helps.