Azure Migration: Server Migration error during Enable Migration: Service returned an error. (Error Code '8079ffff')

R Artes 26

During replication, the service returns error:

Provider error code: 31343
The operation failed with the error: Enable replication failed for virtual machine '

R Artes 26 Reputation points

2021-11-26T11:05:21.377+00:00

Some more information...

I already tried another suggestion: "Renew Certificates" for the Hyper-V host. This had no effect.

VM is a Generation 2 VM, with no checkpoints.

Hyper-V is Windows Server 2016 Datacenter with .NET Framework 4.6.2 installed

The VM is switched off; does this make any difference to replication? I can't find anywhere if it says the VM has to be switched on.

Secure boot off.
R Artes 26 Reputation points

2021-11-26T14:40:00.053+00:00

OK, now the VM is switched on, I get a different error:

Error ID
70094

Error Message
Protection couldn't be enabled for the virtual machine.

Provider error
Provider error code: 31389

Provider error message:
Job 'Enabling Replication' (xxxxxx) failed. Job State Exception. Error Code: 32768. ErrorSummaryDescription: Hyper-V failed to enable replication.. ErrorDescription: .

Provider error possible causes:
Check the error details.

Provider error recommended action:
Resolve the issue and try again.
Possible causes
Protection can't be enabled with the virtual machine in its current state. Check the Provider errors for more information.

On the Hyper-V server it still says the same error message in EventViewer:
Enable replication failed for virtual machine '<NAME>'. Service returned an error. (Error Code '8079ffff').
R Artes 26 Reputation points

2021-11-26T15:08:50.107+00:00

Updated the Configuration Version, did all the pending Windows Updates... reboot again...

Error Message
Protection couldn't be enabled for the virtual machine.

Provider error
Provider error code: 31343

Provider error message:
The operation failed with the error: Enable replication failed for virtual machine '<NAME>' due to a network communication failure.
R Artes 26 Reputation points

2021-11-29T10:49:56.013+00:00

We do have a proxy server but I can't see anything blocked on that end, coming from Hyper-V server.
R Artes 26 Reputation points

2021-12-03T13:22:32.137+00:00

Some more information....

Microsoft support say I need to use version 5.1.7029.0 of the Azure Site Recovery Provider, not 5.1.7030 like installed.

But when I download version 5.1.7029 from Microsoft and install it, i see version 5.1.7030 in the program files! Even when I delete the registry key, or install on a different server without the Azure Site Recovery Provider already installed, Seems like a bug in the agent to me.

https://download.microsoft.com/download/a/3/3/a339c231-5c62-4c44-aa7c-f449c3168f07/AzureSiteRecoveryProvider.exe

It says version 5.1.7029.0, in the Properties/Details, but when you install it, it says 5.1.7030 in the Program Files!!!! Crazy.
SadiqhAhmed-MSFT 37,766 Reputation points Microsoft Employee

2021-12-03T14:09:32.02+00:00

Were you able to resolve the issue with installation of version 5.1.7029.0,?
If you've already reached out to Azure technical support team by raising support ticket, I suggest you report the issue version change to the support engineer. If that is a bug it will rectified and product team will provide a fix.
R Artes 26 Reputation points

2021-12-03T14:19:48.203+00:00

Hi Sadiqh, no the issue is not resolved, every tine I install version 5.1.7029.0 it shows as version 5.1.7030, which MS Support say is not a supported version. Doesn't matter where i install it, always shows the wrong version number.

The support engineer is currently discussing internally.

TrackingID#2111290050000968

Regards
Richard.
R Artes 26 Reputation points

2021-12-21T10:29:57.487+00:00

Almost 1 month later, and Microsoft support still do not have a clue what Error Code '8079ffff' means.
I have been escalated to a clustering expert, they think it has to do with our cluster setup.
I have a feeling it is to do with using ExpressRoute from our LAN to Azure, but that's just a guess.
If there is any resolution I will post an update.
Richard.
R Artes 26 Reputation points

2022-01-20T10:48:33.687+00:00

Microsoft closed the case because I was on holiday for 2 weeks. Now they don't answer when I ask them to re-open the case.
Case still not solved; all suggestions from the support team do not work.
I have to make a new case for Microsoft.

:-<

Azure support sucks.
R Artes 26 Reputation points

