Event ID 9097 WMI Error.. - Microsoft Exchange

This is a discussion on Event ID 9097 WMI Error.. - Microsoft Exchange ; Has anyone dealt with this one before?.. "The MAD Monitoring thread was unable to connect to WMI, error '0x8004100e'." I tried correcting it by following the steps in TechNet article Q288590, however the error still persists in the application log ...

+ Reply to Thread
Page 1 of 4 1 2 3 ... LastLast
Results 1 to 10 of 31

Event ID 9097 WMI Error..

  1. Default Event ID 9097 WMI Error..

    Has anyone dealt with this one before?.. "The MAD Monitoring thread was
    unable to connect to WMI, error '0x8004100e'." I tried correcting it by
    following the steps in TechNet article Q288590, however the error still
    persists in the application log on my Exchange server appearing every five
    minutes or so. I can't monitor the system through "Monitoring and Status"
    in the Exchange Admin now. Everything shows up as "Unknown".

    Server is Exchange2K (SP3) on Win2K (SP3).

    Thanks!


    (*Apologies if you believe i'm cross-posting. I tried to only choose
    relevant newsgroups.)



  2. Default Re: Event ID 9097 WMI Error..

    From the verbose logs of WinMgmt you should have an idea of the namespace
    for which the connectio is being attempted.
    If you really don't have that namespace, as you can verify easily with
    wbemtest.exe,
    then you should try to fing-out if there is a MOF file that contains
    the definition of that namesapce.
    If you re-compile that MOF file, does the situation improve ?

    --
    This posting is provided "AS IS" with no warranties, and confers no rights.
    Use of any included script samples are subject to the terms specified at
    http://www.microsoft.com/info/cpyright.htm


    "jim" <jim@NOSPAM.com> wrote in message
    news:empvBXnQEHA.2716@tk2msftngp13.phx.gbl...
    > Has anyone dealt with this one before?.. "The MAD Monitoring thread was
    > unable to connect to WMI, error '0x8004100e'." I tried correcting it by
    > following the steps in TechNet article Q288590, however the error still
    > persists in the application log on my Exchange server appearing every five
    > minutes or so. I can't monitor the system through "Monitoring and Status"
    > in the Exchange Admin now. Everything shows up as "Unknown".
    >
    > Server is Exchange2K (SP3) on Win2K (SP3).
    >
    > Thanks!
    >
    >
    > (*Apologies if you believe i'm cross-posting. I tried to only choose
    > relevant newsgroups.)
    >
    >




  3. Default Re: Event ID 9097 WMI Error..

    From the verbose logs of WinMgmt you should have an idea of the namespace
    for which the connectio is being attempted.
    If you really don't have that namespace, as you can verify easily with
    wbemtest.exe,
    then you should try to fing-out if there is a MOF file that contains
    the definition of that namesapce.
    If you re-compile that MOF file, does the situation improve ?

    --
    This posting is provided "AS IS" with no warranties, and confers no rights.
    Use of any included script samples are subject to the terms specified at
    http://www.microsoft.com/info/cpyright.htm


    "jim" <jim@NOSPAM.com> wrote in message
    news:empvBXnQEHA.2716@tk2msftngp13.phx.gbl...
    > Has anyone dealt with this one before?.. "The MAD Monitoring thread was
    > unable to connect to WMI, error '0x8004100e'." I tried correcting it by
    > following the steps in TechNet article Q288590, however the error still
    > persists in the application log on my Exchange server appearing every five
    > minutes or so. I can't monitor the system through "Monitoring and Status"
    > in the Exchange Admin now. Everything shows up as "Unknown".
    >
    > Server is Exchange2K (SP3) on Win2K (SP3).
    >
    > Thanks!
    >
    >
    > (*Apologies if you believe i'm cross-posting. I tried to only choose
    > relevant newsgroups.)
    >
    >




  4. Default Re: Event ID 9097 WMI Error..

    You're going way beyond what i know how to do. How do i recompile an MOF
    file? I just want to clear these errors and start monitoring my remote
    Exchange server again. Any thoughts?

    (And remember that i've already tried the steps in Q288590)

    "Ivan Brugiolo [MSFT]" <ivanbrug@online.microsoft.com> wrote in message
    news:OU4EPxpQEHA.3748@TK2MSFTNGP09.phx.gbl...
    > From the verbose logs of WinMgmt you should have an idea of the namespace
    > for which the connectio is being attempted.
    > If you really don't have that namespace, as you can verify easily with
    > wbemtest.exe,
    > then you should try to fing-out if there is a MOF file that contains
    > the definition of that namesapce.
    > If you re-compile that MOF file, does the situation improve ?
    >
    > --
    > This posting is provided "AS IS" with no warranties, and confers no

    rights.
    > Use of any included script samples are subject to the terms specified at
    > http://www.microsoft.com/info/cpyright.htm
    >
    >
    > "jim" <jim@NOSPAM.com> wrote in message
    > news:empvBXnQEHA.2716@tk2msftngp13.phx.gbl...
    > > Has anyone dealt with this one before?.. "The MAD Monitoring thread was
    > > unable to connect to WMI, error '0x8004100e'." I tried correcting it by
    > > following the steps in TechNet article Q288590, however the error still
    > > persists in the application log on my Exchange server appearing every

    five
    > > minutes or so. I can't monitor the system through "Monitoring and

    Status"
    > > in the Exchange Admin now. Everything shows up as "Unknown".
    > >
    > > Server is Exchange2K (SP3) on Win2K (SP3).
    > >
    > > Thanks!
    > >
    > >
    > > (*Apologies if you believe i'm cross-posting. I tried to only choose
    > > relevant newsgroups.)
    > >
    > >

    >
    >




  5. Default Re: Event ID 9097 WMI Error..

    You're going way beyond what i know how to do. How do i recompile an MOF
    file? I just want to clear these errors and start monitoring my remote
    Exchange server again. Any thoughts?

    (And remember that i've already tried the steps in Q288590)

    "Ivan Brugiolo [MSFT]" <ivanbrug@online.microsoft.com> wrote in message
    news:OU4EPxpQEHA.3748@TK2MSFTNGP09.phx.gbl...
    > From the verbose logs of WinMgmt you should have an idea of the namespace
    > for which the connectio is being attempted.
    > If you really don't have that namespace, as you can verify easily with
    > wbemtest.exe,
    > then you should try to fing-out if there is a MOF file that contains
    > the definition of that namesapce.
    > If you re-compile that MOF file, does the situation improve ?
    >
    > --
    > This posting is provided "AS IS" with no warranties, and confers no

    rights.
    > Use of any included script samples are subject to the terms specified at
    > http://www.microsoft.com/info/cpyright.htm
    >
    >
    > "jim" <jim@NOSPAM.com> wrote in message
    > news:empvBXnQEHA.2716@tk2msftngp13.phx.gbl...
    > > Has anyone dealt with this one before?.. "The MAD Monitoring thread was
    > > unable to connect to WMI, error '0x8004100e'." I tried correcting it by
    > > following the steps in TechNet article Q288590, however the error still
    > > persists in the application log on my Exchange server appearing every

    five
    > > minutes or so. I can't monitor the system through "Monitoring and

    Status"
    > > in the Exchange Admin now. Everything shows up as "Unknown".
    > >
    > > Server is Exchange2K (SP3) on Win2K (SP3).
    > >
    > > Thanks!
    > >
    > >
    > > (*Apologies if you believe i'm cross-posting. I tried to only choose
    > > relevant newsgroups.)
    > >
    > >

    >
    >




  6. Default Re: Event ID 9097 WMI Error..

    The KB Article suggests exactly to recompile the MOF file.
    Was the compilation succesful ?

    --
    This posting is provided "AS IS" with no warranties, and confers no rights.
    Use of any included script samples are subject to the terms specified at
    http://www.microsoft.com/info/cpyright.htm


    "jim" <jim@NOSPAM.com> wrote in message
    news:eRxocqyQEHA.3988@tk2msftngp13.phx.gbl...
    > You're going way beyond what i know how to do. How do i recompile an MOF
    > file? I just want to clear these errors and start monitoring my remote
    > Exchange server again. Any thoughts?
    >
    > (And remember that i've already tried the steps in Q288590)
    >
    > "Ivan Brugiolo [MSFT]" <ivanbrug@online.microsoft.com> wrote in message
    > news:OU4EPxpQEHA.3748@TK2MSFTNGP09.phx.gbl...
    > > From the verbose logs of WinMgmt you should have an idea of the

    namespace
    > > for which the connectio is being attempted.
    > > If you really don't have that namespace, as you can verify easily with
    > > wbemtest.exe,
    > > then you should try to fing-out if there is a MOF file that contains
    > > the definition of that namesapce.
    > > If you re-compile that MOF file, does the situation improve ?
    > >
    > > --
    > > This posting is provided "AS IS" with no warranties, and confers no

    > rights.
    > > Use of any included script samples are subject to the terms specified at
    > > http://www.microsoft.com/info/cpyright.htm
    > >
    > >
    > > "jim" <jim@NOSPAM.com> wrote in message
    > > news:empvBXnQEHA.2716@tk2msftngp13.phx.gbl...
    > > > Has anyone dealt with this one before?.. "The MAD Monitoring thread

    was
    > > > unable to connect to WMI, error '0x8004100e'." I tried correcting it

    by
    > > > following the steps in TechNet article Q288590, however the error

    still
    > > > persists in the application log on my Exchange server appearing every

    > five
    > > > minutes or so. I can't monitor the system through "Monitoring and

    > Status"
    > > > in the Exchange Admin now. Everything shows up as "Unknown".
    > > >
    > > > Server is Exchange2K (SP3) on Win2K (SP3).
    > > >
    > > > Thanks!
    > > >
    > > >
    > > > (*Apologies if you believe i'm cross-posting. I tried to only choose
    > > > relevant newsgroups.)
    > > >
    > > >

    > >
    > >

    >
    >




  7. Default Re: Event ID 9097 WMI Error..

    The KB Article suggests exactly to recompile the MOF file.
    Was the compilation succesful ?

    --
    This posting is provided "AS IS" with no warranties, and confers no rights.
    Use of any included script samples are subject to the terms specified at
    http://www.microsoft.com/info/cpyright.htm


    "jim" <jim@NOSPAM.com> wrote in message
    news:eRxocqyQEHA.3988@tk2msftngp13.phx.gbl...
    > You're going way beyond what i know how to do. How do i recompile an MOF
    > file? I just want to clear these errors and start monitoring my remote
    > Exchange server again. Any thoughts?
    >
    > (And remember that i've already tried the steps in Q288590)
    >
    > "Ivan Brugiolo [MSFT]" <ivanbrug@online.microsoft.com> wrote in message
    > news:OU4EPxpQEHA.3748@TK2MSFTNGP09.phx.gbl...
    > > From the verbose logs of WinMgmt you should have an idea of the

    namespace
    > > for which the connectio is being attempted.
    > > If you really don't have that namespace, as you can verify easily with
    > > wbemtest.exe,
    > > then you should try to fing-out if there is a MOF file that contains
    > > the definition of that namesapce.
    > > If you re-compile that MOF file, does the situation improve ?
    > >
    > > --
    > > This posting is provided "AS IS" with no warranties, and confers no

    > rights.
    > > Use of any included script samples are subject to the terms specified at
    > > http://www.microsoft.com/info/cpyright.htm
    > >
    > >
    > > "jim" <jim@NOSPAM.com> wrote in message
    > > news:empvBXnQEHA.2716@tk2msftngp13.phx.gbl...
    > > > Has anyone dealt with this one before?.. "The MAD Monitoring thread

    was
    > > > unable to connect to WMI, error '0x8004100e'." I tried correcting it

    by
    > > > following the steps in TechNet article Q288590, however the error

    still
    > > > persists in the application log on my Exchange server appearing every

    > five
    > > > minutes or so. I can't monitor the system through "Monitoring and

    > Status"
    > > > in the Exchange Admin now. Everything shows up as "Unknown".
    > > >
    > > > Server is Exchange2K (SP3) on Win2K (SP3).
    > > >
    > > > Thanks!
    > > >
    > > >
    > > > (*Apologies if you believe i'm cross-posting. I tried to only choose
    > > > relevant newsgroups.)
    > > >
    > > >

    > >
    > >

    >
    >




  8. Default Re: Event ID 9097 WMI Error..

    Nope. This is the error i get...

    Parsing MOF file: z:\setup\i386\exchange\exwmi.mof
    MOF file has been successfully parsed
    Storing data in the repository...
    An error occurred while opening the namespace for object 1 defined on lines
    14 - 17: Error Number: 0x8004100e, Facility: WMI, Description: Invalid
    namespace
    Compiler returned error 0x8004100e

    Any other ideas?



    "Ivan Brugiolo [MSFT]" <ivanbrug@online.microsoft.com> wrote in message
    news:uwD2Hc0QEHA.1392@TK2MSFTNGP09.phx.gbl...
    > The KB Article suggests exactly to recompile the MOF file.
    > Was the compilation succesful ?
    >
    > --
    > This posting is provided "AS IS" with no warranties, and confers no

    rights.
    > Use of any included script samples are subject to the terms specified at
    > http://www.microsoft.com/info/cpyright.htm
    >
    >
    > "jim" <jim@NOSPAM.com> wrote in message
    > news:eRxocqyQEHA.3988@tk2msftngp13.phx.gbl...
    > > You're going way beyond what i know how to do. How do i recompile an

    MOF
    > > file? I just want to clear these errors and start monitoring my remote
    > > Exchange server again. Any thoughts?
    > >
    > > (And remember that i've already tried the steps in Q288590)
    > >
    > > "Ivan Brugiolo [MSFT]" <ivanbrug@online.microsoft.com> wrote in message
    > > news:OU4EPxpQEHA.3748@TK2MSFTNGP09.phx.gbl...
    > > > From the verbose logs of WinMgmt you should have an idea of the

    > namespace
    > > > for which the connectio is being attempted.
    > > > If you really don't have that namespace, as you can verify easily with
    > > > wbemtest.exe,
    > > > then you should try to fing-out if there is a MOF file that contains
    > > > the definition of that namesapce.
    > > > If you re-compile that MOF file, does the situation improve ?
    > > >
    > > > --
    > > > This posting is provided "AS IS" with no warranties, and confers no

    > > rights.
    > > > Use of any included script samples are subject to the terms specified

    at
    > > > http://www.microsoft.com/info/cpyright.htm
    > > >
    > > >
    > > > "jim" <jim@NOSPAM.com> wrote in message
    > > > news:empvBXnQEHA.2716@tk2msftngp13.phx.gbl...
    > > > > Has anyone dealt with this one before?.. "The MAD Monitoring thread

    > was
    > > > > unable to connect to WMI, error '0x8004100e'." I tried correcting

    it
    > by
    > > > > following the steps in TechNet article Q288590, however the error

    > still
    > > > > persists in the application log on my Exchange server appearing

    every
    > > five
    > > > > minutes or so. I can't monitor the system through "Monitoring and

    > > Status"
    > > > > in the Exchange Admin now. Everything shows up as "Unknown".
    > > > >
    > > > > Server is Exchange2K (SP3) on Win2K (SP3).
    > > > >
    > > > > Thanks!
    > > > >
    > > > >
    > > > > (*Apologies if you believe i'm cross-posting. I tried to only choose
    > > > > relevant newsgroups.)
    > > > >
    > > > >
    > > >
    > > >

    > >
    > >

    >
    >




  9. Default Re: Event ID 9097 WMI Error..

    Nope. This is the error i get...

    Parsing MOF file: z:\setup\i386\exchange\exwmi.mof
    MOF file has been successfully parsed
    Storing data in the repository...
    An error occurred while opening the namespace for object 1 defined on lines
    14 - 17: Error Number: 0x8004100e, Facility: WMI, Description: Invalid
    namespace
    Compiler returned error 0x8004100e

    Any other ideas?



    "Ivan Brugiolo [MSFT]" <ivanbrug@online.microsoft.com> wrote in message
    news:uwD2Hc0QEHA.1392@TK2MSFTNGP09.phx.gbl...
    > The KB Article suggests exactly to recompile the MOF file.
    > Was the compilation succesful ?
    >
    > --
    > This posting is provided "AS IS" with no warranties, and confers no

    rights.
    > Use of any included script samples are subject to the terms specified at
    > http://www.microsoft.com/info/cpyright.htm
    >
    >
    > "jim" <jim@NOSPAM.com> wrote in message
    > news:eRxocqyQEHA.3988@tk2msftngp13.phx.gbl...
    > > You're going way beyond what i know how to do. How do i recompile an

    MOF
    > > file? I just want to clear these errors and start monitoring my remote
    > > Exchange server again. Any thoughts?
    > >
    > > (And remember that i've already tried the steps in Q288590)
    > >
    > > "Ivan Brugiolo [MSFT]" <ivanbrug@online.microsoft.com> wrote in message
    > > news:OU4EPxpQEHA.3748@TK2MSFTNGP09.phx.gbl...
    > > > From the verbose logs of WinMgmt you should have an idea of the

    > namespace
    > > > for which the connectio is being attempted.
    > > > If you really don't have that namespace, as you can verify easily with
    > > > wbemtest.exe,
    > > > then you should try to fing-out if there is a MOF file that contains
    > > > the definition of that namesapce.
    > > > If you re-compile that MOF file, does the situation improve ?
    > > >
    > > > --
    > > > This posting is provided "AS IS" with no warranties, and confers no

    > > rights.
    > > > Use of any included script samples are subject to the terms specified

    at
    > > > http://www.microsoft.com/info/cpyright.htm
    > > >
    > > >
    > > > "jim" <jim@NOSPAM.com> wrote in message
    > > > news:empvBXnQEHA.2716@tk2msftngp13.phx.gbl...
    > > > > Has anyone dealt with this one before?.. "The MAD Monitoring thread

    > was
    > > > > unable to connect to WMI, error '0x8004100e'." I tried correcting

    it
    > by
    > > > > following the steps in TechNet article Q288590, however the error

    > still
    > > > > persists in the application log on my Exchange server appearing

    every
    > > five
    > > > > minutes or so. I can't monitor the system through "Monitoring and

    > > Status"
    > > > > in the Exchange Admin now. Everything shows up as "Unknown".
    > > > >
    > > > > Server is Exchange2K (SP3) on Win2K (SP3).
    > > > >
    > > > > Thanks!
    > > > >
    > > > >
    > > > > (*Apologies if you believe i'm cross-posting. I tried to only choose
    > > > > relevant newsgroups.)
    > > > >
    > > > >
    > > >
    > > >

    > >
    > >

    >
    >




  10. Default Re: Event ID 9097 WMI Error..

    Open the file in notepad, go to source line 14-17, and report the content
    here.
    I would bet that the root\WMI namesapce or the root\cimv2 namespace is
    missing.
    I this case you might have to compile %windir%\system32\wbem\cimwin32.mof
    and/or %windir%\system32\wbem\WMI.mof beforehand.

    --
    This posting is provided "AS IS" with no warranties, and confers no rights.
    Use of any included script samples are subject to the terms specified at
    http://www.microsoft.com/info/cpyright.htm


    "jim" <jim@NOSPAM.com> wrote in message
    news:#VaEX30QEHA.3748@TK2MSFTNGP09.phx.gbl...
    > Nope. This is the error i get...
    >
    > Parsing MOF file: z:\setup\i386\exchange\exwmi.mof
    > MOF file has been successfully parsed
    > Storing data in the repository...
    > An error occurred while opening the namespace for object 1 defined on

    lines
    > 14 - 17: Error Number: 0x8004100e, Facility: WMI, Description: Invalid
    > namespace
    > Compiler returned error 0x8004100e
    >
    > Any other ideas?
    >
    >
    >
    > "Ivan Brugiolo [MSFT]" <ivanbrug@online.microsoft.com> wrote in message
    > news:uwD2Hc0QEHA.1392@TK2MSFTNGP09.phx.gbl...
    > > The KB Article suggests exactly to recompile the MOF file.
    > > Was the compilation succesful ?
    > >
    > > --
    > > This posting is provided "AS IS" with no warranties, and confers no

    > rights.
    > > Use of any included script samples are subject to the terms specified at
    > > http://www.microsoft.com/info/cpyright.htm
    > >
    > >
    > > "jim" <jim@NOSPAM.com> wrote in message
    > > news:eRxocqyQEHA.3988@tk2msftngp13.phx.gbl...
    > > > You're going way beyond what i know how to do. How do i recompile an

    > MOF
    > > > file? I just want to clear these errors and start monitoring my

    remote
    > > > Exchange server again. Any thoughts?
    > > >
    > > > (And remember that i've already tried the steps in Q288590)
    > > >
    > > > "Ivan Brugiolo [MSFT]" <ivanbrug@online.microsoft.com> wrote in

    message
    > > > news:OU4EPxpQEHA.3748@TK2MSFTNGP09.phx.gbl...
    > > > > From the verbose logs of WinMgmt you should have an idea of the

    > > namespace
    > > > > for which the connectio is being attempted.
    > > > > If you really don't have that namespace, as you can verify easily

    with
    > > > > wbemtest.exe,
    > > > > then you should try to fing-out if there is a MOF file that contains
    > > > > the definition of that namesapce.
    > > > > If you re-compile that MOF file, does the situation improve ?
    > > > >
    > > > > --
    > > > > This posting is provided "AS IS" with no warranties, and confers no
    > > > rights.
    > > > > Use of any included script samples are subject to the terms

    specified
    > at
    > > > > http://www.microsoft.com/info/cpyright.htm
    > > > >
    > > > >
    > > > > "jim" <jim@NOSPAM.com> wrote in message
    > > > > news:empvBXnQEHA.2716@tk2msftngp13.phx.gbl...
    > > > > > Has anyone dealt with this one before?.. "The MAD Monitoring

    thread
    > > was
    > > > > > unable to connect to WMI, error '0x8004100e'." I tried correcting

    > it
    > > by
    > > > > > following the steps in TechNet article Q288590, however the error

    > > still
    > > > > > persists in the application log on my Exchange server appearing

    > every
    > > > five
    > > > > > minutes or so. I can't monitor the system through "Monitoring and
    > > > Status"
    > > > > > in the Exchange Admin now. Everything shows up as "Unknown".
    > > > > >
    > > > > > Server is Exchange2K (SP3) on Win2K (SP3).
    > > > > >
    > > > > > Thanks!
    > > > > >
    > > > > >
    > > > > > (*Apologies if you believe i'm cross-posting. I tried to only

    choose
    > > > > > relevant newsgroups.)
    > > > > >
    > > > > >
    > > > >
    > > > >
    > > >
    > > >

    > >
    > >

    >
    >




+ Reply to Thread
Page 1 of 4 1 2 3 ... LastLast

Similar Threads

  1. Event ID 8197 Error Message "Error Initializing Session for Virtual Machine"
    By Application Development in forum Microsoft Exchange
    Replies: 0
    Last Post: 08-16-2004, 02:08 AM
  2. WMI Error - Event ID 9097
    By Application Development in forum Microsoft Exchange
    Replies: 0
    Last Post: 05-26-2004, 12:14 PM
  3. Replies: 1
    Last Post: 04-14-2004, 07:05 AM