Installshield Error 1706
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and error 1706 fix policies of this site About Us Learn more about Stack Overflow the
Error 1706 No Valid Source Could Be Found
company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users
Error 1706 Windows 10
Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes
Error 1706 Office 2013
a minute: Sign up InstallScript project giving Error 1706 when upgrading up vote 1 down vote favorite I have an InstallScript project written from scratch in InstallShield 2010. It contains, amongst other things, three native InstallShield objects and four InstallShield Merge Module Holder Objects which wrap MSM files. When I originally tested the project, it installed fine on a clean environment, error 1706 windows installer but when I tried upgrading to a newer version, each of the four Merge Module Holder Objects produced an "Error 1706. No valid source can be found for product XXXX" message. I did some digging on the net and found that this is a Windows Installer error, and it occurs because the MSI file has to exist on the machine even after the original install media is gone. The recommended way to ensure that is to tick the "cache the msi package locally" checkbox in the Merge Module Holder Object property dialog. I ticked that box for all four merge modules and re-tested, but that did not solve the problem. I then looked at where these merge modules were actually being put on the hard disk. The property dialog said
360 games PC games error 1706 office 2007 Windows games Windows phone games Entertainment All Entertainment error 1706 windows installer cannot continue Movies & TV Music Business & Education Business Students & educators error 1706 setup cannot find the required files office 2010 Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security Internet http://stackoverflow.com/questions/3110029/installscript-project-giving-error-1706-when-upgrading Explorer Microsoft Edge Skype OneNote OneDrive Microsoft Health MSN Bing Microsoft Groove Microsoft Movies & TV Devices & Xbox All Microsoft devices Microsoft Surface All Windows PCs & tablets PC accessories Xbox & games Microsoft Lumia All https://support.microsoft.com/en-us/kb/297834 Windows phones Microsoft HoloLens For business Cloud Platform Microsoft Azure Microsoft Dynamics Windows for business Office for business Skype for business Surface for business Enterprise solutions Small business solutions Find a solutions provider Volume Licensing For developers & IT pros Develop Windows apps Microsoft Azure MSDN TechNet Visual Studio For students & educators Office for students OneNote in classroom Shop PCs & tablets perfect for students Microsoft in Education Support Sign in Cart Cart Javascript is disabled Please enable javascript and refresh the page Cookies are disabled Please enable cookies and refresh the page CV: {{ getCv() }} English (United States) Terms of use Privacy & cookies Trademarks © 2016 Microsoft
your computer. This error is caused by several issues with the Office installer, and has its roots with the likes of having administrative privileges, having corrupt / damaged files, or just not using the CD properly. You may receive an error that looks similar to the following: "Error http://www.personalcomputerfixes.com/general-errors/how-to-repair-windows-installer-error-1706/ 1706. Setup cannot find the required files. Check your connection to the network, or CD-ROM drive. For other potential solutions to this problem, see C:\Program Files\Microsoft Office\Office10\1033\Setup.hlp." What Causes The 1706 Error There a several causes of the Installer Error 1706, of which here are the most common: You originally installed Microsoft Office from a network administrative installation. The network administrative installation is no longer available to you. You are trying to use an Office CD-ROM when you error 1706 are prompted by the Windows Installer for an Office source location. You click Cancel when you are prompted to Insert the CD You have registry errors on your PC The Windows Installer cannot work out the difference between two source types, because the files in an administrative installation are uncompressed, and the files on an Office CD-ROM are compressed. How To Fix The 1706 Error Step 1 - Download The Latest Version Of Install Shield Install Shield often receives error 1706 windows updates to ensure it can with stand all of the latest files. If you are receiving the 1706 error, then it is likely that your InstallShield could possibly be out of date, and recommended that you update it. To do this, you need to be able to download the latest version of InstallShield from their website. Step 2 - Make Sure You Click “Setup.exe” (Not The MSI File) Clicking on the "MSI" file will result in the 1706 error, as it will not have the range of options needed to run. To fix this you should click the Setup.exe application that the program will have. Setup.exe will utilitize the MSI file, and will bring all the different connections together, allowing your computer to run much smoother with the installer working as well as it should. Step 3 - Use An Alternative Network Solution Not having the correct network permissions can result in the 1706 error, because some networks have different protocols. If you don't have the correct network permissions then the permission barriers can prevent you from installing the programs you need, making it a recommended step to use a different network solution. To use an alternative network follow these steps: Click Start and then click Run. In the Open box, type a command line similar to the following, and then click OK new network path\Setup.exe /fvm package name.msi where new network path is