This list contains the common errors that may occur during sIDHistory synchronization and troubleshooting steps we can use to address these errors.
Question: I am getting "The handle is invalid (Error code = 6)." Error when my sIDHistory workflow runs, objects were created without sIDHistory information.
Answer: This error indicates an RPC problem where the migration tool cannot bind to an RPC endpoint on the source primary domain controller. Possible causes include:
TcpipClientSupport on the source primary domain controller or primary domain controller emulator has not been turned on.
The primary domain controller or primary domain controller emulator was not restarted after TcpipClientSupport was configured.
DNS or NetBIOS name resolution is not working.
Question: I am getting " Could not verify auditing and TcpipClientSupport on domains. Will not be able to migrate Sid's. The specified local group does not exist." Error when my sIDHistory workflow runs.
Answer: This error typically indicates that a user or a global or universal group with the {SourceNetBIOSDom}$$$ name already exists. ADMT typically creates the local group of that name, but it cannot do so if a security principal already exists with the name.
© ALL RIGHTS RESERVED. Conditions d’utilisation Confidentialité Cookie Preference Center
