Announcement

Collapse
No announcement yet.

error: The MAD Monitoring thread was unable to read its configuration from the DS

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • error: The MAD Monitoring thread was unable to read its configuration from the DS

    Hello,
    I found the error message in Application log of my Exchange 2003.
    Couple of month ago I removed DC role from one of the bad functionning servers and made other one DC.

    I can just guess that it's related problem. On web I could find this error message applying to Exchange 2000.
    Where could be the problem? Thx.

    Event Type: Error
    Event Source: MSExchangeSA
    Event Category: Monitoring
    Event ID: 9098
    Date: 9/18/2008
    Time: 10:31:20 AM
    User: N/A
    Computer: KYARD-MAIL
    Description:
    The MAD Monitoring thread was unable to read its configuration from the DS, error '0x80041010'.
    For more information, click http://www.microsoft.com/contentredirect.asp.
    "When you hit a wrong note it's the next note that makes it good or bad". Miles Davis

  • #2
    Re: error: The MAD Monitoring thread was unable to read its configuration from the DS

    What exactly did you do?
    Did you remove the domain controller role from an Exchange server, or another DC?
    How many global catalogs do you have?
    Is Exchange pointing to the GC for DNS?

    Simon.
    --
    Simon Butler
    Exchange MVP

    Blog: http://blog.sembee.co.uk/
    More Exchange Content: http://exchange.sembee.info/
    Exchange Resources List: http://exbpa.com/
    In the UK? Hire me: http://www.sembee.co.uk/

    Sembee is a registered trademark, used here with permission.

    Comment


    • #3
      Re: error: The MAD Monitoring thread was unable to read its configuration from the DS

      I had 2 DCs.
      One of them is APPS server and had damaged OS (couldn't install SP2).
      I found replication errors since DEC 2006.
      There is no tech on site. But now I realise that Damaged server was first DC and probably GC.
      To fix replication problems (was too many errors) and I knew that APPS server is corrupted I removed DC role from it and installed new DC.
      Replication was fixed. Later Apps server was reinstalled and is just a member server.

      Exchange is pointing to the DC that was installed long time ago (didcated one). I thought that is was first DC since it's dedicated DC.
      From your question I have a filling that damaged APPS DC had GC.

      I started to read about GC. Found how to install it
      Installing a Global Catalog Server
      The first domain controller installed in your forest will automatically be a Global Catalog server. If you wish to add more itís a simple matter of a tick box. Itís not a simple matter of finding it unless you know where to look.
      1.) Open up Active Directory Sites and Services.
      2.) Expand Sites, Site Name, Servers.
      3.) Select your server and then the NTDS Settings, right click and choose Properties.
      4.) Tick the box marked Global Catalog.

      What workaround do you suggest?
      The network 9 servers 2 DCs. 5 internal users. 5 external.
      More servers than users on site

      Thanks,
      Michael.
      "When you hit a wrong note it's the next note that makes it good or bad". Miles Davis

      Comment


      • #4
        Re: error: The MAD Monitoring thread was unable to read its configuration from the DS

        Have you checked the server holds the GC role?
        What about the other FSMO roles? Were those moved correctly?

        To check, install the Support tools from the Windows Server CD and then run in a command prompt

        netdom query fsmo

        If any of the roles are shown on a non-valid server then you will need to seize the roles. Instructions on how to do that are elsewhere on this site in the main section.

        Simon.
        --
        Simon Butler
        Exchange MVP

        Blog: http://blog.sembee.co.uk/
        More Exchange Content: http://exchange.sembee.info/
        Exchange Resources List: http://exbpa.com/
        In the UK? Hire me: http://www.sembee.co.uk/

        Sembee is a registered trademark, used here with permission.

        Comment


        • #5
          Re: error: The MAD Monitoring thread was unable to read its configuration from the DS

          Thanks, Simon.
          I am once a week on site. But if I will have time I'll check it remotely. I will post the result. Should be interesting troubleshooting.
          "When you hit a wrong note it's the next note that makes it good or bad". Miles Davis

          Comment


          • #6
            Re: error: The MAD Monitoring thread was unable to read its configuration from the DS

            Simon,
            my dedicated DC holds all 5 MOs.
            And it is GC.
            dcdiag is clean.
            Exchange DNS entry is my first DC ip

            In eventvwr the same MAD error every 5 minutes.

            What's next?

            Thx.
            Michael.
            "When you hit a wrong note it's the next note that makes it good or bad". Miles Davis

            Comment


            • #7
              Re: error: The MAD Monitoring thread was unable to read its configuration from the DS

              If you are sure that all roles have been moved and the server has been rebooted since, then either there is a hard coded reference to the non-existent domain controller in ESM somewhere, or something is wrong in the domain. I would go through ESM to begin with, particular recipient update services configuration and the server properties, and confirm that a valid domain controller is listed.

              Otherwise it comes down to a sniff through adsiedit.msc, with all the risks that brings - ie do not change/delete anything unless you are 100% sure that you know what you are doing.

              Simon.
              --
              Simon Butler
              Exchange MVP

              Blog: http://blog.sembee.co.uk/
              More Exchange Content: http://exchange.sembee.info/
              Exchange Resources List: http://exbpa.com/
              In the UK? Hire me: http://www.sembee.co.uk/

              Sembee is a registered trademark, used here with permission.

              Comment


              • #8
                Re: error: The MAD Monitoring thread was unable to read its configuration from the DS

                Hii

                Code 0x80041010 relates to WBEM_E_INVALID_CLASS...which sure enuf is a WMI issue/..


                1>The best possible step is re-install exchange and re-apply the service packs.

                Though there are steps to check if WMI is working or not and troubleshoot it..here are a few of them..

                a>Goto start and run wmimgmt.msc and compare the permissions with a working machine..(It would be really difficult to list all the permissions)



                2>Use Wbemtest.exe to check classes and namespaces

                a. Click Start, click Run, type wbemtest in the Open box, and then click OK.
                b. In the Windows Management Instrumentation Tester dialog box, click Connect.
                c. In the Namespace field, type root\cimv2\applications\exchange , and then click Connect.
                d. Click Enum Classes. Do not enter a superclass name. Select the Recursive option, and then click OK.
                e.Compare these values(Query PAge) with the values from another server that is correctly running the same version of Exchange 2003 with the same service packs. These values should be the same.
                f. Click Close.
                g. In the Windows Management Instrumentation Tester dialog box, click Connect.
                h. In the Namespace field, type root\microsoftExchangeV2 , and then click Connect.
                i. Click Enum Classes. Do not enter a superclass name. Select the Recursive option, and then click OK.
                j. In the Query Result page,Compare these values with the values from another server that is correctly running the same version of Exchange 2003 with the same service packs. These values should be the same.
                k. Click Close.


                3>Incase we are getting any Errors such as Invalid handle or the number of classes are not the same then we need to follow the below listed steps...

                Register the required Exchange 2003 .dll files, and then import the Exchange 2003 namespaces and classes to the WMI repository. To do this, follow these steps:

                a. Click Start, click Run, type cmd in the Open box, and then click OK.
                b. Change to the Exchsrvr\Bin directory.
                c. At the command prompt, type the following commands. Press ENTER after each command.
                exmgmt.exe /uninstall
                exmgmt.exe /install
                regsvr32 /s exwmi.dll
                regsvr32 /s cdowf.dll
                regsvr32 /s cdowfevt.dll
                d. Change to the Windows\System32\Wbem directory.
                e. At the command prompt, type the following commands. Press ENTER after each command.
                mofcomp.exe -class:forceupdate C: \WINDOWS\system32\WBEM\exmgmt.mof
                mofcomp.exe C: \WINDOWS\system32\WBEM\exwmi.mof
                mofcomp.exe -n:root\cimv2\applications\exchange C: \windows\system32\wbem\wbemcons.mof
                mofcomp.exe -n:root\cimv2\applications\exchange C: \windows\system32\wbem\smtpcons.mof
                mofcomp.exe -n:root\cimv2\applications\exchange C: \winnt\system32\wbem\msgtrk.mof
                f. Click Start, click Run, type services.msc in the Open box, and then click OK.
                g.Restart the server........................


                Regards

                Fazal
                Fazal Zaidi
                MCITP-Windows 2008,Exchange 2010,MCTS-Exchange 2007,2010,Lync 2010,MCSE-2000,2003,MCSA-2003,2008,2012,MCP,MCSE -Messaging 2013,ITIL

                Comment


                • #9
                  Re: error: The MAD Monitoring thread was unable to read its configuration from the DS

                  Just by looking Fazal's instructions I am freeking out
                  But the causes are really informative. Thanks.

                  It's not affect e-mail users in anyway.

                  2 questions:

                  1. Is this error critical?

                  2. The Exchange server run Terminal services since it was installed (2years ago).
                  I told to management that it against all the rules. They planning major system upgrade next year. So probably will move to E2007.
                  Could terminal cause the MAD error?

                  I don't like to see any errors in the log that's why would like to repair it.

                  Againg AD is functionning well, no errors. If I shutdown Master DC. Everthing works fine. It means that my new DC doing the job.
                  "When you hit a wrong note it's the next note that makes it good or bad". Miles Davis

                  Comment


                  • #10
                    Re: error: The MAD Monitoring thread was unable to read its configuration from the DS

                    To Sembee.
                    About server rebooted...
                    Possible that I didn't reboot the Master DC since I installed new DC.
                    Don't remember. Because I didn' t perform any operations on it.
                    But I guess I rebooted it after MS updates.

                    As I mentioned in initial post.
                    I found replication errors that appeared since 2006.
                    I removed DC role from Apps server (was clean).
                    And mount new server with DC role.
                    All what I found that DCDIAG became clean.

                    MAD didn't appear before but started later. I can not tell exactly that it started after my AD `playing`. I am once per week on this site.
                    But looks like after my AD žmprovement`

                    Looks like I healed one things but other became seek.

                    Thx.
                    "When you hit a wrong note it's the next note that makes it good or bad". Miles Davis

                    Comment

                    Working...
                    X