After trying to implement High Availability to one of the existing servers following this article
https://www.windowsazure.com/en-us/documentation/articles/virtual-machines-capture-image-windows-server/
After I was done the newly created machine is running, however I cannot RDP or PING any of the services that are running on the server existing. It shows that the VM is running
Has anyone faced such a problem before ?
In case this unexpected issue happens. The workaround is to create an XSmall VM and RDP to the VM that is not responding through internal IP. This should get it to start.
Related
My team have created an IR in an on-premises VM and we are trying to create a Linked Service to an on-prem DB using that IR
Whenever we click on Test Connection in the Linked Service, the connection fails and IR goes into a limited state
We also whitelisted the IPs provided by Microsoft for IR ADF and also checked the network traces and all seems fine there
Also, we stopped and restarted the IR, uninstalled and installed it again but still the problem resists
Have anyone faced a similar kind of issue?
As this has been a long time we are facing this issue which has now become a blocker for us
Thanks!
This is observed when nodes can't communicate with each other.
You can Log in to the node-hosted virtual machine (VM). Go to Applications and Services Logs > Integration Runtime, open Event Viewer, and filter the error logs. If you find the error System.ServiceModel.EndpointNotFoundException or Cannot connect to worker manager
Follow the official documentation with detailed steps for Troubleshooting Error message: Self-hosted integration runtime node/logical self-hosted IR is in Inactive/ "Running (Limited)" state
As it states:
try one or both of the following methods to fix:
- Put all the nodes in the same domain.
- Add the IP to host mapping in all the hosted VM's host files.
I ran into same issue. Our organization has firewall rules preventing specific ports or url's from outside network. We added Data factory services tags with internet facing in Route table, and IR then connected successfully.
I've been evaluating Azure for a couple months. I'm using it via my MSDN subscription. The intention is to determine if my development team should migrate from VMWare to Azure machines.
I managed to setup multiple VMs and work on them successfully. I tend to shut down all VMs as often as I can in order to not use up my monthly resource allowance.
Very often I lose RDP connectivity to all my VMs. Sometimes it helps to resize the VM but not always. I've tried all steps included on the link below, for instance.
What I am missing?
https://azure.microsoft.com/pl-pl/documentation/articles/virtual-machines-troubleshoot-remote-desktop-connections/
Thx guys (and sorry). It was indeed due to network issues (DNS fails on my home internet provider from time to time).
I have a .NET WCF Service application that is running on an Azure Virtual Machine. It connects and interacts with a Azure SQL Database that has been whitelisted and all works correctly. After some amount of time (usually 5 to 7 days), the Azure Virtual Machine can no longer connect to the Azure SQL Database. Here is what I have checked when it is in this broken state:
1) I have turned off connection pooling and checked "netstat -a" to see if my app is leaking connection when it gets to this state. It is not.
2) I pointed my local development machine (running the same app) at the Azure SQL Database. Everything works fine. No issue connecting.
3) I have tried to telnet from the Azure Virtual machine to the Azure SQL Database on port 1433. It does not connect. After the reboot I mention below, I can telnet to 1433 just fine.
4) I have tried to telnet from my local development machine to the Azure SQL Database on port 1433. It connects fine.
So, it appears to be an issue with the Virtual machine finding the Azure SQL Database.
To get it working again, I have to reboot the virtual machine. iisreset or cycling the application pools have no effect.
This has happened 5 times in the last month. Once I reboot the Virtual Machine it will work fine for approximately 5 to 7 days and then gets into this state again. It does not seem to recover on its own, as I have left it in this state for over a day to see if it would self-correct.
Any help to either resolve the issue or ideas on what to check when it gets in this state would be very much appreciated.
Converting comment to answer :
Have you checked for memory leaks? SQL VM does not close any ports voluntarily so the fact that a port gets closed after few days points to a possibility of a memory leak causing the port to close.
This was caused by a windows service that was leaking memory. When the service got to around 400MB of RAM consumption, then I was able to reproduce the block telnet to the DB server on 1433. When I recycled the service, it started to work. I have fixed the leak and everything is now working ok.
This afternoon I have uploaded my WorkerRole in Cloud Service on Azure, this service run on VM with Windows Server 2012. I have realized that WorkerRole can't get query from Databases (BigQuery, TSQL). When I have read the service log in VM I have seen the following error:
The VM and host networking components failed to negotiate protocol version '5.0'
I think that Hyper-V-vsc has something to do. Anybody knows what happens?
Thanks,
Roger
First thing I could check is to make sure the databases you are trying to connect too have whitelisted the VIP for the cloud service you're connecting from. And if you haven't already, remote into an instance of the worker and try reaching the DB's using a thin a client UI as you can.
In my experience, these issues are usually on the db end. Azure doesn't do much with blocking outbound connections. Those that fail are usually more a matter of protocol (UDP multicast for example).
i have been experimenting with azure services using my msdn account. i created a suse enterprise linux virtual machine. deployed sonar+mysql and a few simple java applications. everything was fine for almost a month, until last weekend. i tried to connect via ssh and could not get a response. i tried accessing the sonar website, again no response. i used the axure portal to restart the vm, it seemed to restart but still no response. i used the azure portal to stop the service. its status has been at "stopping" for several days. any thoughts about what i can do to regain connectivity?
It is very much possible that something in your virtual machine had caused this issue and your best bet is to report this problem to following dedicated forum realted with Windows Azure Linux Virtual Machine so you will get proper assistance to troubleshoot your problem:
http://social.msdn.microsoft.com/Forums/en-US/WAVirtualMachinesforLinux/threads