Failing to install a new instance of SQL server 2014/2016

Yesterday, I was working with a client of mine on an issue with configuring SQL server reporting services over a Failover Cluster Instance. Due to issues, we had to uninstall the currently existing instance on the passive node and had to install it freshly.

Before the new install attempt, we cleaned the registry entries and uninstalled the various SQL components using the below command :

WMIC PRODUCT Where "Caption like '%SQL%'" GET Caption, IdentifyingNumber 

This command would list the GUIDs and using which we can uninstall the components using the command :

msiexec /X {guidnumber}

Post which I tried for a new installation of the SQL server instance, it went through all the stages, generated the configuration.ini file as well but failed at the final stage of installation with the below pop up error message :

TITLE: Microsoft SQL Server 2016 Setup
------------------------------
The following error has occurred:
Updating permission setting for file 'G:\System Volume Information\WPSettings.dat' failed. The file permission setting were supposed to be set to 'D:P(A;OICI;FA;;;BA)(A;OICI;FA;;;SY)(A;OICI;FA;;;CO)(A;OICI;FA;;;S-1-5-80-3880718306-3832830129-1677859214-2598158968-1052248003)'.
Click 'Retry' to retry the failed action, or click 'Cancel' to cancel this action and continue setup.
For help, click: https://go.microsoft.com/fwlink?LinkID=20476\&ProdName=Microsoft%20SQL%20Server\&EvtSrc=setup.rll\&EvtID=50000\&ProdVer=13.0.5201.2\&EvtType=0x88792597%25400xBB814387
------------------------------
BUTTONS:
&Retry
Cancel
------------------------------

When we found the contents of the G:\ drive , it was used for the tempDB drive and thus cleared the previous contents of the tempDB drive and post which we retried the installation and things went smooth. A new instance was installed.

Post which using the scale out deployment feature /en-us/sql/reporting-services/install-windows/configure-a-native-mode-report-server-scale-out-deployment?view=sql-server-2017  we configured SSRS over the failover cluster instance and we thus resolved the issue.

 

Hope this helps !! Happy installing !!