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.
Related
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 have two functions on Azure Functions but only one is displayed on Azure Portal.
Both functions works when acessed by URL.
I'm using docker, NodeJS, VSCode. Anyone knows why its happening?
Below is Visual Studio screenshot.
Below is Azure portal screenshot.
Thanks for the contribution of UnbearableLightness and PankajRawat.
So the solution is create a new function instance on azure and then publish your function code to azure. And then it should work.(I met two other people who faced the same problem and they solved it in the same way.)
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.
We try to set up a FTP connection in Azure, to use in a Logic App. Seems very straightforward, the instructions are very clear:
https://azure.microsoft.com/nl-nl/documentation/articles/app-service-logic-connector-ftp/
When we click on 'create' (of the FTP Connector, so before we are actually in the logic app), absolutely nothing happens. The button turns grey, but nothing happens. No notifications, no fails, no FTP connector.
When we try to set up the FTP connector directly in logic app, we get the error message 'error fetching the deployment template. please try again'.
We have tested the connection in FileZilla, this works. We have tested with 2 different FTP connections, both same result. We have played with every parameter in the settings, no change.
We searched here on Stack Overflow, but we haven't found anything that helps. Most questions related to FTP connections and Azure describe situations where it is necessary to connect to Azure. In this case, Azure would be the client and we want to pull in data from a third party's FTP server to analyze in a HDInsight cluster.
We'd like to fix this issue, but it's very difficult with no error message and no response. Has anyone else experienced this and how did you fix it? Does anyone have a clue how to further debug?
Thank you for your time and effort - I'm aware there is not a lot of information here, which is exactly the problem.
I followed the same steps as mentions in link. It created FTP connector successfully. Use portal for this https://portal.azure.com. What service plan you are using? I am using pay-as-go service plan where it's allow to create me.
I am currently trying to deploy a cloud service to Windows Azure but I get the following error message:
"Could not retrieve the list of cloud services.[...]"
Details can be seen on the picture.
It seems to me that VS couldn't find an existing service role in the subscription but my service is available and running, I just can not deploy a new version there.
A few days ago it worked correctly. Any Idea would be appreciated.
Thank you!
After hours of Certificate generation, messing with azure toolkit, etc. I figured out that the problem was that somehow my computer tried to resolve the azure DNS to localhost because Fiddler got crazy and the proxy that Fiddler uses, haven't stopped even after restarting my computer.
I faced same problem, when trying to deploy to azure while fiddler is running. Simply closing fiddler solve the problem.
Go to the previous screen, there will be an option of connecting to Azure using your credentials. Select your subscription and you will be able to download a file to your local machine. That file contains your subscription info as well as the keys. Once you open that file through this wizard, you will be able to publish to your services. You must create cloud services first before you do that.