none
Constant error on client 2008 Servers "Module was unable to connect to namespace 'Win32_LogicalDisk'"

    Question

  • Thanks for reading.

    I've inherited a SCOM 2012 environment and I'm trying to resolve some client errors on 2008 servers.

    This error is occurring on many 2008 R2 servers.

    Log Name:      Operations Manager
    Source:        Health Service Modules
    Date:          14/11/2013 8:51:44 AM
    Event ID:      10401
    Task Category: None
    Level:         Warning
    Keywords:      Classic
    User:          N/A
    Computer:      MyServer.InOurDomain.com
    Description:
    Module was unable to connect to namespace 'Win32_LogicalDisk'

     This has happened 285 times since this instance was loaded.

     HRESULT: 0x8004100e Details: Invalid namespace

    One or more workflows were affected by this. 

    Workflow name: UIGeneratedMonitor463cdab8ccb4471985ceb4a27c1567a6
    Instance name: MyServer.InOurDomain.com
    Instance ID: {F438A6BD-42FB-3299-9D70-0D76303343D1}
    Management group: SCMOPS2012

    I've looked for a bad custom rule but cannot seem to find any. I am a novice with SCOM.

    Geoff.

    Wednesday, November 13, 2013 11:24 PM

Answers

  • Hi Niki,

    Thankyou for your reply. I did look at the WMI and all appeared normal to me.

    But I am closing this enquiry as I've found another person in our org who is investigating too. And it is not effective to have two people looking at the same issue.

    Thankyou to all who attempted to help.

    Regards,

    Geoff.

    Wednesday, November 27, 2013 11:50 PM

All replies

  • Geoff,

    Is this happening with all the 2008 R2 servers that are monitored? Can you check to see if you have the latest management pack for the Windows Server 2008? I believed the latest was released on 10/18/2013 - Update release, version 6.0.7061.0

    Kind Regards,

    Tom


    Kind Regards, Tom Ziegler http://www.sccmguy.com | Twitter @Tom_Ziegler

    Thursday, November 14, 2013 4:04 AM
  • Hi Tom, I appreciate your help,

    I have fully patched with the exception of a very recent patch. 11/11/2013. During my attempts to resolve, I did download and install a rollup 3, KB2852565.

    I have never downloaded a management pack. But since reading your response I download and installed the Oct server pack. To ensure it was loaded, I rebooted SCOM server as well. 

    However, looking at the clients, I can see the issues remains the same on all that I looked at.

    Regards,

    Geoff

    Thursday, November 14, 2013 5:23 AM
  • Hi, try to connect to that namespace 'Win32_LogicalDisk' manually from that computer with the same action account.
    Thursday, November 14, 2013 6:53 AM
  • Hi I would try if you can connect to this WMI Namespace at all. Sometimes WMI gets corrupted and you Need to fix this thing especially on Windows 2003/2008 Systems. Check if you can connect to this Namespace using WMIExplorer http://www.ks-soft.net/hostmon.eng/wmi/ or WBEMTest https://www.google.ch/#q=WBEMTest . See if you get a connection. Check also this here http://technet.microsoft.com/en-us/library/ff404265.aspx .If you Need to rebuild the WMI check this http://blogs.technet.com/b/askperf/archive/2009/04/13/wmi-rebuilding-the-wmi-repository.aspx . Cheers, Stefan

    Blog: http://blog.scomfaq.ch

    Thursday, November 14, 2013 6:58 AM
  • Hi Alexis,

    I did use a simple Vbs to remotely connect to a problem client server through WMI and it worked without errors.

    Geoff.


    Note I did specifically connect to Win32_LogicalDisk class.
    • Edited by to_Geoff Friday, November 15, 2013 2:48 AM Clarify
    Friday, November 15, 2013 1:18 AM
  • Hi Stefan,

    As tested above, a simple vbs script was able to connect remotely to one of the problem servers. I did run the WBEMtest.exe and it did not indicate any errors. Though I have to admit I am not sure if I used it correctly.

    Geoff.

    Friday, November 15, 2013 1:20 AM
  • All,

    Another thought I had, was to track down the entity (script??) that the SCOM runs on the remote servers.

    However, I have no idea how to find this on SCOM. I did try to use the below error fields from the clients to track a script, but I was not able to find them. However, I may be looking in the wrong places.

    Workflow name: UIGeneratedMonitor463cdab8ccb4471985ceb4a27c1567a6
    Instance ID: {F438A6BD-42FB-3299-9D70-0D76303343D1} .   Thoughts?                                   

    Friday, November 15, 2013 3:21 AM
  • Hi,

    I suggest you rebuilt WMI Repository for a test. Here is the detail step.

    http://blogs.technet.com/b/askperf/archive/2009/04/13/wmi-rebuilding-the-wmi-repository.aspx


    Niki Han
    TechNet Community Support

    Saturday, November 16, 2013 4:33 PM
    Moderator
  • Hi Niki,

    I have been in the process of going through the steps in your link. I will let you know the results. in an hour or two.

    Geoff.

    Monday, November 18, 2013 1:01 AM
  • Hi Niki,

    I have gone through the proceedures described. Though there were errors in the results, it did not seem to be an overall failure of WMI.  I corrected many of the errors but the problem remains. In addition I tried removing and reinstalling the agent, but the error returned as soon as I re-installed the agent.

    Any further thoughts would be appreciated.

    Monday, November 18, 2013 6:14 AM
  • The namespace 'Win32_LogicalDisk' may be invalid. Please open the attribute discovery -> go to WMI Configuration and the namespace should be root\cimv2.


    Niki Han

    TechNet Community Support

    Monday, November 25, 2013 7:54 AM
    Moderator
  • Hi Niki,

    Thankyou for your reply. I did look at the WMI and all appeared normal to me.

    But I am closing this enquiry as I've found another person in our org who is investigating too. And it is not effective to have two people looking at the same issue.

    Thankyou to all who attempted to help.

    Regards,

    Geoff.

    Wednesday, November 27, 2013 11:50 PM