how to best trouble shoot "The RPC server is unavailable"

I am not an expert on this, what is the next step to troubleshoot?




            Naming Context: DC=xyz,DC=local

            The replication generated an error (1722):

            The RPC server is unavailable.

            The failure occurred at 2010-03-20 19:52:50.

            The last success occurred at 2010-03-06 11:47:06.

            346 failures have occurred since the last success.

            The source remains down. Please check the machine.

         ......................... xyz-Dom02 failed test Replications

         ......................... xyz-Dom02 failed test SystemLog

         There are warning or error events within the last 24 hours after the

         SYSVOL has been shared.  Failing SYSVOL replication problems may cause

         Group Policy problems.
         ......................... xyz-AV01 failed test DFSREvent

         An error event occurred.  EventID: 0xC0000748

            Time Generated: 03/20/2010   19:55:09

            Event String:

            This is the replication status for the following directory partition on this directory server.


         An error event occurred.  EventID: 0xC0000748

            Time Generated: 03/20/2010   19:55:09

            Event String:

            This is the replication status for the following directory partition on this directory server.


         An error event occurred.  EventID: 0xC0000748

            Time Generated: 03/20/2010   19:55:09

            Event String:

            This is the replication status for the following directory partition on this directory server.


         An error event occurred.  EventID: 0xC0000748

            Time Generated: 03/20/2010   19:55:09

            Event String:

            This is the replication status for the following directory partition on this directory server.


         An error event occurred.  EventID: 0xC0000748

            Time Generated: 03/20/2010   19:55:09

            Event String:

            This is the replication status for the following directory partition on this directory server.


         ......................... xyz-AV01 failed test KccEvent

         [Replications Check,xyz-AV01] A recent replication attempt failed:

         

         ......................... xyz-AV01 failed test Replications

         There are warning or error events within the last 24 hours after the

         SYSVOL has been shared.  Failing SYSVOL replication problems may cause

         Group Policy problems.
         ......................... xyz-DC07 failed test DFSREvent
LVL 1
NAMEWITHELD12Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
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.

Mike KlineCommented:
There is an updated technet article for RPC errors

http://support.microsoft.com/kb/2102154

However in your case that DC hasn't replicated since

The last success occurred at 2010-03-06 11:47:06.

If that date is accurate and it hasn't replicated in almost two years then you are way passed the tombstone lifetime.

In that case you need to clean up that dead DC http://technet.microsoft.com/en-us/library/cc816907(v=ws.10).aspx 

took the below from the askds blog to save on typing :)

1) Forcefully demote the DC by running dcpromo /forceremoval. This will remove AD from the server without attempting to replicate any changes off. Once it is done and you reboot the server and it will be a standalone serve in a workgroup.

2) Run a metadata cleanup of the DC that was demoted per KB article 216498 on one of the replication partners.

3) If the demoted server held any of the FSMO (Flexible Single Master Operations) roles then use the KB article 255504 to seize the roles to another DC.

4) Once replication has occurred end to end in your environment you can rejoin the demoted server back to the domain then promote to a DC.

Thanks

Mike
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
NAMEWITHELD12Author Commented:
well it is actually 2012 where is says 2010 so that was like 2 weeks ago , so if i can get this error to work then i guess it can sync back with ad correctly >?


i am not sure what to do next , thanks for all the help!!! it is greatly appreciated!!!
0
Mike KlineCommented:
ok good, then start going through the steps in the KB, make sure to go through them all, lots of good steps to check ports and other items.

Thanks

Mike
0
NAMEWITHELD12Author Commented:
thank you Mike !

I will and post my findiingS
0
Mike KlineCommented:
Good work, what did the problem end up being?

Thanks


Mike
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
Active Directory

From novice to tech pro — start learning today.