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
Riyan Arshad | January 28, 2025
As a skilled SharePoint developer, I have spent years customizing forms and workflows. My goal is to speed up business processes and improve user experiences. The ability to customize SharePoint to fit individual organizational demands has always been a challenging and rewarding endeavor.
Today, I'll discuss how to create custom SharePoint...
Development
Vladi Gubler | March 27, 2025
The best way to show off your product is of course letting your potential customers try it out. In our case, Ultimate Forms is a Microsoft SharePoint application, so it needs SharePoint to run.
Of course, potential customers can easily install it and we even provide an installation wizard that will completely automate and streamline the...
Development
Will Cooper | May 15, 2025
Dynamic Forms are an essential part of SharePoint solutions. Dynamic Forms change in appearance and functionality according to rules defined in the form. It does so in real time as the user fills out the form. This is the opposite of out-of-the-box static SharePoint forms which don't change in appearance or functionality.
Learning how to how to...
