Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
Product: <application name> -- 1706 <error message>
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What is the role of MsiInstaller?
- 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 ME274473.
Do not run this registry fix for an account that will be copied to C:\Documents and Settings\Default 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.
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:
4. Delete the following files
5. Delete the following registry keys:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework SDK]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup]
6. In C:\WinNT\Installer 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 (NDP10_SP_ME321884_En.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. Start | Run... 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 ME306005 article to reset ASPNET mappings in IIS".
- Product: Microsoft SQL Server Desktop Engine - See ME308856 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".
Error 1706. Message: An installation package for the product <product name> cannot be found. Try the installation again using a valid copy of the installation package "<application name>.msi". This error started occuring after I deleted some shared files while uninstalling another program.
Error 1706. Message: "No valid source could be found for product <application name>. 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.
Error 1706 - I have received this error when I cancelled the "on first use" installation of one of the Word features.
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.
Error 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 Files\Microsoft Office\Office10\1033\SETUP.HLP."
This issue can be corrected by deleting all files in this location: c:\windows\installer. Also run the office cleanup tool from MS.
|Private comment: Subscribers only. See example of private comment|
|Links: .NET Framework Downloads, Microsoft .NET Framework Service Pack 2, Novell Support TID10093508, Veritas Support Document ID: 270155|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (2) - More links...|
Send comments or solutions
- Notify me when updated