Event 2: PerformancePoint Service, Failed to read the acls for an item. Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))

August 2, 2011 Leave a comment

Error from Event Viewer:
Failed to read the acls for an item. Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))

Solution:
$w = Get-SPWebApplication –Identity http://webapplication
$w.GrantAccessToProcessIdentity(“DOMAIN\PPS_account”)

Note: In my case I had to give the account logged in the event viewer access in addition to the PPS Account

Categories: SharePoint 2010

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

July 13, 2010 1 comment

Problem:
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:
First give the Accounts Full control and Full Read permissions respectively via Central Administration and then add the accounts to the web app via stsadm commands.
Note: you must add the user accounts to each Web App.

STEP 1: Create the AD Accounts
Super Reader Account:  domain\SuperReader
Super User Account: domain\SuperUser

STEP 2: Add the user accounts using Central Administration

  1. On the Central Administration Web site, in the Application Management section, click Manage web applications.
  2. Click the name of the Web application that you want to configure.
  3. On the Web Applications tab, in the Policy group, click User Policy.
  4. In the Policy for Web Application window, click Add Users.
  5. From the Zones list, select All zones, and then click Next.
  6. In the Users box, type the user name for the Portal Super User account.
  7. Click the Check Names icon to ensure that the account name can be resolved by the authentication providers on the application server.
  8. In the Choose Permissions section, check the Full Control – Has full control box.
  9. Click Finish.
  10. Repeat Steps 5 through 8 for the Portal Super Reader account.
  11. In the Choose Permissions section, check the Full Read – Has full read-only access box.
  12. Click Finish

STEP 3: Run the stsadm commands
For illustration purposes say I have 2 Web Apps, namely:

  1. http://portal
  2. http://mysites
  • stsadm -o setproperty -propertyname portalsuperuseraccount -propertyvalue domain\SuperUser -url http://portal
  • stsadm -o setproperty -propertyname portalsuperreaderaccount -propertyvalue domain\SuperReader -url http://portal
  • stsadm -o setproperty -propertyname portalsuperuseraccount -propertyvalue domain\SuperUser -url http://mysites
  • stsadm -o setproperty -propertyname portalsuperreaderaccount -propertyvalue domain\SuperReader -url http://mysites
Categories: SharePoint 2010

Event ID: 1004, Detection of product ‘{90140000-104C-0000-1000-0000000FF1CE}’, feature ‘PeopleILM’, component ‘{1C12B6E6-898C-4D58-9774-AAAFBDFE273C}’ failed.

July 13, 2010 Leave a comment

Problem:
Detection of product ‘{90140000-104C-0000-1000-0000000FF1CE}’, feature ‘PeopleILM’, component ‘{1C12B6E6-898C-4D58-9774-AAAFBDFE273C}’ failed. The resource ‘C:\Program Files\Microsoft Office Servers\14.0\Service\Microsoft.ResourceManagement.Service.exe’ does not exist.

Solution:
Give the Network Service account access to the folder located at C:\Program Files\Microsoft Office Servers\14.0 (services and sql folders are the ones you are looking for)

Categories: SharePoint 2010

Volume Shadow Copy Service error: Failed resolving account spfarm with status 1376

July 13, 2010 1 comment

Problem:
Volume Shadow Copy Service error: Failed resolving account spfarm with status 1376. Check connection to domain controller and VssAccessControl registry key.

Error from Event Viewer:
Volume Shadow Copy Service error: Failed resolving account spfarm with status 1376. Check connection to domain controller and VssAccessControl registry key.

Operation:
Initializing Writer

Context:
Writer Class Id: {0ff1ce14-0201-0000-0000-000000000000}
Writer Name: OSearch14 VSS Writer

Error-specific details:
Error: NetLocalGroupGetMemebers(spfarm), 0x80070560, The specified local group does not exist.

Solution:
Navigate to \HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\VssAccessControl using regedit and remove the user (in this case spfarm) from the VssAccessControl.

Registry path:
\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\VssAccessControl

Categories: SharePoint 2010

Load control template file /_controltemplates/TaxonomyPicker.ascx failed

July 13, 2010 Leave a comment

Event log Error:
Load control template file /_controltemplates/TaxonomyPicker.ascx failed: Could not load type ‘Microsoft.SharePoint.Portal.WebControls.TaxonomyPicker’ from assembly ‘Microsoft.SharePoint.Portal, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c’.

Problem:
TaxonomyPicker.ascx located under :\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\CONTROLTEMPLATES\  contains  &#44 which is the HTML number for ,

Solution:
Replace &#44 with ,

Old Line:
<%@ Control className=”TaxonomyPickerControl” Language=”C#” Inherits=”Microsoft.SharePoint.Portal.WebControls.TaxonomyPicker&#44;Microsoft.SharePoint.Portal, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c” %>

New Line:
<%@ Control className=”TaxonomyPickerControl” Language=”C#” Inherits=”Microsoft.SharePoint.Portal.WebControls.TaxonomyPicker, Microsoft.SharePoint.Portal, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c” %>

NOTE: If the error still keeps occurring after trying out this fix. Please follow Todd Carter’s solution below.

