Hi Jo Smith,
CAUSE
This will occur if the original installation source was uncompressed and
the current source is compressed or vise versa. For example, if an
administrator uses a package that has a word count summary property of 2 or
3 to perform an administrative installation, users that initially installed
from the administrative image cannot then reinstall from the original media
source.
This behavior is by design.
For More information:
MORE INFORMATION
The word count summary property is a value that describes the type of
source file image. This value is a type bit field type and it can have a
value from 0 to 5. For additional information, see "word count summary
property" in Windows Installer Help. Note that type 2 and 3 specify that
the source files are in a compressed format (cabinet files):
Property value Type of source file image
0 Original source using long file names. Matches tree in directory table.
1 Original source using short file names. Matches tree in directory table.
2 Compressed source files using long file names. Matches cabinets and files
in the media table.
3 Compressed source files using short file names. Matches cabinets and
files in the media table.
4 Administrative image using long file names. Matches tree in directory
table.
5 Administrative image using short file names. Matches tree in directory
table.
When the administrative image is created, the file and folder structures
are uncompressed. A user can then install from this location and proceed
with maintenance mode activities (repair/reinstall) without errors. If for
some reason the administrative installation point becomes unavailable and
the user tries to revert back to the original compressed installation
media, the user will encounter the error message:
1706. No valid source could be found for product [product name].
This error occurs because the original installation location did not have
any compressed files. When the administrative image becomes unavailable and
the user points back to the original media, the Installer does not expect
to encounter compressed files and therefore returns error 1706.
NOTE: If an installation is from a compressed source such as a CD-ROM, then
the repair source should be of the same source type, compressed. Likewise,
if the installation is from a noncompressed source, then the repair should
be from the same source type, noncompressed.
Steps to Reproduce Behavior
The following is one way to reproduce the problem:
Create an .msi package that includes compressed source files.
Create an administrative image of this .msi package. (The command line
syntax is: msiexec /a [name of .msi package]).
Install the package from the administrative image.
Delete the administrative image.
Repair the installed .msi file and use the original compressed source. (The
command line syntax is: msiexec /f [name of .msi package]. The repair
installation could be also done through the Add/Remove utility in Control
Panel). During the repair installation, you will receive error 1706.
REFERENCES
Windows Installer Platform SDK download page:
http://msdn.microsoft.com/downloads/default.asp?URL=/code/sample.asp?url=/MS
DN-FILES/027/001/457/msdncompositedoc.xml
Thank You...
Raghu...
This posting is provided "AS IS" with no warranties, and confers no rights.
