Problems installing the new ASP.NET hotfix (KB886903 or KB887219)


I got a question from a customer this week who could not get an ASP.NET hotfix installed by launching it from Windows Update (due to an error like some folks have seen with other .NET Framework service packs that I described here).  As a result, he was trying to download the package directly, extract it and install manually, but he was having trouble trying to locate the underlying package and download it.  So I decided to try to do this myself to see how the process really works for an IT admin in the field, and I’m surprised by how complicated this process is.  Here are the specific steps I had to follow to locate and download this ASP.NET hotfix:

  1. I retrieved the KB article number from the Windows Update site
  2. I went to the Microsoft support site and found a link here that announces the security bulletin
  3. From there I followed the link for IT professionals since those links typically contain direct links to download packages to stage for installation in corporate networks or other scenarios where Windows Update is not an ideal option
  4. From there I followed the link to the Microsoft download center and used the suggestion to search for the keyword security_patch and filtered based on the .NET product family.  This gave me this results page
  5. From there I could choose what version(s) of the .NET Framework I wanted to patch and download the appropriate hotfix.  For example, this link leads to the hotfix that applies to .NET Framework 1.1 with SP1
  6. Now that I have downloaded the hotfix package, I can go back to the link for IT professionals and drill down to the details of the version of the hotfix I downloaded to figure out what command line switches to use to extract the contents of the package

It really seems like there should be an easier way to locate, download and extract a hotfix package from Microsoft.  If there is a simpler way that I have missed, please post a comment and let me know.

As a side note, this and any other .NET Framework or ASP.NET hotfixes are packaged using the same self-extracting wrapper as the .NET Framework 1.0 SP3 and 1.1 SP1, and therefore are all susceptible to the same set of issues as those service packs.  There is one big issue (that I consider to be a flaw) in the design for the packaging of the .NET Framework service packs and hotfixes.  The self-extracting wrapper EXE is written in managed code, so that means that if the .NET Framework is broken in any way and needs to be repaired, then the patch package will not even extract and launch correctly, and it cannot even give a useful error message.

 

