DSASTAT

  • Thread starter Thread starter Ryan Rinehart
  • Start date Start date
R

Ryan Rinehart

I can run dsastat just fine between all DCs in 2 of my 4 sites. When I
try to run it against DCs in the other 2 sites, i get the following error:

C:\Program Files\Support Tools>dsastat /s:server1;server2
Stat-Only mode.
Unsorted mode.
Opening connections...
server1...success.
Connecting to server1...
WARN:LocalException <0>: Cannot get ldapServiceName.
ERROR:Invalid MSFTEditor
FAIL: Cannot initialize MsftEditor. Aborting...
FAIL: Unknown error. Could not locate Critical server


I can ping this server and connect to it with AD users and computers to use
AD, but I get this error when I try to run dsastat. Do I need to have any
special ports open for this tool? The other DCs all match up ok, just these
2 won't let me run the trace. There is a firewall between us, but since I
can open AD on them, I didn't think the port for LDAP would be the issue.
Is there something I can do to see why I am getting this error?


Ryan Rinehart
 
Hi Ryan-

We haven't seen this exact error syntax that I could find. Are you certain
that neither DC has any problems? I would consider getting a DCDIAG /V from
both of them to make sure that there are no problems at that end first.
 
Back
Top