Shawn Fletcher on Fri, 11 Jan 2013 17:38:33
I have a SharePoint 2010 Server with SQL 2012 PowerPivot for SharePoint installed. All was working fine until a round of Windows updates which included SQL 2012 SP1. After that SharePoint Health Analyzer was reporting the following:
The SharePoint Health Analyzer detected an error. PowerPivot: PowerPivot: The deployed farm solution is not up-to-date.
PowerPivot: The deployed farm solution is not up-to-date.
PowerPivot: Make sure that farm solution is up-to-date. For more information about this rule, see http://go.microsoft.com/fwlink/?LinkID=208180
I then ran the PowerPivot Configuration Tool which said that "Newer versions of the Powerpivot solution files have been detected. Please select the upgrade option to upgrade your farm. I clicked ok and ran the Upgrade Features. I clicked Validate and then Run. The tasks fail at Update PowerPivot Assembly Information with the following error:
"Upgrade Solution File and Assembly Information Update PowerPivot Assembly Information Failure while running action: Update PowePivot ASsembly Information Set-PowerPivotSystemService : Microsoft SharePoint is not supported with version 4.0.30319.296 of the Microsoft .Net Runtime."
I found and followed this article:
I looked up this error and found that my PowerShell was indeed running 3 0 -1 -1.
I'm not sure how to get these powershell scripts to run correctly using the configurator.
Currently none of our PowerPivot workbooks are able to refresh data.
Elvis Long on Wed, 16 Jan 2013 08:31:34
Could you please help to collect the data refresh log information to us? They are benefit for us to troubleshoot this issue.
Configure and View SharePoint Log Files (PowerPivot for SharePoint): http://msdn.microsoft.com/en-us/library/85f62d29-cdc6-45b3-be1f-ff1182939858
Furthermore, here is an article about Upgrade PowerPivot for SharePoint (PowerPivot Configuration Tool):
TechNet Community Support
Shawn Fletcher on Wed, 16 Jan 2013 23:00:23
Thank you for the reply. I have turned on the verbose logging as described in the article and attempted to refresh the PowerPivot worksheet.
How should I send the log file to you?
Ivan Sanders on Mon, 28 Jan 2013 11:29:05
Is this installation on Windows server 2012?
Right Click on the SharePoint Management Shell Shortcut > and replace the following shortcut target:
C:\Windows\System32\WindowsPowerShell\v1.0\PowerShell.exe -NoExit " & ' C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\POWERSHELL\Registration\\sharepoint.ps1 ' "
With the following Shortcut Target:
(Note the difference and placement between the existing and the new Shortcut target location > -Version 2):
C:\Windows\System32\WindowsPowerShell\v1.0\PowerShell.exe -Version 2 -NoExit " & ' C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\POWERSHELL\Registration\\sharepoint.ps1 ' "
This will run the SharePoint Management Shell with the correct version. Next try running the PowerPivot Configuration Tool (Not the 2013 version), if it completes you should be good to go. If there is a problem run the following PowerShell command.
Add-SPSolution –LiteralPath “C:\Program Files\Microsoft SQL Server\110\Tools\PowerPivotTools\ConfigurationTool\Resources\PowerPivotFarm.wsp”
If you need additional help with PowerPivot PowerShell commands run the following:
and if you need an example ho to create a PowerPivot service application
Get-help new-powerpivotserviceapplication -example
Please reply to this post regardless of the outcome so that we know that you have resolved the issue or that we need to provide additional assistance.
Jarrod C Miller on Fri, 22 Mar 2013 18:46:54
Ivan, the above answer is for running the management shell. I am experiencing the same problem shawn is in that:
Update PowerPivot Assembly Information
Set-PowerPivotSystemService : Microsoft SharePoint is not supported with
version 4.0.30319.296 of the Microsoft .Net Runtime.
At line:1 char:79
it appears the powerpivot configuration tool is compiled for powershell which worked fine until powershell -version 2.0 is required for working with sharepoint 2010.
Shawn, were you able to get resolution somewhere? I have searched all day with no luck.
Shawn Fletcher on Fri, 22 Mar 2013 18:59:07
I never did find an answer unfortunately. It was a development site and we decided to scrap it and start a new one with SharePoint 2013.