Routing group connector error Exchange 2010 Sp1

I’ve tried to create routing group connectors between my two Exchange 2010 SP1 Hub Transport / Client Access servers (EX2010H1 and EX2010H2) and the two clustered Exchange 2003 Hub Transport / Mailbox servers (EXCH1 and EXCH2).

I ran the Exchange Shell command:

New-RoutingGroupConnector -name ex2010H1-svrexch1 -SourceTransportServers ex2010H1.domainname.org.uk -TargetTransportServers svrexch1.domainname.org.uk -Bidirectional $true

This was successful creating routing group connectors between EX2010H1 / EX2010H2 and the 2003 server EXCH1.

When I try to run the command to create connectors between EX2010H1 / EX2010H2 and the 2003 server EXCH2 it shows the following error:

Active Directory operation failed on SVRDC01.domainname.org.uk. 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-03152804, #1:
    0: 000020B5: DSID-03152804, problem 1005 (CONSTRAINT_ATT_TYPE), data 0, Att 482330e2 (msExchTargetBridgeheadServers
DN)
    + CategoryInfo          : NotSpecified: (0:Int32) [New-RoutingGroupConnector], ADConstraintViolationException
    + FullyQualifiedErrorId : 854B6AE9,Microsoft.Exchange.Management.SystemConfigurationTasks.NewRoutingGroupConnector

I've tried pointing the Exchange servers to different DCs but this hasn't helped.

Any ideas?
LVL 3
southwestsixteenAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
Advertise Here
 
southwestsixteenConnect With a Mentor Author Commented:
Hi Shree, I have tried the solution in the Microsoft support article before but it didn't help. I tried it again over the weekend with no success.
0
 
Shreedhar EtteCommented:
Hi,

This issue occurs when the value of the ConfigurationDomainController parameter and the value of the PreferredGlobalCatalog parameter are different. In this scenario, the Mailbox database operation fails because of the replication latency that occurs between the configured domain controllers and the preferred global catalog.

Refer this article:
http://support.microsoft.com/kb/977960

Hope this helps,
Shree
0
 
southwestsixteenAuthor Commented:
Thanks Shree. I'll check it out this evening and let you know.
0
 
southwestsixteenAuthor Commented:
No solution found.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.