search

lithnet / googleapps-managementagent

Google Workspace Management Agent for MIM 2016
MIT License
12 stars 4 forks source link

Full Imports fail every run since yesterday #73

Closed IAmStevenJohnson closed 2 years ago

IAmStevenJohnson commented 2 years ago

Since yesterday afternoon we have been unable to get a full import to complete successfully. We get a "stopped-extension-dll-exception" error after anywhere from 5k to 30k objects being read from google. The beginning of the Windows event log shows:

The extensible extension returned an unsupported error. The stack trace is: "System.AggregateException: One or more errors occurred. ---> System.AggregateException: One or more errors occurred. ---> Google.GoogleApiException: Google.Apis.Requests.RequestError Internal error encountered. [500] Errors [ Message[Internal error encountered.] Location[ - ] Reason[backendError] Domain[global] ]

Here's the full event log error: Failed Full Import.txt

This failure happens in both our production FIM R2 and test MIM environments with separate Google tenants.

For the last month or two we've been having failures writing aliases while provisioning users, which produces "object already exists" errors during each export until a full import is run. After which the aliases are then written. So full imports are very important right now as aliases on new accounts are not written until a full import is completed to recognize that the account was provisioned--just without any aliases.

Any thoughts on what might be causing this? Thanks so much.

ryannewington commented 2 years ago

@IAmStevenJohnson

Unfortunately, it's definitely a google server-side problem

Message[Internal error encountered.] Location[ - ] Reason[backendError] Domain[global]

I know its not what you want to hear, but I've seen these appear for a day or two then disappear. If you have a google support contract, it would be worth getting them to have a look at your tenant, and provide that error string above to them.

IAmStevenJohnson commented 2 years ago

Thank you for responding. That's what I need to hear. I just didn't know how to interpret the error. Really appreciate your response.

ryannewington commented 2 years ago

If you want to open a new issue, we can see if we can work on that alias issue.