Google Cloud Directory Sync - License Management suddenly giving errors

[timbo343]

We GCDS to manage our AD to Google Workspace and part of the GCDS process is to assign the Google Education Workspace License.

 

We have started getting errors such as:

 

Unable to add SKU Google Workspace for Education Plus (Staff) to user {userID}
Exception detail - http code: 412; status message: Precondition Failed; reason(s): conditionNotMet

 

The thing is, the users already have licenses assigned to them and those that don't, the license is added to their account, and those that don't me the requirements / LDAP query - the license is removed, so i'm not sure why on earth we get getting this error.

 

Wondering if anyone else is getting this issue.

 

We are running 5.0.22.0 of the GCDS application.

[Steve21]

The only time I’ve seen that is when you have a vault hold on the user that’s removed the license via the sync

 

Anything like that on yours?

 

Steve

[timbo343]

The only time I’ve seen that is when you have a vault hold on the user that’s removed the license via the sync

 

Anything like that on yours?

 

Steve

 

This is affecting all the users that already have the license assigned to them rather than one individual and there is nothing in the vault that would affect this.

[GPR2023]

Hello ,We have the same problem.The problem started on April 28.Is there a solution for this problem? I have an open incident on google, but they don't resolve it for now.

[timbo343]

Hello ,We have the same problem.The problem started on April 28.Is there a solution for this problem? I have an open incident on google, but they don't resolve it for now.

Ah! I'm glad someone else is having issues. Must be an issue with Google as nothing changed at our side.

[Jaan]

Yep here's the work around:

 

EDIT: just edit your Google settings config file. They are aware of the issue.

 

 

Hello Jaan,

 

I hope this message finds you well.

 

I am reaching out to you for our recent update regarding GCDS Licence Sync issue. We are already aware about this known issue and it is actively being looked at by the engineering team on high priority.

 

Meanwhile from the product engineer team we received a workaround to resolve this issue,

 

Please open the XML file in Notepad and reduce the maxResult tag value from 500 to 190 and save the XML.

 

For example : 190

 

Once this is done, please open the XML file in the GCDS configuration manager and run a simulate sync and then check the results. There should be no license assignment failures.

 

Let me know if the provided workaround works for you.

 

Sincerely,

kiran

Google Workspace Support

[GPR2023]

Great

I have applied what you indicate by modifying the XML to 200 and it has worked perfectly.Users Google Cloud Directory Sync 5/5/23 14:14 - SUCCESS (0 errors, 0 warnings)

 

Thanks

[timbo343]

Yep here's the work around:

 

EDIT: just edit your Google settings config file. They are aware of the issue.

 

 

Hello Jaan,

 

I hope this message finds you well.

 

I am reaching out to you for our recent update regarding GCDS Licence Sync issue. We are already aware about this known issue and it is actively being looked at by the engineering team on high priority.

 

Meanwhile from the product engineer team we received a workaround to resolve this issue,

 

Please open the XML file in Notepad and reduce the maxResult tag value from 500 to 190 and save the XML.

 

For example : 190

 

Once this is done, please open the XML file in the GCDS configuration manager and run a simulate sync and then check the results. There should be no license assignment failures.

 

Let me know if the provided workaround works for you.

 

Sincerely,

kiran

Google Workspace Support

 

Thank you so much for posting the fix! I can confirm this is working too.

[Jaan]

No worries, glad it helped

[Jaan]

Latest update:

At 2023-05-08 18:56 UTC (just now):

We were able to resolve this issue on the backend and GCDS is no longer receiving errors when assigning licenses. You may use the steps below to revert the GCDS config file back to the default attribute values:

 

1. Locate the XML config file used by GCDS

2. Open the XML file with a text editor of your choice and find the maxResults attribute

3. Change the value back to 500. It should look like this: 500

4. Save your changes in the XML config file

5. Simulate a sync first in GCDS and review the results

6. There should no longer be any license assignment errors in the logs. Once you've confirmed this, then it is okay to Sync & Apply Changes

[timbo343]

Latest update:

At 2023-05-08 18:56 UTC (just now):

We were able to resolve this issue on the backend and GCDS is no longer receiving errors when assigning licenses. You may use the steps below to revert the GCDS config file back to the default attribute values:

 

1. Locate the XML config file used by GCDS

2. Open the XML file with a text editor of your choice and find the maxResults attribute

3. Change the value back to 500. It should look like this: 500

4. Save your changes in the XML config file

5. Simulate a sync first in GCDS and review the results

6. There should no longer be any license assignment errors in the logs. Once you've confirmed this, then it is okay to Sync & Apply Changes

 

Tested and can confirm original settings working as expected.