UPDATE:: After doing this fix I received this error again. I checked the Microsoft.SharePoint.Portal assembly and did not find the TaxonomyPicker class!!! So to fix this you may want to rename TaxonomyPicker.ascx to TaxonomyPicker.ascx_broken so we do not try to recompile it each time the AppPool is started. The user control is never used within SharePoint and therefore serves no real purpose.
Ref: Todd Carter

Categories: SharePoint 2010

Unexpected Error has occurred when starting SharePoint Search Service, VSS Error, Event ID 8193

July 12, 2010 2 comments

Server OS: Windows Server 2008 R2 environment
Error: When the Office Search Service tries to start, the content access account tries to access the VSS registry key and fails due to lack of permissions.


SharePoint Error:
 Starting the office search service using NET START OSEARCH causes SharePoint 2010 to throw “An unexpected Error has occurred”. Checking the event logs shows a VSS error with Event ID 8193.
Event ID: 8193 VSS Error

Solution: Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\Diag. Right Click on Diag and select Permissions and give your search account or content access account (in my case spsearch) full control permissions and click Apply. Restart the Office Search Service via command line: NET START OSEARCH or NET START OSEARCH14

VSS Error with Event ID: 8193
Volume Shadow Copy Service error: Unexpected error calling routine RegOpenKeyExW(-2147483646,SYSTEM\CurrentControlSet\Services\VSS\Diag,…). hr = 0x80070005, Access is denied.

Context:
Writer Class Id: {35500004-0201-0000-0000-000000000000}
Writer Name: SPSearch4 VSS Writer
Writer Instance ID: {6e255da6-fe1a-4ef1-a18d-87ac504494e9}

Binary Data:
0000: 6F43202D 203A6564 52474552 43534745
0008: 30303030 36353130 6143202D 203A6C6C
0010: 52474552 43534745 30303030 39323130
0018: 4950202D 20203A44 30303030 38343934
0020: 4954202D 20203A44 30303030 30383535
0028: 4D43202D 20203A44 5C3A4322 676F7250
0030: 206D6172 656C6946 6F435C73 6E6F6D6D
0038: 6C694620 4D5C7365 6F726369 74666F73
0040: 61685320 5C646572 20626557 76726553
0048: 45207265 6E657478 6E6F6973 34315C73
0050: 4E49425C 73736D5C 63726165 78652E68
0058: 20202265 20202020 7355202D 203A7265
0060: 656D614E 4544203A 54454E56 7370735C
0068: 63726165 53202C68 533A4449 352D312D
0070: 2D31322D 39363533 36353339 372D3734
0078: 31313736 38313234 3737312D 30303935
0080: 2D343737 39313131

In Bytes

0000: 2D 20 43 6F 64 65 3A 20 – Code:
0008: 52 45 47 52 45 47 53 43 REGREGSC
0010: 30 30 30 30 30 31 35 36 00000156
0018: 2D 20 43 61 6C 6C 3A 20 – Call:
0020: 52 45 47 52 45 47 53 43 REGREGSC
0028: 30 30 30 30 30 31 32 39 00000129
0030: 2D 20 50 49 44 3A 20 20 – PID:
0038: 30 30 30 30 34 39 34 38 00004948
0040: 2D 20 54 49 44 3A 20 20 – TID:
0048: 30 30 30 30 35 35 38 30 00005580
0050: 2D 20 43 4D 44 3A 20 20 – CMD:
0058: 22 43 3A 5C 50 72 6F 67 “C:\Prog
0060: 72 61 6D 20 46 69 6C 65 ram File
0068: 73 5C 43 6F 6D 6D 6F 6E s\Common
0070: 20 46 69 6C 65 73 5C 4D Files\M
0078: 69 63 72 6F 73 6F 66 74 icrosoft
0080: 20 53 68 61 72 65 64 5C Shared\
0088: 57 65 62 20 53 65 72 76 Web Serv
0090: 65 72 20 45 78 74 65 6E er Exten
0098: 73 69 6F 6E 73 5C 31 34 sions\14
00a0: 5C 42 49 4E 5C 6D 73 73 \BIN\mss
00a8: 65 61 72 63 68 2E 65 78 earch.ex
00b0: 65 22 20 20 20 20 20 20 e”
00b8: 2D 20 55 73 65 72 3A 20 – User:
00c0: 4E 61 6D 65 3A 20 44 45 Name:SERVICEACCOUNTNAME, S
00d8: 49 44 3A 53 2D 31 2D 35 ID:S-1-5
00e0: 2D 32 31 2D 33 35 36 39 -21-3569
00e8: 39 33 35 36 34 37 2D 37 935647-7
00f0: 36 37 31 31 34 32 31 38 67114218
00f8: 2D 31 37 37 35 39 30 30 -1775900
0100: 37 37 34 2D 31 31 31 39 774-1119

Categories: SharePoint 2010

Fixing the Volume Shadow Copy Service

June 28, 2010 Leave a comment

After installing DHCP on Windows Server 2008 R2, you may start to see the following error message in the event logs :

Volume Shadow Copy Service error: Unexpected error calling routine RegOpenKeyExW(-2147483646,SYSTEM\CurrentControlSet\Services\VSS\Diag,…). hr = 0×80070005, Access is denied.

Inspection of the detailed tab of the event log entry will show information about the process that generated the error. Take note of the user mentioned after the “- User: Name:” portion of the bytes. To resolve this error, simply give that user full permission to the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\VSS registry key.