System Data Collector Sets fail on an upgraded 2008 / 2008 R2 DC

System Data Collector Sets fail on an upgraded 2008 / 2008 R2 DC

  • Comments 2
  • Likes

Hello Askperf! Shamesh Pillai here to discuss an interesting issue I recently worked. On Microsoft Windows Server 2008, 2008 R2 Domain Controllers, Perfmon may fail when starting a System Data Collector Set. This includes the Active Directory Diagnostics, System Diagnostics, and System Performance Perfmon logging.

image

When we start any of the System Data Collector Sets, the following error may appear and/or the Data Collector Set may freeze:

Logon failure: the user has not been granted the requested logon type at this computer

image

When this fails, the following Events will be logged in the TaskScheduler event log:

Log Name: Microsoft-Windows-TaskScheduler/Operational
Source: Microsoft-Windows-TaskScheduler
Date: 11/30/2011 6:36:18 AM
Event ID: 101
Task Category: Task Start Failed
Level: Error
Keywords: (1)
User: SYSTEM
Computer: <Computer Name >

Description:
Task Scheduler failed to start "\Microsoft\Windows\PLA\System\{CFCD20D6-D2CE-42D3-A9CB-9916E676DE02}_System Diagnostics" task for user "<Username>". Additional Data: Error Value: 2147943785.

&

Log Name: Microsoft-Windows-TaskScheduler/Operational
Source: Microsoft-Windows-TaskScheduler
Date: 11/30/2011 6:36:18 AM
Event ID: 104
Task Category: Logon failure
Level: Error
Keywords:
User: SYSTEM
Computer: <Computer Name>
Description:
Task Scheduler failed to log on "<UserName>" . Failure occurred in "LsaLogonUser”. User Action: Ensure the credentials for the task are correctly specified. Additional Data: Error Value: 2147943785
.

While troubleshooting the issue, I observed that of all the servers experiencing this behavior, all were Domain Controllers that were upgraded from a Windows Server 2003 Domain Controller. Interestingly though, the issue does not happen on a freshly installed Microsoft Windows 2008, 2008 R2 Domain Controller, or if we upgrade a Member server. In my testing, we observed that “User Defined” Sets were not affected by this problem.

In Microsoft Windows Server 2008 and later operating systems, Perfmon uses Task Scheduler in the background. When we start a System Data Collector Set, it launches Taskeng in the current user context. To launch the job, the user needs to be included in the “Log on as a batch job” User Rights Assignment Policy.

We checked the “Log on as a batch job” Policy and discovered that the “Performance Log Users” group was not included. As soon as we added this group back to the Policy, we were able to successfully start our System Data Collector Sets.

By default, the “Performance Log Users” group is expected to have the “Log on as a batch job” user right. However, when the 2003 Domain Controller was upgraded to Server 2008, the “Performance Log Users” group did not get added to this Policy.

With that, we have concluded our post for today. Take care!

Additional Resources

-Shamesh Pillai

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • Super. I was stuck with this for a few days

  • Hi, I know this was posted a while back but I am having a similar issue except my 2008 R2 server is not an upgraded server. I am trying to remotely monitor a domain controller from another "management" server but I get an access denied error when trying to start the data collector. Any ideas?