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 can't believe Timer Jobs and SharePoint can be this un-predictable.

I deployed my Timer job feature solution to web application A and activated feature, it worked for 3 days in same web application without any kind of problem. Today after nothing at all has been changed other then EVENT RECEIVER failed to load a dll (dunno why tho) and it went to Initialized stage with "0%" progress.

I looked at Solution Management in central Admin and its deployed to web application A

I looked at Timer Job Definition for Web Application A and I can't find definition for Timer job, however we got around 15 Web Applications so I looked at another Web Application let say Web Application B and Timer Job Definition was there.

How strange, I don't even know what exactly to google.

Most people say clear Configuration Cache to make it work, but why would it happen at first place and its our development server I can clear configuration cache but what if it happens on Live, I can't go to Live server and gonna clear Cache whenever this timer job will hang

share|improve this question
    
Was the timer job referencing the DLL at all do you know, ie was it anything to do with what this Timer job was doing? Or maybe the event receiver firing on something on the job or are they not linked at all? –  Hugh Wood Sep 3 '12 at 17:26
    
they are not linked at all, dll was just for event fire that saves values to DB table, but main concern is why Timer job definition says its in a different web application :S –  Muhammad Raja Sep 3 '12 at 19:26
    
Is it a web application scoped timer job? –  Hugh Wood Sep 4 '12 at 7:39
    
yup it is indeed –  Muhammad Raja Sep 4 '12 at 7:54
    
I came this morning and timer job is running successfully, no one touched server at all, except the timed operations happens at early morning, but again I am pretty sure non of operation re-configure cache. –  Muhammad Raja Sep 4 '12 at 8:07
show 4 more comments

1 Answer

up vote 1 down vote accepted

it depends on which web application feature you activated it, if you activated it in web application B then Timer job definition will be in Web App B regardless of where it has been deployed, why ? I don't know to be honest.

share|improve this answer
    
let me try but how can you activate a feature that is not deployed to a specific web application –  Muhammad Raja Sep 4 '12 at 10:29
    
thanks lot it worked, but am still confused –  Muhammad Raja Sep 4 '12 at 10:34
    
glad it worked & for rest gooogle it ;) –  SharePointer Sep 4 '12 at 10:35
1  
The feature activation will decide which Web Application the Timer job is associated to because when you create your timer job using the SPJobDefinition derived class you pass in the SPWebApplication object into that constructor. See msdn.microsoft.com/en-us/library/… –  Simon Doy Sep 4 '12 at 16:00
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.