If you check the event log on a sharepoint system you might see the following erros “Object Cache: The super reader account utilized by the cache does not have sufficient permissions to SharePoint databases.” or “Object Cache: The super user account utilized by the cache is not configured.”. But how can you solve that?
The full error message you might see in the event logs are:
Object Cache: The super reader account utilized by the cache does not have sufficient permissions to SharePoint databases.
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.
 Additional Data:
 Current default super reader account: NT AUTHORITY\LOCAL SERVICE
and
Object Cache: The super user account utilized by the cache is not configured. This can increase the number of cache misses, which causes the page requests to consume unneccesary system resources.
 To configure the account use the following command 'stsadm -o setproperty -propertyname portalsuperuseraccount -propertyvalue account -url webappurl'. The account should be any account that has Full Control access to the SharePoint databases but is not an application pool account.
 Additional Data:
 Current default super user account: SHAREPOINT\system
 To solve these issue you need to configure the “object cache user accounts” as mentioned here.
1.) create two new ActiveDomain users (no service accounts, only two “taskuser” accounts). For Example:
contoso\SpFarm1SuperUser.1
contoso\SpFarm1SuperReader.1
 2.) Go to Central Administration
3.) Go to Application Management
4.) Go to Manage Web Application
5.) Select your web application we’re talking about (e.g. Sharepoint – 80)
6.) Click User Policy
7.) Add Users
8.) Select “All Zones” here. If you didn´t have zones configured this box will not come up.
9.) Click Next
10.) Fill in contoso\SpFarm1SuperUser.1
11.) This account needs to have a User Policy set for that gives it Full Control to the entire web application, so select “Full Control” here.
12.) Click OK
13.) Click User Policy
14.) Add Users
15.) Click Next
16.) Fill in contoso\SpFarm1SuperReader.1
17.) This account needs to have a User Policy set for that gives it Full Read to the entire web application, so select here “Full Read”
18.) Click OK
19.) Make a note of the both usernames you just added. If your web application is using claims based authentication the users should be displayed like “i:0#.w|contoso\spfarm1superuser.1” and “i:0#.w|contoso\spfarm1superreader.1”.
 20.) Assign the right values to the properties of the web application. If you are using classic authentication you could use the following command:
$w = Get-SPWebApplication -Identity "http://<server>/" $w.Properties["portalsuperuseraccount"] = "contoso\SpFarm1SuperUser.1" $w.Properties["portalsuperreaderaccount"] = "contoso\SpFarm1SuperReader.1" $w.Update()
 If you are using claims based authentication run these cmdlets on one of your SharePoint servers:
$w = Get-SPWebApplication -Identity "http://<server>/" $w.Properties["portalsuperuseraccount"] = "i:0#.w|contoso\spfarm1superuser.1" $w.Properties["portalsuperreaderaccount"] = "i:0#.w|contoso\spfarm1superreader.1" $w.Update()
 You can put the content to a textfile (ANSI-encoded) and save it to SetUsers.ps1 then you can run it via poweshell: ./SetUsers.ps1
 21.) After you’ve run the PowerShell cmdlet you need to perform an IISReset or reboot the complet server.
If you perform a IISReset your users will be disconnected!
Â
