wavefullpac

• Error 1706. An Installation Package For The Product Number
• Error 1706. An Installation Package For The Product 2017

Today my team had to install SQL Server 2008 client tools on an instance running SQL Server 2005. Since this instance hosted one of the critical databases of the client, everyone hoped that nothing should go wrong.

It was not the case to be. Yet again was in action.While trying to install the SQL Server 2008 Native Client, it would prompt the error that it setup is unable to find sqlnclix64.msi file.The reaction to this error is to look for the sqlnclix64.msi file in the SQL Server install media which was copied to one of the local drives. It was not there. SQL Server 2008 has sqlncli.msi in it no sqlnclix64.msi. Hence the DBA had no choice but to hit cancel. After hitting the cancel button, setup would fail stating that the installation of the Client Components had failed.Setup’s Detail.txt log file had this information. MSI Error: 1706An installation package for the product Microsoft SQL Server 2008 Native Client cannot be found.Try the installation again using a valid copy of the installation package 'sqlnclix64.msi'.Since it was asking for the file which did not exist, we tried to outsmart SQL Server.

SQL Server 2005 uses a file with this name to install SQL Server Native Client not SQL Server 2008 setup. Since the setup was looking for sqlnclix64.msi, we made a copy of the sqlncli.msi and renamed it as sqlnclix64.msi.Even renaming the file did not had any effect on it. Setup would continue to look for that file until we hit the cancel button.

Now it had to be more than just a missing file. The next place to look for was the Add/Remove Programs applet in Control Panel. Some of the components of SQL Server 2008 were already listed there.Then a little journey down the memory lane, made us recollect that our team had tried installing the same last week and had to cancel it because the Server required a reboot. Since this is a tightly controlled environment, a Change Control to the System Admin team is required to do it.

Error 1706. An Installation Package For The Product Number

Because of all this, that attempt was cancelled. But what the DBA at that time forgot was that he had to uninstall whatever he had installed, if the Change Control was to be rolled back.Alright. Now its time to clean up the mess. Since the last install of Native Client Tools was not properly done, it was kind of a half-baked installation. During the new setup it was looking for a.msi file of SQL Server 2005. The resolution was simple.

Uninstall all the components of SQL Server 2008 and then try to install the Client Components. Luckily we were able to uninstall it without any issues. Then tried the installation again, no error and all the components got installed successfully.This entry was posted in, and tagged, on. Post navigation.

11706Source MsiInstallerType ErrorDescription Product: - 1706English, please! Request a translation of the event description in plain English.Concepts to understand What is the role of MsiInstaller?Comments Peter Hayden (Last update 6/6/2006):- Error message: 'No valid source could be found for product Microsoft Office 2000' - Logon as an Administrator, uninstall Office, and using the customized setup, reinstall the components required with the drop-down list set to 'Run all from My Computer' rather than the default of 'Run from My Computer'. When installation is complete, go into every possible Office component from the Start button to ensure that it does not prompt for the Microsoft Office media.If you do not wish to uninstall Microsoft Office then a partial fix is as follows.

Logon to each user account that has this problem in turn, and run the registry fix from M274473.Do not run this registry fix for an account that will be copied to C:Documents and SettingsDefault User. Microsoft did not intend this fix to be used in this way. If it is then it will mess up Microsoft Office. The separate Microsoft fix for future users (who do not have an existing profile) detailed in M274473 has been tried but did not work.Ionut Marin (Last update 3/11/2006):If you are having problems when installing the '.Net Framework', then read the following newsgroup post. However since this post suggests modifying the registry and other important directories, try to do a backup (or Restore point) before following this post.From a newsgroup post: 'The following is a 'blanket solution' that has resolved many cases in my experience:1. Make sure IIS is not running.2.

