Simcfc73 Posted October 18, 2016 Posted October 18, 2016 Hi, been at this for a good hour now. Trying to migrate a host to a new 2016 box and getting 'an error occured while attmepting to contact the VMM service on desitination "". Verify if the service is running and you are authorised. and in the event log DCOM was unable to communicate with the computer FUL-SIDESHOWBOB.*** using any of the configured protocols; requested by PID 16d8 (C:\Windows\system32\mmc.exe). I've disabled the firewall, disable and re-enabled the live migration table, added the account to the hyper-v local group but its still failing. I can do it between 2012 R2 fine
Simcfc73 Posted October 18, 2016 Author Posted October 18, 2016 LOL. This is even more bonkers. I can sit at my PC and ping the new server... it works. I can log into the hyper-v server and ping the new server... it works I cant connect to the file system on the new server using UNC via its name or the IP
IanT Posted October 19, 2016 Posted October 19, 2016 any help below? Diagnosing Live Migration Failures (Part 1)
Simcfc73 Posted October 19, 2016 Author Posted October 19, 2016 Yeah I've worked through that. Changed it to Kerberos but still no joy. I ended up renaming the new server and putting hyper-v back on as I thought there was some naming issues but its still not working.
IanT Posted October 19, 2016 Posted October 19, 2016 Are you using Hyper-V Clustering or Shared-Nothing Storage here?
Jaan Posted January 16, 2017 Posted January 16, 2017 Did you manage to get this working? I'm seeing afew live migration issues on server 2016 pop up online. I've also got this issue after updating. Just trying something else now, hope it works.
Simcfc73 Posted January 16, 2017 Author Posted January 16, 2017 If I recall it was down to the authentication between the servers. CredSSP issue. I went back to 2012 R2 but did a different server on 2016 and it was this.
Jaan Posted January 16, 2017 Posted January 16, 2017 If I recall it was down to the authentication between the servers. CredSSP issue. I went back to 2012 R2 but did a different server on 2016 and it was this. Is this in Ad under "Delegation"? I thought it might have been a Kerberos issues as i had somethings missing. However i'm still having the issue. trying "Use any auth protocol" also doesn't work. thanks for the reply.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now