Unable to add exernal contacts in Exchange 2010 DC error

Hi trying to add an external contact using the exchange 2010 MMC, under contacts, i get to the last page and get the following issue

Summary: 1 item(s). 0 succeeded, 1 failed.
Elapsed time: 00:00:01


Ian Scandrett
Failed

Error:
Active Directory operation failed on WSCDC2.cnet.wsc.nsw.gov.au. This error could have been caused by user input or by the Active Directory server being unavailable. Please retry at a later time. Additional information: Additional information: The global catalog verification failed. The global catalog is not available or does not support the operation. Some part of the directory is currently not available.
Active directory response: 000020E1: SvcErr: DSID-03200674, problem 5002 (UNAVAILABLE), data 0
.

The server is unavailable.
Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.140).aspx?v=14.2.247.1&t=exchgf1&e=ms.exch.err.Ex872538

Exchange Management Shell command attempted:
New-MailContact -ExternalEmailAddress 'SMTP:ian@justfixit.org.au' -Name 'Ian Scandrett' -Alias 'iscandrettext' -FirstName 'Ian' -Initials '' -LastName 'Scandrett'

Elapsed Time: 00:00:00




Not sure what is going on here, I think there may be some issues going on been noticing some other strange AD issues lately like enabling a disabled account using the AD mmc on my PC dosnt actual go though i have to rdp to one of the DCs and do it

I have two DCs both server 2008 r2, 1 is a VM and 1 is physical
I have two Exchange 2010 servers, both VMs both 2008 r2
wsc-itAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

jrhelgesonCommented:
You are having Active Directory replication issues... what does your AD topology look like?

Run the following commands from each DC:
repadmin /syncall /AePdq
repadmin /syncall /Aedq

Report any errors.

Launch ADSIEDIT.msc
Under the Default naming context, go to System | File Replication service | Domain System Volume (SYSVOL share) container -
Look at named objects...
DO you see any DC's that do not belong?  Do you see anything missing?
0
Exchange_GeekCommented:
I suppose DC WSCDC2.cnet.wsc.nsw.gov.au is one of the two DC.

Now, what you need to check is which DC is being the preferred DC with Exchange as-in Configuration DC Read: link

You can change the Config DC to another DC and check if that solves your mess, if it does - the earlier DC that was being chosen definitely had issues.

Next, run the following cmdlet on your Exchange Server to understand what is the mess with this DC.

- dcdiag /s: DCName
- netdiag /v
- Run Exchange Best Practice Analyzer Tool from within Exchange Management Console Toolbox.
- Check for MSExchange ADAccess errors on your Exchange box, they would start with 21** in application log.

Hope the above helps you start troubleshooting. Please provide feedback, so we can help you further.

Regards,
Exchange_Geek
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
wsc-itAuthor Commented:
DC1 repadmin /syncall /AePdq

Syncing all NC's held on WSCDC1.
Syncing partition: DC=ForestDnsZones,DC=cnet,DC=wsc,DC=nsw,DC=gov,DC=au

SyncAll reported the following errors:
Error contacting server CN=NTDS Settings,CN=WSCDC2,CN=Servers,CN=WSC,CN=Sites,CN
=Configuration,DC=cnet,DC=wsc,DC=nsw,DC=gov,DC=au (network error): 1722 (0x6ba):

    The RPC server is unavailable.

Syncing partition: DC=DomainDnsZones,DC=cnet,DC=wsc,DC=nsw,DC=gov,DC=au

SyncAll reported the following errors:
Error contacting server CN=NTDS Settings,CN=WSCDC2,CN=Servers,CN=WSC,CN=Sites,CN
=Configuration,DC=cnet,DC=wsc,DC=nsw,DC=gov,DC=au (network error): 1722 (0x6ba):

    The RPC server is unavailable.

Syncing partition: CN=Schema,CN=Configuration,DC=cnet,DC=wsc,DC=nsw,DC=gov,DC=au


SyncAll reported the following errors:
Error contacting server CN=NTDS Settings,CN=WSCDC2,CN=Servers,CN=WSC,CN=Sites,CN
=Configuration,DC=cnet,DC=wsc,DC=nsw,DC=gov,DC=au (network error): 1722 (0x6ba):

    The RPC server is unavailable.

Syncing partition: CN=Configuration,DC=cnet,DC=wsc,DC=nsw,DC=gov,DC=au

SyncAll reported the following errors:
Error contacting server CN=NTDS Settings,CN=WSCDC2,CN=Servers,CN=WSC,CN=Sites,CN
=Configuration,DC=cnet,DC=wsc,DC=nsw,DC=gov,DC=au (network error): 1722 (0x6ba):

    The RPC server is unavailable.

Syncing partition: DC=cnet,DC=wsc,DC=nsw,DC=gov,DC=au

