I'm getting the following error while trying to publish an Azure cloud service (classic) from Visual Studio:
There's so little information in that error that I have no idea what to start fixing. Is there a more detailed log somewhere, and what steps (if any) need to be taken to enable it?
The solution for me that works is to refresh the Azure connection. I use for that the Server Explorer - expand the needed service branch lead to the solution.
The solution can be refresh the credentials as well. It may be connected with the Visual Studio or Azure SDK versions, so it is worth to try to start from reinstalling at least Azure SDK.
Related
I am trying to use Azure DevOps pipelines to build a .NET 5 (Core) web app and deploy it to my Azure app service. I can't find any complete examples in the documentation that achieve this so I'm following this:
https://github.com/shahedc/NetLearnerApp/blob/main/azure-pipelines.yml.txt
However, the Azure deploy task keeps returning this vague error:
In my Azure portal I only get this error:
I am assuming the issue is in my pipeline because deployment works when I deploy it directly from the Deployment Center in the Azure portal. Here are the details for the 3 relevant tasks my pipeline:
I found the solution. It turns out the issue was not in the pipeline, but was caused by a Git connection to the app service I had previously set up in the Azure Deployment Center. Even though I disconnected/removed this Git connection, there was somehow still a residual file left over in Azure that was causing the error. I deleted the 'deployments' folder in Kudu (pictured below) and the pipeline started working as expected.
Getting to the above pictured view:
Navigate to your Azure Function project
Search for Advanced Tools
Open PowerShell
Check if you have disk space available.
Yesterday we started getting this error, even if we tried to re-deploy packages that were successfully deployed just an hour before. Our system guys checked and found out that we reached the space limit and that it was time to upgrade.
P.S. I know that this was answered a long time ago. I am just sharing the solution that was not mentioned here and that worked for us.
think what Dan Beaulieu said in above answers is correct, but one thing to add, in my case, after deleting the deployments folder, remember to restart the app service/web app, which will make it take effect.
I have a working azure web app, I cant deploy anything when I click Deployment center it just stuck at Fetching deployment data
If I wait for while I get this:
I have to mention that I had apps before on azure and everything worked smooth.. the only difference between the apps is that the broken app I created with azure VS extension.
all the apps are configured to auto-deploy from Bitbucket
For me, there wasn't enough space on the disk. I saw this "lack of space" error message after clicking Deployments in Kudu (Advanced Tools in your web app). I deleted the LogFiles folder to free up space and everything went back to normal.
I had the same problem with deployment sticking/breaking when I was trying to use the F (free) tier. I was trying to push a .NET Core app with https: support enabled in the app. Because the F tier does not support SSL, it broke everything and there was no trace to say what the problem was. Not sure if this was your problem as well, but if anyone is trying to do the same thing that I did, I hope this is helpful. Changing to an S (standard) tier fixed it. I suppose disabling https: support in the app you are trying to push would work as well, but I did not try that approach.
This happened to me last night. Finished up some changes to an API and front end app. API published to app service without issue from Github pipeline. Front end app would not publish. Error was:
Deployment Failed with Error: Error: Failed to deploy web package to App Service. Conflict (CODE: 409)
Same issue as here. The deploument center would never load and eventually would give me a Gateway Timeout error. Two hours I spent trying to figure out what was wrong. Even opened a support ticket. It was a problem with the Azure service that was resolved by the next morning.
I have release azure function app from VSO Azure App Service Deploy release task,
it gives:
System.Nets.SocketException: An attempt was made to access a socket in a way forbidden by its access permissions I searched on google, people say the sockets get expired but i am using S3 pricing tier
I have then released the same function app from Visual Studio 2017 which runs perfectly fine without any exceptions.
I am attaching the artifacts, build assets, release pipeline details, please help. I will not be able to move to production unless this issue is resolved.
Structure of Artifacts which is not working
Structure of artifacts which is working fine-published from VS2017
Here is the github link for more details regarding the issue.
https://github.com/microsoft/azure-pipelines-tasks/issues/11345
I had to give a proper storage connection string for the following, instead of UseDevelopmentStorage=true,
I have created an Azure WebSite in Visual Studio. I then added a Azure WebJobs project through Visual Studio. I then provided the connection string to my storage account to both the app.config file of my WebJob project and the web.config file of my WebSite project.
I still cannot get the job to complete successfully. It keeps failing, as I can see that on the Dashboard. When I go to the Dashboard, not only do I see the job failing every time I run it, I also get a red notification that my connection string is incorrect for the AzureWebJobsDashboard. I've provided this connection string in both projects, and I've copied from the Azure Portal, so there is no way I'm getting the connection string wrong.
How can I fix this? I'd like to start creating real WebJobs, but I can't even get the example one to work (the one given to you as a ManualTrigger when you add a WebJob project in Visual Studio).
update
I had forgot to mention that this connection string is also in my application settings in the azure portal already and I still see failures.
Try adding the connection strings on the Application Settings page of your WebApp in azure.
UPDATE
Use a General-purpose storage account to get rid of
System.InvalidOperationException exception.
I've been having trouble trying to get Azure diagnostics to work since upgrading to 2.5. I went through the steps here, but I get no data from my cloud service until I click on the role in the server explore, enable diagnostics, and fill out the form again. Any ideas on how to fix this? Since I have to do it each time I deploy (manually) it's a pain.
edit: It looks like this only is failing with powershell deploy, but deploy from VS is working correctly. I'm guessing there are some new calls to make to enable diagnostics from powershell deploy.
The steps at http://blogs.msdn.com/b/kwill/archive/2014/12/02/windows-azure-diagnostics-upgrading-from-azure-sdk-2-4-to-azure-sdk-2-5.aspx should help, in particular the last section which shows how to do this via Powershell.