Sign in
 
HomeOnline20132010Other VersionsLibraryForumsGalleryEHLO Blog
TechCenter >
> 
> 
Name Reference Is Invalid error within multiple domain exchange 2010 environment

Răspuns Name Reference Is Invalid error within multiple domain exchange 2010 environment

  • Thursday, February 23, 2012 2:45 PM
     
     
    Sign In to Vote
    0

    We're having problems with Exchange 2010that have introduced themselves in the last few days that are affecting our ability to create distribution groups, create new mailbox databases, new mailbox database copies, and adding journal recipients to mailboxes, the errors always contain

    "The name reference is invalid.
    This may be caused by replication latency between Active Directory domain controllers."

    We operate a multi domain environment, a forest root domain (Domain A), and two child domains, B and C. Exchange is installed in the forest root domain (Domain A). However the main exchange administration and userbase is Domain C. There is no exchange users or admin in Domain B.

    Running Get-ADServerSettings shows the following

    DefaultGlobalCatalog - GC in Domain B
    PreferredDomainControllerForDomain {}
    DefaultCOnfigurationDomainController - GC in Domain B
    DefaultPreferredDomainController - {GC in Domain B, DC in Domain C}

    UserPreferred DC and GC are blank or {}

    I suspect the cause of most of our problems is that the preferred DC is in Domain B and there is replication delay between these. Is the best way to resolve this to ;

    a) Remove the reference to the DC in domain B as a default preferred domain controller

    b) set user preferred domain controllers using Set-ADServerSettings –PreferredServer <DC FQDN>. Would this be retained after a restart or is this session specific?

    Thanks for any advice




    • Edited by Jon __R Thursday, February 23, 2012 2:54 PM
    •  
     

All Replies

  • Monday, February 27, 2012 8:40 AM
     
     Proposed
    Sign In to Vote
    0

    Hi,

    First we need have GC in Domain C.

    Then you can try to put GC/DC in Domain C to be the prefered domain controller.

    After that, you can try to restart topology services.

    Xiu Zhang

    TechNet Community Support

     
  • Monday, February 27, 2012 2:32 PM
     
     
    Sign In to Vote
    0

    Sounds like a GC issue to me as well. Are your Domain C servers in AD sites and services set as GC servers?

    James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com

     
  • Monday, February 27, 2012 3:07 PM
     
     
    Sign In to Vote
    0

    Sounds like a GC issue to me as well. Are your Domain C servers in AD sites and services set as GC servers?

    James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com

    I am also working on this issue with orignal poster. Thanks for your responses they seem to confirm what we suspected.

    We do have a global catalogue in Domain C in the same site. We are not sure why that would not be processing requests from Exchange but we will make the changes as stated and see how that goes.

     
  • Wednesday, February 29, 2012 6:14 AM
     
     
    Sign In to Vote
    0

    Hi Jon_R,

    How is the issue now?

    Xiu Zhang

    TechNet Community Support

     
  • Wednesday, February 29, 2012 9:57 AM
     
     
    Sign In to Vote
    0

    Hi we are still having the same problem.

    We have ensured that exchange is now configured to look at static DCs within our child domain.

    We are still getting the error shown below

    We thought maybe they show a problem with the arbitration mailbox but we can see these ok when running get-mailbox -arbitration

    We have run repadmin /syncall on our DCs which has not resolved

    We have run setup.com /preparead within the forest root as an enterprise admin

    We are currently liasing with a Microsoft support rep but in the meantime if anyone has any other ideas or suggestions we would be very grateful

    Thanks

     
  • Friday, March 02, 2012 7:02 AM
     
     
    Sign In to Vote
    0

    Hi,

    Firstplease run  Dcdiag on exchange server andrun Dcdiag on DC and then post the error information here.

    Please check event 2080 on Exchange Server and then post the detail information here.

    Please run "nltest /dsgetsite" and then post the value here.

    Please run the command below and then post the result here.

    [PS] C:\Windows\system32> $Forest =[System.DirectoryServices.ActiveDirectory.Forest]::GetCurrentForest()

    [PS] C:\Windows\system32> $Forest.FindAllGlobalCatalogs() | Select Name,SiteName, Domain, Roles

    Please try to run get-exchangeserver servername -status |fl to check the value on originating server and the value on currentconfigdomiancontroller. You can post the result here.

    By the way, have you tried to run setup /preparealldomains?




    Xiu Zhang

    TechNet Community Support

     
  • Friday, March 02, 2012 4:56 PM
     
     
    Sign In to Vote
    0

    Xiu_Zhang

    Due to the nature of our organisation we cannot post information that specific, apologies.

    We are currently progressing a support call through Microsoft.

    I'll post what the resolution was when we have one

    thanks

     
  • Monday, March 05, 2012 5:02 AM
     
     
    Sign In to Vote
    0

    Hi Jon_R,

    Please feel free to update here.

    Besides, you can check if your configuration DC is correct via the command that I mentioned. The CDC should also be the GC.

    Xiu Zhang

    TechNet Community Support

     
  • Monday, March 26, 2012 9:20 AM
     
     Answered
    Sign In to Vote
    0

    Sorry for the late reply, we have resolved this issue with Microsofts support.

    Re-installing the EMC and EMS did not fix the issue, we had to go a step further delete the MMC snap in data, specifically

    C:\Users\xxxxxx\AppData\Roaming\Microsoft\MMC\Exchange Management Console

    C:\Users\xxxxxx\AppData\Roaming\Microsoft\MMC\Exchange Queue Viewer

    Removing these two files allowed them to be recreated when EMC was loaded. Straight away then we were able to re-create groups normally.

    Appears the MMC must have been retaining an old GC/DC setting or something.

    • Marked As Answer by Jon __R Monday, March 26, 2012 9:20 AM
    •  
     
  • Thursday, January 24, 2013 9:14 AM
     
     Proposed
    Sign In to Vote
    0

    Hey! As we ran into the same issue just my update here.

    Deleting the MMC config files has not solved the problem for us.

    We tried to create or modify a DL in domain B (Belgium). Our Exchange 2010 is in domain A (Germany). In site A we have a DC for domain B, but this is not a GC. Domain B (other geo region) has two GC. Whenever we tried to change something we get the error Jon_R mentioned.

    What solved the problem is to create the DL from console with 'new-distributiongroup' and specify the GC in Antwerp as the DC (option -DomainController). After the replication has occured we can change and modify and delete this DL as we want. Even on the DC for domain B in site A.

    Strange ... maybe some GC problem ...