Uninstall the.NET Framework from Control Panel's Add/Remove Programs.3. Delete following folders:C:WINNTassemblyC:WINNTMicrosoft.NET4. Delete the following filesC:WINNTSystem32mscoree.dllC:WINNTSystem32URTTempmscoree.dll5. Delete the following registry keys:HKEYLOCALMACHINESOFTWAREMicrosoft.NETFrameworkHKEYLOCALMACHINESOFTWAREMicrosoftMicrosoft IntegrationHKEYLOCALMACHINESOFTWAREMicrosoftNET Framework SDKHKEYLOCALMACHINESOFTWAREMicrosoftNET Framework Setup6. In C:WinNTInstaller do the following:Switch to Details view.Right-click on the Name column header and choose Comments from the pop-up list.Find the.MSI file with the comment that says ‘Microsoft.NET Framework(English)’ and delete it.7. Download (to your desktop) the.NET Framework (redistributable) from the link below. Once downloaded, run dotnetredist.exe and extract its contents (dotnetfx.exe) to your desktop as well.8.

Download.NET Framework SP2 (NDP10SPM321884En.exe) to your desktop. The download is also listed below.9. Start Run; type 'msconfig' (without quotes) and click OK to start the System Configuration Utility.10. Under the General tab, choose Diagnostic Startup.11. Under the Services tab, find and add a check to Windows Installer.12. Click Apply then Close.13. Reboot when prompted.14.

Type '%temp%' to get into your temporary directory. Delete all contents of the folder.

At this point, reinstall the Framework by running DotNetFX.exe, then SP2. Note that the settings set in the System Configuration Utility will persist from boot up to boot up; to get back to normal startup you must select 'Normal Startup' in the utility and reboot. If Framework and SP2 go on successfully, you may need to use the M306005 article to reset ASPNET mappings in IIS'.- Product: Microsoft SQL Server Desktop Engine - See M308856 and the link to 'Veritas Support Document ID: 270155'.- Product: Microsoft Office - See the link to 'See Novell Support TID10093508'.- Product: Citrix MetaFrame XP Server for Windows with Feature Release 3 - See 'Citrix Support Document ID: CTX107437'.- Product: Citrix MetaFrame Access Suite Licensing - See 'Citrix Support Document ID: CTX108390'.Singularity44 (Last update 5/29/2003):Error 1706. Message: An installation package for the product cannot be found.

Try the installation again using a valid copy of the installation package '.msi'. This error started occuring after I deleted some shared files while uninstalling another program.Wayne Gillo (Last update 5/29/2003):Error 1706. Message: 'No valid source could be found for product. The Windows installer cannot continue.'

This error occurs when a non-administrative user attempts to start Office 2000 the first time on Windows 20000 where an 'Installed on first use' program attempts to load. The reason for the failure is because the user is not allowed to run the installer. You can get around this in one of two ways. Mouse drivers windows xp. Either install the full Office Suite or log on with the Administrator account and run all of the Office programs prior to distributing images/computers to personnel.In this instance, I first checked to see if the Administrator could run this program and it started out without errors.

I then checked to make sure that all of the 'Install on first use' programs were set to be installed on the hard drive. In my particular circumstance, logging on with the Admin and running the Office programs fixed this error, but this same error can be associated with a package that needs to be installed at first use.Adrian Grigorof (Last update 4/29/2003):Error 1706 - I have received this error when I cancelled the 'on first use' installation of one of the Word features.Why bother deciphering Event logs when GFI EventsManager can do everything for you? Free trial here!Dmitriy Zavgorodniy (Last update 4/15/2003):Error 1706. Message: 'No valid source could be found for product Seagate Crystal Reports. The Windows installer cannot continue.' - In this case, my approach would be to check the actual shortcut, that points to the application.

Try to run the application directly from installed location.Another approach would be to copy file ntuser.dat file from the profile, where you installed the application. (I suppose, that this profile must be either Domain Admin or any other account with admin rights).

