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:


Labels:

Comments

Post a Comment

Popular posts from this blog

Users do not show up in SharePoint People Search or People Picker

I had this issue with people picker in a classic mode web application in SharePoint 2013 and this site is in 2010 mode - users in certain sub-domains would not show up in People Picker. I was aware of stsadm commands to fix this and we ran the stsadm command to hook up people picker with another domain some time back. The latest issue was that people picker was not returning users from the root domain and few sub domains. After researching on the internet I found (contrary to my thoughts) that we could use PowerShell and not just stsadm to map People Picker to domains. It is a good idea to first check what domains are added/mapped to the web application using the following commands: $wa = Get-SPWebApplication -Identity http://mywebapp.com #List the Domains $wa.PeoplePickerSettings.SearchActiveDirectoryDomains This will list the domains currently People Picker is looking up for that web application. I used the following script to map our AD forest to People Picker: ...
Post a Comment
Read more

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 ...
5 comments
Read more

"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.
2 comments
Read more