Operation not allowed because the replication state if not initialized

I wanted to move a VM but got the following error:

Operation not allowed  because the replication state if not initialized. The solution is really simple:

 Billedresultat for Operation not allowed because the replication state if not initialized.



All you have to do, is reset the "Hyper-V Virtual Machine management" service. And everything is good to go.







Popular posts from this blog

[SOLVED] Veeam: Failed change tracking (CBT)

Image
Failed to flush change tracking data, using full scan to determine changes. Failed to create change tracking time stamp for virtual disk file I've encountered the above, after i added some new CSV to a cluster. The backup jobs have been running fine for ages before this. As per say, this is not really a critical issue, since the backups just takes longer. Needless to say, i wanted it to function. I tried: Reboot Nodes, Hosts, VMs Fully update Stop VeeamFCT service and Start it again Update hyper-v integration service Delete previous backups Run full backups Read Veeam forums Running Reset-HvVmChangeTracking Din't work. However!
Read more »»»

Fixing Error 25541. Failed to open XML file

Fixing Error 25541. I had to install Compact 4.0 on a client computer today. However, i got the error below: Error 25541. Failed to open XML file C:\Windows\Microsoft.NET\Framework\v2.0.50727\CONFIG\machine.config, system error: -2147024786 Setup failed. Rolling back  This was a huge pain in the a**, but the solution was very simple.
Read more »»»