When attempting to connect to the SQL instance in SQL Server Management Studio, the connection fails when using the Virtual Name( VirtualName\ InstanceName). The error states, 'A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible'. The complete error is shown in Figure 1 below:

Figure 1


Note: When connecting using the physical server name, the connection is successful.

Cause:
This issue occurs when the SQL Server Browser service is not started on the system. This service is not managed by the cluster, so it needs to be set to Automatic and in a 'Running' state. This issue is mostly seen when the SQL Server Browser service is incorrectly set to Manual when configuring SQL Server in the cluster.

Solution:
Ensure that the SQL Browser service is set to 'Automatic' and in a 'Started' state by performing the following steps:

1. Open the Services applet (Start >run > services.msc or Computer Management > Services and Applications >Services).

2. Locate the 'SQL Server Browser' service in the list.

3. Right-click on the 'SQL Server Browser' service and choose the'Properties' option.

4. On the 'General' tab, set the 'Startup type' to Automatic, and select the 'Start' option to start the service.

5. Select'OK', and confirm the service shows started with a startup type of Automatic (as shown in Figure 2).

Figure 2


6. Once complete,relaunch SQL Management Studio and attempt to connect using the Virtual Name of the SQL instance. This should now be successful.