Error 1706 Visual Studio.net
ASP.NET Community Standup Forums Help Home/ASP.NET Forums/Retired Forums/Visual Studio .NET 2003 and Visual Studio .NET 2002 (RETIRED)/Error:1706. No valid source could be found for product Visual Studio... Error:1706. No valid source could be found for product Visual Studio .Net Enterprise Architect RSS 1 reply Last post Oct 13, 2004 04:53 PM by DarrellNorton ‹ Previous Thread|Next Thread › Print Share Twitter Facebook Email Shortcuts Active Threads Unanswered Threads Unresolved Threads Support Options Advanced Search Reply k_hari None 0 Points 47 Posts Error:1706. No valid source could be found for product Visual Studio .Net Enterprise Architect Oct 12, 2004 10:41 AM|k_hari|LINK Hi all Just I was testing web setup project in Visual Studio.net 2003. I got this error when I build the system: "error:1706. No valid source could be found for product Visual Studio .Net Enterprise Architect" I think I don't have Enterprise Architect software or tools whatever with me.So is there any workaround so that I can build this project with windows installer. Any suggestions appreciable. Thanks Reply DarrellNorto... All-Star 66183 Points 10249 Posts ModeratorMVP Re: Error:1706. No valid source could be found for product Visual Studio .Net Enterprise Architec... Oct 13, 2004 04:53 PM|DarrellNorton|LINK Check the Application Event Log, it will let you know what component and feature that it is failing on. Then you may be able to fix it or create some kind of workaround. Darrell Norton, MVP Darrell Norton's Blog Please click "Mark as Answer" if this helped you. ‹ Previous Thread|Next Thread › This site is managed for Microsoft by Neudesic, LLC. | © 2016 Microsoft. All rights reserved. Privacy Statement| Terms of Use| Contact Us| Advertise With Us|
share this, since it cost me 2.5 days... When running Visual Studio .NET 2003 as a Power User, if I pressed F1 for context-sensitive help, I either (consistently for particular highlighted keyword) got the relevant help or else visual studio would say "Please wait while Windows configures Visual Studio .NET Enterprise Developer 2003 - English" then grind away for a while trying to load something (unknown) from somewhere (unknown) and eventually fail with "Error 1706. No valid source could be found for product Visual Studio ..NET Enterprise Developer 2003 - English. The Windows installer cannot continue." Then when I clicked "OK", the sodding thing went off and tried to load it all again. Twice. And then finally it http://forums.asp.net/t/717047.aspx?Error+1706+No+valid+source+could+be+found+for+product+Visual+Studio+Net+Enterprise+Architect would show me the correct help, so it knew how to do it all along. After searching fruitlessly for solutions (Q297103 is a classic "you are in a helicopter") and re-installing twice, I worked it out by looking inside the helpfiles. The offending help/web pages had an ActiveX control 59CC0C20-679B-11D2-88BD-0800361A1803 to do some cookie stuff. That classid should register C:\Program Files\Common Files\Microsoft Shared\MSDN\CookDoc.dll so I found that file on my system and re-registered it. Which has magically worked. So, I hope http://www.pcreview.co.uk/threads/visual-studio-net-help-error-1706.1863789/ this saves somebody else's time. Al. Al, Cambridge, UK, Jun 9, 2005 #1 Advertisements Show Ignored Content Want to reply to this thread or ask your own question? It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum. Sign Up Now! Similar Threads Visual Studio 6 vs. Visual Studio .Net =?iso-8859-1?B?UOVs?=, Jul 8, 2003, in forum: Microsoft Dot NET Replies: 0 Views: 586 =?iso-8859-1?B?UOVs?= Jul 8, 2003 Trivial question - Visual C# .Net vs Visual Studio .Net John Timbers, Oct 2, 2003, in forum: Microsoft Dot NET Replies: 32 Views: 547 Alvin Bruney Nov 8, 2003 can install Visual Studio .NET 2003 over Visual Studio v6? Dan, Nov 10, 2003, in forum: Microsoft Dot NET Replies: 2 Views: 368 William Ryan Nov 10, 2003 compiling with visual studio .NET and linking with visual studio 6.0 Guest, May 4, 2004, in forum: Microsoft Dot NET Replies: 2 Views: 333 Guest May 4, 2004 Visual Studio .NET and Visual Studio 6.0 Guest, May 4, 2004, in forum: Microsoft Dot NET Replies: 1 Views: 257 Klaus H. Probst May 5, 2004 Installing Visual Studio 6 AFTER Visual Studio 2003 trial and Office 2003 - Is it safe? Dave Smithz, Jun 29, 2004, in forum: Microsoft Dot NET Replies: 1 Views: 426 Cowboy \(Gregory A. Beamer\) [MVP] Jun 30, 2004 vi
question and get tips & solutions from a community of 418,505 IT Pros & Developers. It's quick & easy. Deployment error message P: n/a Chuck I'm https://bytes.com/topic/visual-basic-net/answers/375128-deployment-error-message using a setup and deployment project in VB.Net to make my distributable file. http://www.ikangyun.net/Error_1706_Visual_Studio_Net.html I set all my options and go to build my project and I get the following error. Error 1706. No valid source could be found for the following product Visual Studio.Net Enterprise Developer 2003 English. The windows installed could not continue. Any ideas what's going on? Thanks Nov 21 '05 #1 Post Reply error 1706 Share this Question 1 Reply P: n/a Mona \(Grapecity\) Hi Chuck, This error can occur if the media files required to make the .MSI files are not accessible by the framework. This can happen if the media that is currently being used and the media that was originally used to install the program have the MSI file at different relative paths. To work around this problem, error 1706 visual insert the visual studio disk into my cdrom drive and then build the setup project. When it is building the setup project it will search for the visual studio disk and it will fix the problem. For more on this error you can refer the following links [PRB: Error 1706 "No Valid Source Could Be Found" When Installing MSI File from Removable Media] http://support.microsoft.com/default...b;en-us;299803 and [PRB: Changing Source Causes Error 1706] http://support.microsoft.com/default...b;en-us;297103 HTH Mona "Chuck"
is caused when Device Manager calls off a hardware device because the hardware reported to Windows that it's having some kind of unknown problem.This extremely generic message could mean there's a true hardware issue or it could simply indicate that there's a driver problem that Windows isn't seeing as such but that the hardware is being affected by. Manual Solution to fix Error 1706 Visual Studio Net To resolve Error 1706 Visual Studio Net, do the following. To open Device Manager, click Start, click Search programs and files, and then type Device Manager. A list of available matching items appears above the search box; click Device Manager. Device Manager opens with your computer name at the top and a list of devices that are installed on your computer beneath your computer name. Locate the malfunctioning device in the list of devices, right-click the device, and then click Uninstall. When a warning message appears that you are uninstalling a device from your system, click OK. Device manager uninstalls the device. Right-click the computer name in Device Manager and click Scan for hardware changes. Device manager scans your system and automatically reinstalls your device. Right-click the device and click Properties. On the General tab of the device Properties dialog box, in Device status, you should see the message This device is working properly.If the methods above do not dispose of the problems with the device, and if the device is an external drive, such as a USB flash drive or external hard drive, use the taskbar icon to safely eject the device, then unplug the device from the computer. For devices that use AC power, unplug the device from the electrical outlet or power strip, wait 30 seconds, and then plug it back in. Turn on the device power switch, and then plug it in to your computer. If the device includes a drivers disk, ensure that you have it handy to install the device drivers; otherwise, Windows should automatically locate the correct drivers and install them.If you do not have a driver disk and Windows cannot automatically discover the drivers, it means that your hardware manufacturer has not uploaded the drivers for your device to Windows Update. If this is the case, you must go to your device manufacturer web si