Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The distinguished name specified for this replication operation is invalid #23

Closed
MichaelGrafnetter opened this issue Aug 22, 2016 · 2 comments

Comments

@MichaelGrafnetter
Copy link
Owner

commented Aug 22, 2016

A few users have reported that they sometimes see an error with message "The distinguished name specified for this replication operation is invalid" instead of "Access denied" when using the Get-ADReplAccount cmdlet.

@MichaelGrafnetter MichaelGrafnetter modified the milestones: 2.17, 2.19 Aug 22, 2016

@ars1s

This comment has been minimized.

Copy link

commented Sep 26, 2016

Any news about the issue?

@MichaelGrafnetter

This comment has been minimized.

Copy link
Owner Author

commented Oct 2, 2016

This bugfix will be present in the next release of DSInternals. It is actually a workaround, because Microsoft's API itself returns error DS_DRA_BAD_DN instead of DS_DRA_ACCESS_DENIED. So after encountering this error, I send another request to the DC, asking it to transtate this DN into GUID, to check its existence. But it will still not work under some very rare circumstances.

@MichaelGrafnetter MichaelGrafnetter modified the milestones: 2.18, 2.19 Oct 2, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.