JobDefinitions for Timer Jobs in SharePoint -


I've hit a problem with a timer job demand within an event handler is fine on my dev machine Works even where user is a farm administrator. On the staging server (and also production), this user will be different. Obviously it is necessary to become a farm administrator who creates / updates the timer jobs because they have access to Configuration DB.

To combat this perception, I may be updated once several items using used a timer job that datasheet and if that happens, then I edit an update rollup Wanted to keep it in a certain period.

Now I'm thinking I may have "a set time" job and timer job instead of a recurring timer job, check to some situations that no one is perfect before you act.

Any suggestions about achieving my desired result after running a rollup function after any update, but not every one?

The last answer is not correct, or at least not correct for SharePoint 2010. You can not make a definition of job like this in 2010, even with high privileges, because they should be made from central government management. I had a similar problem and it was my search

I suggest that you create an event receiver that is delayed to say 10 minutes (timer or thread sleep) and in the web property bag Register itself, so that another example will not run. This can solve the problem.


Comments

Popular posts from this blog

c# - sqlDecimal to decimal clr stored procedure Unable to cast object of type 'System.Data.SqlTypes.SqlDecimal' to type 'System.IConvertible' -

Calling GetGUIThreadInfo from Outlook VBA -

Obfuscating Python code? -