I am getting the error as below in my Azure Virtual Machine when I save my vhd:-
Failed to capture image vmvhdtrialacc of virtual machine vmvhdalpha
Endpoint Not found: There was no endpoint listening at https://management.core.windows.net:8443/*GUID*/services/hostedservices/vmvhdalpha/deployments/vmvhdalpha/roleInstances/vmvhdalpha/Operations that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.
Any idea what could be wrong here?
Unfortunately your problem is a recently known issue with Windows Azure Virtual Machines, described as "still investigating status", in the following Windows Azure Virtual Machine Forums:
http://social.msdn.microsoft.com/Forums/en-US/WAVirtualMachinesforWindows/thread/29fc7e72-6c95-4704-bf79-b9aba562c6ad
My suggestion will be to submit your issues in the same forum and track the status of your problem in the above link.
Strangely enough I had a running VM, then added an SSL cert to a separate Cloud Service via the portal, and that seemed to doom my VM. It went into a stopped state, and when trying to start it received the error above. Only solution as mentioned in prior post's links, delete the VM (or delete the VM and clone new one from VHD).
Related
I have moved a website to a new on-prem server and I'm currently trying to make CI/CD work. The release pipeline was already configured since we have been using Azure devops for years. So the only thing I needed to do was to register the new server in the development group. I ran the registration script, added the proper tags and didn't set a specific account for the Windows service so the default account NT Authorization\System was used.
The problem is that when a release is triggered, the service doesn't seem to be able to list the site as part of the Manage IISwebsite task. It throws a weird error "The device is not ready". It does though manage to change the apppool. See the logs below:
I have ran the command myself directly on the server using my admin account and it works just fine. The NT Authorization\System is a super user and should have all rights granted by default as well, so I'm a bit clueless here..
Does anybody have any ideas, suggestions? What am I missing?
Thanks in advance.
/Kenia
I had the same problem. In my case the error message was misleading.
It turned out that the Physical path in the release pipeline was wrong. It worked after I changed it to the correct one.
Creating the topic cause I didn't find any info on this issue, followed strictly the Microsoft documentation below but it didn't work.
I need to migrate a couple of Hyper-V VMs to Azure for a Lab that I want to run some study and tests.
I tried to run the procedure described on the doc:
https://learn.microsoft.com/en-us/azure/migrate/tutorial-migrate-hyper-v
I proceed with all the steps with no problems, until the migration itself.
On the first time I ran the Azure Site Recovery Configurator, the process went ok with no errors.
It discovered the machines, but I did not start the replication. At that moment I needed to turn off the computer (Windows Server 2016, Hyper-V Host), so I would go back later to start the migration of the VMs.
On another day, when I start the replication of the VMs it got stuck on 1% and not proceeding.
After several hours stuck, I noticed that the VM Host on Infrastructure Servers page was in a "Not Connected" connection status.
According to the initial page of the application (webpage running on port 44368): Discovery agent, Assessment agent and management app are running.
I ran the PowerShell script that would prepare the host to make the migration (Enable Powershell, open WinRM ports, etc).
It's a home lab so I have no firewall and stuff, just a simple router.
On services, every Microsoft service is running except for RecoveryServicesManagementAgent, which stops immediately after I started it.
I tried to register again with Azure Site Recovery Configurator on the Hyper-V Host and I got the following error:
Registration was successful but setup failed to start Microsoft Azure Site Recovery Service on this machine. Please try starting the service manually.
I didn't find any info on this service and error, and it's not on services.MSC console as well.
I noticed that the server goes to a "Connected" state on Infrastructure Servers page for a while, but it stops again and returns to "Not Connected".
Also, I tried to stop the replication task on the single VM I tried to replicate and it's now stuck on "Disabling Protection" as well, probably because it cant reach the server as there is something wrong with the configuration of services running.
Another problem that I noticed is that my monthly credits are slowly decreasing (Free Trial) after I started this whole process.
Did anyone with a better understanding of this procedure can help me migrate the Hyper-V VMs o Azure or at least point to some direction?
The query needs a further deeper dive technically.
I recommend you to create a technical support ticket. The ticket enables you to work closely with the support engineers and get a quick resolution to your issue.
Here is the link https://learn.microsoft.com/en-in/azure/azure-supportability/how-to-create-azure-support-request to create support case.
please open a Support Ticket so the team can engage directly with you to resolve the issue.
I am not able to login my Azure VM. I have reset the password through azure portal but it is still not logging in. Previously, it used to log in and now it is showing following error :
An authentication error has occurred.
The function requested is not supported"
I have other VM which are logging in fine as before. Please help.
Check out the following link.
This is due to a combination of three factors:
You activated NLA on your target computer
The target computer is not patched for CVE-2018-0886
You enforced the Force updated clients or Mitigated parameters on the source computer
https://itluke.online/2018/03/29/solved-authentication-error-function-not-supported/
I am trying to setup a custom Linux VM in MS Azure.
I found a guide, pointing out that there are Azure-ready Ubuntu Images to be found here:
http://cloud-images.ubuntu.com/
What I did so far:
Downloaded the Trusty Tahr .vhd.zip file from their website.
Unpacked it and uploaded it to a BLOB Storage using Azure Managament Studio
Created a new Virtual Disk using the stored .vhd file
Created a VM that used the new Disk.
It seems to boot just fine, but when I try to SSH onto its public ip adress it gives me: "Server Unexptectedly closed connection".
If I create a Linux VM from the existing MS-Azure Templates everything works fine, so it doesn't seem to be a network problem on my end.
Anyone done this before?
Are there steps that must be done PRIOR to uploading the image to azure?
I've never done this before so a verified step-by-step guide would be highly appriciated.
Thanks in advance!
Regards,
Flo
UPDATE:
I updated my resource group with a security group, in which i defined an ssh-in rule. I then linked my VM's Nic to that Group.
Heres the inbound rule:
ssh-in rule
I am still getting a timeout when I try to connect via putty over ssh.
yes, there are some steps you should take - Linux-specific
and Ubuntu-specific .
Unexpected closed connection can be somehow services-related. You can take some steps from the Linux access troubleshooting guide.
You can take look at what is going on with the Linux boot using Boot Diagnostics and Console. That is the way i would recommend to do first, then try to upload manually.
Then, check if SSH is enabled - go to your VM => Settings => Network interfaces => click on the Network Security Group name => Inbound security rules. Create your 22 SSH rule.
For anyone coming to this ticket in 2018 please not: you also need to connect the security group to the containing subnet in the security group. It's not enough to do it to the NIC.
Also, do NOT go through this complicated process. There are plenty of Ubuntu images you can use and quickly deploy in the marketplace right from the portal.
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.