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

HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...Scheduler GetServer() Throwing Error After Upgrade - 7.0.5 to 7.3.1Scheduler GetServer() Throwing Error After Upgrade - 7.0.5 to 7.3.1
Previous
 
Next
New Post
7/2/2014 12:30 PM
 

After upgrading from 7.0.5 to 7.3.1 I am getting an error thrown from the scheduler. It is being thrown by the internal method GetServer in Scheduler.cs when trying to return a single result from ServerController.GetServers().

internal static ServerInfo GetServer(string executingServer
 {
          return ServerController.GetServers().Single(s => s.ServerName.Equals(executingServer, StringComparison.OrdinalIgnoreCase));

The error in the log is:

2014-07-02 11:56:42,998 [AES-SL-271][Thread:Scheduler Thread][ERROR] DotNetNuke.Services.Exceptions.Exceptions - 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.GetServer(String executingServer)

   at DotNetNuke.Services.Scheduling.Scheduler.CoreScheduler.LoadQueueFromTimer()

   at DotNetNuke.Services.Scheduling.Scheduler.CoreScheduler.Start()

This is happening on my QA as well as local dev machine. 

We actually have in dbo.WebServers multiple entries by the same name and it appears to be looking for a unique record (Single).

Has anyone run into this? Is is a process for the upgrade to blow away this table and let it be rebuilt?

Thanks!

 

 
New Post
7/2/2014 2:04 PM
 

I found an entry in the DNN Tracker at https://dnntracker.atlassian.net/brow... which I am looking into as it appears to be the same issue.

 
New Post
7/2/2014 2:16 PM
 
most likely, there are 2 servers with same name, you should edit webserver table manually to fix this.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
7/2/2014 2:27 PM
 

It appears to the similar to the issue you reported earlier where this line needs to be changed to take into account the IISAppName:

  var thisServer = ServerController.GetServers().Single(s => s.ServerName == executingServer && s.IISAppName == DotNetNuke.Common.Globals.IISAppName);

There's some other logic that is also getting the executing server to compare:

var executingServer = ServerController.GetExecutingServerName();

This gets only the servers that are enabled, where Enabled=1 in the dbo.WebServers table. 

UseAppName is looking to see in that list returned if the unique server name list is < the enabled list and if so it concatenates ServerName and IISAppName as the returned ExecutingServerName. 

In our case in the database we have multiple entries with the same ServerName but different IISAppName and Enabled is false.

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...Scheduler GetServer() Throwing Error After Upgrade - 7.0.5 to 7.3.1Scheduler GetServer() Throwing Error After Upgrade - 7.0.5 to 7.3.1


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