DCDiag produces errors

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi, I have two Win2k AD DC's (DC1 and DC2) and I'm preparing the network for
an Exchange migration.
When I run DCDiag these are the errors:
DC1 - failed test frsevent
DC2 - failed test frsevent and failed test kccevent

Based on this information, can you tell what I need to do to clear up these
errors before I move on to the Exchange Migration?

thanks,
Robert
 
Sorry, no I misspoke. I Haven't run forestprep or domain prep yet. I thought
I'd run DCDiag first to get an idea of where I stand.
DNS is fully operational.
 
I took a look at your document and I don't think it pertains to me.
I'm not quite ready to install Exchange just yet, but would like to soon.
I'm just trying to determine why i could be getting these particular errors.

DC1 - failed test frsevent
DC2 - failed test frsevent and failed test kccevent
 
You are correct, don't run forestprep or domainprep until these issues are
resolved. If replication isn't working properly then all your modifications
to the domain may not be replicated properly.

The info you provided really doesn't provide much info to the newsgroup.
Both of these errors refer to errors in replication that are listed in the
system event log. You should post those errors out here so a better
understanding of what is happening.
 
Paul, this error is coming into the logs (File Replication Service event
log). Source- NtFrs, Event - 13508
LURTZ to MERRY for c:\winnt\sysvol\domain using the DNS name lurtz.hoby.net.
FRS will keep retrying.
Following are some of the reasons you would see this warning.

[1] FRS can not correctly resolve the DNS name lurtz.hoby.net from this
computer.
[2] FRS is not running on lurtz.hoby.net.
[3] The topology information in the Active Directory for this replica has
not yet replicated to all the Domain Controllers.

Lurtz is a previous AD DC not on the network anymore and will not be coming
back to the network. Since the above mentioned error is related to the former
server Lurtz, then I'll have to seize the role of Infrastructure Master
before running NTDSutil and then do a metabase cleanup....does that sound
right?
Also, with the other error....."failed test kccevent" from the DCDiag
output, there is what appears to be a related error and only shows up on the
second AD DC (non-global catalog) event log. Source- NTDS KCC, Event - 1265.
It also references Lurtz (the former AD DC).
The attempt to establish a replication link with parameters

Partition: DC=hoby,DC=net
Source DSA DN: CN=NTDS
Settings,CN=LURTZ,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=hoby,DC=net
Source DSA Address: ccdf3263-46c2-476d-8a3a-699fb269f654._msdcs.hoby.net
Inter-site Transport (if any):
failed with the following status:
The DSA operation is unable to proceed because of a DNS lookup failure.

Does it sound like seizing the Operations Master role Infrastructure Master
from Lurtz (I've confirmed that Lurtz is the owner through AD Users and
Computers) and then doing a metabase cleanup with NTDSutil will clear up
these errors on DCDiag?
Thank you much.
 
If LURTZ has been properly removed as a DC in the AD domain (hoby.net), these
errors should not appear.

Nevertheless, the steps described in the following KB may be necessary:

http://support.microsoft.com/default.aspx?scid=kb;en-us;216498


In addition, ensure that all DNS references to it (forward and reverse
lookup zone) must also be manually deleted, including it being designated as
a Name Server (NS) for the AD domain.

It is vital to clean up AD errors before attempting to introduce Exchange
into the organization.

HTH.



RHS said:
Paul, this error is coming into the logs (File Replication Service event
log). Source- NtFrs, Event - 13508
LURTZ to MERRY for c:\winnt\sysvol\domain using the DNS name lurtz.hoby.net.
FRS will keep retrying.
Following are some of the reasons you would see this warning.

[1] FRS can not correctly resolve the DNS name lurtz.hoby.net from this
computer.
[2] FRS is not running on lurtz.hoby.net.
[3] The topology information in the Active Directory for this replica has
not yet replicated to all the Domain Controllers.

Lurtz is a previous AD DC not on the network anymore and will not be coming
back to the network. Since the above mentioned error is related to the former
server Lurtz, then I'll have to seize the role of Infrastructure Master
before running NTDSutil and then do a metabase cleanup....does that sound
right?
Also, with the other error....."failed test kccevent" from the DCDiag
output, there is what appears to be a related error and only shows up on the
second AD DC (non-global catalog) event log. Source- NTDS KCC, Event - 1265.
It also references Lurtz (the former AD DC).
The attempt to establish a replication link with parameters

Partition: DC=hoby,DC=net
Source DSA DN: CN=NTDS
Settings,CN=LURTZ,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=hoby,DC=net
Source DSA Address: ccdf3263-46c2-476d-8a3a-699fb269f654._msdcs.hoby.net
Inter-site Transport (if any):
failed with the following status:
The DSA operation is unable to proceed because of a DNS lookup failure.

Does it sound like seizing the Operations Master role Infrastructure Master
from Lurtz (I've confirmed that Lurtz is the owner through AD Users and
Computers) and then doing a metabase cleanup with NTDSutil will clear up
these errors on DCDiag?
Thank you much.





