Products

Solutions

Resources

Partners

Community

About

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

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Scheduler exception after Upgrade to 7.3.0Scheduler exception after Upgrade to 7.3.0
Previous
 
Next
New Post
6/14/2014 8:22 AM
 
There should be a unique index on ServerName and IISAppname,
Unfortunately, LoadQueueFromTimer misses to pass the IISAppName, when requesting a single server.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
6/14/2014 10:38 AM
 

Thanks for the replies on this.... correcting the duplicates in the webservers table fixed it for me also

 
New Post
6/14/2014 1:25 PM
 
I'm seeing

System.InvalidOperationException: Sequence contains no matching element
at System.Linq.Enumerable.Single[TSource](IEnumerable`1 source, Func`2 predicate)
at DotNetNuke.Services.Scheduling.Scheduler.CoreScheduler.LoadQueueFromEvent(EventName eventName)
at DotNetNuke.Services.Scheduling.Scheduler.CoreScheduler.RunEventSchedule(EventName eventName)

No duplicates in the webservers table. Doing some digging this weekend to try and track down the source of my error.

Chris Hammond
Former DNN Corp Employee, MVP, Core Team Member, Trustee
Christoc.com Software Solutions DotNetNuke Module Development, Upgrades and consulting.
dnnCHAT.com a chat room for DotNetNuke discussions
 
New Post
6/15/2014 12:40 AM
 
I ended up fixing my issue by doing the following.

1) Locate your webservers table in SQL and figure out what is listed (select * from webservers)
2) Rename your existing webserver (or delete the row, I renamed in case I wanted to bring it back)
3) Restart the app (I killed the app pool in Task Manager, you could recycle in IIS as well.

The next request that comes in will add a new webserver to the table, and after a few minutes all my jobs started back up correctly.

Chris Hammond
Former DNN Corp Employee, MVP, Core Team Member, Trustee
Christoc.com Software Solutions DotNetNuke Module Development, Upgrades and consulting.
dnnCHAT.com a chat room for DotNetNuke discussions
 
New Post
6/15/2014 4:47 AM
 

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Scheduler exception after Upgrade to 7.3.0Scheduler exception after Upgrade to 7.3.0


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