Wednesday, April 25, 2012

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


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
User:          <username>
Computer:      <server>
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: [MachineName]\system
SharePoint 2010 is hosted on this machine.


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

stsadm -o setproperty -propertyname portalsuperuseraccount -propertyvalue DOMAIN\[sp_superuser] -url [WEBAPPURL]
stsadm -o setproperty -propertyname portalsuperreaderaccount -propertyvalue DOMAIN\[sp_superreader] -url [WEBAPPURL]

Step 3B: Using SharePoint Management Shell

Open a shell

Execute the following commands:

$wcm = Get-SPWebApplication -Identity http://[webappurl/]
$wcm.Properties["portalsuperuseraccount"] = “DOMAIN\sp_superuser”
$wcm.Properties["portalsuperreaderaccount"] = “DOMAIN\sp_superreader”

Close the shell

Step 4: Reset IIS

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

Step 5: Test

Opena 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.
Happy Computing!


Event ID 7043: Could not load type 'Microsoft.SharePoint.Portal.WebControls.TaxonomyPicker'


Reviewing the Windows Application event log, you come across the following:
Log Name:      Application
Source:        Microsoft-sharePoint Products-Sharepoint Foundation
Date:          [date]
Event IO:      7043
Task category: Web Controls
Level:         Error
User:          [SharePoint service account]
Computer:      [SharePoint host]
Description:   Load control template file /_controltemplates/Taxonomypicker.ascx failed: could not load type 'Microsoft.sharepoint.portal.webControls.Taxonomypicker' from assembly...
The machine on which this event occurred is the host for a newly installed SharePoint 2010 instance.

  1. Temporary solution:
    1. Open a folder and browse to: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\CONTROLTEMPLATES\.
    2. Open the file TaxonomyPicker.ascx in a text editor.
    3. Search for the string: &#44;
    4. Replace it with just a comma and a space:
    5. Save the file.
    6. Reset IIS.
    7. Perform these steps on each farm server (except the database).
  2. Permanent solution
    1. Delete this file from the controls folder (see above).
  • The problem involves a control template that remains in the control template folder but that has been removed from the code base.  I other words, this is a release error by Microsoft.  A temporary solution is to fix a minor typo in this control, as discussed in KB2481844.  However, the error will re-appear after a system restart, even though the typo no longer exists.  The permanent solution is to remove the control completely. 
  • Renaming the control simply leads to the new problem of a (renamed) control being loaded for which no code exists in the code base.

Sunday, April 22, 2012

SharePoint 2010: Cannot open backup device 'F:\[foldername]'. Operating system error 5(Access is denied.).


Your SharePoint 2010 system employs a SQL Server 2008 server hosted on a different machine. SharePoint 2010 SP1 may or may not have been installed. Both SharePoint 2010 and SQL Server are hosted on Windows Server 2008 platforms.  The MSSQLSERVER service is run under the NETWORK or other domain account.

You attempt to perform a backup from within SharePoint 2010 Central Administration to a network share.  After the backup operation completes, on the status page, you see one of the following errors:
Error: Object SharePoint_Config failed in event OnBackup. For more information, see the error log located in the backup directory.
SqlException: Cannot open backup device '[filename and path]'. Operating system error 3(The system cannot find the path specified.).
BACKUP DATABASE is terminating abnormally.

Error: Object [objectName] failed in event OnBackup. For more information, see the error log located in the backup directory. SqlException: Cannot open backup device Operating system error 5(Access is denied.) BACKUP DATABASE is terminating abnormally.

The problem most likely involves a permissions issue and is trivial to implement. 

The account running the MSSQLSERVER service is the one that actually processes the backup.  The destination folder for the backup must be configured to specifically allow this account access.  Setting access to Everyone is insufficient.  The MSSQLSERVER service account must specifically be granted Full Control access to both the physical folder and its shared representation.  If you have configured your MSSQLSERVER service to run under the NETWORK or other domain account, simply assign Full Control permissions specifically to these accounts.
NOTE: grant permissions to the NETWORK account.  Not the NETWORK SERVICE account.
If you have configured your MSSQLSERVER service to run under the System account, which is local, you will need to change the account to a domain account in order to resolve this issue.

Happy Computing!


Sunday, April 15, 2012

An error (920) occurred during the action Save As.


You are trying to save a Visio 2007 worksheet as a graphic. During this process, you experience the following error:


This problem is often caused by objects outside of the worksheet that Visio is unable to adequately fit into the viewing area for rendering into an image.  These objects can be located so far off the worksheet that it is difficult to immediately view them; and the scroll bar won't give any indication that these objects are there (it only tracks the current worksheet.  However, there is a simple way to remove these unwanted objects lying outside the worksheet.

Zoom out from the worksheet a bit, and then press CTRL + A.  This selects all of the objects on the current tab.  Note that a dashed green line surrounds the worksheet, but that it appears to extend outside of the current zoom view.

This indicates that the current selection has captured objects lying outside of the current worksheet.  Now, zoom outward until you can see the entire selection area.  In the image below, the zoom level is such that the actual worksheet is miniscule; and now the other objects can be seen.

Delete these other objects.  Then press CTRL + A again to ensure that no more objects lay outside of the worksheet.  Once the dashed green selection line only surrounds the current worksheet, you can safely save the current worksheet as an image without encountering further Visio 920 errors.

Happy computing!