When attempting to install the Duet client to user in an automated fashion, the install may fail with an error. The error may seem cryptic, but we have a document on TechNet that can help explain what piece may have failed. For instance here is a excerpt from a setup log that failed:
9/24/2009 : 8:47:28 AM : I: Invoking Duet 1.5 SP3 Install
9/24/2009 : 8:47:28 AM : I: Executing following command
C:\Duet\setup.exe ACCEPT_EULA=YES REBOOT=ReallySuppress READSERVICE_URL=https://contoso.com:8020/DuetReadService.asmx /l*v c:\duet_SetupLog.log /qb!-
9/24/2009 : 8:50:47 AM : I: Unknown Error. Result = 2. Please Check Installer Log for more information
9/24/2009 : 8:50:47 AM : E: InstallDuet Duet Installation Failed - error code: 2
9/24/2009 : 8:50:47 AM : E: InstallDuet Duet Client Install validation failed
9/24/2009 : 8:50:47 AM : E: install Installation/verification failure, see detailed errors
If you navigate to technet.microsoft.com/en-us/library/cc983797.aspx you will see the following chart:
<snip>
/InstallPreReq (or any other install options) – Returns 0 on Success, non-zero values specify the stage at which installation failed.
UNSUPPORTED64BIT -1000
OFFICENOTINSTALLED 1
SQLINSTALLFAILURE 2
VSTOINSTALLFAILURE 4
DOTNETINSTALLFAILURE 8
OWC11INSTALLFAILURE 160
</snip>
From this you can see that error 2 indicates that there was a problem with the SQL client installation. With this information, you can look at other setup logs to figure out why the SQL client failed to install.