Because PowerPivot for Excel and PowerPivot for SharePoint involves so many components from SQL Server 2008 R2 Analysis Services, Office 2010, and SharePoint 2010, this poster provides an end-to-end view of the PowerPivot Security Architecture in one view. This view includes nearly all of the logical security surface areas and illustrates how these systems interact.
Included in this diagram are:
- Service Accounts
- SharePoint Databases
- Security Hardening
- Automatic Data Refresh
- User Identity Flow
- PowerPivot Permissions Levels
Please click through to continue reading: PowerPivot Technical Architecture Diagram
by Kasper de Jonge
In my previous blog posts we made use of a published PowerPivot workbook to use a datasource. In this post we are going to discover what goes on under the hood when you call a PowerPivot workbook on a SharePoint 2010 server.
Read more …
Note from Denny: While Kasper has his own excellent blog, I thought it would be nice to reference his blog posting at PowerPivotTwins.com since its a great quick read to explain what happens. Enjoy!
By powerpivotgeek (email@example.com), on December 11th, 2009
I am inspired by a recent post from a colleague about the various issues that can come up with Excel Services delegation (see a Denny Lee’s blog here: http://dennyglee.com/2009/11/18/troubleshooting-powerpivot-excel-services-connectivity/) and I wanted to take it a bit further (and maybe a bit ‘geekie’-er)
First, why is this a problem? After all, as you can see in Denny’s post, you can see the workbook and you even have a thumbnail for it in the Gallery. What’s up here? The core of the problem is that unless you’ve set the connection to refresh when you first open the workbook, Excel Services uses its pivot cache to construct the pivot table and slicers. It is only if you manually refresh the connection, or click on a slicer, that you make an actual connection to the embedded data. Until then you are just looking at cached information. Until you click on a slicer, you don’t really know if Excel Services is working – so a strong recommendation that I make to any person doing a validating their installation is to “ALWAYS CLICK ON A SLICER” if you want to make sure that your installation is working properly.
Hats off to Dave Wickert (one half of the PowerPivot Twins!) – he’s been blogging like there’s no tomorrow and it’s getting harder and harder to keep up! Saying this, he’s included on his blog, PowerPivotGeek.com, two great tips for PowerPivot:
1) Ensure when you install Excel 2010 that you also install Office Shared Tools, it contains VSTO which is necessary for the PowerPivot add-in to work properly. You can read more in his posting: And oh, you need this one more thing.
2) When you save your workbooks, save them in cell A1 so that way when your workbook is saved to SharePoint, Excel Services will render the workbook properly centered. For more info, check out his posting: Another tip – always save your workbooks at cell A1.
You’re on your way to PowerPivot for SharePoint functionality – you’ve uploaded your PowerPivot for Excel workbook to your SharePoint PowerPivot Gallery. You view the thumbnails of your report and they look nice.
From the thumbnail, you click on the report you want to see, and the report renders nicely.
But then you click on a slicer, and then all of a sudden you get an error like the one below.
What can you do?