Announcement

Collapse
No announcement yet.

exchange2003 member server problems

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

  • exchange2003 member server problems

    I am running a domain that already has 2 exchange servers on it. (both on DC's, one active, one backup)

    I am trying to set up exchange on a member server, then will down the other 2 servers.


    I installed server 2003, then installed server 2003 SP2.

    Installed exchange 2003.
    - Added on IIS and other required bits before kicking off the actual install.
    - I did NOT run domain/forest prep as I already had an exchange server on the domain.

    I had a heap of errors in the event viewer, and the box would take an hour to reboot.

    I installed exchange service pack 2, hoping it would fix any problems.

    It didn't.
    I used dcdiag, nslookup, ping, nbtstat etc. to try and resolve naming issues. Could not find any problems.

    The member server is listed in system manager on the original exchange box.

    I am about to wipe it and start again, but don't really want to stuff around removing this server from AD, then potentially having the same issue again.

    Any help is very very gratefully received.


    The errors I'm getting are below:

    __________________________________________

    Event Type: Error
    Event Source: MSExchangeMU
    Event Category: General
    Event ID: 1042
    Date: 24/10/2008
    Time: 10:21:00 AM
    User: N/A
    Computer: EXCHANGE6
    Description:
    Metabase Update failed to read the Configuration namespace property from the domain controller. Error code is 80040a01.


    Event Type: Error
    Event Source: MSExchangeDSAccess
    Event Category: Topology
    Event ID: 2114
    Date: 24/10/2008
    Time: 10:20:48 AM
    User: N/A
    Computer: EXCHANGE6
    Description:
    Process MAD.EXE (PID=1616). Topology Discovery failed, error 0x80040a02.


    Event Type: Error
    Event Source: MSExchangeDSAccess
    Event Category: Topology
    Event ID: 2114
    Date: 24/10/2008
    Time: 10:16:51 AM
    User: N/A
    Computer: EXCHANGE6
    Description:
    Process WMIPRVSE.EXE -EMBEDDING (PID=2184). Topology Discovery failed, error 0x80040a02.


    Event Type: Error
    Event Source: MSExchangeDSAccess
    Event Category: Topology
    Event ID: 2102
    Date: 24/10/2008
    Time: 10:16:38 AM
    User: N/A
    Computer: EXCHANGE6
    Description:
    Process MAD.EXE (PID=1616). All Domain Controller Servers in use are not responding:
    s1.zzz.local
    s2.zzz.local
    s3.zzz.local
    s4.zzz.local
    s5.zzz.local
    s6.zzz.local
    s7.zzz.local
    s8.zzz.local


    For more information, click http://www.microsoft.com/contentredirect.asp.

  • #2
    Re: exchange2003 member server problems

    All of those errors mean the same thing.
    The machine cannot communicate with the domain controllers.
    Taking an hour to boot is the same thing.

    Therefore ensure that you only have domain controllers configured as the DNS servers in the network configuration. No external DNS servers should be listed anywhere.

    The servers that currently have Exchange on them should be global catalogs.

    If you do decide to rebuild the machine, remove Exchange first using add/remove programs, which should remove it from the AD correctly. If it does not,m then finish the uninstall, drop the machine in to a workgroup and shutdown. Wait about an hour for the domain to catch up. You should then be able to right click on the now dead server in ESM and choose Delete or Remove (I can't remember which and at this time of night too lazy to check).

    Then rebuild the machine with a new name and reinstall Exchange.

    However this looks like a network or AD issue, rather than Exchange, so you may well resolve it by looking at that part first.

    Do NOT be tempted to drop it out of the domain with Exchange installed - then you will have a mess.

    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: exchange2003 member server problems

      Hi Simon,

      Thank you for taking the time to reply.


      I previously tried setting the DNS server setting on the broken exchange to 2 different DC's, but have the same result. Both of the DNS server DCs have the Global catalog on them.

      The broken box has no external DNS available.

      Comment


      • #4
        Re: exchange2003 member server problems

        When the Exchange 2003 CD auto plays it comes up with an installation menu and checklist. On that checklist are some bits to do domain verification using some tools from the Windows Support Tools. I would suggest that you complete that and see if there are any obvious problems.

        Otherwise remove Exchange and rebuild the box as I have already indicated.

        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: exchange2003 member server problems

          Update:

          uninstalled exchange and formatted.

          reinstalled, and had the same problems.

          Stubbornness and my refusal to give in and make the server a DC, yielded the following find:

          The Exchange Enterprise Servers group must have Manage auditing and security logs permissions on all the domain controllers in the domain.
          http://support.microsoft.com/kb/328662

          Can't figure out why it was missing in the first place, given that there is already an exchange server running on a DC in the domain.

          Comment


          • #6
            Re: exchange2003 member server problems

            Running domain prep again may well have resolved that problem as well.

            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

            Working...
            X