Skip to main content

Windows Azure Instance - Remote Access Problems

La orice instanta din Windows Azure, un user se poate conecta remote ca si pe orice alta masina. Acesta are acces la orice fel de resurse din sistemul de operate incepand de la task manager la event logs sau la Windows Services.
Pentru a ne putea conecta remote la instanta unui rol este nevoie ca de portalul Windows Azure sa selectam instanta la care vrem sa ne conectam, iar apoi din meniul de sus sa apasam butonul "Connect". Browser-ul o sa faca download la un fisier cu extensia .rdp, care se foloseste pentru conextiune remote. Odata rulat acest fisier, totul o sa decurga normal, o sa fie nevoie sa introduceti credentialele si gata, sunteti conectat remote in Cloud.
Pana aici nu o sa aveti nici o problema, totul o sa mearga ca uns. Insa in unele cazuri o sa va treziti ca instanta pe care o aveti nu poate sa fie gasita, orice ati face. Cand incercati sa dati conect, aplicatia sta cateva secunde iar apoi primiti o eroare de genul:
The specified user name does not exist. Verify the username and try logging in again. If the problem continues, contact your system administrator or technical support.
Desi rolul functioneaza, la fel si instantele pe care le aveti, totul este in regula. Acest lucru apare uneori dupa 2-3 zice ce ati folosit fara problema remote conenction-ul pe cloud. O solutie simpla pe care am gasito la aceasta problema este sa deschideti cu un editor text fisierul .rdp si sa inlocuiti friendly name-ul (DNS name) pe care il aveti pe prima linie cu IP-ul instantei.
Before:
full address:s: myApp.cloudApp.net
After:
full address:s: 123.123.123.123
Am observat ca acest lucru se intampla dupa ce se schimba administratorul la o subscriptie (acest lucru se poate face doar la cerere si este facut direct de cei de la Windows Azure support) sau se fac modificari complexe.
Sper ca acuma functioneaza si la voi :-).

Comments

Popular posts from this blog

How to audit an Azure Cosmos DB

In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...

Can User Technical Profile Influence AI Architecture Decisions?

In the last few days, I ran a small experiment on Devin/Windsurf/Cascade, BMAD, and LLM-based architecture decisions. The initial concern was simple: if an AI coding assistant knows something about the user, for example, that the user is a Java developer or a .NET developer, can this information influence the architecture and technology stack that the AI will propose? This question is important because many companies are starting to use AI tools not only for coding but also for product discovery, architecture, documentation, and technical decision-making. If the AI is influenced by the developer's personal profile, the result may not be fully neutral. It may look like a business or architecture decision, but in reality, it may be partially shaped by the context of the person using the tool. The test was done using BMAD with Devin/Windsurf/Cascade. The scenario was a unified field service operations platform. The task was to let BMAD refine the product, define the architecture and s...

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see...