locked
New-GlobalAddressList Fails - AD44A06F RRS feed

  • Question

  • Hi,

    When trying to create a Global AddressList using Exchange Management Shell e.g.

    New-GlobalAddressList -name NewGal

    I get the following error:

    WARNING: One or more global address lists were missing from the Active Directory attribute.  This is likely caused by using legacy Exchange management tools to create global address lists.
    Active Directory operation failed on KLZ-OXF-DC01.klz.local. This error is not retriable. Additional information: The name reference is invalid.
    This may be caused by replication latency between Active Directory domain controllers.
    Active directory response: 000020B5: AtrErr: DSID-0315286E, #1:
        0: 000020B5: DSID-0315286E, problem 1005 (CONSTRAINT_ATT_TYPE), data 0, Att 907ff (globalAddressList2)
        + CategoryInfo          : NotSpecified: (0:Int32) [New-GlobalAddressList], ADConstraintViolationException
        + FullyQualifiedErrorId : AD44A06F,Microsoft.Exchange.Management.SystemConfigurationTasks.NewGlobalAddressList

    I'm able to do other things like create address-lists etc.. using the same shell. I can create a new GAL using ADSI, which does show in EMC

    Thanks

    Tuesday, February 28, 2012 10:15 AM

Answers

  • Found the answer...

    Open up ADSI.msc, then add in configuration.

    Expand Services and right-click CN=Microsoft Exchange and select properties

    Check all the GAL's listed in globalAddressList and globalAddressList2 are valid.

    Remove any that aren't and it should work

    • Marked as answer by eaigs Tuesday, February 28, 2012 10:35 AM
    Tuesday, February 28, 2012 10:35 AM
  • Hi eaigs,
    This forum is for software developers who are using the Open Specification documentation to assist them in developing systems, services, and applications that are interoperable with Microsoft products. The Open Specifications can be found at: http://msdn.microsoft.com/en-us/library/cc203350(PROT.10).aspx. Since your post does not appear to be related to the Open Specification documentation set we would appreciate it if you could try to post your question in a more relevant forum.

    Exchange Server Forums -> Administration

    Thank you.


    Josh Curry (jcurry) | Escalation Engineer | Open Specifications Support Team

    Tuesday, February 28, 2012 2:15 PM

All replies

  • Found the answer...

    Open up ADSI.msc, then add in configuration.

    Expand Services and right-click CN=Microsoft Exchange and select properties

    Check all the GAL's listed in globalAddressList and globalAddressList2 are valid.

    Remove any that aren't and it should work

    • Marked as answer by eaigs Tuesday, February 28, 2012 10:35 AM
    Tuesday, February 28, 2012 10:35 AM
  • Hi eaigs,
    This forum is for software developers who are using the Open Specification documentation to assist them in developing systems, services, and applications that are interoperable with Microsoft products. The Open Specifications can be found at: http://msdn.microsoft.com/en-us/library/cc203350(PROT.10).aspx. Since your post does not appear to be related to the Open Specification documentation set we would appreciate it if you could try to post your question in a more relevant forum.

    Exchange Server Forums -> Administration

    Thank you.


    Josh Curry (jcurry) | Escalation Engineer | Open Specifications Support Team

    Tuesday, February 28, 2012 2:15 PM
  • Found the answer...

    Open up ADSI.msc, then add in configuration.

    Expand Services and right-click CN=Microsoft Exchange and select properties

    Check all the GAL's listed in globalAddressList and globalAddressList2 are valid.

    Remove any that aren't and it should work

    Hi,

    Anyone facing this error can use my powerShell script to find corrupted GAL entries in AD object 'CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Domain,DC=local'

    http://social.technet.microsoft.com/Forums/en-US/exchange2010hosters/thread/52854856-f517-4827-b3d3-3e589a422672?prof=required

    You would have to remove them manually using ADSIEdit.msc or some other AD Editor tool.

    Regards,


    Laeeq Qazi|Team Lead(Exchange + Sharepoint + BES + DynamicsCRM) www.HostingController.com

    Tuesday, May 15, 2012 2:15 PM