I have an azure webjob that was deployed few days ago and it seems that it was working normally. Since this morning, if I'm trying to access the azure webjob through the new portal, I'm getting a strange error message: Error loading part...
Does someone knows how this can be "debugged"?
Thank you
Evdin
Many of the Azure users are facing this issue due to migration from Old portal to New portal. As the new portal is still in preview it's better to use old portal if you face any issue in new portal.Also, raise a support ticket to inform microsoft so that they can work on your problem.
I have been experiencing numerous problems with the Azure portal today. First and foremost continous deployment stopped working so, I've been unable to update my web apps.
But I'm also getting: "Error loading part..." in several other areas. I can only recommend creating some buzz, so Azure is alerted to the issues.
If you see these type of errors in IE you can press F12 to see the errors.
Chrome/Firefox can also show HTTP message details.
I am also seeing errors in the new portal.
I was trying to see azure website and I saw "error loading part" errors.
Microsoft_Azure_Billing] 9:30:19 AM MsPortalFx.Base.Diagnostics.ErrorReporter 2 message: Access is denied.
[WebsitesExtension] 9:30:19 AM MsPortalFx.Base.Diagnostics.ErrorReporter 2 message: Access is denied.
New portal is in preview but is no longer optional as many of the services are only available in the new portal. Azure support should be informed to make them aware of this issue.
It seems that the issue is now fixed but I see another strange issue now - the webjob that I described above is showing as "running on demand" in the new portal (I didn't set it up like this) and is showing as "running every six hours" in the old portal (this is how I set it up)... So it seems that everything is screwed overthere...
Thank you for your responses and your help.
Evdin
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
After performing numerous deployments of some software to Azure, I'm hitting a strange problem which is stopping the deployment from working. (I am doing all these deployments in this case by using Visual Studio's Package command, and then using the Azure portal's Upload button.)
The portal initially says it has successfully started the deployment:
It also says it is creating the staging deployment:
(ignore timestamp, screenshot is from another attempt):
But that's all. It never proceeds to show the instance, going through various states and finally running, as has always happened before. There are no further notifications and no error messages. (Even after 24hrs, for the avoidance of doubt.)
[2
You can also look at the Deployments log for a Resource Group in the Azure Portal by going to that Resource Group > Deployments. All deployments, successful and failed, should be listed there. If you click a failed deployment there should be a note at the top that says Failed. Click here for details. This often gives some more details to why the deployment failed.
Microsofts documentation for this: Troubleshoot common Azure deployment errors with Azure Resource Manager
This held us up for several days. Incredible as it sounds, there's apparently a major bug in the "new portal" that stops the error reporting from working, resulting in a silent failure instead of an explanatory message or logging. In our case we had simply hit our limit of 20 cores in the Azure subscription, but the portal wasn't letting on.
As soon as we deleted a service we didn't need any more, the deployment worked as normal.
The cause was discovered by pure chance, when someone else tried to create a new cloud service just at the time this problem was occurring. A UI message informed them the new service could not be created due to hitting the limit.
The lack of an equivalent message when updating an existing service is is a jaw-dropping defect in the "new portal". Very sadly we are well used to MS error messages being unhelpful, and often even very misleading, but with this silent failure MS seem to have excelled even themselves as far as standards of error reporting go.
EDIT: the old portal helpfully reports core utilization on the dashboard:
Unfortunately that doesn't seem to work on the new portal.
Of far greater significance, though, is that the OLD portal DOES report the deployment failure, rather than failing silently as the "new portal" does:
...which leads to:
So the moral of the tale seems to be: if you have an unexplained deployment problem, use the old portal (https://manage.windowsazure.com). You will probably then find the cause straight away, as the old portal actually reports the failure reason instead of just failing silently as the "new portal" does.
I'm trying to get diagnostics to work on my Azure Web Worker Role. I start out with the stock Web Worker Role solution by selecting 'New Project/Azure Cloud Service'. If I de-select the 'Enable Diagnostics' on the properties Worker Role, then I can successfully deploy the stock web role. It doesn't do much, but it deploys and appears to run. If I select the 'Enable Diagnostics', the deploy fails with:
9:27:34 PM - Applying Diagnostics extension.
9:27:37 PM - Value cannot be null.
Parameter name: s
I've tried various combinations for the 'Configure...' choices but get the same error. This appears on two machines now, so the chances that it's some sort of corruption are slim.
Anyone have a clue what's going on or have a simple, working example of emitting and reading diagnostic messages?
I got a different answer from MS support: “Our Product Team has rolled back the changes.”
I test it, and now I can publish with the diagnostic enabled without problem.
I got an answer from the support : it's an identified backend issue and the tech team is working on it with the highest priority.
As a workaround, disable diagnostics :
I am looking for any advise out there on a error I am getting with the Azure Backup Agent.
A few weeks ago, my free subscription expired and was automatically disabled. I subsequently contacted support and got the service re-enabled in the Azure portal.
Since this time, I have been getting an error on the Azure Backup Agent every time I open it, stating that 'A Problem has occurred with Azure' and 'please contact Microsoft Support' if the problem persists. The Backup Agent will not let me do anything, it is completely locked out (listing no jobs or other options to be able to click on), however it keeps on running every day and I am unable to stop it.
Upon logging a support request via the Azure portal, I have been informed that I need to purchase a support package to be able to receive any technical support.
I have tried searching the usual forums, and have not been able to find anything in regards to this specific problem.
I am posting here in the hope that someone can advice me on how to resolve the error, or alternately how to get someone from Microsoft to respond to me without it costing me an additional $40 per month.
Any help would be greatly appreciated.
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.