"Error during the validation of the provider URL" error while registering a VASA provider with vCenter Server.

Products

• VMware vCenter Server

Issue/Introduction

VASA Providers can take many forms.

• Dell is reportedly developing a vCenter plugin to report capabilities.
• EMC and NetApp will use a software application that runs on a virtual or physical server.

In all cases, the software uses a proprietary call to the storage array, in effect relaying and translating the VMware request.

Symptoms:

• Cannot register a VASA provider with vCenter Server.
• Registering a VASA provider with vCenter Server fails.
• You see the error:

             Error during the validation of the provider URL ex:https://<host>:9080/version.xml  

• Windows vCenter log location In the C:\ProgramData\VMware\Infrastructure\Profile-Driven Storage\Logs\sps.log file, you see entries similar to:

• VCSA appliance log location /var/log/vmware/vmware-sps\sps.log file, you see entries similar to:

ERROR opId=sps-Main-777194-480 com.vmware.vim.sms.provider.ProviderFactory - Error during the validation of the provider URL java.net.SocketTimeoutException: connect timed out
        at java.net.PlainSocketImpl.socketConnect(Native Method)
        at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
        at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
        at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
        at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
        at java.net.Socket.connect(Socket.java:589)
        at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:668)
        at sun.net.NetworkClient.doConnect(NetworkClient.java:175)
        at sun.net.www.http.HttpClient.openServer(HttpClient.java:463)
        at sun.net.www.http.HttpClient.openServer(HttpClient.java:558)
        at sun.net.www.protocol.https.HttpsClient.<init>(HttpsClient.java:264)
        at sun.net.www.protocol.https.HttpsClient.New(HttpsClient.java:367)

         

Environment

VMware vSphere ESXi 7.x

VMware vSphere ESXi 8.x

Cause

This issue occurs due to 9080 port blocking used by the Storage Monitoring Server and the vCenter Management Webservices component.

To check port connectivity in vCenter server use Using Curl to test port connectivity in VMware vCenter Server Appliance

 

Resolution

To address the underline problem use below steps

1. The VASA provider registration with vCenter server fails due to VMware Profile-Driven Storage Service. This is expected behavior when Profile-Driven Storage Service is stopped in the vCenter server. 
   
   Checked the service status from vCenter command line and start the service.
   
   # service-control --status vmware-sps 

   If the service is in stopped state, then start the service 
   
   # service-control --start vmware-sps


2. It might also occur due to the improper cleanup of legacy registered instances of VASA Provider. You must clean up legacy VASA Provider instances, register VSC with the vCenter Server instance again, and then enable VASA Provider.
   
   
3. If there are any left over folder in vCenter server, you need to delete the plug-in folder in vCenter server and then restart and register VSC and VASA provider.
   
   
4. Connect to the VASA provider via port 9080 and determine if the VASA XML information is returned, if fails then check the firewall 

VCSA Appliance: Use the CURL utility to check the VASA provider URL 

# curl --insecure https://<host>:9080/version.xml

Windows vCenter:  Use a web browser to check the VASA Provider by navigating to https://<host>:9080/version.xml

Note: If this type of XML response is not received even though the VASA provider is running, it indicates that something may be interfering with communication between vCenter Server and the VASA like port number or firewall blocking.