Dataset Refreshes Fail when Ownership Account is Disabled

[SELECTDBA]

Hello;

We've noticed that as Dataset owner's AD accounts are disabled the Dataset will fail to refresh.  Meaning lets say you deploy a Dataset, you are automatically set as the Owner, and if your AD account is disabled (say you leave the company) then all of your Datasets fail to refresh.  Normally I would think this is by design, but with the way Gateways are configured, and how Datasets refresh using those service accounts, this seems like a bug.  

Thanks in advance.  

[lbendlin]

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.

[SELECTDBA]

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.    

[lbendlin · Accepted solution]

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.

[VizKid]

Do you have the sample Script? 

[SELECTDBA]

Thanks for the suggestion.  That's a good idea and something we'll look to implement.