I have written a timer job which works fine on my development server and another test server. By this I mean that when I schedule it to run every 5 minutes, it runs once every 5 minutes. This is what I expect to happen. So far so good. I have now deployed this timer job to a customers development and test servers and with both of these servers, the following happens: 1st time the job is scheduled to run, it runs once, 2nd time it runs twice, 3rd time it runs thrice, etc etc. Does anyone know what could be causing this? I presume it is a server configuration/setup issue as it doesnt happen everywhere, but I dont know where to start looking. Regards Jeff

Thanks for the reference links you posted. This could indeed be the problem as I started my timer job development using the Andrew Connell examples which uses the SPJobLockType.ContentDatabase. I realised that since I got everything working, I never went back and looked at how this was set up. I will make the suggested change from SPJobLockType.ContentDatabase to SPJobLockType.Job and see how that goes. Having read the articles you refer to, and having more understanding now than when I started, it sounds promising. It will take me a couple of days to test this as I am not on the customers site for a while. I will assume that it works, and mark as answer. Once again, many thanks for your prompt response. Jeff