While testing some of our products on SharePoint 2010 I came across an annoying problem. Some of our products use custom timer jobs, and when trying to register such a job, say using feature receivers, caused a completely unexpected Access denied exception. I tried to run the code with elevated privileges, no use.
It took me some time, but I finally got it - in SharePoint 2010 you must register the timer jobs only in feature receivers scope to the farm or web application level. Although I can see some logic in it, I still find it extremely annoying that something that used to work smoothly under MOSS would be completely broken under 2010, no matter what the reason is.
Add your comment
UltimateForms
100% No-Code Solution
It's never been easier, to create, innovate and share, all you need is your web browser!
Cost-effective
Address business process pain points immediately. Save time and money.
Fantastic Support Team
Facing difficulties installing the application? Contact our fantastic support team.