• Sign In
 
  • MSDN Blogs
  • Microsoft Blog Images
  • More ...
Common Tasks
  • Blog Home
  • Email Blog Author
  • RSS for comments
  • RSS for posts
Search
  • Advanced search options...
Tags
  • .NET Framewor
  • .NET Framework
  • Ajax/Javascript
  • ASP.NET
  • CLR
  • Cool stuff
  • DataAccess
  • Debugging/Windbg
  • Hotfix/Service Pack
  • IDEVDataCollector
  • IIS
  • Internet Explorer
  • Italian techs
  • LogParser
  • OT
  • Personal
  • Productivity
  • Random
  • Scripting/ASP
  • Security
  • Technology
  • Tools
  • Troubleshooting
  • Vista/Longhorn
  • Visual Studio
Archives
Archives
  • November 2010 (1)
  • October 2010 (1)
  • July 2010 (2)
  • April 2010 (1)
  • March 2010 (2)
  • February 2010 (2)
  • January 2010 (1)
  • October 2009 (2)
  • September 2009 (2)
  • August 2009 (1)
  • July 2009 (5)
  • June 2009 (1)
  • May 2009 (1)
  • April 2009 (3)
  • March 2009 (3)
  • February 2009 (5)
  • January 2009 (3)
  • December 2008 (5)
  • November 2008 (3)
  • October 2008 (2)
  • September 2008 (3)
  • August 2008 (3)
  • July 2008 (3)
  • June 2008 (5)
  • May 2008 (4)
  • April 2008 (8)
  • March 2008 (4)
  • February 2008 (5)
  • January 2008 (2)
  • December 2007 (4)
  • November 2007 (6)
  • October 2007 (6)
  • September 2007 (8)
  • August 2007 (6)
  • July 2007 (7)
  • June 2007 (10)
  • May 2007 (9)
  • April 2007 (12)
  • March 2007 (8)
  • February 2007 (5)
  • January 2007 (3)
  • December 2006 (1)
  • November 2006 (4)
  • October 2006 (2)
  • September 2006 (9)
  • August 2006 (2)
  • July 2006 (1)

WMI warnings 35 and 40 with ASP.NET

MSDN Blogs > Never doubt thy debugger > WMI warnings 35 and 40 with ASP.NET

WMI warnings 35 and 40 with ASP.NET

Carlo Cardella
4 Jun 2008 10:58 AM
  • Comments 11

Over the past couple of weeks I got to almost identical cases where the customer had the event log on their servers “spammed” by the following messages:

Event Type:      Warning
Event Source:   WinMgmt
Event Category:           None
Event ID:           40
Date:                <date>
Time:                <time>
User:                N/A
Computer:        <computername>
Description:
WMI ADAP was unable to create the object Win32_PerfRawData_ASPNET_2050727_ASPNETAppsv2050727 for Performance Library ASP.NET_2.0.50727 because error 0x80041001 was returned

Event Type:      Warning
Event Source:   WinMgmt
Event Category:           None
Event ID:           35
Date:                <date>
Time:                <time>
User:                N/A
Computer:        <computername>
Description:
WMI ADAP was unable to load the ASP.NET_2.0.50727 performance library because it returned invalid data: 0x0

Article How to troubleshoot WinMgmt-based performance counter errors does not help in this case (we do not have Event ID 37, 41 or 61).

The fix for this problem was scheduled to be added in .NET 3.5 SP1 (as also explained in this post) then we decided to ship a standalone hotfix too: the KB article is not yet available but you can request the fix (which by the way resolved both my cases) to CSS as usual, asking for 951683.

 

 

Carlo

Quote of the day:
Always do right. This will gratify some people and astonish the rest. - Mark Twain
  • 11 Comments
ASP.NET, Hotfix/Service Pack
Leave a Comment
  • Please add 4 and 5 and type the answer here:
  • Post
Comments
  • Pieter
    4 Jun 2008 11:15 AM

    Thanks for commenting my blog about this issue, ill adjust the post and add an extra link to this page.

    Ciao!

  • &raquo; Windows 2003 eventlog gives you weird errors (Source: WinMgmt)
    4 Jun 2008 11:18 AM

    PingBack from http://pieter.wigleven.com/it/archives/62

  • SCAdmin
    11 Jun 2008 1:32 PM

    Thank you!  The only way I've been able to fix this error until now was to disable the counter using excrtlst.exe (Extensible Counter List).  Thanks for giving the hotfix number.

  • Mike
    2 Jul 2008 12:46 PM

    I seem to have just this error.  I had installed MOSS 2007 on a WinSer 2003 R2 box, was running the Sharepoint Configuration and Technologies Wizard when it shut down and I found these errors.

    I'm just an end-user, so how do I get this unpublished hotfix?

  • Carlo Cardella
    3 Jul 2008 3:16 AM

    Mike, as long as you have purchased one of Microsoft products you can always give CSS a call to have support or ask for an hotfix... have a look at this post (http://blogs.msdn.com/raffael/archive/2008/05/14/get-what-you-paid-for.aspx) from my colleague Raffaele for further info :-)

    HTH

  • Mike
    7 Jul 2008 12:00 PM

    I don't have SA, so can't contact CSS without paying first.  Isn't there SOME way to get this hotfix? (I saw that .NET 3.5 SP1 Beta is out, but I am hesitant to get it until it's in final form.)

  • Carlo Cardella
    7 Jul 2008 12:14 PM

    Mike, you can contact CSS even if you have purchased a Microsoft product in a store (say the Visual Studio box, for example), or if you have a valid MSDN subscription etc...

    I'm not sure if you can open a "grace" call directly, I think the screener (the person whom will first take your call) will have to check for a valid Product ID anyway, but you can give it a try if you wish.

    The call will be closed as "Non decrement" anyway, so even if you'll need to purchase a PPI (Pay Per Incident) you'll get a refund (or even better your credit card will not be charged because the transaction will be cancelled), but I understand that might not be the same "feeling" as having a free incident.

    I just had a look on Code Gallery (http://code.msdn.microsoft.com/Project/ProjectDirectory.aspx?TagName=Hotfix) where it's possible to find and download some fixes without involving CSS, but I've not ben able to find this one, sorry...

    You can give SP1 a try but you're right, that is still a beta version so install it with care if that is a sensitive/production machine.

  • Mike
    7 Jul 2008 2:41 PM

    Thanks for the additional information.

  • Mike
    7 Jul 2008 4:57 PM

    Called the toll-free number and was told that they couldn't give me the hotfix.  Since it didn't have a corresponding KB article, they consider it unsupported and so won't give it out.

    Guess I'll have to wait.

  • CC
    10 Jul 2008 4:07 PM

    I was able to request this fix from MS, with a bit of hesitation...

    I have the hot fix now and will be installing it this evening.

    if my server blows up, I will let you know

  • Mark Yannone
    26 Jul 2008 2:21 PM

    Any solution yet?

    mjyannone@aol.com

Page 1 of 1 (11 items)
  • © 2012 Microsoft Corporation.
  • Terms of Use
  • Trademarks
  • Privacy Statement
  • Report Abuse
  • 5.6.131.143