I'm trying to deploy a simple AspNetCore web application to Azure Websites using the following process:
https://docs.asp.net/en/latest/tutorials/publish-to-azure-webapp-using-vs.html
I keep getting the error message:
"ErrorEntity": {
"Code": "NotFound",
"Message": "Cannot find user.",
"ExtendedCode": "09004",
"MessageTemplate": "Cannot find user.",
"Parameters": [],
"InnerErrors": null
}
I have tried this from a new project and existing project and both give the same error.
Googling for the issue turns up the following:
https://social.msdn.microsoft.com/Forums/en-US/7743aca4-1a88-4ef5-ab74-98992f2bbf22/cannot-find-user-error-when-creating-new-app-service-plan?forum=windowsazurewebsitespreview
However I haven't been able to get a solution so far.
Anyone else had this issue or managed to find an answer?
Thanks
Microsoft stated it was an intermittent issue. There is a workaround they provided but it's not longer an issue for me so I can't test it. Might help someone so I've provided it below anyway for the sake of completeness. If like me you no longer have an issue I suggest this question is closed.
Go to portal.azure.com -> Browse -> App Services -> (open any web app) -> Settings -> Deployment Credentials
Enter in a new password and save (please ignore the validation error after saving)
After the update succeeds, try creating a new App Service Plan, or Web App with a new App Service Plan.
Related
I hope somebody can guide me with this issue. I do not have issues deploying resources via the web interface. This time I am trying to automatize my infrastructure and I am deploying via ARM. All the resources for the Service Fabric cluster I am trying to create are deployed with no issue, except for the VMSS which throws me this error:
{
"status": "Failed",
"error": {
"code": "LinkedAuthorizationFailed",
"message": "The client has permission to perform action 'Microsoft.KeyVault/vaults/deploy/action' on scope '/subscriptions/xxxxxx/resourcegroups/AllyStage-v2/providers/Microsoft.Compute/virtualMachineScaleSets/StageNode', however the linked subscription 'xxxxx' was not found. "
}
}
Thanks.
It would have helped to look at the ARM template that you're trying to deploy. However, I suspect the problem is that the resource ID for a resource or subscription isn't resolving correctly. Here is a similar issue from the past.
Also, if you are deploying the ARM template from within another bash/PowerShell script, I suggest you ensure that you have the correct context/subscription set before initiating the template deployment, and verify the scope of permissions of the principal performing the deployment.
I am trying to deploy a model to Kubernetes in Azure Machine Learning Studio, it was working for a while, but now, it fails during deployment, the error message is as follows:
Deploy: Failed on step WaitServiceCreating. Details: AzureML service API error.
Your container application crashed. This may be caused by errors in your scoring file's init() function.
Please check the logs for your container instance: pipeline-created-on-07-28-2020-r.
From the AML SDK, you can run print(service.get_logs()) if you have service object to fetch the logs.
You can also try to run image viennaglobal.azurecr.io/azureml/azureml_6ae744633f749472feb283065055dc2c:latest locally.
Please refer to http://aka.ms/debugimage#service-launch-fails for more information.
{
"code": "KubernetesDeploymentFailed",
"statusCode": 400,
"message": "Kubernetes Deployment failed",
"details": [
{
"code": "CrashLoopBackOff",
"message": "Your container application crashed. This may be caused by errors in your scoring file's init() function.
Please check the logs for your container instance: pipeline-created-on-07-28-2020-r. From the AML SDK, you can run print(service.get_logs()) if you have service object to fetch the logs. \nYou can also try to run image viennaglobal.azurecr.io/azureml/azureml_6ae744633f749472feb283065055dc2c:latest locally. Please refer to http://aka.ms/debugimage#service-launch-fails for more information."
}
]
}
I know this question is about a different error, but the debugging steps should still be the same.
AML - Web service TimeoutError
It seems it was a bug, got corrected by itself today. Closing this question now
I'm trying to automatically deploy a resource of type Microsoft.BotService/botServices on Azure and the deployment gets stuck endlessly retrying it while only giving me a "Internal server error (500)" message.
Is there any way to get more specific information?
Click on the resource group you're deploying to in the Portal.
In the Azure portal I select my web app and then "Application settings" and it shows this:
An error message, "Failed to load settings", for application settings and also for connection strings.
How do I fix this?
Additional information:
Another user with the same privileges than me is also experiencing this issue when going to the same Application settings page. Also I'm able to deploy so I have the privilege to modify web.config
Additional information #2:
So I used Chrome Inspector as suggested and its trying to get application settings with a POST to https://management.azure.com/subscriptions/xxxxxxxxxxx/resourceGroups/xxx/providers/Microsoft.Web/sites/xxx/config/appSettings/list?api-version=2015-08-01
This is the JSON response:
{
"error": {
"code":"ReadOnlyDisabledSubscription",
"message":"The subscription 'xxxxxxxxxx' is disabled and therefore marked as read only. You cannot perform any write actions on this subscription until it is re-enabled."
}
}
Sometimes the Azure portal has bugs.
Also try https://preview.portal.azure.com, occasionally that works for me when the main portal has errors.
When I try access e.g. myapp.azurewebsites.net/parse I get the error {"error":"unauthorized"}.
I'm not sure why as the parse web app I had previously on azure (before the trial ended - now deleted) worked fine. Since the trial has ended I have created a new web app identical to the last (different name however), using the same github deployment and app settings. I can't figure out where I've gone wrong and can't seem to find any advice online. Thanks!
So after digging it seems that they have configured the dashboard to be at the following url:
https://[YOURSITE].azurewebsites.net/parse-dashboard/
You can log in with your parse appid and masterkey.