Question : ISAPI Filter 'C:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_filter.dll' could not be loaded due to a configuration problem

I don't exactly know what is causing this but, I added SQL Server 2008 today to my 2008 R2 server and now I'm getting these events every few minutes.  How do I solve this

Log Name:      Application
Source:        Microsoft-Windows-IIS-W3SVC-WP
Date:          7/6/2010 6:09:12 PM
Event ID:      2268
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      SPCALA144.LASPCA.LOCAL
Description:
Could not load all ISAPI filters for site 'DEFAULT WEB SITE'.  Therefore site startup aborted.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-IIS-W3SVC-WP" Guid="{670080D9-742A-4187-8D16-41143D1290BD}" EventSourceName="W3SVC-WP" />
    <EventID Qualifiers="49152">2268</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2010-07-07T01:09:12.000000000Z" />
    <EventRecordID>6622</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>SPCALA144.LASPCA.LOCAL</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name="SiteName">DEFAULT WEB SITE</Data>
    <Binary>C1000000</Binary>
  </EventData>
</Event>

Answer : ISAPI Filter 'C:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_filter.dll' could not be loaded due to a configuration problem

Hey just wanted to thank you for all your help.

In the end I called up Microsoft Support as this issue was critical and needed to be resolved quickly as I would have had 75 angry laptop users.

Ok so the problem was: As the 75 laptops had been imaged exactly the same, it meant the CMID of each laptop was exactly the same. When the clients sent requests to the KMS server the count would not increase.

In order to resolve it: you have to run the slgmr -rearm command on every single laptop and then slmgr -ato to activate it. Once more than 25 were activated, all started activating so everything was fine.