DataCollectorJob not executing due to locked/inactive Run as account - Support and Troubleshooting

DataCollectorJob not executing due to locked/inactive Run as account Issue Performance Analytics widgets and reports on Dashboard show outdated data, despite Data Collection jobs running.

Symptoms To verify if the issues described in this article are causing the problem, check the logs for specific error messages associated with recent Performance Analytics Data Collection job runs.

For a locked out user account in the Run As field, the following error message will appear:

DataCollectorJob: not executed, user has been locked out.

For the case in which the account in the Run As field is marked as inactive, the following error message will appear in the Scheduled Data Collection Job log corresponding to that execution of the Job:

DataCollectorJob: not executed, user is not active. If the Run As field in the Data Collector Job record is blank or empty, the error message will show as:

DataCollectorJob: not executed, run_as user is empty. Cause The causes of errors in Data Collection jobs are due to an invalid Run As account, preventing job authentication. Common reasons include:

Blank or deleted Run As reference field Locked or inactive account Account in different Domain Each condition generates an error in the Job Log. Other account options don't affect job running capability.

Resolution Create a new dedicated account for running scheduled jobs, ensuring it's valid, active, and not locked out. No special permissions or roles needed.

To maintain security, assign a random password unknown, not needed for Scheduled Data Collection Jobs.

After creation, associate the account with Performance Analytics Data Collector Jobs to resolve issues with the configured Run As account.

Related Links Create or schedule a data collection job