Easing patching of vRealize products with vRSLCM 2.0

If you are looking  for patching  of vRealize product  through vRSLCM 2.0, Here is link :-

Patching of vRealize products with vRSLCM 2.0

vRealize Operations Manager Sizing

If you are planning to deploy or resize vRealize  Operation Manager , you can see below vmware link - 

Realize Operations Manager Sizing

New Announcement - There will no longer be an option to deploy the external PSC in VMware vSphere Releases.

VMware is deprecating the external Platform Services Controller deployment model. In a future vSphere release (not update release), there will no longer be an option to deploy the external PSC.

Read more in below link :-

VMware Blog  Link


 

Database connection failed While deploying vRA 7.3.x

While deploying vRA from LCM2.0 getting error in 6th step stating "Database connection failed". 


I  seen  below error message inside log file

   Result: Database connection failed. Verify that you are using the full instance name typed correctly, that the database user and password are correct, and that TCP/IP is enabled for the instance. Error details: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

 

The most common reasons for this error can be resolved using the one or more of the steps below. 

Solution 

There could be several reasons you get these error messages. Follow the below steps to see if you can resolve the issue.

Step 1

Make sure you are able to ping the physical server where SQL Server is installed from the client machine. If not, you can try to connect to the SQL Server using an IP Address (for default instance) or IP Address\Instance Name for a named instance. 

Step 2

Make sure the SQL services are running You can check the SQL Server services by using the SC command or SQL Server Configuration Manager. Many times you may find that the SQL Server instance is not running. 

Step 3

Make sure you are using the correct instance name. When you connect to a default instance, machinename is the best representative for the instance name and when you connect to a named instance such as sqlexpress, you should specify machinename\instancename 

Step 4

Check for TCP/IP and Named Pipes protocols and port. Open SQL Server Configuration Manager and check the SQL Server Network Configuration protocols. You should enable Named Pipes and TCP/IP protocol.

For the TCP/IP protocol, right click and select properties to check the TCP/IP communication port as well. The default port is 1433, which can be changed for security purposes if needed. 

 

Note -  I used SQLEXPRESS in my Lab . 

Next time you have issues connecting, check these steps to resolve the issue.

Thank you