Hot answers tagged owstimer
SharePoint 2010 RTM'd in April 2010. That article is from December 2009, when it was in beta. We're now into SP1, so it wouldn't surprise me if they changed the dispatcher to use w3wp.exe instead of owstimer.exe. Personally, if you know that it runs under either of the two, debug either until you hit breakpoints. I don't reckon it's that much of a deal. ...
This isn't my forte but I ran across the note below on this MSDN posting; perhaps that will help. If you wanted a job to run on all servers, including application servers, your class should derive from SPServiceJobDefinition. Pass the timer service (SPFarm.Local.TimerService) as the SPService parameter of the SPServiceJobDefinition(String, ...
Disclaimer: While this won't bypass the need to provide a set of user credential, at least will somehow avoid to store them as clear text. The general idea is to use the Secure Store Service to store a set of credential that will be used in the request. You need to define an "app" and then access that application via codebehind from the timer job instance. ...
Based on my experiments in the case of an OWSTimer process you should access your external data using the BCS API instead of running a CAML query against the external list. See details here: http://pholpar.wordpress.com/2012/02/14/accessing-external-data-from-sharepoint-timer-jobs-or-from-event-receivers-triggered-by-incoming-mail/
Only top voted, non community-wiki answers of a minimum length are eligible