Scheduler: Request Range Not Satisfiable

Do you have the main domain in the sites domain box? If so is it just the domain or do you have HTTP(s) or anything like that in there? The value should be something like www.domain.com or domain.com.

Secondly, what do you have for domain aliases? Is it possible that your aliases are being called an don't have a proper DNS entry setup or maybe those aliases are setup like I first mentioned?

Lastly and probably more important, do you have the scheduler running custom code? If so, have you attempted to put in some event logging to give you more info into the scheduled task?

I'm not 100% any of these will help resolve the problem, but these are things I've had issues with the scheduling engine in the past so figured I'd pass along.

Hi Brenden!
Thanks for your reply. The settings for domain are correct and I don't use HTTPS for my site. The site worked fine about a week ago. But some days ago I noticed that some Kentico tasks aren't executed. All custom tasks are executed correctly by Windows Service. Unfortunataly, some tasks do not have a checkbox 'Use external service' in settings, so it's impossible to run them by windows service. But maybe I can just update that scheduled tasks data in DB, but I'm afraid of that will cause some other exceptions.

Hi Anton,

Have you considered using request scheduler for some time and disable key? Request scheduler uses context of last request and it might not create malformed request.

Still 416 exception is rather strange. We create a web client which than tries to reach scheduler page to trigger task collection. It takes credentials and page address if they are supplied from web config keys otherwise it uses default address ~/cmspages/scheduler.aspx and anonymous access.

Can you try setting up network monitoring on this page? It would be interesting to see why a request would be malformed. Another thing, that I can think of is to set a webClient object in some custom code a, make a request with client.DownloadData(url); and see in debug how is the request formed. We are not doing anything special in RunSchedulerRequest code and method is really simple with use of just mentioned .net object.