Questions & Answers
Help with MSI 1706
Help with MSI 1706
How helpful is this to you?
Windows Installer (MSI)
Windows Installer (MSI) Error Messages
Help with MSI (Microsoft Installer) error 1706: No valid source could be found for product .
[ + ] Show Comments
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
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
. 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:
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:
Answer this question
on this question for clarity
Don't be a Stranger!
Sign up today to participate, stay informed, earn points and establish a reputation for yourself!
Windows Logo Testing warning on XP
Deploying Acrobat 6.01 with GPO using MSIEXEC switches
Repackaging Software that requires a Unique Serial Number
Application & Content Deployment Tool
MYOB14 (Ver 2004) Error 20000 Message
Office 2003 WITH SP1
MS Project 2000 via Group Policy Woes
SMS 2003 SP1 & Win XP SP2
SoftDeployer Home Page
K2000 Deployment Appliance Documentation
Smart Software Synchronisation Home Page
PolicyMaker Home Page
ActiSetup Product FAQ
Zenworks Suite Support
Rembo Auto-Deploy Support
Applying community-inspired innovation to software updates
Right-Click and Install Your MSI/MST with Verbose Log Without Using BAT or CMD
Active Setup Concept
K1 Asset Managed Software Deployments at Image Time
InstallShield Error Codes (Setup.log)
InstallShield Setup Silent Installation Switches
AppDeploy: Articles: ActiveSetup
AppDeploy Command Line Installation Tips
Removing CCleaner through Kaspersky Security Center