Paul Bergson said:
You are correct, don't run forestprep or domainprep until these issues are
resolved. If replication isn't working properly then all your modifications
to the domain may not be replicated properly.

The info you provided really doesn't provide much info to the newsgroup.
Both of these errors refer to errors in replication that are listed in the
system event log. You should post those errors out here so a better
understanding of what is happening.

--

Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA

This posting is provided "AS IS" with no warranties, and confers no rights.
Click to expand...
Click to expand...
 
Desmond, the problem is that Lurtz was not properly moved from the network.

Robert

Desmond Lee said:
If LURTZ has been properly removed as a DC in the AD domain (hoby.net), these
errors should not appear.

Nevertheless, the steps described in the following KB may be necessary:

http://support.microsoft.com/default.aspx?scid=kb;en-us;216498


In addition, ensure that all DNS references to it (forward and reverse
lookup zone) must also be manually deleted, including it being designated as
a Name Server (NS) for the AD domain.

It is vital to clean up AD errors before attempting to introduce Exchange
into the organization.

HTH.



RHS said:
Paul, this error is coming into the logs (File Replication Service event
log). Source- NtFrs, Event - 13508
LURTZ to MERRY for c:\winnt\sysvol\domain using the DNS name lurtz.hoby.net.
FRS will keep retrying.
Following are some of the reasons you would see this warning.

[1] FRS can not correctly resolve the DNS name lurtz.hoby.net from this
computer.
[2] FRS is not running on lurtz.hoby.net.
[3] The topology information in the Active Directory for this replica has
not yet replicated to all the Domain Controllers.

Lurtz is a previous AD DC not on the network anymore and will not be coming
back to the network. Since the above mentioned error is related to the former
server Lurtz, then I'll have to seize the role of Infrastructure Master
before running NTDSutil and then do a metabase cleanup....does that sound
right?
Also, with the other error....."failed test kccevent" from the DCDiag
output, there is what appears to be a related error and only shows up on the
second AD DC (non-global catalog) event log. Source- NTDS KCC, Event - 1265.
It also references Lurtz (the former AD DC).
The attempt to establish a replication link with parameters

Partition: DC=hoby,DC=net
Source DSA DN: CN=NTDS
Settings,CN=LURTZ,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=hoby,DC=net
Source DSA Address: ccdf3263-46c2-476d-8a3a-699fb269f654._msdcs.hoby.net
Inter-site Transport (if any):
failed with the following status:
The DSA operation is unable to proceed because of a DNS lookup failure.

Does it sound like seizing the Operations Master role Infrastructure Master
from Lurtz (I've confirmed that Lurtz is the owner through AD Users and
Computers) and then doing a metabase cleanup with NTDSutil will clear up
these errors on DCDiag?
Thank you much.





Paul Bergson said:
You are correct, don't run forestprep or domainprep until these issues are
resolved. If replication isn't working properly then all your modifications
to the domain may not be replicated properly.

The info you provided really doesn't provide much info to the newsgroup.
Both of these errors refer to errors in replication that are listed in the
system event log. You should post those errors out here so a better
understanding of what is happening.

--

Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA

This posting is provided "AS IS" with no warranties, and confers no rights.



Hi, I have two Win2k AD DC's (DC1 and DC2) and I'm preparing the network
for
an Exchange migration.
When I run DCDiag these are the errors:
DC1 - failed test frsevent
DC2 - failed test frsevent and failed test kccevent

Based on this information, can you tell what I need to do to clear up
these
errors before I move on to the Exchange Migration?

thanks,
Robert
Click to expand...
Click to expand...
Click to expand...
 
If that is the case, go ahead and follow carefully the steps described in
the KB.
Thereafter AD should be happy to welcome Exchange :)

Good luck and keep us posted!


RHS said:
Desmond, the problem is that Lurtz was not properly moved from the network.

Robert

Desmond Lee said:
If LURTZ has been properly removed as a DC in the AD domain (hoby.net), these
errors should not appear.

Nevertheless, the steps described in the following KB may be necessary:

http://support.microsoft.com/default.aspx?scid=kb;en-us;216498


In addition, ensure that all DNS references to it (forward and reverse
lookup zone) must also be manually deleted, including it being designated as
a Name Server (NS) for the AD domain.

It is vital to clean up AD errors before attempting to introduce Exchange
into the organization.

HTH.



RHS said:
Paul, this error is coming into the logs (File Replication Service event
log). Source- NtFrs, Event - 13508
LURTZ to MERRY for c:\winnt\sysvol\domain using the DNS name lurtz.hoby.net.
FRS will keep retrying.
Following are some of the reasons you would see this warning.

[1] FRS can not correctly resolve the DNS name lurtz.hoby.net from this
computer.
[2] FRS is not running on lurtz.hoby.net.
[3] The topology information in the Active Directory for this replica has
not yet replicated to all the Domain Controllers.

