Additional suggested workaround for TargetInvocation exception in .NET Framework 1.0 SP3 or 1.1 SP1


Yesterday, I wrote about some of the problems encountered so far with the .NET Framework 1.0 SP3 and 1.1 SP1 in an article here.  I was talking to one of the developers who worked on these service pack setups, and he suggested a couple additional workarounds for cases where someone encounters the TargetInvocation exception:



  1. Repair .NET Framework 1.0 or 1.1 (depending on what version you are trying to install the service pack for) and then try applying the service pack again.  To perform a repair, you can follow the steps in %windir%\Microsoft.NET\Framework\v1.0.3705\repair.htm or %windir%\Microsoft.NET\Framework\v1.1.4322\1033\repairRedist.htm.
  2. Clear the Windows Update temporary downloads cache.  See http://support.microsoft.com/?kbid=193385 for more information about how to do this.  You may also need to delete the contents of %windir%\SoftwareDistribution\Download in addition to the steps listed in the KB article.

Hope this helps….


<update date=”10/27/2005″> The link in item 2 above is broken because the KB article was unpublished; updated with a new link and an additional step </update>


 

Comments (4)

  1. Hi monkeyBoy – thank you for the heads up on the broken link. I’ve updated the text of the article with a link that works…

  2. I have posted a couple of previous items about .NET Framework 1.0 SP3 and 1.1 SP1 installation issues

Skip to main content