Azure site recovery associate replication policy error

%3CLINGO-SUB%20id%3D%22lingo-sub-354005%22%20slang%3D%22en-US%22%3EAzure%20site%20recovery%20associate%20replication%20policy%20error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-354005%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%20class%3D%22yj-message-list-item--body-message%20yj-message%22%3EWe%20were%20replicating%20VMs%20from%20single%20Hyper-V%20host%20(without%20VMM)%20without%20problems.%20Then%20we%20disconnected%20host%20from%20ASR%2C%20cleaned%20up%20resources%20and%20decided%20to%20associate%20with%20other%20recovery%20vault%2C%20other%20region%20(other%20subscription%20as%20well).%20%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22yj-message-list-item--body-message%20yj-message%22%3EAfter%20uninstalling%20agent%2C%20cleaning%20registry%20and%20installing%20agent%20again%2C%20registering%20with%20ASR%20(successfully)%20we're%20getting%20stuck%20at%20associating%20replication%20policy.%20Any%20ideas%20how%20to%20fix%20it%3F%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-354005%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20Site%20Recovery%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-354007%22%20slang%3D%22en-US%22%3ERe%3A%20Azure%20site%20recovery%20associate%20replication%20policy%20error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-354007%22%20slang%3D%22en-US%22%3EError%20(attached%20as%20file%20as%20well)%3A%3CBR%20%2F%3E%3CBR%20%2F%3EError%20ID%3CBR%20%2F%3E10003%3CBR%20%2F%3EError%20Message%3CBR%20%2F%3EProtection%20couldn't%20be%20configured%20for%20cloud%2Fsite%20Site1.%3CBR%20%2F%3EProvider%20error%3CBR%20%2F%3EProvider%20error%20code%3A%2031389%3CBR%20%2F%3EProvider%20error%20message%3A%3CBR%20%2F%3EJob%20'Getting%20Virtual%20Disk%20Information'%20(11A56E5F-4C81-4333-B348-40A6DFEA8A89)%20failed.%20Job%20State%2010.%20Error%20Code%3A%2032779.%20ErrorSummaryDescription%3A%20.%20ErrorDescription%3A%20.%3CBR%20%2F%3EProvider%20error%20possible%20causes%3A%3CBR%20%2F%3ECheck%20the%20error%20details.%3CBR%20%2F%3EProvider%20error%20recommended%20action%3A%3CBR%20%2F%3EResolve%20the%20issue%20and%20try%20again.%3CBR%20%2F%3EPossible%20causes%3CBR%20%2F%3EOne%20or%20more%20hosts%20couldn't%20be%20prepared.%20Check%20the%20Provider%20error%20for%20more%20information.%3CBR%20%2F%3ERecommendation%3CBR%20%2F%3EResolve%20the%20issue%20and%20retry%20the%20operation.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1356721%22%20slang%3D%22en-US%22%3ERe%3A%20Azure%20site%20recovery%20associate%20replication%20policy%20error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1356721%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F17445%22%20target%3D%22_blank%22%3E%40Rimvydas%20Velykis%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWere%20you%20able%20to%20resolve%20the%20issue%3F%3C%2FP%3E%3CP%3EWe%20are%20facing%20similar%20error%20messages%20and%20unable%20to%20find%20what%20could%20be%20wrong.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Contributor

We were replicating VMs from single Hyper-V host (without VMM) without problems. Then we disconnected host from ASR, cleaned up resources and decided to associate with other recovery vault, other region (other subscription as well).

After uninstalling agent, cleaning registry and installing agent again, registering with ASR (successfully) we're getting stuck at associating replication policy. Any ideas how to fix it?

 

2 Replies
Error (attached as file as well):

Error ID
10003
Error Message
Protection couldn't be configured for cloud/site Site1.
Provider error
Provider error code: 31389
Provider error message:
Job 'Getting Virtual Disk Information' (11A56E5F-4C81-4333-B348-40A6DFEA8A89) failed. Job State 10. Error Code: 32779. ErrorSummaryDescription: . ErrorDescription: .
Provider error possible causes:
Check the error details.
Provider error recommended action:
Resolve the issue and try again.
Possible causes
One or more hosts couldn't be prepared. Check the Provider error for more information.
Recommendation
Resolve the issue and retry the operation.

Hi @Rimvydas Velykis 

 

Were you able to resolve the issue?

We are facing similar error messages and unable to find what could be wrong.