Error when setting up ASR for the first time

I'm setting up my first Azure ASR configuration and I'm getting the following error when I try to apply the policy that I cannot sort out.  Looking for some direction in solving this.

ERROR MESSAGEProtection couldn't be configured for cloud/site EGMHypVsite.
PROVIDER ERRORProvider error code: 31389

Provider error message:
      Job 'Getting Virtual Disk Information' (EBC8738D-3E57-411E-B500-06A6C779B532) 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 CAUSESOne or more hosts couldn't be prepared. Check the Provider error for more information.
RECOMMENDATIONResolve the issue and retry the operation.
jterharkIT ConsultantAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Binu B KCloud/Azure Infrastructure ConsultantCommented:
Can you give us a little bit more details? What type of Azure site Recovery are you confiuring? is it azure to azure or Hyper-v to azure or vmware to azure

I would follow the doc
If you are doing that how far are you reached and where are you failing?


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
jterharkIT ConsultantAuthor Commented:
I determined that the problem was left over files from a vm that had been deleted from the cluster manager.  Once the files were deleted, the problem went away.
Binu B KCloud/Azure Infrastructure ConsultantCommented:
This is resolved by the submitter
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.