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

vCenter Server 7.0 Update 2b MCS Storage Issue


Julian Jakob

Question

Hello,

 

I'm facing the following issue at two customers (1912 LTSR CU2) after applying the following Patch to the VMware Infrastructure:

 

vCenter Server 7.0 Update 2b | 25 MAY 2021 | ISO Build 17958471

MCS stopped working, not able to rollout a new snapshot with the error "StorageNotFound" "Storage "datastore-4037" not found.
Testing HostingConnection is OK, Testing Ressource is nOK, failes with the info, storage is not available.

In both sites, there was no changes to LUN / Storage renaming or sth else. I'm wondering if there are any known issues, as of https://support.citrix.com/article/CTX131239 "vSphere 7.0 (Up to update 2)" should include 2b?

 

Thanks and best Regards

Julian

Link to comment

2 answers to this question

Recommended Posts

  • 0
On 6/16/2021 at 12:32 PM, Julian Jakob said:

Hello,

 

I'm facing the following issue at two customers (1912 LTSR CU2) after applying the following Patch to the VMware Infrastructure:

 

vCenter Server 7.0 Update 2b | 25 MAY 2021 | ISO Build 17958471

MCS stopped working, not able to rollout a new snapshot with the error "StorageNotFound" "Storage "datastore-4037" not found.
Testing HostingConnection is OK, Testing Ressource is nOK, failes with the info, storage is not available.

In both sites, there was no changes to LUN / Storage renaming or sth else. I'm wondering if there are any known issues, as of https://support.citrix.com/article/CTX131239 "vSphere 7.0 (Up to update 2)" should include 2b?

 

Thanks and best Regards

Julian

 

Hi,

 

we are experiencing exactly the same issue with 1912 LTSR CU3 and vCenter Build 17958471.

Hosting connection ressource test error:
"The storage with ID /<datacenter>/<cluster>/<storage> could not be read from the data store. Ensure the storage exists on the data store and has the appropriate permissions."

 

As this is our production environment, a quick solution would be great.

 

Thank you!

 

Kind Regards,

 

Arne

 

 

Link to comment
  • 0

Hello,

 

the reason was a corrupt vCenter configuration file of the reverse proxy.

The file /etc/vmware-rhttpproxy/endpoints.conf.d/vpxd.conf should have the following lines:

/    namedpipe    /var/run/vmware/vpxd-webserver-pipe    redirect    allow

/Query    found    8080    allow    reject

/pcnotification    local    9232    reject    allow

/vsan/sdkTunnel    namedpipetunnel    /var/run/vmware/vsan-sdkTunnel-pipe    allow    reject

/vsanHealth    namedpipe    /var/run/vmware/vsan-sdk-pipe    redirect    allow

/vws    found    8080    allow    allow

 

After adding the lines and restarting the service, our MCS was back.

 

Thanks to the Citrix & VMware support.

 

Kind Regards,

 

Arne

 

Link to comment

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...