04-29-2016 08:01 AM
Issue with Active Directory Macro. Found the following error with AD macro run:
ERROR: Change data contains changes that will violate integrity constraints in the server or cause other errors during this or
future synchronizations. See mduchgv.mduchgverrors for information regarding problems encountered.
ERROR: Validation errors detected by %mduchgv. Load not attempted.
With more analysis , identifed the dataset "mduchgverrors" which is loaded with Duplicate entries. Not really sure how to proceed with the AD sync run. Please advise.
04-29-2016 08:08 AM
04-29-2016 08:08 AM
04-29-2016 08:29 AM
05-02-2016 01:31 AM
So we need to re run the entire sync with a manual deletion of entries with dataset "mducghv" . As the entire sync is already happening here on a daily basis and the error seems to be persisting. I believe it would be wise to run , emptying the dataset "mducghv".
05-02-2016 07:03 AM
05-02-2016 07:45 AM
I meant removing all the entries from the dataset mduchgv.
The comparison between user ids with update library which is from mduchgv dataset with Metadata is going to be a cubersome process, as i find all metadata defined users with the error list.
Also there are two set of errors "Person with this name already exists in the Metadata Server." and "Userid being added is already owned by another Identity." for the same id and the number of users with the error list is more than 1000 and both the errors combined its becoming more than 2000 entries with the mduchgv dataset.
Not sure what will be right procedure to follow here?
05-02-2016 07:49 AM
05-02-2016 07:55 AM
Yes this is sync job is a successfully running job, which was working fine till a week before. But due to unknown reasons facing the current issue.
Can you please elaborate on this sentence of "
I would want to first investigate a couple users and figure out what has changed in AD that is different from what is in metadata before doing anything else."
Could please let me know the troubleshooting steps to do this?
Thanks and much appreciated!!
05-02-2016 08:00 AM
05-03-2016 05:04 AM
here the issue seems to be due to keyids. Already existing Users are lacking the external ID parameter(checked the same from SMC), but at the same time the new chnages datasets part of the AD sync is having this key id.
Now the fix can be as follows:
1.Recover the metadata from a best available metadata backup
2.Remove all the users from metadata and then run the AD sync job
3.Modify the adsync program, such a way that the job will take the error table as exception table, with that it will continue add the new users to metadata and will not change anything for the existing metadata users
Considering the Risk and Impact , we are confused to make a decision here. Can you please comment which could the right option to go ahead? Thanks again!!
05-03-2016 07:03 AM
Need further help from the community? Please ask a new question.