All blogs / DevOps / SRE / infrastructure
Demystify
learn.microsoft.com/en-us/archive/blogs/pratyay
Learn to unbox hurdles in technologies
DevOps / SRE / infrastructureDistributed systems / cloudWeb developmentMicrosoft blogsMSDN archive
- Posts
- 19 from 1 Feb 2016 to 16 Aug 2018
- Posting
- archived, read-only
- Kind
- personal blog
- Feed
- https://learn.microsoft.com/en-us/archive/blogs/pratyay/feed.xml
2018 17
- RDP not working for my cloud service
- Scenario 8 : ASP.NET SignalR application is not working in azure cloud service
- Scenario 7 : I cannot access my website, although all role instances are in running state
- Scenario 6 : Not able to RDP to only 'HealthMonitor' worker role instance and getting an error : This computer can't connect to the remote computer
- Scenario 5 : My website is throwing HTTP Error 503. The service is unavailable when browsed over the default cloud service domain url (*.cloudapp.net)
- Scenario 4 : ProcessorEngine role is stuck in Busy state stating - Preparing to start role... System is initializing
- Scenario 3 : Autoscale is not triggering for FileUploader role although CPU utilization in one of the instance FileUploader_IN_1 always stays at 100%
- Scenario 2 : AssemblyBinder role instances is throwing System.IO.IOException -There is not enough space on the disk and stuck between Busy and Restarting state
- Scenario 1 : ZipEngine role is looping between Restarting and Busy state throwing an unhandled exception: Could not load file or assembly - An attempt was made to load a program with an incorrect format
- Azure Cloud Service Troubleshooting Series
- Scenario 5 - Request throttling problems and HTTP 403 - Forbidden issues
- Scenario 4 - Performance hit in API calls
- Scenario 3 - Receiving unauthorized errors (401) while invoking APIs
- Scenario 2 - SOAP based API returning 404 and 500 HTTP status codes
- Azure API Management Troubleshooting Series
- Scenario 1 - API returning blank response
- Install .NET Core in Linux using Azure Batch Start Task