The super user account Config error resolving

If you have a SharePoint Publishing site and you check the event viewer, you might see the following warning:

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 unnecessary 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

This means that the cache accounts for your web application aren’t properly set and that there will be a lot of cache misses. If a cache miss occurs the page the user requested will have to build up from scratch again.

Solution

The way to correct this problem is to first create two normal user accounts in AD. These are not service accounts. You could call them domain\superuser and domain\superreader.

The domain\superuser account needs to have a User Policy set for that gives it Full Control to the entire web application. In order to do this the following steps need to be performed:

– Go to Central Administration
– Go to Application Management
– Go to Manage Web Application
– Select the web application we’re talking about
– Click User Policy
– Add Users
– Click Next
– Fill in domain\superuser
– Select Full Control
– Click OK

The domain\superreader account needs to have a User Policy set for that gives it Full Read to the entire web application. In order to do this the following steps need to be performed:

– Go to Central Administration
– Go to Application Management
– Go to Manage Web Application
– Select the web application we’re talking about
– Click User Policy
– Add Users
– Click Next
– Fill in domain\superreader
– Select Full Read
– Click OK

If you are using classic mode authentication run the following PowerShell cmdlets on one of your SharePoint servers:
$w = Get-SPWebApplication “http:///”
$w.Properties[“portalsuperuseraccount”] = “domain\superuser”
$w.Properties[“portalsuperreaderaccount”] = “domain\superreader”
$w.Update()

If you are using claims based authentication run these cmdlets on one of your SharePoint servers:
$w = Get-SPWebApplication “http:///”
$w.Properties[“portalsuperuseraccount”] = “i:0#.w|domain\superuser”
$w.Properties[“portalsuperreaderaccount”] = “i:0#.w|domain\superreader”
$w.Update()

After you’ve run these PowerShell cmdlets you need to perform an IISRESET to finish it off.
Now you should be freed from the warnings in the event viewer.

Leave a Reply

Your email address will not be published. Required fields are marked *