Comments (42)

  1. I somehow must have managed to mess up the .NET Framework installation, both on XP and 2KPro. This is very embarrassing, since I’m the believer in keeping machines "clean" and would always rant against my colleagues installing 3rd party add-ons all over VS, but actually none of them had this problem.

    I couldn’t get the patch to install, so I tried repairing/removing/reinstalling .NET Framework 1.1 (SP 1) but all that failed with 1612.

    Repairing VS2003 Pro didn’t help and neither did installing VS2003 EntAr.

    So I took the path described. It’s a relief, but doesn’t feel good.

  2. Hi Henry,

    Error 1612 means that Windows Installer was unable to find the source location. In the cases that I have seen this for the .NET Framework, it has been because someone tried to silently install a hotfix for the .NET Framework (for example by using Windows Update), and Windows Installer detected that the .NET Framework needed to be repaired first. Because the .NET Framework is installed using an IExpress package, the source files are copied to the %temp% folder and then deleted when setup exits. In order to fix this, here is what I normally try first:

    1. Re-download dotnetfx.exe or locate it on a CD that you installed from

    2. Run dotnetfx.exe /t:c:dotnet /c to extract the source files

    3. Run msiexec.exe /fvecms c:dotnetnetfx.msi to repair the .NET Framework

    I hope this helps…

  3. Eric says:

    When I install the 887219 patch I get the Targetinvocation error. I have the reg key and the local MSI exists. When I try to repair, uninstall, or reinstall the .NET Framework I get a Windows Installer error:

    "The feature you are trying to use is on a netowkr resource that is unavailable.

    Click OK to try again, or enter an alternate path to a folder containing the installation pakage ‘tmp7.tmp’ in the box below:"

    The "box below" has my temp path in it. When I click Browse, it is looking for an MSP package, but I don’t know where that MSP is, so my reinstall fails.

    I’m available at

    webmaster AT ruskin DOT com

    if you have any suggestions

    thanks

  4. Work is being done to replace the managed wrapper and to return better error codes. This has been a huge problem and actually increases the size of the patch, though compressing the MSTs separate from the MSPs yields better compression since the CAB compression algorithm will save space for the mostly-similar MSTs, where an MSP will compress each MST separately and you lose out in the size savings.

    Apparently there was a reason, but I wasn’t here at that time.

  5. Hi Eric, I will follow up with you via email also but I wanted to post some general info about the error you ran into. The error you’re seeing is a Windows Installer source media request that is triggered by a health check that returned a failure (which indicates that component(s) that are part of the product are broken and need to be repaired). In the past, the most common scenario was that the .NET Framework itself needed to be repaired, and in those cases the source prompt dialog would be asking for the file netfx.msi. The way to get that file is to do the following:

    1. Re-download dotnetfx.exe

    2. Run dotnetfx.exe /t:c:dotnet /c to extract the contents

    3. Browse to c:dotnetnetfx.msi when you have a source prompt dialog

    Now that several hotfixes and service packs have shipped for the .NET Framework 1.0 and 1.1, the source prompt dialog will sometimes detect that it needs to repair the hotfix or service pack. If you are asked for a file named *.tmp in the source prompt dialog, it is much more tricky to figure out how to get the source file because there may be multiple hotfixes/SPs on the machine and you have to figure out which one needs to be repaired, and also because the patch installation setup wrapper generates the name of the patch file on the fly. Here is a rough set of steps that I think will work to get the file you need in this scenario (but I haven’t tried it yet so I may have to post an update here if I find problems with this so please bear with me):

    1. Run eventvwr.exe and choose to view the Application event log

    2. Look for the most recent events from the "MsiInstaller" source – this should give you the exact product/patch that failed the health check and requested source code

    3. Download the hotfix or SP that failed the health check

    4. Run the hotfix/SP exe with the switch /xp:<path> to extract the Windows Installer patch (MSP) from the exe

    5. Rename the MSP to be the exact name listed in the source prompt dialog

    6. Browse to the MSP with the updated name in the source prompt dialog

  6. Hey Heath – thank you for posting information about the plans for the hotfix/SP wrapper setup executable. I am really happy to hear that these setups will be more robust and debuggable in the future.

  7. Hi John, it would help if you can provide more details about what error messages you are receiving and what troubleshooting steps you have tried so far. There are a lot of suggestions in this blog article and in some of my previous postings that will hopefully be useful to you. Please let me know.

  8. Dave Mann says:

    OS: XP Home

    "…Registeresd JIT debugger is not available…"

    I’m sending this in for a fiend. This all the info I have. Could I, how can I, turn JIT debugging off? This machine is only used for email and surfing. Thanks Aaron.

  9. Eric says:

    Aaron, did you get my email about trying your suggestion? Basically the MsiInstaller event only said this so I couldn’t tell which hotfix was the problem. I found in the registry that it might have been SP1, but that MSP wasn’t accepted when I tried to uninstall and browsed to the MSP when it asked for tmp7.tmp

    Event Type: Information

    Event Source: MsiInstaller

    Event Category: None

    Event ID: 11708

    Description:

    Product: Microsoft .NET Framework 1.1 — Installation failed.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    Data:

    0000: 7b 43 42 32 46 37 45 44 {CB2F7ED

    0008: 44 2d 39 44 31 46 2d 34 D-9D1F-4

    0010: 33 43 31 2d 39 30 46 43 3C1-90FC

    0018: 2d 34 46 35 32 45 41 45 -4F52EAE

    0020: 31 37 32 41 31 7d 172A1}

  10. dan says:

    When I try to install the KB886903 fix through win update, or by using the hotfix exe directly, it gives me an error in "SL14a.tmp" and exits. (actually, SLXXX.tmp, since the last 3 characters of the filename before the extension appear to be randomly generated). the full text of the error is as follows:

    Dialog title:

    SL14a.tmp – Common Language Runtime Debugging Services

    Dialog body:

    Application has generated an exception that could not be handled.

    Process id=0xbc0 (3008), Thread id=0xea8 (3752).

    Click ok to terminate, cancel to debug.

    anyone have any idea what this is caused by, and what i could do to get this installed?

  11. Hi Eric, I did send you a reply email yesterday, please let me know if you did not get it and I will resend. Thanks!

  12. Eric says:

    Aaron, I didn’t get the reply. Go ahead and resend, and I’ll ask our admin to be on the lookout in case it’s getting blocked.

  13. Dan – for the CLR debugging error you are seeing, I would suggest first trying the troubleshooting steps listed in one of my older blog items – http://blogs.msdn.com/astebner/archive/2004/11/23/268934.aspx“>http://blogs.msdn.com/astebner/archive/2004/11/23/268934.aspx. That item is about the .NET Framework 1.0 SP3 and 1.1 SP1 but the setup wrapper is the same as for these ASP.NET hotfixes so the issues there are equally valid for both.

    Dave – I am researching some of the Windows debugger registry settings to answer your question. In the meantime I would suggest that your friend also take a look at the troubleshooting guide at http://blogs.msdn.com/astebner/archive/2004/11/23/268934.aspx“>http://blogs.msdn.com/astebner/archive/2004/11/23/268934.aspx.

    Eric – I have resent the mail from yesterday. It did have an attachment on it but I renamed it from .exe to .txt so hopefully it will not be blocked by your mail server.

  14. Mike says:

    Aaron,

    Receiving similar messages related to the .net update from last weekend. Still have not been able to resolve. Not quite sure which steps to follow. XP Pro is the operating system. I have looked for hte uninstall of the .net framework but do not see it’s location. Suggestions appreciated.

    Mike

  15. Hi Mike, the best place to start is the troubleshooting guide that I posted here – http://blogs.msdn.com/astebner/archive/2004/11/23/268934.aspx. I will also follow up with you via email.

  16. Dave – I am not sure how to turn off debugging but I have found this registry key that controls what debugger gets launched when a crash occurs. It is located at HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionAeDebug. The data in the Debugger value is the executable that is launched when a crash occurs.

  17. Todd says:

    Just an FYI

    The SMS mssecure.cab had an error in it the first week it was out.

    886903 was mistaken for 886904. Machines would try to install 886904 instead of the correct 886903.

  18. Deamon says:

    I have windows 2000 pro with sp4 and tryed to install dotnetfx and gets this error"

    RegSvcs.exe – Common Language Runtime Debugging Services

    Apllication has generated an exception that could not be handled.

    Process id=0Xa5c (2652), Thread id-0xac4 (2756)

  19. Hi Deamon – at the end of last week we had 2 reports of this problem from customers who called our Product Support team. These cases are still under investigation because our common troubleshooting steps did not work. I will post a follow-up on my blog as soon as we identify what the root cause is and what the possible workarounds are.

  20. J.C. Brunel says:

    I am just an average user and I keep finding this KB886903 download in my update, cannot install it and the yellow shield is permanently on my taskbar telling me to install a critical update. I do not even use net framework. How do I stop winxp from notifying me about this

    Thanks

  21. Severin says:

    SLxx.tmp – Common Language Runtime Debugging Services

    Hi. I think this is the same problem as reported by Dan above, but I haven’t been able to fix it yet.

    I looked at the .NET configuration workaround procedure but My_Computer_Zone looks different from the description. If I go under Properties then there’s a Permission Set tab, under which FullTrust is already set.

    Still doesn’t install. Help!

  22. J.C. – the best solution to get WinXP to stop notifying you about this hotfix is to figure out why it is failing to install and resolve that issue. The reason I say that is that you may not knowingly use the .NET Framework, but you may have some products installed that are built on top of the .NET Framework. Could you try to go to the download site for this hotfix and download it and try to run it directly? This will show more detailed error information. You will probably need this version of the hotfix – http://www.microsoft.com/downloads/details.aspx?FamilyID=8ec6fb8a-29eb-49cf-9dbc-1a0dc2273ff9&DisplayLang=en. However, depending on what version of the .NET Framework you have on your machine you might need a different hotfix – you can go to http://www.microsoft.com/downloads/results.aspx?freetext=security_patch&productID=C9C8FCFB-BFF3-40CA-B59D-216F6850000A&DisplayLang=en and choose what version of the hotfix to download.

    Then after downloading the hotfix you can run it by double-clicking it and it will probably give some kind of error. If you can let me know what the exact error is, we can try some additional troubleshooting steps.

  23. Severin – there are several different causes of the CLR Debugging Services error that you are seeing. Like for Dan, my first suggestion to you would be to check the troubleshooting doc I published a little while ago. You can find that at http://blogs.msdn.com/astebner/archive/2004/11/23/268934.aspx. If the suggestions there do not work, please contact me via email at aaronste (AT) microsoft (DOT) com and I can try to help further.

  24. SYLVAIN says:

    Problem with KB886903.

    I have a message:

    Process ID = 0xabc(2748)

    Thred ID = 0x634 (1588)

    Now i’m stuck and I can’t make any update on my windows… Can you help me…? Thanks.

  25. SYLVAIN says:

    Problem with KB886903.
    <br>
    <br>I have a message:
    <br>
    <br>Process ID = 0xabc(2748)
    <br>Thred ID = 0x634 (1588)
    <br>
    <br>Now i’m stuck and I can’t make any update on my windows… Can you help me…? Thanks.

  26. Hi Sylvain – can you try to do the following to download and extract the patch and try to install it directly? I am hoping that this will give you a more detailed error message:

    1. Locate the .NET Framework hotfix you want to install by going to the Microsoft download center and searching for the keyword security_patch and filtering based on the .NET product family.

    2. Download the correct version of the .NET Framework hotfix you want to install. Every .NET Framework hotfix ships with a separate version that will only install if you have a specific .NET Framework service pack installed. So you will need to download the hotfix that matches the service pack you have installed

    3. Extract the hotfix MSP package to a folder by running <name of hotfix>.exe /Xp:c:dotnetnetfxhotfix.msp

    4. Go to c:dotnet and right-click on netfxhotfix.msp and choose Apply

    If this gives an error can you try to use the instructions at the bottom of the article at http://blogs.msdn.com/astebner/archive/2004/11/23/268934.aspx to generate a verbose log file and then send that to me?

  27. I wrote an application late last year that is designed to clean up computers that have problems getting…

  28. James Lunt says:

    Thank you Aaron – your advice right at the top of the thread solved my problem I was having with Automatic Updates trying and failing to install the KB886903 security update for .NET Framework 1.1 SP1 on Windows XP Pro SP2.

    James

  29. GENANS@CHARTER,NET says:

    IS THE D**N THING [SERVICE PACK 1 {KB886903} NEEDED—-I KEEP GETTING A MESSAGE STATING THAT IT CANNOT BE DOWNLOADED—-EVERY DAY

  30. astebner says:

    Hi Genans – Can you please try to use the steps listed at http://blogs.msdn.com/astebner/archive/2005/10/11/479928.aspx to clean off and re-install the .NET Framework 1.1 and see if that will resolve this issue? The item you listed is Service Pack 1 for the .NET Framework 1.1 and it would definitely be good to install that if possible.

  31. justme says:

    I hope to be alive to see Microsoft going to the drain

    Do people have to suffer and guess what secrecy is beyond their reach in order to fix problems that MS created?

    Do people have to waste countless hours and risk their health just because MS?

    How did we get to this point, were we have to consider ourselves lucky because we can fix some of the countless probles MS created?

    M should be switch to B then we have BS

    I will use every opportunity in my reach to contribute tu put BS down

  32. astebner says:

    Hi Justme – I would like to try to help you resolve the problems that you have run into.  Can you please provide more details about the exact error you are seeing so I can try to narrow down the cause and determine a workaround/fix?

  33. Bob Land says:

    Why doesn’t MS just pull this piece of crap until they get a version that doesn’t require a rocket scientist?

  34. astebner says:

    Hi Bob – I’m sorry that you have been encountering problems installing this hotfix.  I cannot tell from your post whether or not you are still having problems.  If so, can you please try the steps listed at http://blogs.msdn.com/astebner/archive/2005/10/11/479928.aspx and see if they help resolve this issue on your system?

  35. Vijay says:

    I am facing an issue with installation of the .net framework patches (KB886903 and KB886906). I get the following error: SLxx.tmp – Common Language Runtime Debugging Services

    I referred your suggestions in the following links and have tried most of the troubleshooting steps informed. Yet, my problem is not solved.

    http://blogs.msdn.com/astebner/archive/2005/02/13/371967.aspx

    http://blogs.msdn.com/astebner/archive/2004/11/23/268934.aspx

    http://blogs.msdn.com/astebner/archive/2004/09/21/232653.aspx

    I had the same issue while I was trying to deploy the same two patches about a year back. I solved this issue at that moment by performing the steps in the following URL:

    http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/html/cpconenablingjit-attachdebugging.asp

    If I create the registry key HKEY_LOCAL_MACHINESoftwareMicrosoft.NETFrameworkDbgJITDebugLaunchSetting with value as 1, the patches got installed at that time.

    But now, even that is not solving this issue. I am getting this error inconsistently on my client machines.

    My workstation is a standard Windows XP Pro SP2 with Office 2003 SP1 configuration.

    I need to deploy these patches along with some other applications to my users ASAP and would greatly appreciate any inputs from you regarding this. Please let me know if you need any more information.

    Thanks in advance.

  36. astebner says:

    Hi Vijay – I would suggest trying the workaround described at http://blogs.msdn.com/astebner/archive/2005/10/11/479928.aspx and see if that solves this issue.

  37. jamshedd says:

    Hi Aaron,

    Firstly, thanks for the great work you’re doing here by posting information about problems with security updates.

    I received a question about a problem someone’s having installing the security update describe by KB 886903, and was pointed to your post. This got me reading 😉

    You’ve listed the steps necessary to find and download update, the posed the question whether this can be done in an easier way.

    Here’s how I actually did it :

    1. Get the KB number from Windows Update just like you did – this is KB886903.

    2. In my IE search bar (I’m using IE7 RC1 and live search), I entered "KB886903" (without quotes). Hit search.

    3. The first result is a direct link to the download page and the second link takes me to the bulletin for IT professionals. Both are exactly what I wanted. So I went ahead and downloaded the update from the download page, and then looked up the command line switches in case I want to use any.

    Note: You can simply double-click the package to apply the patch, no need to extract it’s contents first unless you have a specific reason for that.

    Now I understand that not everybody uses Live Search and search results may vary from one update to another. Assuming I did not get a quick hit for my KB number in my first search, I would do the following:

    1. Go to http://support.microsoft.com and enter the KB number 886903. Click Search.

    2. The search results will show me to the bulletin page: http://www.microsoft.com/technet/security/bulletin/ms05-004.mspx . I open up this page (the bulletin)

    3. Under Affected Software, I click on the version of .Net I want to patch (in my case this is 1.1). Right there I see listed every patch for this bulletin organized by the different operating systems.

    4. I pick my OS (Windows XP in my case) and that takes me to the download page for the patch for Windows XP.

    Overall I feel there is never any need to go to the download center and start searching for an update. In general no download is ever published without a corresponding KB page and a bulletin in case of security updates. The bulletin will *always* directly take you to the correct download link.

    Thanks,

    Jamshed

    Program Manager, Developer Division Sustained Engineering Team

  38. i32123 says:

    A recent Windows Update failure (Error number 0x80190193)

    encountered when applying patch kb886903 to .NET 1.1 SP1

    was completely resolved and eliminated by temporarily

    shutting down an old version of the ZoneAlarm firewall.

    (A dozen other, more complicated fixes had no effect.)

    YMMV

    HTH

  39. Irma says:

    i was wanting to know what this means…Process ID= 0x1718 (5912), Thread ID= 0xac4 (2756)….when i get on facebook and i try playing a game or upload vidoes on it it says that the internet stopped working and then that appears…

  40. astebner says:

    Hi Irma – Troubleshooting crashes in web browsers is not in my areas of expertise.  You may want to try to upgrade to a new version of your browser or try a different browser to see if that helps in this scenario.