Skip to main content

Access is Denied, Exception from HRESULT: 0X80070005

I'm not a fan of re-posting content but I'm doing it so that the possibility of somebody finding a solution for this error increases.

I received the following error while trying to schedule a crawl on our SharePoint farm:




I was able to start a full or incremental crawl and it would complete successfully and this led to the possibility of some issue with scheduling mechanism. Now SharePoint would leverage Windows tasks scheduler to schedule events from SharePoint and so it makes sense that this error disappears when we explicitly provide the local server group "WSS_WPG" read and write permission on the "Tasks" folder within Windows folder on the Index server.

Here are the steps (Close all explorer windows before performing these steps):

1. Start - Run - type "Cmd" and execute the following command:

attrib -s %windir%\tasks

This is done so that the "Security" tab appears in the Tasks properties window.

2. Right click Windows\Tasks folder and navigate to Properties - Security tab

3. Add the group "WSS_WPG" group with Read and Write permission. Make sure the location is set to local server and not domain because this group is a local group.

4. Start - Run - type "Cmd" and execute the following command:

attrib +s %windir%\tasks

There were few blogs and a MS article that discuss about this issue:


Comments

Popular posts from this blog

Difference between the architectures of SSPs and SharePoint Service Application

SharePoint 2010 has some new features and components, which help to overcome difficulties such as redundancy and service-sharing that we faced while using SharePoint 2007.  Services in MOSS 2007 were implemented with the help of Shared Service Providers or SSPs. But we cannot use the services of one SSP for another SSP. So each SSP has to have its own set of services and applications, which increases redundant data in the farm.  For example, different managers in the same organization use a SharePoint site to maintain official data associated with an SSP. This SSP is associated with different services, such as Search service, BDC service, and a user profile service. A project manager in this organization requests an exclusive user profile service to maintain project data security. To provide this, we first need to create a separate SSP for the project manager and then a separate service called user profile service - project name. Next, we need to associate the SSP with ...

SharePoint Designer Workflow Failed to Start - Cancelled by System Account

I was working on a List workflow the other day in SharePoint Designer 2010. This list already had a workflow which was working perfectly fine and I needed another manual workflow in it. No matter what I tried the workflow would fail and would log a message in the history list that Workflow failed to start and it was cancelled by System Account . I observed that the same happened with new workflows in that list, new workflows in other lists and I even tried creating new subsites and workflows were behaving the same way. I googled for a while and there were many suggestions to clear SPD cache which did not help me. I played with SPD 2010 for a while and observed that the workflow xml and xoml files were checked out. I read in some blogs that this could cause this issue as well. I tried to check those files in but then I was greeted with a new error! " Cannot perform this operation. The file is no longer checked out or has been deleted ." I had no clue what was happening...

"Cannot impersonate user for data source" - SSRS reports

We were getting this strange error while viewing our reports in SharePoint that was deployed using BIDS 2005: An error has occurred during report processing. Cannot impersonate user for data source 'datasource' Logon failed I tried many things but nothing worked. I did some research and found many blog posts which suggested me to reapply the password on the datasource file specified in the error message and save it again. That didn't work for me. I saw some check boxes in the data source file that read "Use as Windows Credentials" and "Set Execution Context to this report" and I didn't know what they meant. I unchecked those in my data source and then when the refreshed the page the report started displaying.