I have recently been experiencing some problems with a SBS 2003 DC in that it would not replicate with its partner and the ntfrs service never managed to get to log event 13516. At the time I was using DCDIAG to help me find the problem. I decided that the issue was with the replication partner DC which, since it served little pupose in our organisation as a DC, I decided to demote. I was then in a catch 22 becuase I could not log on to the secondary DC to demote it because it claimed it could not find a DC! I then tried ADSiEdit to remove the secondary DC and although this seemed to get rid of it I still could get a 13516 event.
I eventually forced the replication to complete by changing the Burflags registry entry to D4 and manually restarting the ntfrs service. After that I was able to log on to the secondary DC and demote it properly.
Now I want to run DCDIAG on the main DC to confirm all is OK and this is all I get:
C:\Documents and Settings\Administrator.CTS>dcdiag /v
Domain Controller Diagnosis
Performing initial setup:
* Verifying that the local machine Chromis, is a DC.
* Connecting to directory service on server Chromis.
* Collecting site info.
Nothing else at all! I don't know where to start to rectify this. I am worried that I mat have screwed something with ADSiEdit but the DC seems to be working as expected.