I deployed an Azure Function 2 months ago.
My VS Code was running perfectly according to my needs. Now I had to make some changes to my deployed function. but upon opening it is showing nothing.
Even from sidebar Azure extension it is not loading exiting azure functions. I tried everything, signin-signout, reinstalling, restarting, but nothing is working out for me. If I try to make a new function it asks me to create a new source although our company subscription is arleady listing in sidebar.
Can someone please help me in this regard?
Screenshot is attached.
We have a lot of function apps deployed since many months and in recent days, but they are showing in the Visual Studio Code Azure Extension under Function App Resources.
Few Steps to retrieve the existing resources in the VS Code Azure Extension are:
Uninstall and Install the Extensions like Azure Account, Azure Functions, Azure Resources, Azure Tools under Extensions blade:
Click on Settings (Gear Icon) > Make Sure your Microsoft Account is synced. If not, Sync it:
Check one of the workaround given for similar issue by #HAL9000
Related
I want to publish an Azure Function Project using the Visual Studio 2022 publish option, but the Create button is always disabled without any visible reason for it:
How can I further research on this, get any error message or so?
Multiple times, Even I too faced the similar issue and haven’t found any permanent solution to it where I’m having the latest Version of Azure Functions Core Tools (4.0.4915), VS 2022 17.4.4 Version, .NET 6 SDK & Runtime installed.
I found the Similar SO issue where many users faced this issue #67813149.
I also found one of the causes of above issue - i.e., If we do not have access to the Azure Subscription, then I observed this Create button is greyed or disabled in the Visual Studio Azure Functions Project > Publish > Create New Function App Window.
Also, Please check you have right RBAC Access to manage the resources in the Subscription such as Contributor role for the Azure Function App Management. Visit this MS Q&A #669276 for more information.
After Sign-out and Sign-in in Visual Studio, System Restart, I got this fixed and working good as of now, but this should not be the fix. If you are facing this issue frequently, mail to azcommunity#microsoft.com.
I'm gettting rather weird error when attempting to create new Azure Function App with Azure Functions VS Code extension:
Subscription MY_SUB_GUID_HERE was not found.
No matter what I've tried: reloading VS Code, re-installing Azure Functions extension (incl. older versions), logging out from my MS account in browser, restarting PC, clearing TenantId in VS Code Azure Account extension, removing Azure Functions extension completely including its folder in C:\Users\USER_NAME\.vscode\extensions, signing out and back in via Azure Account extension, creating Azure Function application through the Azure portal incl. new resource group (I've found some old issue on GitHub which supposedly got fixed and one workaround was to create Azure func app through the portal first) - still the same error message, which occurs after selecting location, but actually in VS Code Log (Window) I can see that it fails immediately after 1st step (error code is SubscriptionNotFound + error message above) when you provide a unique name for the application.
At the same time, creating App Service, Resource Group, Static Web App all works like a charm through the corresponding extensions. Of course I see my subscription on Resources pane in VS Code and hence I'm saying that the error is a weird one.
OS: Windows 10 Pro x64 21H1, build 19043.1826
VS Code: 1.69.2
Azure Functions extension: 1.7.4
Azure subscription: free trial
Azure Functions version: ~4
.NET: 6.0
I cannot understand for love of god where the problem is - friend of mine tried it with his Visual Studio Enterprise subscription and it worked without any problem, so perhaps this is an account-related issue? Strange though that other things like App Service seem to work fine. I have "Owner" role for this subscription so it should not be due to the lack of rights or something similar.
Have you updated the az-cli?
e.g. az login or az logout?
What does az account show shows you?
You will be facing this issue because the Azure subscription is absolutely completely empty and the environment could not able to pick up your subscription.
Restart your environment after deploying a sample resource to your subscription.
Now that the subscription is not empty, It will be able to identify your subscription id. Additionally, confirm that your Azure free trial membership has not expired.
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
When i try to create a new DevOps project from Azure portal by clicking Python as my new application, Django as framework and Web App for Containers as service, i cannot click on "additional settings" button while filling in project details. I have tried 2 seperate accounts and all the available browsers but the behaviour is the same.
It is not a bug, the Additional settings work fine on my side, please try again. Besides, I notice your subscription is a free version, may be you could try to use another one.
Update:
As #Ali Maan said, you should create a devops organization first then it will work fine.
I am developing with Azure storage locally using VS2015. I created and accessed my development storage blob container fine. I upload three images and have code to calculate the size of the images.
For some unknown reason, I cannot expand the Blob Containers node in Cloud Explorer any more. I.e. Cloud explorer > Storage Accounts > (Development) > Blob Containers. Doing so results in the following error message:
Cloud Explorer has encountered an unexpected error: Unable to retrieve
child resources.
It has been working fine in the past, so not sure what's changed. I know there are containers inside and I can seemly create one but then it doesn't show up in the list.
It works for live Azure storage accounts but not development.
Though I can still write code against this Development container - so it's there and functional but Cloud Explorer just not listing the containers i.e. no access to view files / upload file through VS UI.
Here are my steps to resolve
Uninstall Cloud Explorer via Extensions and Updates
Restart VS
Update the Cloud Explorer in Extensions and Updates (that apparently wasn't uninstalled)
Experience the catastrophic behaviour (very slow)
Restart VS
Fixed (seemingly)
Look into Extensions and Updates to see Cloud Explorer is disabled
Everything is fixed.
Update (29/07/2018)
If you are having trouble launching Microsoft Azure Storage Explorer (Development) e.g. blob storage and get the error message "Unable to retrieve child resources" followed by details of "A network error occurred...ECONNREFUSED 127.0.0.1:10002" then simply (install and) run the Azure Storage Emulator.
The aforementioned solution didn't work for me.
The error went away after upgrading to Azure SDK 3.0 (using web platform installer). After that I am able to expand the child resources in App Services, and attach the debugger.
Another option that worked was using the Server Explorer to expand files/attach the debugger, but that option seems to have been turned off in 3.0.
The name of the Storage Account Name is case sensitive to teh azure service. The client however is not.
Because of this you can connect, but when the Storage Explorer tries to enumerate the child object it will fail if the Storage Account is not entered with the proper case.
I got this error when my system-clock was accidentally set a couple of hours back in time. Just saying.