sorry for the late reply, i was travelling home from our home office and am still jetlagged. As for other ideas, I'm afraid I dont have many - I would check to see if youre running in a webgarden (http://www.dotnetnuke.com/Resources/Wiki/Page/Webgardens.aspx) as the additional threads could be the issue (note: it may also be an idea to change to request mode if youre user time mode - make sure and unload the application pool to kill off any running threads). Id also suggest truncating the schedulehistory table in case updating it is causing the failure (due to its size)

---

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US

I had the exact same issue w/ a custom scheduler.  I even chimed in on the gemini ticket.  But found my issue.  Was something I fixed in my custom module before - but didn't upgrade that specific user.

Basically - in my custom scheduler item - I was calling "Completed()" in my DoWork() method upon completion.  But we're no longer suppose to call Completed().  So if you are calling Completed() - remove it and your scheduler will work as expected.

Here's my initial forum post regarding the issue and solution: http://www.dotnetnuke.com/Resources/Forums/forumid/108/postid/441266/scope/posts.aspx#441266

Hope this helps you.

---

---

Andrew Walker

If you enjoy making your own beer and/or wine - be sure to check out http://www.ForemostBrewing.com