Software Deployment Question

Help with MSI 1706

02/14/2004 99499 views
Help with MSI (Microsoft Installer) error 1706: No valid source could be found for product [2].
0 Comments   [ + ] Show comments


Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

All Answers

Where "2" is the name of the program attempting to install/repair.
If you installed your software from CD, you will need to provide the CD in order for the action to complete. If you installed your software from a network drive letter, make sure the drive is mapped again.
To locate the area the software is attempting to look. Check the following registry subkey:
In here you will see several subkeys with long hexadecimal strings for names. These represent various Windows Installer applications installed on your system. Use the "find" feature or look in each until you find the one with a "DisplayName" value that matches that of your software (denoted in the error message as the number two). There are several values that control how the repair or removal of the software should be performed. Look for the "InstallSource" value- this is the location being checked for the applications installation files.
This error is normally seen after an application is already installed. When you run the program using the shortcut created by the installation, Windows Installer first checks to ensure all the files deemed important to the program are present and available. If one of these files is missing, or even corrupt, Windows Installer will attempt to go to the installation source (by default this is where it was initially installed from) and restore the files with fresh coppies.
Some common causes:
- a file has been deleted
- another program was installed that removed or replaced a file needed by the application
- another program was uninstalled and removed files needed by your application.
- security limitations that do not allow the system to see that a required file is present.
Look to your logs for more detail on just what file has been deemed unavailable:
1) Check the Application Log in Event Viewer (eventvwr.exe).
2) See our tip on turning on Windows Installer logging here. Once logging is enabled, attempt to launch the program again and look in your %TEMP% folder for the installer log file. You will see the path and filename for the problem file here (search for "ERROR").
Answered 02/14/2004 by: AppDeploy.com
Red Belt

I followed the directions as noted above. Found the program and did an "uninstall" of the program. After reboot a new program error came up. It seems all errors are being generated by an HP software program. I have begun "uninstalling" all HP software/devices from system. This will be a continuing evolution until I get down to the last one. Once I find it and "uninstall" fails to work. what do I do then?
Answered 05/10/2007 by: counselorchief
Yellow Belt

This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