Announcement

Collapse
No announcement yet.

Exchange not Resolving

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

  • Exchange not Resolving

    We have an Exchange 2003 Server running on a Windows Server 2000 Server BDC. The BDC server crashed and the backup restored was about 10 days old. There may be a domain controller replication issue as the BDC data was 10 days older than the PDC.

    The server is now unable to create new mailboxes. It shows creation as successful, but new users cannot open their mailbox with outlook. Existing mailboxes are OK.

    I tried rerunning forestprep and domain prep, but to no avail.
    It still does not create new mailboxes or resolve during outlook profile creation. Existing users resolve ok.

    In the event I can't get this running, I would like to move the exchange to a new Windows 2003 member server or get it running again properly on the existing box

    Any Ideas?

  • #2
    Re: Exchange not Resolving

    Might be a problem with the RUS and/or replication to the Global Catalog.

    Just curious, how did you restored your second DC (and please forget about this PDC/BDC things there are no such things in AD except an PDC emulator)?

    What is the state of AD replication right now? Does it work properly, any errors relating to replication in the logs?

    Comment


    • #3
      Re: Exchange not Resolving

      You shouldn't have restored a backup of a domain controller, particularly if it involved system state restore. The only thing you should have restored was data.

      I would be looking to remove that restore domain controller and build it fresh.

      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


      • #4
        Re: Exchange not Resolving

        It was a drive crash.

        How will running DCPROMO to demote and remove the AD references to the bad DC then recreating the DC effect the Exchange Server Loaded on the DC.

        Or alternately, can the box be left as a member server with Exchange loaded on it?

        Comment


        • #5
          Re: Exchange not Resolving

          You can't run DCPROMO on an Exchange server and expect Exchange to operate correctly afterwards. Microsoft do not support running DCPROMO on Exchange.

          Therefore you would have two options.

          1. Rebuild the machine manually and carry out a complete domain controller recovery. Then install Exchange.

          2. As above, but remove references to the domain controller from the domain, but ensuring that you do not remove the machine account,t hen reinstall Exchange using the disasterrecovery switch before restoring the data.

          One of the key reasons for NOT putting Exchange on to a domain controller is that it complicates the disaster recovery options considerably. It is fine when you only have one domain controller and Exchange is installed on it (such as SBS) but once you get past that stage, Exchange should really be on a member server with separate domain controllers.

          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


          • #6
            Re: Exchange not Resolving

            Third option ??

            Is it possible to install another Windows 2003 Member Server and Exchange 2003 then move the Exchange Databases over?

            Then delete the old server and exchange from the Domain?

            Thanks!

            Comment


            • #7
              Re: Exchange not Resolving

              Hi there

              As you have written the old mail boxes are working fine, the problem exist only with the new one, so i believe that youe exchange shoud be OK just some minor issue. Here is what we can do
              1) Verify AD replication is working fine and also Take Dcdiag on both the DC's and resolve if you find any issue
              2) carefully monitor the process when u create new mailboxes, see if you get any specific error, also look into event vwr for some errors and provide us with that, then we should be able to help you.

              As far as restoring exchange from backup is concenred, here is what you can do, if you have the exchange specific backup seprately ie without AD/system state back up , then you can create a new exchange server with same SP level and same orgnisation/storage grp/mailbox store name and then can import it.

              As of now look for specific errors, we might be able to fix it

              Karan
              PledgeTech
              Best Regards,
              Pledge Technologies

              Comment


              • #8
                Re: Exchange not Resolving

                Here is the DCDIAG from the First Server Named "FS2"


                Domain Controller Diagnosis
                Performing initial setup:
                Done gathering initial info.
                Doing initial required tests

                Testing server: Default-First-Site-Name\FS2
                Starting test: Connectivity
                ......................... FS2 passed test Connectivity
                Doing primary tests

                Testing server: Default-First-Site-Name\FS2
                Starting test: Replications
                [Replications Check,FS2] A recent replication attempt failed:
                From SERVER to FS2
                Naming Context: CN=Schema,CN=Configuration,DC=LOCAL,DC=HEG,DC=com
                The replication generated an error (8456):
                The source server is currently rejecting replication requests.
                The failure occurred at 2009-12-07 11:56.59.
                The last success occurred at 2009-11-07 03:53.52.
                727 failures have occurred since the last success.
                Replication has been explicitly disabled through the server options.
                [Replications Check,FS2] A recent replication attempt failed:
                From SERVER to FS2
                Naming Context: CN=Configuration,DC=LOCAL,DC=HEG,DC=com
                The replication generated an error (8456):
                The source server is currently rejecting replication requests.
                The failure occurred at 2009-12-07 12:04.12.
                The last success occurred at 2009-11-07 03:53.52.
                6181 failures have occurred since the last success.
                Replication has been explicitly disabled through the server options.
                [Replications Check,FS2] A recent replication attempt failed:
                From SERVER to FS2
                Naming Context: DC=LOCAL,DC=HEG,DC=com
                The replication generated an error (8456):
                The source server is currently rejecting replication requests.
                The failure occurred at 2009-12-07 11:56.59.
                The last success occurred at 2009-11-07 03:54.45.
                1634 failures have occurred since the last success.
                Replication has been explicitly disabled through the server options.
                ......................... FS2 passed test Replications
                Starting test: NCSecDesc
                ......................... FS2 passed test NCSecDesc
                Starting test: NetLogons
                ......................... FS2 passed test NetLogons
                Starting test: Advertising
                ......................... FS2 passed test Advertising
                Starting test: KnowsOfRoleHolders
                ......................... FS2 passed test KnowsOfRoleHolders
                Starting test: RidManager
                ......................... FS2 passed test RidManager
                Starting test: MachineAccount
                ......................... FS2 passed test MachineAccount
                Starting test: Services
                ......................... FS2 passed test Services
                Starting test: ObjectsReplicated
                ......................... FS2 passed test ObjectsReplicated
                Starting test: frssysvol
                ......................... FS2 passed test frssysvol
                Starting test: kccevent
                An Error Event occured. EventID: 0xC00005F8
                Time Generated: 12/07/2009 12:01:53
                Event String: The Inter-Site Messaging (ISM) Service SMTP
                An Error Event occured. EventID: 0xC000055D
                Time Generated: 12/07/2009 12:01:53
                Event String: The query for messages for service
                ......................... FS2 failed test kccevent
                Starting test: systemlog
                ......................... FS2 passed test systemlog

                Running enterprise tests on : LOCAL.HEG.com
                Starting test: Intersite
                ......................... LOCAL.HEG.com passed test Intersite
                Starting test: FsmoCheck
                ......................... LOCAL.HEG.com passed test FsmoCheck

                ================================================== ======

                Here is the DCDIAG from the (Restored) Exchange Server Named "SERVER"


                DC Diagnosis
                Performing initial setup:
                Done gathering initial info.
                Doing initial non skippeable tests

                Testing server: Default-First-Site-Name\SERVER
                Starting test: Connectivity
                ......................... SERVER passed test Connectivity
                Doing primary tests

                Testing server: Default-First-Site-Name\SERVER
                Starting test: Replications
                [Replications Check,SERVER] Inbound replication is disabled.
                To correct, run "repadmin /options SERVER -DISABLE_INBOUND_REPL"
                [Replications Check,SERVER] Outbound replication is disabled.
                To correct, run "repadmin /options SERVER -DISABLE_OUTBOUND_REPL"
                ......................... SERVER failed test Replications
                Starting test: NCSecDesc
                ......................... SERVER passed test NCSecDesc
                Starting test: NetLogons
                ......................... SERVER passed test NetLogons
                Starting test: Advertising
                Warning: DsGetDcName returned information for \\FS2.LOCAL.HEG.COM, when we were trying to reach SERVER.
                Server is not responding or is not considered suitable.
                ......................... SERVER failed test Advertising
                Starting test: KnowsOfRoleHolders
                ......................... SERVER passed test KnowsOfRoleHolders
                Starting test: RidManager
                ......................... SERVER passed test RidManager
                Starting test: MachineAccount
                ......................... SERVER passed test MachineAccount
                Starting test: Services
                NETLOGON Service is paused on [SERVER]
                ......................... SERVER failed test Services
                Starting test: ObjectsReplicated
                ......................... SERVER passed test ObjectsReplicated
                Starting test: frssysvol
                ......................... SERVER passed test frssysvol
                Starting test: kccevent
                ......................... SERVER passed test kccevent
                Starting test: systemlog
                ......................... SERVER passed test systemlog

                Running enterprise tests on : LOCAL.HEG.com
                Starting test: Intersite
                ......................... LOCAL.HEG.com passed test Intersite
                Starting test: FsmoCheck
                Error: The server returned by DsGetDcName() did not match DsListRoles() for the PDC
                ......................... LOCAL.HEG.com passed test FsmoCheck
                =================================================

                From DS Log

                12/7/2009 5:44:06 AM NTDS Replication Warning (5) 1586 HEG\Administrator SERVER The checkpoint with the PDC was unsuccessful. The checkpointing process will be retried again in four hours. A full synchronization of the security database to downlevel domain controllers may take place if this machine is promoted to be the PDC before the next successful checkpoint. The error returned was: The destination server is currently rejecting replication requests.


                ============================================

                Please let me know what else you may need....

                Thanks!

                Comment

                Working...
                X