Sign in
 
HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums
Windows Server TechCenter >
> 
> 
Error on a bunch of Windows 2003 servers. Not showing apparent issue but needs to be explained.

Answered Error on a bunch of Windows 2003 servers. Not showing apparent issue but needs to be explained.

  • Thursday, February 07, 2013 8:47 PM
     
     
    Sign In to Vote
    0

    Recently a large portion of our Windows 2003 servers are all throwing an error on their screen and the following corresponding event in their logs:

    Faulting application wmiprvse.exe, version 5.2.3790.4455, faulting module msvcr90.dll, version 9.0.30729.6161, fault address 0x00056b1d.

    All of them are doing it around the same time.   I thought originally this was because of SCCM, however nothing on the server or via the SCCM console is scheduled to happen around the given time this occurs (9:21PM)

    I know it's clearly a WMI crash.. But not sure how to tell what is causing the crash, because msvcr90.dll is part of the Microsoft Visual C runtime and a lot of things use that.  

     

All Replies

  • Thursday, February 07, 2013 8:58 PM
     
     
    Sign In to Vote
    0

    To find the root cause of the problem you will have to create a dump file using the procdump from sysinternals and then you will need to use the windbg and analyze the dump

    http://technet.microsoft.com/en-gb/sysinternals/dd996900.aspx

    http://msdn.microsoft.com/en-us/windows/hardware/gg463009.aspx

    http://www.arabitpro.com

     
  • Thursday, February 07, 2013 9:00 PM
     
     
    Sign In to Vote
    0

    To find the root cause of the problem you will have to create a dump file using the procdump from sysinternals and then you will need to use the windbg and analyze the dump

    http://technet.microsoft.com/en-gb/sysinternals/dd996900.aspx

    http://msdn.microsoft.com/en-us/windows/hardware/gg463009.aspx

    http://www.arabitpro.com


    Can I take the procdump now or do I need to wait until it happens again?
     
  • Thursday, February 07, 2013 9:04 PM
     
     
    Sign In to Vote
    0
    you will have to run the procdump and wait untill the crash to generate the dump

    http://www.arabitpro.com

     
  • Thursday, February 14, 2013 7:01 PM
     
     Answered
    Sign In to Vote
    2

    We noticed this started happening on our 2003 servers after the SP1 client was installed.  I have the EXACT same error as you.  It happens during the hardware inventory process when it queries for recently used applications.  I can even run the query in WBEM test and cause the fault.

    I have opened an issue with the CM12 team on this.

    https://connect.microsoft.com/ConfigurationManagervnext/feedback/details/779238/sp1-client-causes-wmi-application-fault-on-windows-server-2003

    • Proposed As Answer by RichardG123 Thursday, February 14, 2013 7:01 PM
    • Marked As Answer by John Owens - BDC Monday, February 18, 2013 6:10 PM
    •  
     
  • Friday, February 15, 2013 12:29 PM
     
     
    Sign In to Vote
    0

    Hi Richard,

    thanks for the hint. We are monitoring the same behaviour on our systems.

     
  • Friday, February 22, 2013 5:17 PM
     
     
    Sign In to Vote
    0
    I am also experiencing the same issue after upgrading SCCM 2012 clients from RTM to SP1. It is limited to Server 2003. The issue is not seen on our WS08/08R2 servers. I've opened up a support case on this issue and have been waiting for over a week to have my case assigned. My colleague has opened another case with another issue and he's also getting very slow response from support.  I think the SCCM support team has been busy supporting SP1 issues here and there.
     
  • Wednesday, March 06, 2013 4:13 AM
     
     
    Sign In to Vote
    0
    For the record, I'm also seeing this issue with SCCM 2012 SP1 and Windows Server 2003.
     
  • Friday, March 08, 2013 5:18 PM
     
     
    Sign In to Vote
    0
    We are seeing the same behavior on all of our Server 2003 SP2 machines.  It began exactly the day we upgraded the SCCM 2012 client agent to SP1.  It doesn't appear to actually do any harm, although the mini-dump files do build up.  Has anyone gotten any resolution on this?
     
  • Wednesday, March 13, 2013 3:40 PM
     
     
    Sign In to Vote
    0

    Hello,
    I'm seeing this post was answered, but I'm experiencing same error on Windows Server 2003 after installed SCCM Client with SP1.

    Do you get some information on how to resolve it ? It seems a common problem.

    Bye,
    Luca

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

     
  • Thursday, March 14, 2013 3:17 PM
     
     
    Sign In to Vote
    0
    Same issue here. The migration from SCCM 2007 to SCCM 2012 SP1 is causing many of our Server 2003 SP2 machines to throw WMI errors. Rebuilding the WMI repository has no affect. Unable to access the link in the post marked as answer. Any update on this?
     
  • Thursday, March 14, 2013 9:54 PM
     
     Proposed
    Sign In to Vote
    0

    Hi, folks. I'm on the Configuration Manager product group. This thread was brought to my attention from one of our PFEs so I wanted to take a moment to respond to it.

    This crash is an issue caused by some combinations of certain security software packages and the Configuration Manager 2012 SP1 client. It only affects Windows XP and Windows Server 2003. We have fixed this issue in the upcoming ConfigMgr 2012 SP1 CU1.

    Thanks to all of you that reported this issue.


     
  • Thursday, March 14, 2013 9:56 PM
     
     
    Sign In to Vote
    0
    What's the release date of the CU?
    • Edited by rpxn Thursday, March 14, 2013 9:56 PM
    •  
     
  • Friday, March 15, 2013 3:08 PM
     
     
    Sign In to Vote
    0
    When is it going to be released?
     
  • Friday, March 22, 2013 3:15 PM
     
     
    Sign In to Vote
    0

    My customer has also experienced this issue since the upgrade to SP1.  When is the projected release day of CU1.

     
  • Friday, March 22, 2013 3:26 PM
     
     
    Sign In to Vote
    0

    Hello guys,
    even if Adam announced the problem will be solved on CU1 for SCCM with SP1, I opened a support ticket at Microsoft.

    I'll give you feedback once I get some feedback.

    Regards,
    Luca

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights

    • Edited by Luca Fabbri Friday, March 22, 2013 3:38 PM
    •  
     
  • Friday, March 22, 2013 3:29 PM
     
     
    Sign In to Vote
    1

    I just wanted to mention that we DID workaround the issue by removing the "Recently Used" applications from the Hardware Inventory cycle.

     
  • Sunday, March 24, 2013 8:17 PM
     
     Proposed
    Sign In to Vote
    1

    It's been released (quietly it appears):

    http://support.microsoft.com/kb/2817245/en-us

    • Proposed As Answer by rpxn Sunday, March 24, 2013 8:18 PM
    •  
     
  • Sunday, March 24, 2013 9:29 PM
     
     
    Sign In to Vote
    0

    Thank you very much rpxn.

    Regards,
    Luca

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

     
  • Sunday, March 24, 2013 9:33 PM
     
     
    Sign In to Vote
    0

    Hello RichardG123,
    in my case, I don't have hardware inventory selected, however I get same WMI error.

    Cumulative Update 1 for System Center 2012 with SP1 has been released (rpxn user post).

    Bye,
    Luca

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.


    • Edited by Luca Fabbri Monday, March 25, 2013 10:33 AM
    •  
     
  • Monday, March 25, 2013 5:58 PM
     
     
    Sign In to Vote
    0

    CU1 was just released. You can download it from: http://support.microsoft.com/kb/2817245

    Among its fixes are:

    The hardware inventory on a computer that is running a 32-bit version of Windows Server 2003 R2 may cause the Wmiprvse.exe process to exit unexpectedly.  Additionally, when you view the results of the fault, the details of the fault resemble the following:

    Faulting application wmiprvse.exe, version 5.2.3790.4455, faulting module msvcr90.dll, version 9.0.30729.6161, fault address 0x00056b1d