VMM 2008 R2: Can´t manage cluster with Error ID: 10403

Hello!

Our VMM Server 2008 R2 manages 6 lusters Hyper-V 2008 R2.

One had a problem, so I decided to remove and add it again.

Trying to add, it returnos the following error:

  • my.cluster.fqdn is not listed in Active Directory Domain Services.
  • Verify that the computer name and the domain name are correct, and then try the operation again.
  • ID: 10403

When I try to add using the "Skip Active Directory Name Verification", the job sarts and then:

  • Error (415)
    Agent installation failed copying E:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\agents\I386\2.0.4521.0\msiInstaller.exe to \\my.cluster.fqdn\ADMIN$\msiInstaller.exe.
     (The network name cannot be found)
  • Recommended Action
    1. Ensure my.cluster.fqdn is online and not blocked by a firewall.
    2. Ensure that file and printer sharing is enabled on my.cluster.fqdn and it not blocked by a firewall.
    3. Ensure that there is sufficient free space on the system volume.
    4. Verify that the ADMIN$ share on my.cluster.fqdn exists. If the ADMIN$ share does not exist, reboot my.cluster.fqdn and then try the operation again.

I cant access access the path \\my.cluster.fqdn\ADMIN$ using Windows Explorer, but if I try each node name \admin$, it access ok.

Any idea how to solve this?





August 26th, 2015 8:56pm

Hi Sir,

>>

  • my.cluster.fqdn is not listed in Active Directory Domain Services.
  • Verify that the computer name and the domain name are correct, and then try the operation again.

>>Agent installation failed copying E:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\agents\I386\2.0.4521.0\msiInstaller.exe to \\my.cluster.fqdn\ADMIN$\msiInstaller.exe.
 (The network name cannot be found)

According to the error message, it seems that it might be caused by computer account missing or the wrong DNS resolution  , I would suggest you to check the cluster's virtual computer name and cluster nodes' names in AD .

In addition you can use powershell to list all the computers in AD , the following article mentioned how to list them for 2008 DC :

http://blogs.technet.com/b/askds/archive/2010/02/04/inventorying-computers-with-ad-powershell.aspx

Also please check if the cluster and cluster nodes DNS resolution is correct .

Best Regards,

Elton Ji

Free Windows Admin Tool Kit Click here and download it now
August 27th, 2015 6:10am

Thanks for answering!

This is a 2 nodes cluster... The name resolution for the nodes and CNO is OK!

All of them are listed in AD, when using ADUC (dsa.msc).

Tried using powershell get-adcomputer filtering the CNO and the nodes names, all of them are there, enabled.

All of them have: "PasswordExpired : False"

Any othr idea?

August 27th, 2015 8:01am

I found that thread bellow.

Id like to reset the nodes accounts, but how I never needed to do this before, I dont know what are the impacts, in case of the problem is not that problem. 

https://social.technet.microsoft.com/Forums/en-US/2771adb7-3f80-4843-aba1-9c61cc8beb9c/erro-ao-adicionar-host-cluster-no-scvmm?forum=hypervpt

What happens if i reset healthy computer accounts?

Free Windows Admin Tool Kit Click here and download it now
August 27th, 2015 4:01pm

Hi Sir,

Have you tried to disable all firewall and access that path (\\my.cluster.fqdn\ADMIN$\) from DC ?

Did you check if the cluster works correctly , is there any error log in cluster ?

Also please try to list the spn for that cluster and nodes  .

In my case  the output is :

Any information please feel free to let us know .

Best Regards,

El

August 28th, 2015 2:24am

Hi Elton!

Thanks for helping.

Firewall are all disabled on all related servers. 

But I didnt try to access the shares from the DCs before. I tried just now, and the name resolves OK but it doesnt work for the cluster name. 

Cluster is OK, I can do live migrations OK, Cluster validation only shows warning for pending updates, but both servers show no updates when running windows update.

PS C:\> setspn -L myclustername

Registered ServicePrincipalNames for CN=myclustername,OU=HOST,OU=SERVERS,OU=VCA,OU=COMPANYNAME,DC=COMPANYDOMAIN,DC=com,DC=
br:
        MSServerCluster/myclustername.redebahia.com.br
        MSServerCluster/myclustername
        MSServerClusterMgmtAPI/myclustername.fqdn
        MSServerClusterMgmtAPI/myclustername
        MSClusterVirtualServer/myclustername.fqdn
        MSClusterVirtualServer/myclustername
        HOST/myclustername.fqdn
        HOST/myclustername

PS C:\>

Any other idea?


Free Windows Admin Tool Kit Click here and download it now
August 28th, 2015 11:41am

I was just checking:

https://social.technet.microsoft.com/forums/systemcenter/en-US/8c712d02-3651-4bf4-b06c-4a9a41a0006b/adding-hyperv-cluster-to-vmm-fails-with-code-13805

That was solved after update DNS record. So Id follow this procedure:

https://support.microsoft.com/en-us/kb/969049

But when checking DNS service, I found a situation that may me related.

On DNS Servers of the Site that the cluster has the problem, its missing the reverse zone.

All of other 14 DNS servers (domain controllers) have this reverse zone, that is the reverse zone for the LAN IP addresses.

I solved this problem of DNS replication, but the problem persists. 


August 31st, 2015 7:25pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics