Error 1706 Visual Studio 2005
Setup & Install by Heath Stewart Application Lifecycle Management Application Insights Release Management Team Foundation Server Testing Visual Studio Team Services All Languages Visual C++ Visual F# JavaScript TypeScript Python .NET .NET .NET with Beth Massi ASP.NET by Scott Hanselman OData Team WPF Platform Development Apps for Windows Bing Edge Microsoft Azure Office 365 Development Web Data Development SQL Server SQL Server Data Tools DocumentDB Setup & Install by Heath Stewart About Windows Installer, the .NET Framework, and Visual Studio. Resolving Prompts for Source ★★★★★★★★★★★★★★★ December 2, 2005 by Heath Stewart (MSFT) // 13 Comments 0 0 0 When discussing the Windows Installer cache, I mentioned how cabinet streams are stripped from the .msi file when the Windows Installer package is cached, and how this is a contributing factor to prompts for source. A prompt for source will occur when repairing or patching a product if the source for a file to reinstalled is not present. This results in the Windows Installer error 1706 to be displayed if installing with a user interface and in the log, and the Windows error 1603 (ERROR_INSTALL_FAILURE) to be returned from the process. Prior to Windows Installer 2.0 the original installation source was always necessary but that was fixed by Windows Installer 2.0. Now by adhering to certain rules you can mitigate prompts for source: Ensure no custom action access the original source location. Populate the MsiFileHash table for un-versioned files. Correctly populate the Version and Language columns in the File table for versioned files. Using whole files in a patch is also a good idea, but if you can support only Windows Installer 3.0 and newer you can support binary delta patching against a baseline cache that Windows Installer creates for smaller patch size. This allows patches to contain a binary delta between the target and upgrade binary files. For example, a QFE targeting the RTM can contain deltas between the RTM- and QFE-level binaries regardless of other patches that are installed, as long as that patch would supersede any other QFE that patched the same file set. To take advantage of the baseline cache, one must author the MsiPatchSequence table into their .msp file. Administrators can set the maximum size for all baseline caches o
360 games PC games Windows games Windows phone games Entertainment All Entertainment Movies & TV Music Business & Education Business Students & educators Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security Internet https://blogs.msdn.microsoft.com/heaths/2005/12/02/resolving-prompts-for-source/ 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
17, 2007 4:27 PM Yet another interesting quirk in the annals of Visual Studio 2005 SP1 issues: I've been wondering why periodically, attempting to build a Windows application solution in Visual http://www.andornot.com/blog/post/Visual-Studio-2005-SP1-Strikes-Again.aspx Studio 2003 (which includes a setup project), my machine would inexplicably decide to start a (seemingly) endless installation process that I would need to cancel and then proceed to kill all spawned msiexec processes running. I had done some quick googles to find out a solution before but hadn't come up with anything so I left it - I would soon be moving on to my new developer machine and would error 1706 probably repave my old machine. However, as I'm taking awhile to fully transition to my new machine running Vista (which I love, and sometimes despise), I'm still doing VS2003 builds on the old machine and was getting tired of the whole process which kills about 15 minutes of productivity everytime I need a final MSI installer to deploy. I let the build run while taking a break and saw the error 1706 visual ensuing error message: Error 1706.An installation package for the product Microsoft Visual Studio 2005 Pro - ENU cannot be found. Try the installation again using a valid copy of the installation package 'vs_setup.msi'. What the?!? We're not doing anything with Visual Studio 2005 here, only Visual Studio 2003! Thank goodness for Alex Thissen's post at really long link here. Turns out that SP1 not only messes with itself, but can also start playing havoc with VS2003 builds as well. The Visual Studio 2005 installer cache was confused, so whenever I did an MSI build, it was attempting to find and then install Visual Studio 2005. Cool! That's just what I want to do every time I do a totally unrelated task ;-) Did I mention that this all started to happen way back when following a finally successful Visual Studio 2005 SP1 upgrade? Fortunately the fix is relatively easy (took about 10 minutes for it to churn through the following): open a command prompt and, depending on what version of VS2005 you're running, run the following command: msiexec /fvomus {437AB8E0-FB69-4222-B280-A64F3DE22591} /l*v vs8_repair.log If you're like me, you attempted it while there were still some half-finished installers going on in the background from the previous half-finished MSI builds that you hadn't