I made a web job for my azure website. It works when I click "Run Once" in the azure website web jobs tab but it doesn't work when I set it at determinate time every day.
The web job is marked as success but the it does nothing. I was checking the web jobs logs and it seems that there were five attempts but all of them shows: Http Action - Request to host '******.scm.azurewebsites.net' failed: The job is missing basic auth fields. I have the AzureWebJobsDashboard and AzureWebJobsStorage in the website config, the web job config and in the azure connection string config, I added them everywhere hoping for a fix but it didn’t work.
It was working fine yesterday but today I made a small change, when I uploaded the new version it didn’t work at the time it was set. The change was a new column in a sql query. Has anyone gotten this error? Thank you in advance for your help.
Loading the web job using the azure web page and then configuring the schedule solved the problem. I don´t know why my deploy from visual studio is not working with schedule when it worked fine 2 days ago.
Where exactly are you finding that "missing basic auth fields" error message? What type of scheduled job are you using? I suspect Azure Scheduler. Are you finding this error in the Azure Scheduler logs?
If you're in the Basic or Standard pricing tier, since you're using the WebJobs SDK, there is a simpler schedule mechanism that you can use. See TimerTrigger here.
Related
I've got a free tier Azure Cloud Account. I used to have a project and requested a free agent for running pipelines. All was ok.
I deleted that project and created a new one.
I'm now trying to create a very basic Hello World kind of pipeline and getting it to run, to test things. The pipeline fails to run with the error below.
Error Message: No hosted parallelism has been purchased or granted. To request a free parallelism grant, please fill out the following form https://aka.ms/azpipelines-parallelism-request
I can see in my organization settings that I have that free agent available and 1800 mins/month of run time available. But i think that agent isn't getting used/found by my pipeline jobs.
I'm a noob at azure, so pardon me for any goof ups in the question.
You just write message to https://aka.ms/azpipelines-parallelism-request with your name, email, project etc. and after 24-48 hours you can run your pipeline
Microsoft comes with some temporary alternative approach until the automate is implemented to grant the permission for those users who requires the free hosted agent pools.
Now users needs to be drop the email to get the free tier access based on the project visibility types.
There is not a standard timeline for approval which someone can predict approval in days, but by considering the mass requests and manual approval process we can consider the timeline of 7 to 15 working days from your email.
For More information -> https://devblogs.microsoft.com/devops/change-in-azure-pipelines-grant-for-private-projects/
Solution: Just after posting this question, I thought of creating another project and make it private. I then ran a sample pipeline and it worked. So basically, my issue was that the pipeline granted to me was for a private project and not a public one. I had forgotten about it as i was revising azure after some time.
I have a web app, ironradio.org, that I've deployed on Azure from VSCode. I've made some updates to the site and am now trying to deploy the newest version. Now when I try to deploy using this button:
I get the error 403 - This web app is stopped in the output window:
I've already deployed several versions of the site using the same method and it's never failed before. Also, the app is definitely not stopped because I can still browse to the site and it shows up.
My best guess as to what's going on is that I associated the App Service with a new resource group since the last deployment, so maybe VSCode isn't recognizing that? Does anyone have any idea what's going on here?
I tried the link given in the error message, but it wasn't much help.
Microsoft foreseen this type of error and how it can affected its customers greatly and this is why the deployment slot is for you.
Firstly, you have to delete the app and reupload again except you set up continuous deployment which work mostly with GitHub and other version control platforms.
Apart from this, I will suggest you check out the deployment slot docs. It’s very simple and easy to use
https://learn.microsoft.com/en-us/azure/app-service/deploy-staging-slots
i am trying to have dedicated service connections per pipeline, so i have removed the "allow all pipelines to use this service connection" and i have pointed a task at the service connection, which works fine. But when i look in the service connection list under "policies" it doesnt show anythinf under "authorized pipelines", from an admin perspective it would be useful to see this. Am i doing something wrong? ive looked all over but cant find anything to suggest what it could be (ive tried in 2 different ado orgs aswell, they have the same issue)
This should relevant with our side, and be delayed due to the time.
If some pipelines created and executed not long ago, it will not display under authorized pipelines immediately. It needs some time to let it updated in the Service Connection page.
Some old pipeline which exists for several days, could be detected by the server. Then displayed under the authorized pipelines pattern:
Just wait for patience, if these pipeline still not display under authorized pipelines pattern. Please raise this issue on our official community: Microsoft Developer Community. We would involve the product group to investigate this abnormal issue.
I'm currently trying Azure Logic Apps and Integration Services.
I always get an IntegrationAccountNotReady error message, when I'm trying to transform a XML-File with Azure Logic Apps and an Azure Integration Account.
The message says I should try it again later. However, I waited 5 days with no success.
My Logic App and the Integration Account are successfully connected.
Here is my flow:
On File Changed Trigger (One Drive) - Works as expected
Tranform XML - The error is raised
Is there any easy solution to solve this problem?
Regards,
Florian
I tried it again and again. Finally it worked - without any changes in my configuration, integration service or logic app. Strange...
Sorry I got no better answer to this...
I had a similar problem. Refreshing the Resources in Dashboard solved it immediately.
I'm trying to get diagnostics to work on my Azure Web Worker Role. I start out with the stock Web Worker Role solution by selecting 'New Project/Azure Cloud Service'. If I de-select the 'Enable Diagnostics' on the properties Worker Role, then I can successfully deploy the stock web role. It doesn't do much, but it deploys and appears to run. If I select the 'Enable Diagnostics', the deploy fails with:
9:27:34 PM - Applying Diagnostics extension.
9:27:37 PM - Value cannot be null.
Parameter name: s
I've tried various combinations for the 'Configure...' choices but get the same error. This appears on two machines now, so the chances that it's some sort of corruption are slim.
Anyone have a clue what's going on or have a simple, working example of emitting and reading diagnostic messages?
I got a different answer from MS support: “Our Product Team has rolled back the changes.”
I test it, and now I can publish with the diagnostic enabled without problem.
I got an answer from the support : it's an identified backend issue and the tech team is working on it with the highest priority.
As a workaround, disable diagnostics :