By powerpivotgeek (firstname.lastname@example.org), on July 12th, 2010
Oh the joys of SharePoint again. I just responded to an internal posting where someone was raising the issue that “Path not found” errors were being reported when Excel Desktop tried to publish a workbook to SharePoint. Again, this isn’t PowerPivot directly, but it can be reported as a PowerPivot problem if the workbook contains PowerPivot data.
Continue Reading: If running on Windows Server, make sure you have ‘Desktop Experience’ feature turned on
By powerpivotgeek (email@example.com), on July 12th, 2010
So . . . here I am playing around with PowerPivot to get ready for a demo. As this is a group from the SharePoint dev team (actually SharePoint Online), I wanted to include some cool SharePoint functionality into the demo. Trying to be cool and ‘wow’ them, I decide to use a SharePoint list as a data source. I want to show the data mashup capabilities of PowerPivot so I have the bulk of my demo come from the Contoso sample database (the three product catalog tables) and the 4 million row Sales Fact table.
I create my SP list by extracting the 11 distinct manufacturers – and I assign them to a ‘shipper’ that I made up.
Continue reading: Using a SharePoint list as a data source
By powerpivotgeek (firstname.lastname@example.org), on June 17th, 2010
Recently ran into this situation: Customer installed the wrong PowerPivot bits on their machine. They were running on a 64-bit OS with Office 2010 x64, but installed PowerPivot for Excel 32-bit. Everything installed OK, but when they clicked on the PowerPivot tab in Excel; then the PowerPivot Window they received the following error:
Click through to continue reading.
PowerPivotGeek has posted some mightly good stuff concerning the installation and uninstallation of PowerPivot. The quick summaries are:
Compliments of PowerPivotGeek!
May 23, 2010 by dennyglee | Edit
As you may have noted in my original posting Delegation, Claims, Active Directory…Oh My!…Aw Crap!, it quickly described how to solve issues surrounding the delegation of the claims token within an Active Directory environment. In it I referenced Lee Graber’s excellent posting: The data connection uses Windows Authentication and user credentials could not be delegated.
By powerpivotgeek (email@example.com), on April 7th, 2010
For all of you that are running a combined all-in-1 system, i.e. domain controller, SharePoint and all of PowerPivot (desktop + server), you will notice that if you are trying to debug with non-administrator accounts that you can no longer remote desktop on to your machine. This is because by default only administrators are allowed to remote desktop onto a domain controller. To allow all Remote Desktop users that right:
- Click on Start and type “gpedit.msc” into the Start Search box
- Navigate to “Computer Configuration – Windows Settings – Security Settings – Local Policies – User rights Assignment”
- Click on “Allow log on through Terminal Services”
- You will notice that only Administrators are listed. Add “Remote Desktop Users”
Continue reading: Giving remote users rights to log on to your domain controller
Published March 25, 2010
By powerpivotgeek (firstname.lastname@example.org), on March 25th, 2010
Recently we been hit with a rash of inquiries around whether folks should install the 32-bit version of the PowerPivot client, or go with the larger capacity 64-bit version. Office 2010 is the first version of Office to offer a native 64-bit option. In previous releases, you had to install the 32-bit version to run under WOW (Windows-On-Windows) mode. WOW emulates a 32-bit environment under the 64-bit OS. That is cool and all, but you were still limited by the 32-bit address space (2GB of memory). Now with Office 2010 64-bit the memory use is virtually unlimited for a client application.
So where to begin . . . Being a geek, let’s start off with a technical topic. When you are running in a 64-bit process, then you can only use dlls and other executables that are build as native 64-bit applications. Therefore whatever our choice, 32-bit or 64-bit, the ‘bit-ness’ of our approach has to hold for the entire process. For example, if we pick 64-bit, then we need the 64-bit version of Excel 2010, we need the 64-bit versions of any add-ins, such as PowerPivot for Excel, and we need 64-bit versions of any OLE DB providers or ODBC drivers (using the 64-bit version of the OLE DB Provider for ODBC here). So let’s keep that in mind.
Ok, here we go:
By powerpivotgeek (email@example.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.
By Denny Lee, Ed Campbell
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.
Published February 24, 2010
By powerpivotgeek (firstname.lastname@example.org), on February 24th, 2010
A trick for the client-side folks doing build-to-build reinstallations (or if you wish to clear all of the PowerPivot code from your client): besides uninstalling “Microsoft PowerPivot for Excel” (via control panel Add/Remove/Uninstall Programs, the exact wording varies depending on the OS you are running), you may also have to delete files in: