Written by Suhas Savkoor
When trying to install the SQL agent for vSphere Data Protection the agent installation fails with the error:
"VMware VDP for SQL Server Setup Wizard ended prematurely"
Here, under Installation directory:\Program files, there will be a directory called avp that would be created. This folder will have the logs which will contain the details regarding the failure. However, with the failure and roll back of the agent installation, this folder is removed automatically. So, the logs are lost. To gather the logs, we will have to redirect the msi installer logs to a different location.
To perform this run the below command:
To perform this run the below command:
msiexec /i "C:\MyPackage\Example.msi" /L*V "C:\log\example.log"
The /i parameter will launch the MSI package. After the installation is finished, the log is complete.
Once the installation now fails, the above log file will have the logging for the cause of failure.
In my case, the following was noticed:
In my case, the following was noticed:
Property(S): UITEXT_SUPPORT_DROPPED = This release of the VMware VDP client software does not support the operating system version on this computer. Installing the client on this computer is not recommended.
The "EMC Avamar Compatibility and Interoperability Matrix" on EMC Online Support at https://support.EMC.com provides client and operating system compatibility information.
So the failure here is due to unsupported Guest OS. The SQL version was 2014 which was very well supported. This SQL was running on a Windows 2012 R2 box.
From the VDP admin guide (Page 162), we see that SQL 2012 R2 is unsupported Guest OS for the client:
From the VDP admin guide (Page 162), we see that SQL 2012 R2 is unsupported Guest OS for the client:
From the EMC Avamar Compatibility matrix (Page 38) we see this again is not supported.
So, if you see such issues please verify if the Agent being installed is compatible with the Guest OS release.
That's pretty much it!