<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Issues I've seen so far with installing .NET Framework 1.0 SP3 and 1.1 SP1</title><link>http://blogs.msdn.com/astebner/archive/2004/09/20/232236.aspx</link><description>I have been talking to some folks inside of Microsoft, looking at a few failures that have been reported internally and externally and read some newsgroup posts and it appears that there are 3 major points where setup has been failing for the .NET Framework</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Re: Issues I've seen so far with installing .NET Framework 1.0 SP3 and 1.1 SP1</title><link>http://blogs.msdn.com/astebner/archive/2004/09/20/232236.aspx#232263</link><pubDate>Tue, 21 Sep 2004 07:05:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:232263</guid><dc:creator>uwe@magerquark.de</dc:creator><description>Regarding the TargetInvocationException:&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;I just downloaded the file end started it from cmd prompt with &amp;lt;br&amp;gt;&amp;lt;br&amp;gt;     NDP1.1sp1-KB867460-X86.exe /l:uwelog.txt OR&amp;lt;br&amp;gt;     NDP1.1sp1-KB867460-X86.exe /l:c:\uwelog.txt&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;But unfortunately it did NOT generate any logfile, also the exception occured and was displayed.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;Maybe I'm wrong on one of the following things:&amp;lt;br&amp;gt;- I should not pass the &amp;amp;quot;/l&amp;amp;quot; parametert to NDP1.1sp1-KB867460-X86.exe but rather to some temporary setup file, extracted by NDP1.1sp1-KB867460-X86.exe.&amp;lt;br&amp;gt;- My machine is a development machine and therefore brings up the &amp;amp;quot;use debugger&amp;amp;quot; dialog box instead of writing to a log file.&amp;lt;br&amp;gt;- I use a german Windows XP and .NET. Maybe this only works with native english?</description></item><item><title>re: Issues I've seen so far with installing .NET Framework 1.0 SP3 and 1.1 SP1</title><link>http://blogs.msdn.com/astebner/archive/2004/09/20/232236.aspx#232271</link><pubDate>Tue, 21 Sep 2004 07:16:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:232271</guid><dc:creator>Uwe</dc:creator><description>Regarding the TargetInvocationException:&lt;br&gt;&lt;br&gt;I just downloaded the file end started it from cmd prompt with &lt;br&gt;&lt;br&gt;     NDP1.1sp1-KB867460-X86.exe /l:uwelog.txt OR&lt;br&gt;     NDP1.1sp1-KB867460-X86.exe /l:c:\uwelog.txt&lt;br&gt;&lt;br&gt;&lt;br&gt;But unfortunately it did NOT generate any logfile, also the exception occured and was displayed.&lt;br&gt;&lt;br&gt;Maybe I'm wrong on one of the following things:&lt;br&gt;- I should not pass the &amp;quot;/l&amp;quot; parametert to NDP1.1sp1-KB867460-X86.exe but rather to some temporary setup file, extracted by NDP1.1sp1-KB867460-X86.exe.&lt;br&gt;- My machine is a development machine and therefore brings up the &amp;quot;use debugger&amp;quot; dialog box instead of writing to a log file.&lt;br&gt;- I use a german Windows XP and .NET. Maybe this only works with native english?</description></item><item><title>re: Issues I've seen so far with installing .NET Framework 1.0 SP3 and 1.1 SP1</title><link>http://blogs.msdn.com/astebner/archive/2004/09/20/232236.aspx#232321</link><pubDate>Tue, 21 Sep 2004 11:08:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:232321</guid><dc:creator>Barry Dorrans</dc:creator><description>Another point of failure then. I have 3 Win2003 machines with the 1.0 and 1.1 frameworks on. 1.1 updates perfectly, but when 1.0 tries to update it complains ....&lt;br&gt;&lt;br&gt;&lt;br&gt;Product: Microsoft .NET Framework (English) -- Error 1706.No valid source could be found for product Microsoft .NET Framework (English).  The Windows installer cannot continue.&lt;br&gt;</description></item><item><title>Microsoft .NET 1.1 SP1, .NET 1.0 SP3, XP SP2 and potential problems.</title><link>http://blogs.msdn.com/astebner/archive/2004/09/20/232236.aspx#232418</link><pubDate>Tue, 21 Sep 2004 18:31:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:232418</guid><dc:creator>AddressOf.com</dc:creator><description /></item><item><title>re: Issues I've seen so far with installing .NET Framework 1.0 SP3 and 1.1 SP1</title><link>http://blogs.msdn.com/astebner/archive/2004/09/20/232236.aspx#232431</link><pubDate>Tue, 21 Sep 2004 15:58:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:232431</guid><dc:creator>Aaron Stebner</dc:creator><description>Regarding the first issue - it is possible that the TargetInvocationException happens before the log file command line is parsed.  Could you try to run a simple /? on that package and see if it still throws the exception?  Also, you may want to check out the application event log and determine whether or not there are any interesting entries there.  One other thing to try would be to take that EXE to a different machine, then run it with /Xp:&amp;lt;path&amp;gt;.  This will extract the patch package (*.MSP) to the location you specify.  Then you can take that MSP back to the other machine and right click and choose to install.&lt;br&gt;&lt;br&gt;For the 2nd issue, that is a repair being triggered because a component is detected as being broken.  Extracting the original dotnetfx.exe using /t:c:\temp /c and then browsing to that copy of netfx.msi when prompted should let you get past that.  You can also look in the application event log for information about why the repair was triggered.&lt;br&gt;&lt;br&gt;If the above doesn't help please email me directly at aaronste &amp;quot;at&amp;quot; microsoft &amp;quot;dot&amp;quot; com and we can look at it in more detail....&lt;br&gt;</description></item><item><title>.NET Service Pack Setup Issues</title><link>http://blogs.msdn.com/astebner/archive/2004/09/20/232236.aspx#232647</link><pubDate>Wed, 22 Sep 2004 05:17:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:232647</guid><dc:creator>OdeToCode Link Blog</dc:creator><description /></item><item><title>re: Issues I've seen so far with installing .NET Framework 1.0 SP3 and 1.1 SP1</title><link>http://blogs.msdn.com/astebner/archive/2004/09/20/232236.aspx#240970</link><pubDate>Mon, 11 Oct 2004 22:04:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:240970</guid><dc:creator>nel</dc:creator><description>i just tried to install Microsoft .NET Framework 1.1 Service Pack 1 on my Windows ME machine and it kept failing without giving me an error.  I was finally able to install it successfully when i did a Ctrl+Alt+Del while setup was in progress and noticed two processes Sla325 and Ndp1.  I went ahead and KILLED/end Task the Sla325 and setup was able to successfully install the service pack1.</description></item><item><title>re: Issues I've seen so far with installing .NET Framework 1.0 SP3 and 1.1 SP1</title><link>http://blogs.msdn.com/astebner/archive/2004/09/20/232236.aspx#417462</link><pubDate>Sat, 14 May 2005 16:44:56 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:417462</guid><dc:creator>Qflash</dc:creator><description>RePost:&lt;br&gt;&lt;a rel="nofollow" target="_new" href="http://www.yeyan.cn/SoftwareEngineering/NETFrameworkinstalling.aspx"&gt;http://www.yeyan.cn/SoftwareEngineering/NETFrameworkinstalling.aspx&lt;/a&gt;</description></item><item><title>More detailed troubleshooting ideas for .NET Framework 1.0 SP3 and 1.1 SP1 failures</title><link>http://blogs.msdn.com/astebner/archive/2004/09/20/232236.aspx#8993316</link><pubDate>Fri, 10 Oct 2008 00:16:08 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8993316</guid><dc:creator>Aaron Stebner's WebLog</dc:creator><description>&lt;p&gt;I have posted a couple of previous items about .NET Framework 1.0 SP3 and 1.1 SP1 installation issues&lt;/p&gt;
</description></item></channel></rss>