I have this resolved and have successfully package Teradata SQL Assistant. The trick was to use merged isolation on the ../NCR/GSS directories to find that that thinapp version then saw the needed files that the locally installed copy had placed there that for some reason, Thinapp did not put in the package. I then manually copied the files installed under the C:\Program Files\NCR\Teradata GSS to the Package (%ProgramFilesDir%) and repackaged.

Specifically it was missing many files and directories in the LCLIENT sub-directory of the Teradata GSS installation.

If you ever have to install this software, you need to install the software in order (like many applications) and I chose to package the ODBC portion separately and then link the Teradata SQL Assistant to the ODBC package to make my troubleshooting easier.

My installation order was as follows:

Take snapshot
Install TDICU
Install GSS
Install ODBC Drivers
Take post install snapshot
Create Package
Copy installed C:\Program Files\NCR\Teradata GSS directory and all subdirectories and files to the Package.
Build Package.

Take snapshot
Install Teradata SQL Assistant
Take Post install snapshot
Create Package
Edit Package.INI to link to ODBC package I created above
Build Package

I don't see why you couldn't build it all together at this point. I chose not to so that I could easily troubleshoot what part of the package the error was coming from.

Adjust your cooking time for altitude; your results may vary.

Bryan

Read more at: http://communities.vmware.com/message/1535615