I have a Bot App Service in the Azure Portal. I had it in a subscription under a resource group called "pnibot", then I had to move it to another subscription, now under a resource group called "PNI". The app itself is working properly.
My problem is that when I click the resource to open it and get the build options (the view that lets you open the code editor or download the source code), I get this error:
"The Resource 'Microsoft.Web/sites/pnibot' under resource group 'pnibot' was not found."
As I said the bot works properly, and I can open the other tabs with no problem (Channels, Analytics, Settings), but I need to be constantly opening this view to work on the code and sometimes download it, so this is a tedious issue. Can anyone help?
Related
While exploring Azure Virtual Networks, I tried to delete NetworkWatcherRG resource group. The deletion was not successful as it seems. After that I am not able to run any connectivity tests.
The error seems to be with the process of deletion of NetworkWatcherRG. Here is the raw format of the error provided by Azure.
"message": "Cannot deploy to resource group NetworkWatcherRG: deleting.",
"name": "Error",
"stack": "Error: Cannot deploy to resource group NetworkWatcherRG: deleting.\n at https://portal.azure.com/Content/Dynamic/KqF9_ozsrMOn.js:2:14004\n at s (https://portal.azure.com/Content/Dynamic/fcfeK376smSa.js:17:2614)\n at Object.next (https://portal.azure.com/Content/Dynamic/fcfeK376smSa.js:17:1907)\n at o (https://portal.azure.com/Content/Dynamic/fcfeK376smSa.js:17:1680)",
"extension": "Microsoft_Azure_Network"
I have waited for more than 2 hours to complete the deletion process, but the same error is popping up.
The error you have posted says that the NetworkWatcherRG resource group is stuck at deleting. So I would request you to try the below provided steps to delete the resource group completely:
-Open a web browser and navigate to https://resources.azure.com
-Log-in to the appropriate Azure account.
-In the blade on the left side of the browser, expand subscriptions, then expand the desired subscription name.
-In the blade on the left side of the browser, expand resource groups.
-Under resource groups, click on the Resource Group "NetworkWatcherRG".
-Near the top of the content window of the browser, select the Read/Write push button
-Select the Actions(POST, DELETE) tab on the NetworkWatcherRG resource group within the resource explorer and click on Delete. It should give a green tick if succeeded and red exclamation with the error message at the bottom of the page, in case it fails.
Confirm if the resource group is deleted. (It will take some time to delete, so please wait for at least 15 mins).
Once you confirm that it is deleted, you can enable Network watcher for all the regions where you have Vnets deployed via Azure portal following the below article:
https://learn.microsoft.com/en-us/azure/network-watcher/network-watcher-create#create-a-network-watcher-in-the-portal
After you have enabled all the Vnet regions in your Network Watcher, you can check if the connectivity tests are working.
I am new to azure and i am exploring it now, as first step i created a free azure account and in that i created a Resource group and an App service to that resource group.
When i try to access the Url https://azurehome.azurewebsites.net/ its giving an error 'The service is unavailable.'
any help on this ?
Please follow this document to troubleshoot:
https://learn.microsoft.com/en-us/azure/app-service/troubleshoot-http-502-http-503
By the way, this problem may be caused by the region you choose, trying to change the region may be effective. I'm using Central US and it works fine.
If it still doesn't resolve, please provide more information.
If you need support, you can click this link:
https://azure.microsoft.com/en-us/support/options/
I'm new to Azure platform. I'm trying free trial and creating a CI/CD setup for docker by following from the below link.
https://www.azuredevopslabs.com/labs/vstsextend/docker/
I have no issue until setting up build definition. I'm getting below issues when doing changes in the release definition.
when i click on "Authorize" button in azure subscription, I'm getting below issue.
Please let me know what mistake i am doing.
well, the text says it all. you are trying to create a connection with a name that already exists. you need to call it something different or rename the existing one
I have created a new service connection and mapped in the release definition.
Click on Manage link
Click on New service connection button
at top right corner
Select Azure resource manager
Once you select the respective option and click Next. Enter valid name and select respective subscription and resource group details.
I am getting error while creating bot. I am trying to deploy a Web app bot. After specifying the name of resource group and their location I click on create. After which bot deployment process starts. But it ends up with an error:
MsaAppId: MsaAppId is already in use..
What can I do successfully deploy a basic bot. This is second time in a week, I am facing something like this on Azure.
Edit
Initially I was using Autocreate MsaAppId & Password option. That didn't work out (although that used to work)
Then I tried a couple of times with Create MsaAppId & Password option. Which takes to a different page to generate AppId & password, and I pasted the new keys in the provided fields.
Still the same result. MSA App Id already in use
Edit 2
As one of the answer mentioned, I tried creating a separate Bot Registration which I will link up with the Web app later.
But that fails with a weird message saying, App Insights is already deployed, and cannot deploy with same name, when in fact, I have not asked for any new App Insights instance to be deployed. Attaching a screenshot
it ends up with an error:
MsaAppId: MsaAppId is already in use..
I have same problem, when I create the web app bot (select Auto create App ID and password option), it failed at creating botServices resource.
Deployment:
Failed operation details:
I also tried to manually create app on https://apps.dev.microsoft.com and provide App ID and password for creating botService, but the deployment still failed.
As a workaround, I manually created Bot Channels Registration and specify corresponding web application URL as message endpoint, and then modify Application settings of that corresponding Azure web site with new App ID and password, which works for me.
Note:
I suspect something wrong with Azure while performing deployment and creating botServices, if possible, you can report it on Azure portal or create an issue on github.
Updated:
I click Automation options and download the template after I enter the required information/fields for creating a new web app bot, and then I perform deployment by using powershell with downloaded template¶meter file, which work for me, you can try it.
I have published an API app from Visual Studio to a new resource group, also created an App Service Plan, so after the deployment the resource group contains 2 items:
AppServicePlan1
AppService1
Now I am trying to deploy these items to another resource group as follows:
Select 'Automation script' in the resource group settings
Click 'Deploy'
Select 'Create new' resource group, enter its name
Enter 'Serverfarms_AppServicePlan1_name' parameter value (new app service plan name, e.g. AppServicePlan2)
Enter 'Sites_AppService1_name' parameter value (new app service name, e.g. AppService2)
Tick 'Agree to terms and conditions'
Click 'Puchase'
The process fails with the following error message:
"The host name AppService1.azurewebsites.net is already assigned to another Azure website: AppService1."
I have tried different things - deploying app service plan, logic apps, etc. from one resource group to another works fine, but deploying an app service fails as described above.
I have tried changing the hostNames property in the template file to ["AppService2.azurewebsites.net"] manually - I'm not getting the error then (although I'm not sure, maybe something else also needs to be changed, e.g. properties enabledHostNames, hostNameSslStates?) and the deployment seems to work, however the 'deployed' app service can't be used as it contains only 1 file - hostingstart.html.
What am I missing?
I think you have everything correct - as you noticed when you use the generated automation script it will create everything with the same properties that currently exist. We try to parameterize the correct value (like the web app name) but there are some details that can be overlooked (like host names). After changing all that it sounds like you got it to deploy.
The "code" however is not part of the automation script - only the infrastructure and configuration. So you still need to deploy your app to have it be identical. You can folder app deployment into the JSON template (using webdeploy or github) but since that requires access to external artifacts, that's not done automatically.
That help?