Lurtz is a previous AD DC not on the network anymore and will not be coming
back to the network. Since the above mentioned error is related to the former
server Lurtz, then I'll have to seize the role of Infrastructure Master
before running NTDSutil and then do a metabase cleanup....does that sound
right?
Also, with the other error....."failed test kccevent" from the DCDiag
output, there is what appears to be a related error and only shows up on the
second AD DC (non-global catalog) event log. Source- NTDS KCC, Event - 1265.
It also references Lurtz (the former AD DC).
The attempt to establish a replication link with parameters

Partition: DC=hoby,DC=net
Source DSA DN: CN=NTDS
Settings,CN=LURTZ,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=hoby,DC=net
Source DSA Address: ccdf3263-46c2-476d-8a3a-699fb269f654._msdcs.hoby.net
Inter-site Transport (if any):
failed with the following status:
The DSA operation is unable to proceed because of a DNS lookup failure.

Does it sound like seizing the Operations Master role Infrastructure Master
from Lurtz (I've confirmed that Lurtz is the owner through AD Users and
Computers) and then doing a metabase cleanup with NTDSutil will clear up
these errors on DCDiag?
Thank you much.





:

You are correct, don't run forestprep or domainprep until these issues are
resolved. If replication isn't working properly then all your modifications
to the domain may not be replicated properly.

The info you provided really doesn't provide much info to the newsgroup.
Both of these errors refer to errors in replication that are listed in the
system event log. You should post those errors out here so a better
understanding of what is happening.

--

Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA

This posting is provided "AS IS" with no warranties, and confers no rights.



Hi, I have two Win2k AD DC's (DC1 and DC2) and I'm preparing the network
for
an Exchange migration.
When I run DCDiag these are the errors:
DC1 - failed test frsevent
DC2 - failed test frsevent and failed test kccevent

Based on this information, can you tell what I need to do to clear up
these
errors before I move on to the Exchange Migration?

thanks,
Robert
Click to expand...
Click to expand...
Click to expand...
 
Thanks much Desmond, appreciate it.


Desmond Lee said:
If that is the case, go ahead and follow carefully the steps described in
the KB.
Thereafter AD should be happy to welcome Exchange :)

Good luck and keep us posted!


RHS said:
Desmond, the problem is that Lurtz was not properly moved from the network.

Robert

Desmond Lee said:
If LURTZ has been properly removed as a DC in the AD domain (hoby.net), these
errors should not appear.

Nevertheless, the steps described in the following KB may be necessary:

http://support.microsoft.com/default.aspx?scid=kb;en-us;216498


In addition, ensure that all DNS references to it (forward and reverse
lookup zone) must also be manually deleted, including it being designated as
a Name Server (NS) for the AD domain.

It is vital to clean up AD errors before attempting to introduce Exchange
into the organization.

HTH.



:

Paul, this error is coming into the logs (File Replication Service event
log). Source- NtFrs, Event - 13508
LURTZ to MERRY for c:\winnt\sysvol\domain using the DNS name lurtz.hoby.net.
FRS will keep retrying.
Following are some of the reasons you would see this warning.

[1] FRS can not correctly resolve the DNS name lurtz.hoby.net from this
computer.
[2] FRS is not running on lurtz.hoby.net.
[3] The topology information in the Active Directory for this replica has
not yet replicated to all the Domain Controllers.

Lurtz is a previous AD DC not on the network anymore and will not be coming
back to the network. Since the above mentioned error is related to the former
server Lurtz, then I'll have to seize the role of Infrastructure Master
before running NTDSutil and then do a metabase cleanup....does that sound
right?
Also, with the other error....."failed test kccevent" from the DCDiag
output, there is what appears to be a related error and only shows up on the
second AD DC (non-global catalog) event log. Source- NTDS KCC, Event - 1265.
It also references Lurtz (the former AD DC).
The attempt to establish a replication link with parameters

Partition: DC=hoby,DC=net
Source DSA DN: CN=NTDS
Settings,CN=LURTZ,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=hoby,DC=net
Source DSA Address: ccdf3263-46c2-476d-8a3a-699fb269f654._msdcs.hoby.net
Inter-site Transport (if any):
failed with the following status:
The DSA operation is unable to proceed because of a DNS lookup failure.

Does it sound like seizing the Operations Master role Infrastructure Master
from Lurtz (I've confirmed that Lurtz is the owner through AD Users and
Computers) and then doing a metabase cleanup with NTDSutil will clear up
these errors on DCDiag?
Thank you much.





:

You are correct, don't run forestprep or domainprep until these issues are
resolved. If replication isn't working properly then all your modifications
to the domain may not be replicated properly.

The info you provided really doesn't provide much info to the newsgroup.
Both of these errors refer to errors in replication that are listed in the
system event log. You should post those errors out here so a better
understanding of what is happening.

--

Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA

This posting is provided "AS IS" with no warranties, and confers no rights.



Hi, I have two Win2k AD DC's (DC1 and DC2) and I'm preparing the network
for
an Exchange migration.
When I run DCDiag these are the errors:
DC1 - failed test frsevent
DC2 - failed test frsevent and failed test kccevent

Based on this information, can you tell what I need to do to clear up
these
errors before I move on to the Exchange Migration?

thanks,
Robert
Click to expand...
Click to expand...
Click to expand...
 
Back
Top