And then paste this file into default user profile.Joseph MikitishError 1706. Message: '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 FilesMicrosoft OfficeOffice101033SETUP.HLP.' This issue can be corrected by deleting all files in this location: c:windowsinstaller. Also run the office cleanup tool from MS.Links M274473, M306005,.NET Framework Downloads, Microsoft.NET Framework Service Pack 2, Novell Support TID10093508, Veritas Support Document ID: 270155, Citrix Support Document ID: CTX107437, Citrix Support Document ID: CTX108390.

11706Source MsiInstallerType ErrorDescription Product: - 1706English, please! Request a translation of the event description in plain English.Concepts to understand What is the role of MsiInstaller?Comments Peter Hayden (Last update 6/6/2006):- Error message: 'No valid source could be found for product Microsoft Office 2000' - Logon as an Administrator, uninstall Office, and using the customized setup, reinstall the components required with the drop-down list set to 'Run all from My Computer' rather than the default of 'Run from My Computer'. When installation is complete, go into every possible Office component from the Start button to ensure that it does not prompt for the Microsoft Office media.If you do not wish to uninstall Microsoft Office then a partial fix is as follows.

Error 1706. An Installation Package For The Product 2017

Logon to each user account that has this problem in turn, and run the registry fix from M274473.Do not run this registry fix for an account that will be copied to C:Documents and SettingsDefault User. Microsoft did not intend this fix to be used in this way.

If it is then it will mess up Microsoft Office. The separate Microsoft fix for future users (who do not have an existing profile) detailed in M274473 has been tried but did not work.

Ionut Marin (Last update 3/11/2006):If you are having problems when installing the '.Net Framework', then read the following newsgroup post. However since this post suggests modifying the registry and other important directories, try to do a backup (or Restore point) before following this post.From a newsgroup post: 'The following is a 'blanket solution' that has resolved many cases in my experience:1.

Make sure IIS is not running.2. Uninstall the.NET Framework from Control Panel's Add/Remove Programs.3. Delete following folders:C:WINNTassemblyC:WINNTMicrosoft.NET4. Delete the following filesC:WINNTSystem32mscoree.dllC:WINNTSystem32URTTempmscoree.dll5. Delete the following registry keys:HKEYLOCALMACHINESOFTWAREMicrosoft.NETFrameworkHKEYLOCALMACHINESOFTWAREMicrosoftMicrosoft IntegrationHKEYLOCALMACHINESOFTWAREMicrosoftNET Framework SDKHKEYLOCALMACHINESOFTWAREMicrosoftNET Framework Setup6. In C:WinNTInstaller do the following:Switch to Details view.Right-click on the Name column header and choose Comments from the pop-up list.Find the.MSI file with the comment that says ‘Microsoft.NET Framework(English)’ and delete it.7.

Download (to your desktop) the.NET Framework (redistributable) from the link below. Once downloaded, run dotnetredist.exe and extract its contents (dotnetfx.exe) to your desktop as well.8. Download.NET Framework SP2 (NDP10SPM321884En.exe) to your desktop. The download is also listed below.9.

Start Run; type 'msconfig' (without quotes) and click OK to start the System Configuration Utility.10. Under the General tab, choose Diagnostic Startup.11. Under the Services tab, find and add a check to Windows Installer.12. Click Apply then Close.13. Reboot when prompted.14.

Type '%temp%' to get into your temporary directory. Delete all contents of the folder. At this point, reinstall the Framework by running DotNetFX.exe, then SP2. Note that the settings set in the System Configuration Utility will persist from boot up to boot up; to get back to normal startup you must select 'Normal Startup' in the utility and reboot. If Framework and SP2 go on successfully, you may need to use the M306005 article to reset ASPNET mappings in IIS'.- Product: Microsoft SQL Server Desktop Engine - See M308856 and the link to 'Veritas Support Document ID: 270155'.- Product: Microsoft Office - See the link to 'See Novell Support TID10093508'.- Product: Citrix MetaFrame XP Server for Windows with Feature Release 3 - See 'Citrix Support Document ID: CTX107437'.- Product: Citrix MetaFrame Access Suite Licensing - See 'Citrix Support Document ID: CTX108390'. Singularity44 (Last update 5/29/2003):Error 1706. Message: An installation package for the product cannot be found.

