Forum Discussion
Dataset Refreshes Fail when Ownership Account is Disabled
- 5 years ago
We do this proactively - we run scripts against our AD to identify workspace admins and dataset owners that are no longer valid and we alert the remaining admin(s) that they must add at least a second admin and/or fix the ownership. Combination of Powershell and API calls.
dataset ownership is not (directly) related to gateway connection refresh, But I can imagine that loss of that dataset owner will trigger the issues you described.
The remedy is quick - have someone else take ownership of the dataset either on the service UI or via API call.
- SELECTDBA5 years ago
Advocate I
Thanks for the response. That's what we have been doing as far as taking over ownership, but thats time consuming, and sometimes days late after the account has been disabled.
- lbendlin5 years ago
Super User
We do this proactively - we run scripts against our AD to identify workspace admins and dataset owners that are no longer valid and we alert the remaining admin(s) that they must add at least a second admin and/or fix the ownership. Combination of Powershell and API calls.
- SELECTDBA5 years ago
Advocate I
Thanks for the suggestion. That's a good idea and something we'll look to implement.