Solved

“Access Denied” while Activating Custom Timer Job in Sharepoint 2010

Posted on 2013-01-26
4
2,082 Views
Last Modified: 2013-05-03
When trying to Activate Feature of Timer Job in a host header site collection, it returns error : Access Denied

Scope of Feature is "Site". The account is registered as Farm service account. But Still not Working.

Tried to disable RemoteAdministratorAccessDenied feature, still not working.

Any help or suggestion is appreciated.

Thanks,
ash84
0
Comment
Question by:Ash84
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
4 Comments
 
LVL 31

Expert Comment

by:Jamie McAllister MVP
ID: 38824000
0
 
LVL 3

Expert Comment

by:EvoLord
ID: 38825046
Jamie's right the link should explain why you can't activate your feature through the GUI. However, what it fails to explain is how else you can activate on other environments that do not have VS ( like your test and production environments). For those environments use the powershell commands for activation. The powershell command will run by the owstimer and so uses the farm service account for activation.

Here a msdn link with the enable feature so command http://msdn.microsoft.com/en-us/library/ms442691(v=office.14).aspx

Lastly, remember that farm features are automatically activated, so if you are using one then deploy your solution using powershell!

If the above does not help, let me know via a response to this post and if your willing to share your code I'll be happy to have a look and sort out the issue for you.
0
 
LVL 9

Expert Comment

by:kukdai
ID: 38827365
I would prefer changing the scope of the solution to higher level rather than site.
i do have a custom timer created but it is activated at the web application level and the process is actually for each site collection.

can't the scope of the site be changed to web application level hopefully that should fix the issue.
0
 
LVL 3

Accepted Solution

by:
EvoLord earned 500 total points
ID: 38828803
You should have no issues changing the scope to the web application level. Just activate the feature using powershell. Timerjob activation through the GUI will use the app pool account the GUI runs under. Activating using powershell uses the app account the Timerjob service runs under.


Hope this helps.
0

Featured Post

Enterprise Mobility and BYOD For Dummies

Like “For Dummies” books, you can read this in whatever order you choose and learn about mobility and BYOD; and how to put a competitive mobile infrastructure in place. Developed for SMBs and large enterprises alike, you will find helpful use cases, planning, and implementation.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Work Over Net is a new and very powerful collaboration product. With its new easy interface it is becoming very competitive to other similar products like webex and office interactive. WON 2010 have the standard business tools needed for multi-offic…
I thought I'd write this up for anyone who has a request to create an anonymous whistle-blower-type submission form created using SharePoint 2010 (this would probably work the same for 2013). It's not 100% fool-proof but it's as close as you can get…
Nobody understands Phishing better than an anti-spam company. That’s why we are providing Phishing Awareness Training to our customers. According to a report by Verizon, only 3% of targeted users report malicious emails to management. With compan…
How to Install VMware Tools in Red Hat Enterprise Linux 6.4 (RHEL 6.4) Step-by-Step Tutorial

756 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question