Try the installation again using a valid copy of the installation package '.msi'. This error started occuring after I deleted some shared files while uninstalling another program. Wayne Gillo (Last update 5/29/2003):Error 1706. Message: 'No valid source could be found for product. The Windows installer cannot continue.'

This error occurs when a non-administrative user attempts to start Office 2000 the first time on Windows 20000 where an 'Installed on first use' program attempts to load. The reason for the failure is because the user is not allowed to run the installer. You can get around this in one of two ways. Either install the full Office Suite or log on with the Administrator account and run all of the Office programs prior to distributing images/computers to personnel.In this instance, I first checked to see if the Administrator could run this program and it started out without errors. I then checked to make sure that all of the 'Install on first use' programs were set to be installed on the hard drive.

In my particular circumstance, logging on with the Admin and running the Office programs fixed this error, but this same error can be associated with a package that needs to be installed at first use. Adrian Grigorof (Last update 4/29/2003):Error 1706 - I have received this error when I cancelled the 'on first use' installation of one of the Word features. Why bother deciphering Event logs when GFI EventsManager can do everything for you? Free trial here! Dmitriy Zavgorodniy (Last update 4/15/2003):Error 1706.

Message: 'No valid source could be found for product Seagate Crystal Reports. The Windows installer cannot continue.' - In this case, my approach would be to check the actual shortcut, that points to the application. Try to run the application directly from installed location.Another approach would be to copy file ntuser.dat file from the profile, where you installed the application. (I suppose, that this profile must be either Domain Admin or any other account with admin rights). And then paste this file into default user profile.

Joseph MikitishError 1706. Message: '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 FilesMicrosoft OfficeOffice101033SETUP.HLP.' This issue can be corrected by deleting all files in this location: c:windowsinstaller. Also run the office cleanup tool from MS.Links M274473, M306005,.NET Framework Downloads, Microsoft.NET Framework Service Pack 2, Novell Support TID10093508, Veritas Support Document ID: 270155, Citrix Support Document ID: CTX107437, Citrix Support Document ID: CTX108390.Producto: Microsoft Office 2000 Professional - Error 1706. No se encuentra un origen vdo para el producto Microsoft Office 2000 Professional.

Windows Installer no puede continuar.Oct 13, 2009.Product: Microsoft Office Professional Edition 2003 - Error 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 FilesMicrosoft OfficeOFFICE111033SETUP.CHM.Dec 01, 2009.Product: Roxio Media Manager - Error 1706.No valid source could be found for product Roxio Media Manager. The Windows Installer cannot continue.Jan 29, 2010.Product: Microsoft Office 2000 Disc 2 - Error 1706. No valid source could be found for product Microsoft Office 2000 Disc 2.

The Windows installer cannot continue.May 13, 2010.Product: Status - Error 1706. An installation package for the product Status cannot be found. Try the installation again using a valid copy of the installation package 'status.msi'.Dec 02, 2010.Product: Roxio Update Manager - Error 1706. An installation package for the product Roxio Update Manager cannot be found. Try the installation again using a valid copy of the installation package 'UM.MSI'.Dec 03, 2010.message string data: Product: SolutionCenter - Error 1706. An installation package for the product SolutionCenter cannot be found.

Try the installation again using a valid copy of the installation package 'SolutionCenter.msi'., (NULL), (NULL), (NULL), (NULL),Mar 23, 2011.Product: Symantec Endpoint Protection Manager - Error 1706.No valid source could be found for product Symantec Endpoint Protection Manager. The Windows Installer cannot continue.Oct 16, 2012.Product: SQL Server 2012 Database Engine Shared - Error 1706. An installation package for the product SQL Server 2012 Database Engine Shared cannot be found. Try the installation again using a valid copy of the installation package 'SQLENGINECORESHARED.MSI'.Aug 10, 2014.