PowerPivot was a great new tool when it released several years ago. Now the newest version is out along side SQL Server 2012.You can still install the 2008 R2 version of PowerPivot or you can try out the new 2012 RTM version. There are some nifty improvements that Devin Knight has chronicled (Blog | Twitter). There are several requirements that are not part of the 2008 R2 requirements. The install instructions are the following with the first step being the new requirements:
- Install .NET Framework 4.0 and Visual Studio 2010 Tools for Office Runtime.
- If you are running Windows Vista or Windows Server 2008, install the platform update.
- Install Microsoft® Office 2010.
- Install PowerPivot for Microsoft Excel
There are plenty of blogs out there discussing the error message that says you need to install the proper version (32 bit or 64 bit) because you downloaded the incorrect one for the version of office installed. However, I installed both the prerequisites (.Net 4 and Visual Studio Tools) and still had the following error:
“Microsoft SQL Server 2012 PowerPivot for Excel Setup
Setup is missing prerequisites:
This add-in requires the Microsoft Visual Studio 2012 Tools for Office Runtime and the .NET Framework 4.0. For more information, go to <some website URL>”
Come to find out if you have both of these already installed and then try to install PowerPivot and get this error message the fix is pretty simple and one that is not listed on the Microsoft page about the install.
You have to install the components in a certain order:
- .Net Framework 4.0
- Microsoft Visual Studio 2010 Tools of Office Runtime
- PowerPivot 2012 for Excel
The problem I had was installing the Visual Studio 2010 Tools, then .Net Framework 4.0 then PowerPivot. Luckily you don’t need to roll everything back. Simply uninstall the Visual Studio 2010 Tools and reinstall them, this way they are put on the system AFTER .Net 4. I tried running a repair on the Visual Studio Tools about 4 times at different point after the .Net 4.0 install was finished with no luck. I did a simple uninstall and immediate reinstall and everything worked PERFECT!
So when setting up PowerPivot 2012 be sure to install in the order listed above. If you do switch number 1 and 2 just uninstall the Visual Studio Tools and run the install again. Worked like a charm.
[…] Read this article: SQL Server 2012 PowerPivot for Excel Prerequisites Error » Bradley … […]
Saved my day!
Thanks for taking the time to post this fix. I’ve been using the older powerover and wanted to use the new dax functions in the 2012 version. I tried following your instructions, even went a step further and completely uninstalled the .net framework and Visual Studio 10 and reinstalled them in the proper order but I am still getting the error…any other issues that you may have ran into that could help me out?
When you say you uninstalled Visual Studio 10, do you mean actual Visual Studio 2010 or do you mean the Visual Studio 2010 Tools for Office Runtime?
You’re a miracle worker. This is the only post on the web that solved my problem. Take a bow.
THANK YOU! Had 2 servers out of 10 that wouldn’t install and spend ages trying to find out why….
Same problem with Windows Server 2008 R2 64bits and Office 2012 32bits. Uninstalled the Tool and it’s now working.
Thanks a million! This has been a big problem for me for the last 4 mounths, but your advise was spot on! I own you a cup-of-something next time you are i Copenhagen.
Thank you. This helped.
THANKS!!! Worked great
Thanks.Wow its really work 🙂
[…] SQL Server 2012 PowerPivot for Excel Prerequisites Error » Bradley …Apr 5, 2012 … PowerPivot was a great new tool when it released several years ago. Now the newest version is out along side SQL Server 2012.You can still … […]
Hi Bradley … thanks for the article. I did what you have said. I have windows 7 professional. I uninstalled SQL Server and the .net framework 4.5 and started from there by installing the .net 4.0 framework, then visual studio for office 2010 (64 bit) and then tried the PowerPivot. I still get the same error. Any ideas?