SyncAll reported the following errors:
Error contacting server CN=NTDS Settings,CN=WSCDC2,CN=Servers,CN=WSC,CN=Sites,CN
=Configuration,DC=cnet,DC=wsc,DC=nsw,DC=gov,DC=au (network error): 1722 (0x6ba):

    The RPC server is unavailable.


and

DC1 repadmin /syncall /aedq

Syncing all NC's held on WSCDC1.
Syncing partition: DC=ForestDnsZones,DC=cnet,DC=wsc,DC=nsw,DC=gov,DC=au

SyncAll reported the following errors:
Error contacting server CN=NTDS Settings,CN=WSCDC2,CN=Servers,CN=WSC,CN=Sites,CN
=Configuration,DC=cnet,DC=wsc,DC=nsw,DC=gov,DC=au (network error): 1722 (0x6ba):

    The RPC server is unavailable.

Syncing partition: DC=DomainDnsZones,DC=cnet,DC=wsc,DC=nsw,DC=gov,DC=au

SyncAll reported the following errors:
Error contacting server CN=NTDS Settings,CN=WSCDC2,CN=Servers,CN=WSC,CN=Sites,CN
=Configuration,DC=cnet,DC=wsc,DC=nsw,DC=gov,DC=au (network error): 1722 (0x6ba):

    The RPC server is unavailable.

Syncing partition: CN=Schema,CN=Configuration,DC=cnet,DC=wsc,DC=nsw,DC=gov,DC=au


SyncAll reported the following errors:
Error contacting server CN=NTDS Settings,CN=WSCDC2,CN=Servers,CN=WSC,CN=Sites,CN
=Configuration,DC=cnet,DC=wsc,DC=nsw,DC=gov,DC=au (network error): 1722 (0x6ba):

    The RPC server is unavailable.

Syncing partition: CN=Configuration,DC=cnet,DC=wsc,DC=nsw,DC=gov,DC=au

SyncAll reported the following errors:
Error contacting server CN=NTDS Settings,CN=WSCDC2,CN=Servers,CN=WSC,CN=Sites,CN
=Configuration,DC=cnet,DC=wsc,DC=nsw,DC=gov,DC=au (network error): 1722 (0x6ba):

    The RPC server is unavailable.

Syncing partition: DC=cnet,DC=wsc,DC=nsw,DC=gov,DC=au

SyncAll reported the following errors:
Error contacting server CN=NTDS Settings,CN=WSCDC2,CN=Servers,CN=WSC,CN=Sites,CN
=Configuration,DC=cnet,DC=wsc,DC=nsw,DC=gov,DC=au (network error): 1722 (0x6ba):

    The RPC server is unavailable.
0
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

wsc-itAuthor Commented:
DC2 repadmin /syncall /AePdq

DsBindWithCred to WSCDC2 failed with status 1722 (0x6ba):
    The RPC server is unavailable.

and

repadmin /syncall /aedq

DsBindWithCred to WSCDC2 failed with status 1722 (0x6ba):
    The RPC server is unavailable.
0
wsc-itAuthor Commented:
Rebooted DC2 and now the errors seem to have gone away, What service do i need to monitor for that???

Also, i tried adding the contact again and now get access denied?

Summary: 1 item(s). 0 succeeded, 1 failed.
Elapsed time: 00:00:00


firstname surname
Failed

Error:
Active Directory operation failed on WSCDC2.cnet.wsc.nsw.gov.au. This error is not retriable. Additional information: Access is denied.
Active directory response: 00000005: SecErr: DSID-031521D0, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0


The user has insufficient access rights.
Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.140).aspx?v=14.2.247.1&t=exchgf1&e=ms.exch.err.Ex6AE46B

Exchange Management Shell command attempted:
New-MailContact -ExternalEmailAddress 'SMTP:user@email.com-Name 'firstname(External)' -Alias 'alias name' -FirstName 'first' -Initials '' -LastName 'last'

Elapsed Time: 00:00:00
0
jrhelgesonCommented:
It is the NTFRS service - but that really doesn't appear to be the issue. We are dealing with Active Directory problems here.  If AD hasn't been replicating for some time, then the records can be tomstoned and you'll never start replication without manual intervention.  We need to figure out why replication broke in the first place, and we need to get it working again.

As an aside, this is no longer an exchange issue, but an Active Directory issue.

When a server reboots, it will restart the NTFRS sync, but it will likely fail again.

What does your AD Topology look like? Do you have only 2 Domain Controllers?

Now that you've rebooted, lets try running the commands again:
repadmin /syncall /AePdq
repadmin /syncall /Aedq

Report any errors.