2022-01-24T14:10:31.137+00:00

At last I got this working. The clue was in the MARS agent log file on the Hyper-V host: CBEngineCurr.errlog

https://pod01-prot2.we.backup.windowsazure.com/ProtectionService.svc that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. ---> System.Net.WebException: The remote server returned an error: (407) Proxy Authentication Required.

I had to create an exception in the proxy server that bypassed authentication for backup.windowsazure.com.

Also, even though the MARS agent asks you if you have a proxy server, DO NOT USE IT!
When you install the MARS agent, choose the option "Connect directly to Azure Site Recovery without a proxy server".
If you choose "Connect using a proxy server" then the agent tries to connect via HTTPS which is not supported by Azure.

4 answers

Limitless Technology 39,356 Reputation points

2021-11-26T18:59:46.477+00:00

Hello anonymous user

Please try the next steps to resolve the issue:

1.Stop replication in Azure Portal of affected Virtual Machine
2. This will disable and remove replication menu from affected Virtual Machine in Hyper-V
3. Remove all checkpoints from the Virtual Machine as shown above in Hyper-V
4. Enable replication again in Azure Migrate of affected Virtual Machine, this should enable replication correctly without errors and replication will start shortly after

Hope this helps with your query,

--If the reply is helpful, please Upvote and Accept as answer-
Please sign in to rate this answer.

1 person found this answer helpful.
R Artes 26 Reputation points

2021-11-29T10:16:20.557+00:00

Thanks @Limitless Technology .

Done (difficult without a valid support ticket!)

Ok, I don't see any difference but OK.

There are no checkpoints on this VM

OK, done

Same problem:

Error ID
70094
Error Message
Protection couldn't be enabled for the virtual machine.
Provider error
Provider error code: 31343

Provider error message:
The operation failed with the error: Enable replication failed for virtual machine '<NAME>'. Service returned an error. (Error Code '8079ffff').

Provider error possible causes:
Failure while replicating the virtual machine to Azure.

Provider error recommended action:
Check Microsoft Azure Recovery services event viewer logs on the Hyper-V host and resolve any errors.
Possible causes
Protection can't be enabled with the virtual machine in its current state. Check the Provider errors for more information.

Same error in the Event Log in the Hyper-V host:

Enable replication failed for virtual machine '<NAME>'. Service returned an error. (Error Code '8079ffff').
Sign in to comment
R Artes 26 Reputation points

2022-01-24T14:09:18.423+00:00

At last I got this working. The clue was in the MARS agent log file on the Hyper-V host: CBEngineCurr.errlog

https://pod01-prot2.we.backup.windowsazure.com/ProtectionService.svc that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. ---> System.Net.WebException: The remote server returned an error: (407) Proxy Authentication Required.

I had to create an exception in the proxy server that bypassed authentication for backup.windowsazure.com.

Also, even though the MARS agent asks you if you have a proxy server, DO NOT USE IT!
When you install the MARS agent, choose the option "Connect directly to Azure Site Recovery without a proxy server".
If you choose "Connect using a proxy server" then the agent tries to connect via HTTPS which is not supported by Azure.
Please sign in to rate this answer.

1 person found this answer helpful.
SadiqhAhmed-MSFT 37,766 Reputation points Microsoft Employee

2022-01-24T19:53:06.187+00:00

anonymous user Thanks for the update. Glad to hear that you were able to find solution to this issue.

Thanks once again for sharing the solution with Microsoft Q&A Community forum.

R Artes 26 Reputation points

2022-01-25T09:45:03.42+00:00

Thanks Sadiqh!

SadiqhAhmed-MSFT 37,766 Reputation points Microsoft Employee

2022-01-25T10:08:11.553+00:00

You're most welcome! :)
Sign in to comment
Alaa Kalakech 10 Reputation points

2023-12-12T21:08:07.5+00:00
follow the steps below :

disable and remove replication of selected VM/s

remove site recovery agent and Mars agent from Host server

restart host server

Reinstall new azure site recovery provider setup + register + renew certificate

restart replication.
Please sign in to rate this answer.

1 person found this answer helpful.

0 comments No comments
Sign in to comment
Eigenmann René 1 Reputation point

2024-03-22T12:10:39.63+00:00

Thanks works fine for me
Please sign in to rate this answer.

0 comments No comments
Sign in to comment