Virtual SAN is not available because no Virtual SAN datastores are configured.

[iomasm]

Hello to everyone,

i have an implementation of Vmware Horizon on premises. We have 2 connection servers and a vxrail vcenter. Untill a week ago everything was working perfectly. I had 10 desktop pools that were stored to the vsan.

On the previous Monday i tried to create another desktop pool. When storage should be selected i got the message "Virtual SAN is not available because no Virtual SAN datastores are configured.". I stop and restarted the 2 connection servers but the problem was the same.

I then realized that i couldn't edit the old desktop pools because when i was trying to select and edit them a got the message below.

I didn't change anything on vsan or vxrail or vcenter! I am now reading every log that exists but couldn't find anything! Is there anyone that has any ideas on this!!!

Thanks in advance!

[Mickeybyte]

Check the configuration of the vCenter in the Horizon Admin Console. It seems there's an issue there, that's why you can't edit pools or choose vSAN.

[iomasm]

Thank you for your response, but i didn't changed anything!

Also among the others i tried to remove and add again the vcenter and it worked. I am using a full administrator account for this connection...

[Mickeybyte]

@iomasm 

I didn't say you changed anything, but it's the first place to look since the issue is clearly with the vCenter configuration.

You said you tried to "remove and add again the vCenter and it worked": You _cannot_ remove the vCenter if there are still desktop pools in Horizon that use that vCenter, so that's a bit strange. 

Can you post some screenshots of

• vCenter configuration in Horizon: Settings - Servers - vCenter Servers (also try to edit the vCenter config here and save it again to be sure it's all OK)
• configuration of an existing desktop pool: Inventory - Desktops - click on a desktop pool - Summary

[iomasm]

Sorry, i meant that i changed the user who connects to vcenter. I had a user with specific rights but i changed them with a user with full administrator rights.

The screenshots you have asked are below.

For the win10c desktop pool as you can see i cannot check anything because it gives me the message i have posted before.

[Mickeybyte]

Very strange. 

Can you check if you can access the vCenter from your Horizon connection servers? Either try accessing the vCenter from a supported browser on the servers, or do a test-netconnection in powershell on the servers to check if the connectivity is OK.

If that is all OK, I would suggest to open a SR with VMware to have a deeper look of what is happening. 

[iomasm]

Thank you @Mickeybyte for you answers.

The problems were with the replication on the second connection server. We couldn't find it because we usually connected to the first one via round robin. After deleting the ADAM and re syncing the configuration almost everything was working.

The second thing I did was to add the vcenter certificate to the trusted root certificates of the connection server and it solved all the problems.