Solved

REAPADMIN Operational Error

Posted on 2013-05-18
16
607 Views
Last Modified: 2013-05-19
HI,

We have two AD Controllers KOS and RHODOS. Due to migration of our VmWare ESXi servers
From 4.1 to 5.1 we moved RHODOS to Vmware EXI 5.1 and get the following errors on rhodos :
       
       
repadmin /replsummary /sort:delta  
netdom query /domain:wegaworld.local fsmo

Open in new window

     
	Experienced the following operational errors tryping to retrieve replication information
	58 - kos.wegaworld.local

Open in new window

     

Any Suggestions ?
screenshot-kos-rhodos-01.pdf
0
Comment
Question by:hgraesslin1
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
16 Comments
 
LVL 22

Expert Comment

by:Haresh Nikumbh
ID: 39177372
need to check couple of things

1) check if any Firewall is not blocking
2) check if DNS entry is correct on new server

if both are fine then check it out this link

http://social.technet.microsoft.com/Forums/en-US/winserverDS/thread/69690286-7493-44bd-98df-7dead5fae680
0
 
LVL 120

Assisted Solution

by:Andrew Hancock (VMware vExpert / EE MVE^2)
Andrew Hancock (VMware vExpert / EE MVE^2) earned 400 total points
ID: 39177436
I normally use

repadmin /replsum
0
 

Author Comment

by:hgraesslin1
ID: 39177490
well it was a clone and I moved the vm, not copied it.. so i think its not a firewall or dns problem or ?... maybe some windows updates...

repadmin /replsum nearly the same

repadmin /replsum		

Replication Summary Start Time: 2013-05-18 19:52:26
		
		Beginning data collection for replication summary, this may take awhile:
		  .....
		
		
		Source DSA          largest delta    fails/total %%   error
		 KOS                       54m:13s    0 /   5    0
		
		
		Destination DSA     largest delta    fails/total %%   error
		 RHODOS                    54m:14s    0 /   5    0
		
		
		Experienced the following operational errors trying to retrieve replication inf
		rmation:
		          58 - kos.wegaworld.local

Open in new window

0
Does Powershell have you tied up in knots?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
LVL 120
ID: 39177544
can you explain in detail how you moved

From 4.1 to 5.1 we moved RHODOS to Vmware EXI 5.1

also dcdiag, will also help you, any event logs errors?
0
 

Author Comment

by:hgraesslin1
ID: 39177580
I do  not really understand, but I inserted in the hosts file an entry of
the server the replysummy has an error

192.x.x.x     kos.wegaworld.local

good or bad news ?

repadmin /replsummary /sort:delta
Replication Summary Start Time: 2013-05-18 21:19:36

Beginning data collection for replication summary, this may take awhile:
  .....


Source DSA          largest delta    fails/total %%   error
 RHODOS                    26m:39s    0 /   5    0
 KOS                       21m:23s    0 /   5    0


Destination DSA     largest delta    fails/total %%   error
 KOS                       26m:39s    0 /   5    0
 RHODOS                    21m:23s    0 /   5    0

Open in new window

0
 

Author Comment

by:hgraesslin1
ID: 39177583
How I moved :
I simply used a tool ... Trilead software to replicate the VM

and then on the new ESX i told the vSphere that I moved the machine.
0
 
LVL 120

Assisted Solution

by:Andrew Hancock (VMware vExpert / EE MVE^2)
Andrew Hancock (VMware vExpert / EE MVE^2) earned 400 total points
ID: 39177669
Okay, the IP Address or Network Interface has not changed in the VM?

Check all network information has not changed.

can you ping via fqdn both DCs from each other?

what is output from DCDIAG
0
 
LVL 120
ID: 39177673
that's good it's replicating fine now.....

last delta approx 20 mins ago, no errors or failures

it would seem maybe issue with DNS
0
 
LVL 9

Assisted Solution

by:Zenvenky
Zenvenky earned 100 total points
ID: 39178077
58 - kos.wegaworld.local error 58 refers to manually created connection objects under Sites and Services. It also refers AD related ports are blocked / filtered at Firewall / router / Switch.

If there is a manually created connections there, then delete them and let KCC take care of it. Run repadmin /kcc * to fix it. If AD related ports are blocked, check with PortQryUI to know exact issue.

RPC server Unavailable
0
 

Author Comment

by:hgraesslin1
ID: 39178180
repadmin /kcc *

Repadmin: running command /kcc against full DC kos.wegaworld.local
Default-First-Site-Name
Current Site Options: (none)
Consistency check on kos.wegaworld.local successful.

Repadmin: running command /kcc against full DC RHODOS.wegaworld.local
Default-First-Site-Name
Current Site Options: (none)
Consistency check on RHODOS.wegaworld.local successful.

Open in new window

   




dcdiag
 

Directory Server Diagnosis

 

Performing initial setup:

   Trying to find home server...

   Home Server = RHODOS

   * Identified AD Forest.

   Done gathering initial info.

 

