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.
Related
I remember reading that the DNN platform edition struggles with the MS Azure web app environment in regards to the scheduler tasks.
this quote comes for this DNN connect blog
The DNN Platform / Community scheduler does not support Azure Web
Sites as the server names running the web site are ever changing as
Azure scales up and down, or upgrades underlying machines. There is a
solution for Evoq.
I am getting the following scheduler errors in my DNN instances on Azure:
THREAD ID:59
TYPE:DotNetNuke.Services.Search.SearchEngineScheduler,DOTNETNUKE
EXCEPTION:Lock obtain timed out:
NativeFSLock#D:\home\site\wwwroot\App_Data\Search\write.lock
It is happening A LOT. THis is on a 08.00.04 version
I am also getting the following error on a 08.00.01 version
TYPE:DotNetNuke.Services.Scheduling.PurgeScheduleHistory, DOTNETNUKE
EXCEPTION:Execution Timeout Expired. The timeout period elapsed prior
to completion of the operation or the server is not responding.
My question is whether dnn platform's scheduler works properly in the azure web app environment, and what version saw this delivered. This will help me in getting these errors resolved.
Thanks
We often host Test and QA Evoq environments in Azure and the machine names do change, therefore require us to reactivate licensing. But these are on the Free or Shared pricing tiers. I believe if you move to Basic and above, the environment should be dedicated. You can also confirm with DNN Corp on this because their own OnDemand hosting uses Azure.
The Search write-lock error I have seen on other environments so I don't believe it's an Azure problem necessarily. For this issue, restart the app pool and delete all files in the App_Data\Search folder. Then start the site, go to Settings > Site Settings > Search and click the Re-index Content button. Then start the Site Crawler job from the scheduler. Ensure in Site Settings > Servers > Server Settings > Web Servers, that only the current server name is there -- delete any old server names. In Settings > Scheduler, edit the Search: Site Crawler task. In the Servers textbox, you can enter the name of the server so that it ensures it only runs on that server to ensure no overlap in processing (thinking it's in webfarm mode).
I have a deployment slot on Azure. During debug of my debug slot it suddenly stopped working. I therefore stopped and started it again. Now I am not able to access it on the azure portal:
If I tried to navigate to the service from VS I get:
Starting and stopping is not working. And I cannot find anybody with this issue. I can't even delete it to recreate it, since the deployment slots has completely disappeared :/
Anybody have an idea of how to tackle this, e.g. through azure command prompt or powershell?
Error Message in Azure
When I try to publish I get the following:
Web deployment task failed. (Could not connect to the remote computer ("AppServie-development.scm.azurewebsites.net") using the specified process ("Web Management Service") because the server did not respond. Make sure that the process ("Web Management Service") is started on the remote computer. Learn more at: http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_COULD_NOT_CONNECT_TO_REMOTESVC.) AppService C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\Web\Microsoft.Web.Publishing.targets 4283
happened to all our services including DB connections just a short moment ago. Now waiting for resolution from their side....
https://azure.microsoft.com/en-us/status/
it only mentioned global DNS issue, but I guess that means all services?... anyway, I'm sitting duck here waiting my boss to shout at me
14:03
All our services are back online
we are not paying the support subscription so unofficially we are their second class customers...?
but anyway problem solved, a typical 1 hour experience as we have with Microsoft in most technical issues.... (personal opinion - not bad overall when running in a cloud)
All our services went down as well due to connection issues with DBs
I am also following on Twitter on "#azure". Seems to be a problem that hits a lot of people right now. Also many of the bigger websites in North Europe seems to be super slow / down.
Seems to be only in North/West Europe.
News from : https://azure.microsoft.com/en-us/status/
DNS - Multi-Region
Last updated 5 minutes ago
Starting at 11:48 UTC 15 Sep, 2016 a subset of customers using DNS in multiple regions may experience difficulties connecting to their resources hosted in this region. This issue is also having knock-on impact on impact on multiple Azure services, including SQL Database, Virtual Machines, Visual Studio Team Services, and App Service \ Web Apps. Engineers are aware of this issue and are actively investigating. The next update will be provided in 60 minutes, or as events warrant.
This morning our Azure VM running Server 2008 and SQL Server 2008 went offline, and took about 1 hour to restart. The event log shows only:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
and the Azure dashboard says there were no availability incidents during this time (US - West)
Is it safe to believe the Azure dashboard, which implies that Windows crashed? We don't have Azure support (yet).
When this is a production environment I highly recommend you to configure Availability Sets. This document can guide you: http://azure.microsoft.com/en-us/documentation/articles/virtual-machines-manage-availability/
Back to your question on trusting the Azure Service Dashboard:
You have one Virtual Machine running on a host in the Azure data center. Now assume this one host would fail, I doubt this will trigger a performance degradation or service interruption alert.
Maybe someone with more background about how the Service Dashboard works can confirm!
However, I do find it strange that it took 1 hour to restart. Could this be SQL Server recovering the database(s)? This should be visible in the Event log.
If I have a Windows Azure Service consisting of only Worker Roles, do the worker roles start automatically or I need to start it manually?
I have some debugging print statements like Trace.WriteLine(...) in the Run and OnStart methods, but it seems those statements are not logged. What could be the causes?
When the service is deployed the role instances will start up automatically. Cory Fowler wrote up a great post explaining the Startup Lifecycle of a Windows Azure Role. The article is a little older as it still mentions the VM Role which as been deprecated in favor of the new Windows Azure Virtual Machine features. The information about the actual start up stuff is all still golden as far as I know.
As for why you are not seeing your trace writelines, where are you looking for them at? You may not have all the configuration setting correct to gather then up. Check out the Hands on Lab for Debugging Cloud Services for step by step and compare to your solution.
As you can tell from the title, I set up a virtual machine on Azure and installed a website and database that my company is hosting for a client. The spending limit was not lifted, and after it was reached my VM was deleted.
Since that time I have lifted the spending limit, but I have no idea how to get the VM back, or if that is possible at all. What are the steps I need to take in order to get back to where it was? Is the database that was on this server gone for good? I spent hours getting this server up to date with updates and Web Platform Installer software. This would be rather cruel if everything is now lost.
Are you sure the VM was actually deleted, or was the deployment deleted? Check in the portal under the Virtual Machines tab. Look under the Disks section and see if you have a disk there that represents the server that was running.
If so, you should be able to create a new Virtual Machine instance by using the New button at the bottom of the portal. Click on the New button and select Compute > Virtual Machine > From Gallery. Then click on the My Disks under the popup screen. This will let you select the disk that represents the OS disk from your server.
You may also want to check to see if the Cloud Service container that was running the server was also deleted. When you create a Virtual Machine a Cloud service is created to act like a container for that machine instance. You can also add additional machines to that same container. Take a look under Cloud Services in the portal and see if one is there named like what you had setup for the virtual machine. If so, then you'll either have to delete this one so you can reuse the name, or you can user the PowerShell cmdlets to start the virtual machine and put it into the already existing cloud services container.
I had the same experience. Our Azure Virtual machine was gone, and I got really scared when it was also missing from the management portal. I solved it like this.
Remove the spending limit on the credit card from the Azure account portal.
Delete the cloudservice that had the same name as the VM. The cloud service was only an empty container now that the VM was gone.
It is easy to restore the missing VM by creating a new Virtual Machine. Choose to create a new VM from Gallery, and under the Gallery you can find your missing machines harddisk under "My disks".
Wait while the machine is restored, and then start it.
Now you have to manually recreate all network endpoints. That was a pain as I had quite a few different streaming servers installed.
I wish that Azure only stopped an virtual machine instead of silently removing it when the customer fails to pay. Especially because it is quite hard to understand which services are free, which services are free trials and which services that you must pay for.