Unfortunately, the Health Checker won’t tell you about it but the System Application Event Log does. If you are running slow, check the Application Log (Start > Administrative Tools > Event Viewer then click on the Application Log) and usually, SharePoint will start displaying an error regarding the SharePoint Cache.
The error states that the SharePoint Cache is not working properly due to the Super Reader account being set to LOCAL SERVICE (usually, but it may be another account) – the issue of course being that that account does not have any access to the SharePoint database. A rarity, SharePoint actually tells you how to fix the problem however, there’s not much information about what account to use – the message in the event log shows:
To configure the account use the following command ‘stsadm -o setproperty -propertyname portalsuperreaderaccount -propertyvalue account -url webappurl’. It should be configured to be an account that has Read access to the SharePoint databases.
As it turns out, the BEST account to use is either the Application Pool account running the SharePoint Site or alternately the account assigned as the Content Access account. Note that in most of my installs, I use SPAppPool; this seems to have the proper read access vs. the Content Access account. If you use an account that does not have adequate access, the site won’t render at all (I have actually lost a site and could not reset it).
The account must be specified using the full domain name – so assume MYDOM using a Site URL of http://sp2010.intranet.com, to correct the issue, you need to open up a command window (cmd) as an Administrator then go to the SharePoint bin folder in the hive (c:\program files\common files\microsoft shared\web server extensions\14\bin) then enter the following STSADM command:
stsadm -o setproperty -propertyname portalsuperreaderaccount -propertyvalue MYDOM\SPAppPool -url http://sp2010intranet.com/
After you run this, enter:
If you are running multiple servers, you have to run IISReset on all of them (the STSADM command should only be run once on the server running Central Administration)
David Sterling, Sterling International Consulting Group – Maine/North Carolina Microsoft Partner