It sounds like we might be at the point where an Issue should be created in GitHub.  This is too consistent for those experiencing it.  There must be a newly introduced feature/bug in 9.11.02 that needs to be looked at. 

I'm wondering if Localization has anything to do with this too... Are these sites using multiple languages as well? 

Thanks a lot for your precious time and investigation!
25% of all sites are multilingual, 75% are not.

My site is in Dutch, nothing else

I'm seeing this on a (single language) site too

Are there any other impacts resulting from this issue, other than perhaps larger log files? Would this be a reason not to upgrade to 9.11.2?

Ok I think this is caused by the newly introduced "Monitor Web Servers"  scheduled task.

https://github.com/dnnsof...Platform/issues/5575
https://github.com/dnnsof...n.Platform/pull/5586

If I understand correctly this is only needed on multi server environments.

On a single server you could disable the task or set the frequency to once a day.
After I did that the "webserver updated" admin log entries stopped showing up.

FYI, I also found this "issue".

https://github.com/dnnsof...Platform/issues/5634

I deleted that task and now get this:
04/29/2023 19:59:20
Scheduler Exception


AbsoluteURL DefaultDataProvider DotNetNuke.Data.SqlDataProvider DotNetNuke
AbsoluteURL:

DefaultDataProvider:DotNetNuke.Data.SqlDataProvider, DotNetNuke

ExceptionGUID:dc73c5bf-7309-4df1-9fdd-c81316336343

AssemblyVersion:

PortalId:-1

UserId:-1

TabId:-1

RawUrl:

Referrer:

UserAgent:

ExceptionHash:QYyt2knVhnhKZyrIMBDaSbPHh8g=

Message:Sequence contains no elements

StackTrace:

at System.Linq.Enumerable.First[TSource](IEnumerable`1 source)
at DotNetNuke.Services.Scheduling.Scheduler.CoreScheduler.ValidateServersAreActiveForScheduledItem(ScheduleItem scheduleItem)
at DotNetNuke.Services.Scheduling.Scheduler.CoreScheduler.AddToScheduleQueue(ScheduleHistoryItem scheduleHistoryItem)
at DotNetNuke.Services.Scheduling.Scheduler.CoreScheduler.LoadQueueFromTimer()
at DotNetNuke.Services.Scheduling.Scheduler.CoreScheduler.Start()
InnerMessage:

InnerStackTrace:

Source:System.Core

FileName:

FileLineNumber:0

FileColumnNumber:0

Method:

Server Name: IIS

I got the same error as Mariette every 10 minutes after setting the frequency to once a day.
After recycling the application pool, the message was terminated.

Posted By Timo Breumelhof - 40FINGERS on 4/28/2023 4:31 AM

Ok I think this is caused by the newly introduced "Monitor Web Servers"  scheduled task.

https://github.com/dnnsof...Platform/issues/5575
https://github.com/dnnsof...n.Platform/pull/5586

If I understand correctly this is only needed on multi server environments.

On a single server you could disable the task or set the frequency to once a day.
After I did that the "webserver updated" admin log entries stopped showing up.

FYI, I also found this "issue".

https://github.com/dnnsof...Platform/issues/5634

Multi-server and cloud environments like Azure, where your server(s) could change.  

 

This is still an issue. One server, 3 languages and lots of errors in the log like:
at System.Linq.Enumerable.First[TSource](IEnumerable`1 source)
at DotNetNuke.Services.Scheduling.Scheduler.CoreScheduler.ValidateServersAreActiveForScheduledItem(ScheduleItem scheduleItem)
at DotNetNuke.Services.Scheduling.Scheduler.CoreScheduler.AddToScheduleQueue(ScheduleHistoryItem scheduleHistoryItem)
at DotNetNuke.Services.Scheduling.Scheduler.CoreScheduler.LoadQueueFromTimer()
at DotNetNuke.Services.Scheduling.Scheduler.CoreScheduler.Start()

I have disabled the task, deleted the task, recreated the task but it keeps coming back.