On Demand Migration for Active Directory - Failed to add objectSid

During the Staging Workflow, according to the logs there were 5 user objects that had an error "Write: Failed to add objectSid.The source object's SID already exists in destination forest" however when double checking the SID in the target forest, it does not exist. What could be the reasoning this is happening? Looking at AD in target, the SID History attribute is indeed blank.

Parents

0 scott russo over 1 year ago

Thank you for posting to the On Demand Migration (ODM) forum. I understand you are experiencing issues with Dirsync SIDHistory. This issue is going to require additional investigation and resources then are available via the community forum. We will need a Service Request properly track and investigate this issue.

Please include the Dirsync log from the workflow.

Did you search the error in our Knowledge Base?

Here is a link to create a Service Request:

https://support.quest.com/create-service-request
Cancel
Up -1 Down

Reply

Verify Answer

Cancel
0 derrick fernandez over 1 year ago in reply to scott russo

I submitted a ticket. The logs do not give me any error codes other than the error itself.
Cancel
Up 0 Down

Reply

Verify Answer

Cancel

Reply

0 derrick fernandez over 1 year ago in reply to scott russo

I submitted a ticket. The logs do not give me any error codes other than the error itself.
Cancel
Up 0 Down

Reply

Verify Answer

Cancel

Children

No Data