Ir al contenido principal

SharePoint 2010 - Event 7362 – Web Content Management

 

Problem:

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

Solution

Step 1 – Create AD Domain Accounts

Create domain accounts for the ‘portalsuperuseraccount’ and ‘portalsuperreaderaccount’. I use sp.superuser and sp.superreader but the naming is up to you.

Step 2- Assign Account Permissions

Run SharePoint Management Shell and execute the following commands:

$wcm = Get-SPWebApplication -Identity http://<url of web application>
$wcm.Properties["portalsuperuseraccount"] = “<domain>\sp.superuser”
$wcm.Properties["portalsuperreaderaccount"] = “<domain>\sp.superreader”
$wcm.Update()

Step 3- Modify the Web Application User Policy

Central Admin -> Manage Web Application -> User Policy
Add sp.superuser – Full Control
Add sp.superreader – Full Read

Reboot your SharePoint farm

You will need to reboot your SharePoint servers for the changes to take effect.

Note* You have to run the above commands on each Web Application if you have more than one.

Testing

SharePoint Management Shell, type the following command

stsadm -o getproperty -propertyname portalsuperuseraccount -url <url of web application>

The output should be something like this.

<PropertyExist=”Yes” Value=”<domain>\sp.superuser” />

 

Fuente: http://mysharepointadventures.wordpress.com/2011/05/23/event-7362-web-content-management/

Comentarios

Entradas populares de este blog

Get SharePoint Online Site and SubSites permission using PowerShell

The below PowerShell script retrieves the following for the given SharePoint Online Site All the Sub-site's URL Security group attached with each Sub-site with their permission level Prerequisites: This PowerShell script uses the latest version of SharePoint Online PnP Module. Download the installer from https://github.com/SharePoint/PnP-PowerShell/releases  Install-Module SharePointPnPPowerShellOnline  Install-Module - Name ' SharePointPnP.PowerShell.Commands.Files.Recurse ' function  connect - site( $webs , $creds ){    Connect - PNPonline  - Url  $webs   - Credentials  $cred     }    function  get - sitepermission( $web , $cred ){    $rec =@()    connect - site  - webs  $web   - creds  $cred     if ( $web   - eq  $parentsitename )  {  #Write-Host "Parent site permission" $web   $Pgroups =G...

Conexión desde casa a una VPN sin perder salida a internet

Solución, asumiendo que estas en Windows: Panel de Control, Conexiones de Red. Clic derecho en la VPN, dale a propiedades. Anda a la pestaña de "Funciones de Red" y selecciona Protocolo Internet TCP/IP y clic en el botón "Propiedades". Ahora hazle clic al botón "Opciones Avanzadas..."En la pestaña "General", desmarca la opción que dice "Usar la puerta de enlace predeterminada en la red remota". Dale a aceptar a todas las ventanitas de opción, y ahora conéctate a la VPN nuevamente. Con eso deberías entrar a la VPN sin perder la conexión local de tu red e internet.

Event ID 8031 The uri endpoint information may be stale

An exception occurred while updating addresses for connected app {6783ce5e-c88h-4021-8d5b-12614875cbfa_b79f19ab-1d40-4824-9911-3466cf8b070a}. The uri endpoint information may be stale. System.InvalidOperationException: The requested application could not be found.    at Microsoft.SharePoint.SPTopologyWebServiceApplicationProxy.ProcessCommonExceptions(Uri endpointAddress, String operationName, Exception ex, SPServiceLoadBalancerContext context)    at Microsoft.SharePoint.SPTopologyWebServiceApplicationProxy.ExecuteOnChannel(String operationName, CodeBlock codeBlock)    at Microsoft.SharePoint.SPTopologyWebServiceApplicationProxy.GetEndPoints(Guid serviceId)    at Microsoft.SharePoint.SPConnectedServiceApplicationAddressesRefreshJob.Execute(Guid targetInstanceId) After de-commissioning some SharePoint servers, you might notice the above error on other WFEs /Application server’s event viewer . It appears that the SharePoint still has a reference...