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.
Loading...
Add your comment
Comments are not meant for support. If you experiencing an issue, please open a support request.
Reply to: from
Development
Custom SharePoint Forms and Workflows with Ultimate Forms
Riyan Arshad | January 28, 2025
As a skilled SharePoint developer, I have spent years customizing forms and workflows. My goal is...
Development
How to Integrate Power Apps with Infowise Ultimate Forms A Step-by-Step Guide for Non-Developers
Riyan Arshad | January 17, 2025
In our previous blog, we introduced the concept of building a Power Apps dashboard integrated with...
Development
Creating a No-Code HR Dashboard in SharePoint Infowise Ultimate Forms and PowerApps
Riyan Arshad | January 17, 2025
In today’s fast-paced business environment, decision-makers such as HR managers, controllers, and...