Jump to content
Welcome to our new Citrix community!
  • 0

XD 7.6 MCS


Lee Cooper1709153757

Question

Hi,

Recently upgraded VMware to ESI 6.0.0 2809209 and now when trying to update the catalogs I get the following error -

 

Reason : ItemNotFoundException
    Message : Current Node not found. id = 'DistributedVirtualPortgroup:dvportgroup-320', type = 'network'
    Sdk Error Message : An exception occurred.  The associated message was Current Node not found. id = 'DistributedVirtualPortgroup:dvportgroup-320', type = 'network'
    Sdk Error ID : Citrix.XDPowerShell.Status.ExceptionThrown,Citrix.HostingUnitService.Sdk.Commands.GetHypConfigurationObjectForItemCommand
    ErrorCategory : NotSpecified
    DesktopStudio_PowerShellHistory : GetHypervisorDetailsScript
    07/03/2016 09:27:16
    
    Get-HypConfigurationObjectForItem  -AdminAddress "server.local:80" -LiteralPath "XDHyp:\HostingUnits\NetApp\TEMPLATE.vm\"
    Get-HypConfigurationObjectForItem : An exception occurred.  The associated message was Current Node not found. id = 'DistributedVirtualPortgroup:dvportgroup-320', type = 'network'
        + CategoryInfo : InvalidOperation: (:) [Get-HypConfigurationObjectForItem], InvalidOperationException
        + FullyQualifiedErrorId : Citrix.XDPowerShell.Status.ExceptionThrown,Citrix.HostingUnitService.Sdk.Commands.GetHypConfigurationObjectForItemCommand

 

When i run the Hypervisor resource checks from Studio i get following -

 

Check the hypervisor storage.
Run the hypervisor-specific storage tests on storage locations defined in the hosting unit.
Test run on controllers: server.local
Controller server.local: The storage with ID /xxx.datacenter/xxx.cluster/xxx.storage could not be found. Error: Current Node not found. id = 'datastore-12', type = 'storage'.
Ensure that the storage exists, or use different storage.
Controller server.local: Could not find the storage with ID /xxx.datacenter/xxx.cluster/xxx.storage.
Ensure that the storage exists, or use different storage.
Controller server.local: The storage with ID /xxx.datacenter/xxx.cluster/xxx.storage could not be found. Error: Current Node not found. id = 'datastore-12', type = 'storage'.
Ensure that the storage exists, or use different storage.

 

Check the hypervisor networks.
Run the hypervisor-specific network tests on the networks defined in the hosting unit.
Test run on controllers: server.local
Controller server.local: The network with ID /xxx.datacenter/xxx.cluster/xxx.network could not be found. Error: Current Node not found. id = 'DistributedVirtualPortgroup:dvportgroup-320', type = 'network'.
Ensure that the network exists, or use a different network.
Controller server.local: The network with ID /xxx.datacenter/xxx.cluster/xxx.network could not be found. Error: Current Node not found. id = 'DistributedVirtualPortgroup:dvportgroup-320', type = 'network'.
Ensure that the network exists, or use a different network.
 Host 07/03/2016 08:15:43 Failed

Check the hypervisor connection.
Check that a connection to the hypervisor can be established.
Test run on controllers: server.local
 Host 07/03/2016 08:15:43 Successful

Check for connection maintenance mode.
Check that the hypervisor for the connection is not in maintenance mode.
Test run on entire Site
 Host 07/03/2016 08:15:27 Successful

Check hypervisor specific connection details
Check the details of the hypervisor connection and run tests specific to the target hypervisor.
Test run on controllers: server.local
 Host 07/03/2016 08:15:43 Successful

Check the hypervisor infrastructure.
Run the hypervisor-specific infrastructure tests for the hosting unit.
Test run on controllers: server.local
 Host 07/03/2016 08:15:43 Successful

 

The Network and Datastore names have not been changed in VMware.

 

Has anybody else seen anything similar when upgrading VMware?

 

Link to comment

4 answers to this question

Recommended Posts

Are you using a service account to connect to vCenter? If you assign the permissions at the vCenter level instead of the datacenter level, does it work?

Hi, Yes service account and i've just tried that but same error.

 

I believe the upgrade comes with a new self-singed certificate, so maybe that's your problem?

It was only a minor VMware update, the cert looks good and is trusted.

Link to comment

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...