If SharePoint is being used with a Publishing Site and the following error message is displayed within ULS Logs or Event Viewer:

“Object Cache: The super user account utilized by the cache is not configured”

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 be build up from scratch again. Files and information will be retrieved from the database and the file system and the page will be rendered. This means an extra hit on your SharePoint and database servers and a slower page load for your end user.

There are two ways to fix this and it is well documented over here TechNet: Configure Object Cache User Accounts in SharePoint Server 2013

 

The problem was that even after I had configured the same, I got the following when browsing back to my site.

Say what?!!

Turns out, it was because I had been using a Claims Based Authentication.

For most scenario the following piece of code is more than sufficient:

1
2
3
4
5
6
7
$w = Get-SPWebApplication "http://<server>/"

$w.Properties["portalsuperuseraccount"] = "domain\superuser"

$w.Properties["portalsuperreaderaccount"] = "domain\superreader"

$w.Update()

 

And for the Claims based sites, the following code needs to be executed instead:

1
2
3
4
5
6
7
$w = Get-SPWebApplication "http://<server>/"

$w.Properties["portalsuperuseraccount"] = "i:0#.w|domain\superuser"

$w.Properties["portalsuperreaderaccount"] = "i:0#.w|domain\superreader"

$w.Update()

That should solve the problem.

Cheers