Take the 2-minute tour ×
SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.

I created a custom timer job and deployed it into my development farm. The job runs fine. The thins is that after I deployed it to the QA farm. The status of the job says succeeded in central admin, but nothing happens. I added extra logging and nothing is being logged.

I thought it was something with that specific timer job, so I created another timer job that just has an assert and displays a pop up when it runs. Again, it just in the dev farm but not in the QA one. In this case though, the status of the job says Initialized and 0% completed, but no pop up.

I think it has something to do with permissions, but I cannot find what it is. Any toughts??

share|improve this question
    
Have you tried to debug your timer job? –  spevilgenius Nov 16 '10 at 23:42
    
Yes, I tries, but did not work for me. I installed the remote debugger tools in the server. I ran it, and then connected from my dev machine. The thing is that VS tells me that there is no symbols loaded for the code. I'm doing something wrong here :P –  Omar Nov 18 '10 at 14:40
    
Perhaps it's a good idea to add some more logging to your app to see where an exception is (possibly) thrown. Also add some informational logging. You can do this in the eventviewer support.microsoft.com/kb/307024 or in the Sharepoint logs: salviashish.wordpress.com/2009/05/16/writing-in-sharepoint-logs That way you'll probably be able to find out where the job is quiting. –  Jan_V Dec 1 '10 at 17:33
add comment

2 Answers 2

When you deploy to your QA environment have you ensured that you have restarted the timer service on all of your SharePoint boxes? The OWSTimer service will cache DLLs and cause very strange issues when trying to debug and test new timer jobs.

share|improve this answer
    
Yes, I even restarted the server. –  Omar Nov 18 '10 at 15:16
add comment
up vote 0 down vote accepted

I erased the cache of the server and the job started working again. However each time the I change the schedule of the timer job, I have to clear the cache again.

share|improve this answer
    
how did you clear the cache? –  e.ozmen Jan 18 '13 at 8:57
    
follow these steps blogs.msdn.com/b/josrod/archive/2007/12/12/… –  Omar Jan 18 '13 at 16:48
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.