Posts Tagged 'SharePoint'



PowerPivotGeek’s Tips, How-to, and A Peek Inside!

PowerPivotGeek has been doing a lot of GREAT posts the last week and its getting harder and harder to keep up with greatness!  Saying this, here are some great tips, how-to, and A Peek Inside!

Tips!

 

How-To

 

A Peek Inside!

Enjoy!

TechEd NorthAmerica 2010 Sessions

For a listing of PowerPivotGeek’s PowerPivot sessions at TechEd North America 2010 (also known as the BI Conference 2010), check out:

TechEd NorthAmerica 2010 Sessions.

One thing that is missing from this list is also the joint session between Rob Collie (@PowerPivotPro) and Dave Wickert whom will do a PowerPivot power chalk talk.  If you’re in New Orleans for the BI Conf / TechEd NA and into PowerPivot – these are your sessions!

PowerPivot Technical Diagram: PowerPivot Client/Server Architecture

Because PowerPivot for Excel and PowerPivot for SharePoint involve many components from SQL Server 2008 R2 Analysis Services, Office 2010, and SharePoint 2010, this poster contains all of the key components that make up PowerPivot in one view. This view includes nearly all of the logical architecture components and illustrates how these componets work together.

Included in this diagram are the components for:

  • PowerPivot for Excel
  • PowerPivot for SharePoint
  • Browser-Based Clients and their connection to PowerPivot
  • Data Import and Data Providers in relation to PowerPivot
  • Analysis Services Clients and their ability to connect to PowerPivot
  • Timer Jobs, Health and Usage Data Collection in relation to PowerPivot

For more information, please go to the reference sqlcat.com site: PowerPivot Technical Diagram: PowerPivot Client/Server Architecture

Why PowerPivot requires ‘classic-mode’ web applications

By powerpivotgeek (dwickert@hotmail.com), on April 22nd, 2010

SharePoint 2010 has a new ‘claims-based’ authentication system that allows you to use federated identities with SharePoint. And there are certainly some customers that are excited to start playing around with this capability. That is neat and cool and all . . . but that isn’t the major reason why folks should be getting excited about ‘claims’. It is just a side-effect. The real reason why SharePoint uses claims is to bypass the Kerberos requirement within the farm. This is a huge benefit for SharePoint. In SharePoint 2007 once you grow beyond a single machine, then you must configure Kerberos between all of the servers – this quickly becomes a huge problem and limits both SharePoint adoption and its growth because many customers do not have the infrastructure needed to run Kerberos. But before you get too carried away with claims, particularly with PowerPivot, you have to remember two things: (a) PowerPivot only support Windows users and (b) we don’t support claims integration down to the client. The first one is easy to understand as SSAS only supports Windows credentials – and Excel Services uses that to establish the Windows identity for the connection. Having claims down to the client means that the user can perform one login to SharePoint – and have it be remembered for all future logins.

Continue reading: Why PowerPivot requires ‘classic-mode’ web applications

Howto: Write to the ULS

By powerpivotgeek (dwickert@microsoft.com), on April 14th, 2010

As more and more folks start to get into PowerPivot and SharePoint, there is a need to programmatically write entries into the ULS. Since all of PowerPivot and all of SharePoint share this common logging infrastructure, why not also include log entries from your own processes. Here is some sample code for doing that:

First via PowerShell:

Continue reading Howto: Write to the ULS

Installing the right version of SharePoint

By powerpivotgeek (dwickert@microsoft.com), on March 4th, 2010

So you think that you have done everything right, but still SQL setup (in PowerPivot SharePoint integration mode) still reports “You don’t have a ‘Complete’ SharePoint installation.” How can this happen?

  • You might not have followed the installation guide. It tells you to first select “Farm” and then “Complete” on your first two screens after you enter your SharePoint product key. If you are installing on a domain controller, then the only selection that is supported is “Farm” and “Complete”, thus on a domain controller you won’t even be asked – it just defaults to this configuration. They don’t even offer you the possibility of running in an unsupported configuration. Just double check what you asked for. BTW: If you are running a RC0 version of SharePoint there is a known bug that a “Standalone” rather than “Farm” install is done. This is a RC0 only bug and it was fixed in a later build.

Read more…

Why you may want to use RBS for your #PowerPivot for #SharePoint Farm

By Denny Lee, Ed Campbell

Introducing RBS

So what is RBS and why would I want to use it in order to help my PowerPivot for SharePoint farm?  Well, RBS in this particular case is Remote Blob Store which was introduced as part of one of the SQL Server 2008 Feature Packs.  As of this post, the current version can be found in the SQL Server 2008 R2 November CTP Feature Pack (search SQL Server 2008 R2 Remote Blob Store).  Simply put, remote blob store allows you to put blobs outside of the SQL Server database so you can reduce the performance and manageability impact of storing blobs directly within the database.  For more information about RBS, please refer to the documentation linked below.

Read more…

PowerPivot for SharePoint Quick tip: Don’t forget to install Desktop Experience

For those of you who are using Windows 7 client, you should be good-to-go already because you already have Desktop Experience installed.  But if you are using a Windows Server  OS (e.g. Windows Server 2008, Windows Server 2008 R2), you will need to install it as part of an additional feature via the Server Manager.

Why you ask?

Read more…

Cannot add the specified assembly to the global assembly cache

By Lee Graber (leegr@microsoft.com), on February 12th, 2010

This is part of my continuing series on debugging SharePoint and PowerPivot. In this case, I do not expect any PowerPivot users to ever encounter this error in the context of PowerPivot. However, the general SharePoint developer who is in the early stages of building and testing his custom solutions might hit this and since so many people on our team have been confused by it, I thought I would throw out some help for other developers. This error is hit when trying to deploy a SharePoint solution package to the farm. It could be an ApplicationServer solution or a WebFrontEnd solution, the important part is that it has an assembly marked to be deployed to the GAC:

Read more…

The data connection uses Windows Authentication and user credentials could not be delegated

By Lee Graber (leegr@microsoft.com), on February 8th, 2010

This is one of the two main errors that users could see from Excel Services when using PowerPivot. This is encountered when refreshing PowerPivot data connections or performing an action which requires re-querying the PowerPivot database, such as clicking on a slicer or expanding a node in a pivot table. To debug, some level of understanding of what Excel Services is doing is required. For this, I recommend reading an earlier post on this blog by Dave … http://powerpivotgeek.com/2009/12/11/excel-services-delegation/. In general, this is an add-on to Dave’s post which is a quick summary of how to debug this error.

Read more…

« Previous PageNext Page »



Follow

Get every new post delivered to your Inbox.