locked
WCF service errors after installing WindowsXP updates

    Question

  • Greetings, 

    today before I start working on my application I updated my WinXP. After all updates have been installed my WCF service stop working. There is a following error when I try to open service.svc file in the browser:

     

    Configuration Error
    
    Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately. 
    
    Parser Error Message: An error occurred creating the configuration section handler for system.serviceModel/bindings: Could not load type 'System.Security.Authentication.ExtendedProtection.Configuration.ExtendedProtectionPolicyElement' from assembly 'System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'.
    
    Source Error: 
    
    
    Line 131:		</behaviors>
    Line 132:
    Line 133:		<bindings>
    Line 134:			<wsHttpBinding>
    Line 135:				<binding name="MyWSHttpBinding" maxReceivedMessageSize="2147483647">
    
    The colleague of my tried to run the same service before update and it works fine. He has the same problem after installing updates. Can someone please help me?

     

    Wednesday, June 09, 2010 8:44 AM

Answers

  • It seems that if you remove KB976769v2 update, it fixes the problem.   You can find it under Add/Remove Programs under "Microsoft .NET Framework 3.0 Service Pack 2".  Don't forget to check "Show Updates" at the top first.

    After removing it, Automatic Updates (if enabled) may ask you to install KB979909 and/or KB982168.  I'd recommend ignoring these for now until a hotpatch or fix is available, especially as this is just a temporary fix.

    Does anyone have an official Connect or other item from MSFT that recognizes this bug?   We need something official for our infrastructure team to recognize and track...

    • Proposed as answer by TLD49 Thursday, June 10, 2010 10:23 PM
    • Marked as answer by niao Friday, June 11, 2010 9:58 AM
    Thursday, June 10, 2010 10:23 PM
  • Greetings, Cedric from SO contacted with Microsoft. Here's the Cedric answer:

    so far : the problem seems to come indeed from the update KB982168 and only on 2003 servers. Microsoft support suspects a bug in the HttpTransportSecurity constructor that tries to instanciate a ExtendedProtectionPolicy object, but this class does not exists in system.dll on a 2003 server (or XP machines) (you can check with reflector). And it is indeed present on the DLL on a 2008 or Vista and above. If the problem is confirmed, i think there will be a hot fix released very soon. MeanWhile it is recommanded to not install the update. I'll keep you informed

    • Marked as answer by niao Thursday, June 10, 2010 11:23 AM
    Thursday, June 10, 2010 10:23 AM

All replies

  • Same problem here.  Please help.
    Wednesday, June 09, 2010 5:47 PM
  • Greetings, Cedric from SO contacted with Microsoft. Here's the Cedric answer:

    so far : the problem seems to come indeed from the update KB982168 and only on 2003 servers. Microsoft support suspects a bug in the HttpTransportSecurity constructor that tries to instanciate a ExtendedProtectionPolicy object, but this class does not exists in system.dll on a 2003 server (or XP machines) (you can check with reflector). And it is indeed present on the DLL on a 2008 or Vista and above. If the problem is confirmed, i think there will be a hot fix released very soon. MeanWhile it is recommanded to not install the update. I'll keep you informed

    • Marked as answer by niao Thursday, June 10, 2010 11:23 AM
    Thursday, June 10, 2010 10:23 AM
  • Same problem here, all the developers are unable to work!! No point recommending us not to install the updates as these must be updates without a machine reset :O(

    I cannot believe this was allowed through!!

    Thursday, June 10, 2010 11:58 AM
  • I've heard that reinstalling .net framework (without machine restart) helps.
    Thursday, June 10, 2010 12:58 PM
  • It seems that if you remove KB976769v2 update, it fixes the problem.   You can find it under Add/Remove Programs under "Microsoft .NET Framework 3.0 Service Pack 2".  Don't forget to check "Show Updates" at the top first.

    After removing it, Automatic Updates (if enabled) may ask you to install KB979909 and/or KB982168.  I'd recommend ignoring these for now until a hotpatch or fix is available, especially as this is just a temporary fix.

    Does anyone have an official Connect or other item from MSFT that recognizes this bug?   We need something official for our infrastructure team to recognize and track...

    • Proposed as answer by TLD49 Thursday, June 10, 2010 10:23 PM
    • Marked as answer by niao Friday, June 11, 2010 9:58 AM
    Thursday, June 10, 2010 10:23 PM
  • Hello,

    We have exactly the same problem on our environment, we have fixed it (Remove KB976769v2 from previous post).

    Thank you for your forum that has help us to solve this issue.

     

     

    Friday, June 11, 2010 9:29 AM
  • Niao - thanks! I removed this update - no restart required - presumably because it only impacts the framework, and my WCF services are working again.

    This is a major issue - being new to this forum how do we know if MS are aware and actually dealing with it??


    Thanks
    Friday, June 11, 2010 12:17 PM
  • Thanks dude, removing KB976769v2 fixed the problem.  

    It's not fun when web services start failing after a 'simple' windows update.

    Friday, June 11, 2010 5:44 PM
  • It seems that if you remove KB976769v2 update, it fixes the problem.   You can find it under Add/Remove Programs under "Microsoft .NET Framework 3.0 Service Pack 2".  Don't forget to check "Show Updates" at the top first.

    After removing it, Automatic Updates (if enabled) may ask you to install KB979909 and/or KB982168.  I'd recommend ignoring these for now until a hotpatch or fix is available, especially as this is just a temporary fix.

    Does anyone have an official Connect or other item from MSFT that recognizes this bug?   We need something official for our infrastructure team to recognize and track...


    Thank you for posting this - we've had same exact issue this morning with these patches that took down production environment.

    Luckily for this post we've been able to quickly recover from it.

    Wednesday, June 16, 2010 2:15 PM
  • We caught this on our QA servers before rolling the same patches to production, took me a few hours till I found this post, hope MS catches up with a bug Fix quickly, as keeping the patch level to the latest is mandatory in our environment.
    Thursday, June 17, 2010 10:58 AM
  • Microsoft Connect has an official entry now:

    http://connect.microsoft.com/VisualStudio/feedback/details/567497/system-security-authentication-extendedprotection-configuration-extendedprotectionpolicyelement-doesnt-exist

    It's still a workaround.  We're planning to test their temporary patch later this week, assuming MSFT does not have a more permanent fix before then.

     

     

    Monday, June 21, 2010 2:30 PM
  • The official KB article for this issue has been posted at the following location: http://support.microsoft.com/kb/2262911 .

     

    If you are still hitting this issue, please follow the steps listed in the KB article which will resolve the installation issue and also install Updates 982167 or 982168 (selected depending on the operating system installed on the machine).

     

    The patch provided in the KB article has been validated to resolve the installation issue as well as safe for production environments. We will also be publishing in the KB article a Fix-It patch to seamlessly resolve this issue without needing to go through the workaround steps. Given that we have identified the root cause of this issue, all previous hotfixes which cause the installation failure will be updated appropriately.

     

    It is important that WCF applications are unblocked and able to successfully install Windows Update KB # 982167 and/or 982168 on all machines. 

     

    Sorry for this inconvenience.

     

    Thanks,

     

    Erica

    Microsoft Program Manager


    Erica Mohler - MSFT
    Thursday, July 01, 2010 2:19 AM
  • Windows update is constantly asking to install update 

    MICROSOFT .NET FRAMEWORK 1.1 SP1 ON WINDOWS XP KB2416447 and it fails everytime is there anyway around this? sorry if this this the wrong place to put this question. thanks jhona

    Thursday, February 23, 2012 4:25 PM