Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Has the DotNetNuke Scheduler been fixed yet?Has the DotNetNuke Scheduler been fixed yet?
Previous
 
Next
New Post
10/30/2009 5:30 PM
 

This problem has been going on for 2 days now, with Active Forums unable to retrieve email from the servers as a result.

Today I finally got an inpiration and stumbled into how to "fix" it - go to the Host Settings page and restart the application.  Presto, no more Event Log entries from Active Forums complaining about POP3 errors, no more duplicate events running in the scheduler.

Looks like a bug in the Scheduler to me - not sure if it's specific to the Active Forums event or not.

William

 
New Post
4/26/2010 4:20 AM
 
I am not aware???? The scheduler has a reputation of being buggy... Just last week I had this result in 4.9.4: S: 23-4-2010 14:33:21 E: 23-4-2010 14:34:45 N: 3-4-2010 20:36:25 So the next task is scheduled in the past, if that's not buggy, then I don't know what is...
 
New Post
4/26/2010 5:26 PM
 

The scheduler has had some exensive rework in the last few months and works great.  Among the improvements is a "start now" button for jobs which makes it easy to run on demand if you need to catch something up.  However, all of these changes are in the 5.x series (around 5.2.3 I think).


Scott Willhite, Co-Founder DNN

"It is only with the heart that one can see rightly... what is essential is invisible to the eye. "
~ Antoine de Saint-Exupéry

 
New Post
4/26/2010 8:05 PM
 
AFAIK there are still issues for scheduler jobs to access portal context, but besides, scheduler jobs need to set next execution to a value in the past, if "catch up" is enabled. In this case, the scheduler is run for each cycle missed, after the site has been restarted.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
4/26/2010 9:50 PM
 
Sebastian Leupold wrote:
AFAIK there are still issues for scheduler jobs to access portal context
 

This is not an "issue" although I understand might be an enhancement request.  The Scheduler does not run in context of a portal and was not designed to.


Scott Willhite, Co-Founder DNN

"It is only with the heart that one can see rightly... what is essential is invisible to the eye. "
~ Antoine de Saint-Exupéry

 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Has the DotNetNuke Scheduler been fixed yet?Has the DotNetNuke Scheduler been fixed yet?


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out