Scheduled Tasks won’t run in DNN 7.3.0

Monday, June 16, 2014 By

Chris Hammond

If you’ve recently upgraded to DotNetNuke 7.3, you might not have noticed that your scheduled tasks aren’t running. How do you know if your tasks are running or not? Follow these steps

Login with a super user account (typically HOST)
Navigate to the Host/Schedule page from within the Control Panel’s Host menu
Pick a task that is enabled, and click on the Icon in the LOG column
On the schedule history page that loads, see if the task has started/ended at all since you upgraded to DNN 7.3

If you find that the schedule tasks haven’t been running since you upgraded to DNN 7.3 than you are likely experiencing the bug that was introduced. Long story short of the bug is that the Server Name in the schedule is now case sensitive, and you likely have Upper Case server names in the WebServers table in the database.

Initially, before I realized it was a case sensitivity issue I performed the followings steps to get my schedule running again.

Update the name of the server in the Web Servers table to be SERVERNAME-2 instead of SERVERNAME
Restart the Application Pool in IIS

This caused DNN to add a new server entry into the web servers table, and thus the scheduled tasks started firing off correctly.

I believe, though I haven’t tested this myself, you could simply take the following two steps to get this fixed

Rename your webserver in the webservers table to be lowercase
Restart the Application Pool in IIS

There also appears to be another bug in the web server infrastructure for scheduling related to duplicate web servers listed in the table, though I haven’t experienced that on my sites, I would assume that it would be possible to have the upper and lowercase variants of the server name in the table and perhaps that causes some DNN issues.

I believe that both of these are being worked on for the DNN 7.3.1 release, though I have no clue when that release will be made available.

Add a Comment

Recent Comments

Hi. I am experincing this problem: ---- System.InvalidOperationException: Sequence contains more than one matching element at System.Linq.Enumerable.Single[TSource](IEnumerable`1 source, Func`2 predicate) at DotNetNuke.Services.Scheduling.Scheduler.CoreScheduler.LoadQueueFromTimer() at DotNetNuke.Services.Scheduling.Scheduler.CoreScheduler.Start() ---- Is this the issue you are describing above? I have tried to find the servername in the database, but can't. Would really appreciate a little help ;-) Kind regards and best new year wished Niki Gade

Posted By: Niki Gade on Jan 2015

Niki, you need to find the WebServers table

Posted By: Chris Hammond on Jan 2015

Thanks for your fast reply - and sorry for me not following up on it. Some other urgent stuff came up, however we have had to move up the launch of the website in question (launched 1 week ago), and now I need to figure this thing out. I have located the WebServers table, but don't know what to edit or how to do it. We use SQL management studio (free edition). Help is appreciated. Thanks.

Posted By: Niki Gade on Jan 2015

Niki, you need to learn some T-SQL, or hire someone who knows it. The updates are pretty darn simple to do once you know t-sql

Posted By: Chris Hammond on Jan 2015

Thanks for your help Chris. I totally forgot to write back to you, and just remembered it now. For me the problem was that the same servername was listed twice in the WebServers table. Somehow that happened during the update of DNN. I did however also change the name to lowercase when deleting the dobbelt record. Thanks for all your help.

Posted By: Niki Gade on Jul 2015

We had another issue causing the Scheduler to not run any Scheduled Task. For testing purposes we've extended Global.asax with a custom Application_BeginRequest(). Because of this Initialize.RunSchedule(app.Request); was never called 🤦

Posted By: Benjamin Gemperle on Sep 2017

Add Comment

Please add your comment by filling out the field(s) below. Your comment may need to be approved before it becomes visible.