Doing initial required tests

 

   Testing server: Default-First-Site-Name\RHODOS

      Starting test: Connectivity

         The host 6b1317cb-1af8-4f1c-8b02-6df30225a8f6._msdcs.wegaworld.local

         could not be resolved to an IP address. Check the DNS server, DHCP,

         server name, etc.

         ......................... RHODOS failed test Connectivity

 

Doing primary tests

 

   Testing server: Default-First-Site-Name\RHODOS

      Skipping all tests, because server RHODOS is not responding to directory

      service requests.

 

 

   Running partition tests on : ForestDnsZones

      Starting test: CheckSDRefDom

         ......................... ForestDnsZones passed test CheckSDRefDom

      Starting test: CrossRefValidation

         ......................... ForestDnsZones passed test

         CrossRefValidation

 

   Running partition tests on : DomainDnsZones

      Starting test: CheckSDRefDom

         ......................... DomainDnsZones passed test CheckSDRefDom

      Starting test: CrossRefValidation

         ......................... DomainDnsZones passed test

         CrossRefValidation

 

   Running partition tests on : Sche...

Open in new window

0
 

Author Comment

by:hgraesslin1
ID: 39178211
better now, changed DNS Entry in Network card to local dns server, maybe this problem is not due to vmware move....

C:\temp>dcdiag

Directory Server Diagnosis

Performing initial setup:
   Trying to find home server...
   Home Server = RHODOS
   * Identified AD Forest.
   Done gathering initial info.

Doing initial required tests

   Testing server: Default-First-Site-Name\RHODOS
      Starting test: Connectivity
         ......................... RHODOS passed test Connectivity

Doing primary tests

Open in new window


but  dcdiag /test:dns
   Testing server: Default-First-Site-Name\RHODOS

      Starting test: DNS

         DNS Tests are running and not hung. Please wait a few minutes...
 ERROR: NO DNS servers for IPV6 stack was found
         ......................... RHODOS passed test DNS

   Running partition tests on : ForestDnsZones

   Running partition tests on : DomainDnsZones

   Running partition tests on : Schema

   Running partition tests on : Configuration

   Running partition tests on : wegaworld

   Running enterprise tests on : wegaworld.local
      Starting test: DNS
         Test results for domain controllers:

            DC: RHODOS.wegaworld.local
            Domain: wegaworld.local


               TEST: Basic (Basc)
                  Warning: The AAAA record for this DC was not found

               TEST: Forwarders/Root hints (Forw)
                  Error: Forwarders list has invalid forwarder: 62.2.17.60 (<nam
e unavailable>)
                  Error: Forwarders list has invalid forwarder: 62.2.17.61 (<nam
e unavailable>)

Open in new window



what do you think ... fixed ??
0
 
LVL 120
ID: 39178232
check replication after a few hours (4 hours)

any event log errors appearing?
0
 

Author Comment

by:hgraesslin1
ID: 39178318
what ist an appropriate check ?
dcdiag /test:dns
repadmin /replsummary /sort:delta
0
 
LVL 120
ID: 39178336
Yes it is, but you will see after 4 hours, if you have no continued rteplication errors.

We always like to wait, doublecheck and check afterwards, if everything is replicating ok.
0
 

Author Comment

by:hgraesslin1
ID: 39178430
               TEST: Forwarders/Root hints (Forw)
                  Error: Forwarders list has invalid forwarder: 62.2.17.60 (<nam
e unavailable>)
                  Error: Forwarders list has invalid forwarder: 62.2.17.61 (<nam
e unavailable>)

Open in new window


fixed because we have two internet providers and on this server the wrong external dns servers are specified

only three warnings now ...

Network Adapter
      [00000006] Intel(R) PRO/1000 MT Network Connection:
         Warning:
         Missing AAAA record at DNS server 192.168.0.6:
         RHODOS.wegaworld.local

         Warning:
         Missing AAAA record at DNS server 192.168.0.6:

         gc._msdcs.xxx.local

   Warning: Record Registrations not found in some network adapters

Open in new window

0
 
LVL 120

Accepted Solution

by:
Andrew Hancock (VMware vExpert / EE MVE^2) earned 400 total points
ID: 39178455
so replication and AD is working fine.
0

Featured Post

Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

A company’s centralized system that manages user data, security, and distributed resources is often a focus of criminal attention. Active Directory (AD) is no exception. In truth, it’s even more likely to be targeted due to the number of companies …
Always backup Domain, SYSVOL etc.using processes according to Microsoft Best Practices. This is meant as a disaster recovery process for small environments that did not implement backup processes and did not run a secondary domain controller that ne…
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…
Microsoft Active Directory, the widely used IT infrastructure, is known for its high risk of credential theft. The best way to test your Active Directory’s vulnerabilities to pass-the-ticket, pass-the-hash, privilege escalation, and malware attacks …

730 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question