Keith Smith - Think Ahead. Learn More. Solve Now!

Sharepoint

Keith Smith - Think Ahead. Learn More. Solve Now! > Sharepoint

The super user account utilized by the cache is not configured

Wednesday, April 19, 2017 - Posted by Keith A. Smith, in Sharepoint

SharePoint: Event ID: 7362: The super user account utilized by the cache is not configured


ProblemAngry
You encounter the following error appears in the Windows Application event log:
Log Name:      Application
Source:        Microsoft-SharePoint Products-Web Content Management
Date:          <date>
Event ID:      7362
Task Category: Publishing Cache
Level:         Warning
Keywords:      
User:          <username>
Computer:      <server>
Description:
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 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: [MachineName]\system SharePoint 2010 is hosted on this machine.

SolutionSmile
On new installations, the SharePoint super user account is configured to run under the machine's local System account.  However, this causes complications and thus the warning.  This should be addressed during setup, but isn't included in the setup wizard.  Anyway, resolving it is simple.  There are two ways: using STSADM or using Powershell.  We'll go through both here.

Step 1: Create Super User and Super Reader Domain Accounts
Create super user and super reader domain accounts
Example: DOMAIN\sp_superuser, DOMAIN\sp_superreader

Step 2: Configure Accounts in SharePoint Central Administration
Go to SharePoint CA: Central Admin -> Manage Web Application -> User Policy
Add DOMAIN\sp_superuser – Full Control
Add DOMAIN\sp_superreader – Full Read

Check to make sure these accounts have similar access to the SharePoint databases.  Next, use one of the following steps: A or B.
Step 3A: Using STSADM
Open a command prompt
Execute:
stsadm -o setproperty -propertyname portalsuperuseraccount -propertyvalue DOMAIN\[sp_superuser] -url [WEBAPPURL]
And
stsadm -o setproperty -propertyname portalsuperreaderaccount -propertyvalue DOMAIN\[sp_superreader] -url [WEBAPPURL]
Step 3B: Using SharePoint Management Shell

Open a shell
Execute the following commands:
1.$wcm = Get-SPWebApplication -Identity http://[webappurl/]
2.$wcm.Properties["portalsuperuseraccount"] = “DOMAIN\sp_superuser”
3.$wcm.Properties["portalsuperreaderaccount"] = “DOMAIN\sp_superreader”
4.$wcm.Update()
Close the shell.

Step 4: Reset IIS
Reset IIS either from the GUI or executing "IISReset" at the command prompt.

Step 5: Test
Open a command prompt
Execute the following:
stsadm -o getproperty -propertyname portalsuperuseraccount -url [WEBAPPURL]
Output should read:
<PropertyExist=”Yes” Value=”DOMAIN\sp_superuser” />


Similarly for the super reader account.  The references below provide good background.

-End
View Comments 0 Comments
Share Post   


Failure trying to synch web application Event ID 5555

Wednesday, April 19, 2017 - Posted by Keith A. Smith, in Sharepoint

One of the errors I got after upgrading sharepoint that I couldn’t shake until recently.

Failure trying to synch web application <guid>, ContentDB <guid> Exception message was Microsoft.Office.Server.UserProfiles.UserProfileApplicationNotAvailableException: No User Profile Application available to service the request. Contact your farm administrator.
at Microsoft.Office.Server.Administration.UserProfileApplicationProxy.get_ApplicationProperties()
at Microsoft.Office.Server.Administration.UserProfileApplicationProxy.get_PerfmonInstanceHandle()
at Microsoft.Office.Server.UserProfiles.ContentDBSynchronizer..ctor(ELogType logType, SPContentDatabase cdb, SPJobState jobState)
at Microsoft.Office.Server.UserProfiles.WSSProfileSyncJob.Execute()

Run from the sharepoint bin directory in a cmd prompted

Stsadm -o sync -listolddatabases 2
Stsadm -o sync -deleteolddatabases 2


Finally, and I’m not sure if this is necessary, but I read that you should change timer job “Timer Service Recycle” (Central Administration –> Job Definitions) to run at 06:30 PM.  This last step can be done through Central Administration.  After doing this my errors went away.  I did however need to run a full user profile synchronization by going to Central Administration –> Manage Profile Service: SharedServicesSearch_UserProfile –> Start Profile Synchronization


-End

View Comments 0 Comments
Share Post   


Access is denied. Verify that either the Default Content Access Acc

Sunday, April 09, 2017 - Posted by Keith A. Smith, in Sharepoint

Access is denied. Verify that either the Default Content Access Account has access to this repository

Error:Censored
Access is denied. Verify that either the Default Content Access Account has access to this repository, or add a crawl rule to crawl this repository. If the repository being crawled is a SharePoint repository, verify that the account you are using has "Full Read" permissions on the SharePoint Web Application being crawled.

Reason:
This error will occur, at the time of crawling the SharePoint application content. because, you may have provided a URL to access the SharePoint web application like http://portal.KeithIT.com (just an example).
When the search engine tried to crawl the content using the portal.KeithIT.com (just an example) URL, the server will reject the request. because, it will take the request as "LoopBackRequest".

Solution:Thumbs Up
So you need to disable the LoopBackRequest in registry. To do this, just follow my instructions:

1. Go to command window and type regedit.exe
2. Once opened the registry editor, just navigate to "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa"
3. Right click on "Lsa" and create a new 32bit DWORD value
4. Rename it as "DisableLoopbackCheck" (Note: you cannot rename it actually. so, once created the DWORD value, directly paste/type as "DisableLoopbackCheck".
5. Then again modify the value of "DisableLoopbackCheck" as "1"
6. Close the registry editor.
7. Now start to crawl the content.


-End
View Comments 0 Comments
Share Post   


SideBySide Error EventID 33 on conhost.exe

Thursday, April 06, 2017 - Posted by Keith A. Smith, in Sharepoint

Problem
SideBySide Error EventID 33 on conhost.exe

Solution
installed hotfix 977648

uninstall KB2507938


-End
View Comments 0 Comments
Share Post   


locked-out-of-sharepoint-site

Sunday, March 19, 2017 - Posted by Keith A. Smith, in Sharepoint

*run in a cmd prompt from C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN *
STSADM.EXE -o siteowner -url http://site.domain.net -ownerlogin domain\user

iisreset after the cmd above to make it take affect

-End

View Comments 0 Comments
Share Post   


Page  <1234>