The Secondary Logon service is used for PowerPivot Workbook Thumbnail generation.  According to the PowerPivot 2012 Health rule reference (http://msdn.microsoft.com/en-us/library/hh230899.aspx),it is recommended to change the Secondary Logon service to a Startup Type of Manual, but the Health Rule checks if the Secondary Logon service has a Status of Running, not a Startup Type of Manual (or Automatic):

I’m unsure as to which is correct, the health rule itself or the health rule reference text, but to avoid this health rule from generating an error, make sure the Secondary Logon service is set to Automatic and Started on all SharePoint Servers in the farm.

This is not fixed in SQL 2012 Cumulative Update 1.

When PowerPivot runs the health rule, PowerPivot: ADOMD.NET is not installed on a standalone WFE that is configured for central admin, it checks for a file version of “11.0.0.0”:

The file version is passed from this property in Microsoft.AnalysisServices.AdomdClient.AdomdConnection:

The FileVersion property of the Microsoft.AnalysisServices.AdomdClient.dll (for SQL 2012) is:

11.0.2100.60 ((SQL11_RTM).120210-1917 )

Since that doesn’t compare to “11.0.0.0”, the rule fails.  This rule can be ignored for now, just make sure the proper Microsoft.AnalysisServices.AdomdClient.dll is installed at C:\Windows\assembly\GAC_MSIL\Microsoft.AnalysisServices.AdomdClient\11.0.0.0__89845dcd8080cc91\.

7/22/2011: This issue is resolved in SQL Server 2008 R2 SP1 (applied to the PowerPivot instance on SharePoint).

I have an ongoing issue where the PowerPivot Management Dashboard in the Silverlight control just displays a Red X, and the Activity List is blank, no matter how many PowerPivot-enabled workbooks you interact with.  When viewing the Management Dashboard, the following error in the ULS log is present:

03/24/2011 14:18:57.16 w3wp.exe (0x0DFC) 0x0598 SSAS Mid-Tier Service Request Processing 106 High Error loading history for workbook history bubble chart eb9fce20-5fa7-4395-b7c5-03a79648e8cf

03/24/2011 14:18:57.16 w3wp.exe (0x0DFC) 0x0598 SSAS Mid-Tier Service Request Processing 99 High EXCEPTION: System.NullReferenceException: Object reference not set to an instance of an object. at Microsoft.AnalysisServices.AdomdClient.AdomdDataReader.GetString(Int32 ordinal) at Microsoft.AnalysisServices.SharePoint.Integration.WorkbookHistoryDataProvider.GetHistory(WorkbookHistoryDataSet& historyDataSet) at Microsoft.AnalysisServices.SharePoint.Integration.WebServices.PowerPivotOperationsServiceImpl.GetWorkbookHistory(WorkbookHistoryDataSet& history) eb9fce20-5fa7-4395-b7c5-03a79648e8cf

In speaking with MS PSS, they let me know that this is an issue if you installed any SharePoint Cumulative Updates prior to installing PowerPivot.  If you install SharePoint RTM, then PowerPivot, then any updates, this error will not appear.  PSS is working with development and product managers to resolve the issue (namely being certain tables in the Usage database do not contain primary keys).

When installing PowerPivot in a multi-WFE scenario, you may need to manually register the Microsoft.AnalysisServices.ChannelTransport.dll on WFEs that do not have PowerPivot installed.

To do this, run a command prompt with an Administrator token.  Navigate to (and this path may change in the future, but hopefully not):

C:\Windows\assembly\GAC_MSIL\Microsoft.AnalysisServices.ChannelTransport\10.0.0.0__89845dcd8080cc91\

Once in that directory, run:

Reanalyze the problem in Health Monitor and the issue will disappear.