- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-11-2020 12:25 AM
Hello All, I'm getting an error DataCollectorJob: [PA Incident] Daily Data Collection not executed, user admin is not activeI'm running as a sys administrator and is active. The error message is
Please let me know if anyone is aware of this
Solved! Go to Solution.
- Labels:
-
Performance Analytics
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-11-2020 02:30 AM
The error is stating that the 'Run As' user is currently inactive. Please check the System Administrator account and make it active or alternatively, change the 'Run As' user on your data collection job.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-11-2020 04:34 AM
Yes, you are right! the System administrator has become inactive.
But not sure how it become inactive. Any possibilities you can think of on why it became inactive? I'm not a system administrator. and the list is showing that the inactive is done by me.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-12-2020 01:10 AM
You shouldn't mark your answer as correct mate.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-12-2020 01:31 AM
Oh, sorry! My mistake. Marked correctly now
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-12-2020 09:40 AM
It is a security best practice (in many systems) to rename/inactivate/remove the default admin account.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-11-2020 11:12 AM
There is no need to actually run this as System Administrator. I would recommend creating a new dedicated user with no roles (generally called performance.analytics). Run your job as that user. Scripts run as this user, but the normal data collection for the indicator source bypasses ACL so admin is an overkill.