Error creating Webjob schedule

Question

I have source code hosted in TFS 2012 when installed in place. When I try to publish my Azure WebJob for Azure from Visual Studio 2015, I get the following error.

Error: An error occurred while creating the WebJob schedule: the response status code does not indicate success: 409 (conflict).

The web application is created in the web application, but it is set to On Demand, and not according to the schedule.

When I open Fiddler to try to fix this problem, I get the following error.

Error ERROR_CONNECTION_TERMINATED: The network deployment task could not be completed. (Web Deploy had a problem connecting to the server and had to end the connection. Contact your server administrator if the problem persists. Find out more: http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_CONNECTION_TERMINATED .)

How can I publish my planned WebJob for Azure? Or at least get more specific errors?

Answer 1

I had the same problem, and it turned out that the publishing process failed, because I set it to repeat every 10 minutes, while the application was intended to run on a free level. As MS describes:

https://azure.microsoft.com/en-us/documentation/articles/websites-dotnet-deploy-webjobs/

You can expand all frequencies other than those specified in minutes.

Answer 2

If the VS tool does not work, and you do not want to manually configure the Scheduler, you can try using the built-in scheduler that Kudu provides (web application management infrastructure) - https://github.com/projectkudu/kudu/wiki/Web-jobs# scheduling-a-triggered-webjob

To schedule WebJob to start, you need to add the schedule property to the settings.job file. The schedule value is a cron expression that has 6 fields to represent the graph: {second} {minute} {hour} {day} {month} {day of the week} .

To do this, you need to use standard WebApp with "Always On" enabled to make it work.

So, you just add the following to the settings file if you want to run every 5 minutes.

 { "schedule": "* */1 * * * *" } 

Sorry for the problems with the tools, this is what I am trying to solve.

Answer 3

I had problems deploying Web Job several times and had to manually deploy it through the azure portal. This is a little annoying, but much more reliable.