ALSO - PLEASE MAKE SURE YOU DO THIS:
Launch ADSIEDIT.msc
Under the Default naming context, go to System | File Replication service | Domain System Volume (SYSVOL share) container -
Look at named objects...
DO you see any DC's that do not belong?  Do you see anything missing? (You should see a listing for each DC you have, and there may be ghosts lingering there that need to be deleted.)
0
Exchange_GeekCommented:
RPC Server is unavailable is being seen simply cause the DC is not reachable.

Were you able to change the Config DC and then re-try with your test?

Regards,
Exchange_Geek
0
wsc-itAuthor Commented:
Please see below results for commands run

DC2:

repadmin /syncall /AePdq

Syncing all NC's held on WSCDC2.
Syncing partition: DC=ForestDnsZones,DC=cnet,DC=wsc,DC=nsw,DC=gov,DC=au
SyncAll terminated with no errors.

Syncing partition: DC=DomainDnsZones,DC=cnet,DC=wsc,DC=nsw,DC=gov,DC=au
SyncAll terminated with no errors.

Syncing partition: CN=Schema,CN=Configuration,DC=cnet,DC=wsc,DC=nsw,DC=gov,DC=au

SyncAll terminated with no errors.

Syncing partition: CN=Configuration,DC=cnet,DC=wsc,DC=nsw,DC=gov,DC=au
SyncAll terminated with no errors.

Syncing partition: DC=cnet,DC=wsc,DC=nsw,DC=gov,DC=au
SyncAll terminated with no errors.



repadmin /syncall /Aedq

Syncing all NC's held on WSCDC2.
Syncing partition: DC=ForestDnsZones,DC=cnet,DC=wsc,DC=nsw,DC=gov,DC=au
SyncAll terminated with no errors.

Syncing partition: DC=DomainDnsZones,DC=cnet,DC=wsc,DC=nsw,DC=gov,DC=au
SyncAll terminated with no errors.

Syncing partition: CN=Schema,CN=Configuration,DC=cnet,DC=wsc,DC=nsw,DC=gov,DC=au

SyncAll terminated with no errors.

Syncing partition: CN=Configuration,DC=cnet,DC=wsc,DC=nsw,DC=gov,DC=au
SyncAll terminated with no errors.

Syncing partition: DC=cnet,DC=wsc,DC=nsw,DC=gov,DC=au
SyncAll terminated with no errors.


DC1:

repadmin /syncall /AePdq

Syncing all NC's held on WSCDC1.
Syncing partition: DC=ForestDnsZones,DC=cnet,DC=wsc,DC=nsw,DC=gov,DC=au
SyncAll terminated with no errors.

Syncing partition: DC=DomainDnsZones,DC=cnet,DC=wsc,DC=nsw,DC=gov,DC=au
SyncAll terminated with no errors.

Syncing partition: CN=Schema,CN=Configuration,DC=cnet,DC=wsc,DC=nsw,DC=gov,DC=au

SyncAll terminated with no errors.

Syncing partition: CN=Configuration,DC=cnet,DC=wsc,DC=nsw,DC=gov,DC=au
SyncAll terminated with no errors.

Syncing partition: DC=cnet,DC=wsc,DC=nsw,DC=gov,DC=au
SyncAll terminated with no errors.


repadmin /syncall /Aedq

Syncing all NC's held on WSCDC1.
Syncing partition: DC=ForestDnsZones,DC=cnet,DC=wsc,DC=nsw,DC=gov,DC=au
SyncAll terminated with no errors.

Syncing partition: DC=DomainDnsZones,DC=cnet,DC=wsc,DC=nsw,DC=gov,DC=au
SyncAll terminated with no errors.

Syncing partition: CN=Schema,CN=Configuration,DC=cnet,DC=wsc,DC=nsw,DC=gov,DC=au

SyncAll terminated with no errors.

Syncing partition: CN=Configuration,DC=cnet,DC=wsc,DC=nsw,DC=gov,DC=au
SyncAll terminated with no errors.

Syncing partition: DC=cnet,DC=wsc,DC=nsw,DC=gov,DC=au
SyncAll terminated with no errors.

When I go into Adsedit and have a look at the File Replication Service it only shows my two domain controllers, there does not appear to be anything unusual in this section.
0
Exchange_GeekCommented:
I'm out of this thread. Good Luck guys.

Regards,
Exchange_Geek
0
jrhelgesonCommented:
At this point, check event logs for any AD errors on the DC's.
Within exchange, I would try simply rebooting the server, allow exchange to get new Kerberos tickets from the domain controllers that now appear to be working 'better'.
0
wsc-itAuthor Commented:
Hi Exchange_Geek

I changed the domain controller in the Organisation as per your post to the main domain controller and it now works I can create the External Record. I will run the commands and see what I can find on stats and post.
0
wsc-itAuthor Commented:
Thanks I will schedule a reboot tonight of the Exchange server and monitor to see how it goes
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.