Error 1606 Could Not Access Network Location Windows 7 Infragistics
Contents |
Wed, Jan 4 2012 10:41 AM Reply Hello friends, Now I'm installing NetAdvantage 2004 vol. 3 but I obtain this error: error 1606. could not access network location %SystemDrive%\inetpub\wwwroot I've tried error 1606 could not access network location appdata windows 7 this solution posted by team Infragistic: http://devcenter.infragistics.com/Support/KnowledgeBaseArticle.aspx?ArticleID=10058 But I obtain the same results, error 1606 could not access network location 0 please, What must I do? PC: Windows 7 64 bits, Help, this is urgent.... Thanks, regards. Reply Post Points: 20 Verified error 1606 could not access network location systemdrive inetpub wwwroot Answer [Infragistics] Brian Wint Points 681 Replied On: Thu, Jan 5 2012 10:15 AM Reply Verified by ErosDark Hello, Since you are on a 64-bit machine, Windows is likely redirecting the installation to
Error 1606 Could Not Access Network Location Public Desktop
use the 32-bit registry hive. Try updating the value from the 32-bit registry hive at HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\InetStp. Brian Wint Infragistics Release Engineer Need help? Find the various ways you can get help from Infragistics. Reply Post Points: 55 All Replies [Infragistics] Brian Wint Points 681 Replied On: Thu, Jan 5 2012 10:15 AM Reply Verified by ErosDark Hello, Since you are on a 64-bit machine, Windows is likely redirecting error 1606 could not access network location adobe reader the installation to use the 32-bit registry hive. Try updating the value from the 32-bit registry hive at HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\InetStp. Brian Wint Infragistics Release Engineer Need help? Find the various ways you can get help from Infragistics. Reply Post Points: 55 ErosDark Points 1,210 Replied On: Thu, Jan 5 2012 10:17 AM Reply Thanks, I've solved this problem with your suggestion. Regards. Reply Post Points: 5 Mike Rudel Points 20 Replied On: Fri, May 10 2013 5:22 PM Reply Hello Brian, I am having the same issue. Which setting are you referring to here? The InstallPath, PathWWWRoot or something else? Thanks, Mike Reply Post Points: 20 [Infragistics] Brian Wint Points 681 Replied On: Mon, May 13 2013 9:26 AM Reply Hello Mike, It's the PathWWWRoot value. Brian Wint Infragistics Release Engineer Need help? Find the various ways you can get help from Infragistics. Reply Post Points: 5 Previous | Next Page 1 of 1 (5 items) | RSS Tweets by @infragistics Recent Posts Re: Selecting rows in group by display based upon context menu set in columnheader Selecting rows in group by display based upon context menu set in columnheader Re: How to access the "String" in the UltraGrid Cell? How to
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more error 1606 could not access network location vmware vcenter site recovery manager about Stack Overflow the company Business Learn more about hiring developers or posting ads
Error 1606 Could Not Access Network Location Autodesk
with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow
Error 1606 Could Not Access Network Location Null
is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Error 1606. Could not access network location %SystemDrive%\inetpub\wwwroot\ while installing on IIS7 up http://www.infragistics.com/community/forums/t/64049.aspx vote 8 down vote favorite I'm trying to port our software installer which currently supports Windows 2000 and Windows 2003 to a Windows 2008 environment. Currently, the installer gets an error which reads "Error 1606. Could not access network location %SystemDrive%\inetpub\wwwroot." %SystemDrive% is without a doubt C:\, and C:\inetpub\wwwroot\ has the correct accessibility. It is interesting that if I hardcode the path in the following keys in the registry http://stackoverflow.com/questions/1202136/error-1606-could-not-access-network-location-systemdrive-inetpub-wwwroot-whi to C:\inetpub\wwwroot\, without using the environment variable, the installer works correctly. • HKLM/Software/Wow6432Node/Microsoft/InetStp/PathWWWRoot • KHLM/Software/Microsoft/InetStp/PathWWWRoot. This seems like a very poor hack. I do not want to tell our clients that they need to hack their registry before they will be able to install our product. Another option is to change the registry behind the scenes, do our install, and revert the registry keys to their original values at the end of the install, but obviously I don't like this solution either. I find it hard to believe that Microsoft would have done this without reason, so there must be an alternate approach to get these installers to work without modifying the registry. Any tips appreciated. installer windows-server-2008 share|improve this question edited Aug 6 '09 at 19:10 bdonlan 133k18185269 asked Jul 29 '09 at 18:26 Mark add a comment| 2 Answers 2 active oldest votes up vote 12 down vote I encountered this error during an Infragistics 2007 installation. The solution was to modify the registry key value. The issue is with the installation program. The %SystemDrive% portion of the value should be replaced with C: For 32bit machines the key is HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\InetStp\PathWWWRoot. For 64 bit machines the key that needs to be modified should be HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Mic