“Error while creating user firstname.lastname@example.org due to address collision (either an excluded resource has this address, or a change was made outside of GCDS and the cache is stale).” This would happen daily and both to staff and student accounts.
Status: Known issue in Google Cloud Directory Sync 4.4.26 but due to the drastic changes in this version rolling back is not recommended.
According to support, this is a known issue in Google Cloud Directory Sync 4.4.26 but due to the drastic changes in this version rolling back is not recommended.
Work Around: This argument added to the command line flushes the cache:
“C:\Program Files\Google Cloud Directory Sync\sync-cmd.exe”
-a -f -c C:\Users\user\yourconfigurationfile.xml
The -f argument is listed in the documentation as ‘resolves specific troubleshooting issues’ but it flushes the cache.
To confirm clearing the cache resolved the issue support had me locate the GADS_nonAddressPrimaryKeyFile.tsv in C:\Users\USER_GADS and rename it to GADS_nonAddressPrimaryKeyFile_Old.tsv. The path to the file is located in the .xml file:
The .tsv file holds a primary key for all the users. Renaming it causes GCDS to take alot longer as it recreates all the primary keys. The primary key is used as a unique identifier for name changes.
I hope this helps if you run into it!