Windows Forum

Ask something
Discussion Locked

error when running DCDiag.exe

0 helpful
6 replies

by able-admin

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

returns error:

dcdiag.exe - Entry Point Not Found : The procedure entry point DsIsMangledDnW could not be located in the dynamic link library NTDSAPI.dll.

does it have to be run from the PDC-E FSMO role holder? or will any Domain Controller do? The reason I ask is, I've used this command on my main DC for years without a problem. I recently reorganized the FSMO roles and now it fails on that computer (only holding the roles of "Schema, Domain naming master"). the command works fine on the new PDC-E holder, however I also just installed the support tools on that server to test it.

can anyone verify this? dcdiag.exe works on DC not holding PDC-E role?

an ideas?

6 replies

by curlergirl

I have never heard of any such restriction for using dcdiag. Since it's a tool that's supposed to be used to check the status of a domain controller, it wouldn't make sense that it would be restricted to domain controllers with certain roles. Hope this helps!

by joseph moore

Did you see Technet article 320063? It states, "Additionally, any domain controller that is an authoritative master (that has a writable copy) of a particular container, or is a non-transitive (direct replication) partner of the testing server passes the topology test and is not listed in the list of disconnected servers."

It lists a fix for the DLL you mentioned in your error message, but it is one of those fixes that you have to pay Microsoft for.

Here is the URL:
http://support.microsoft.com/default.aspx?scid=kb;en-us;320063
(please remove any spaces)

hope this helps

by able-admin

thanx, but I believe this issue was delt with by the SP3 support tools release. Still having problems

by spanky

Check the version of NTDSAPI.dll against a known good machine. If it's a different version, patch the failing machine with the hotfix that was previously listed (it may not be included in the service pack). The fix looks like it's free from Microsoft, but requires that you call them to request it.

This discussion is closed to new replies.