Task Scheduler errror: Failure occurred in "LogonUserExEx" . User Action: Ensure the credentials for the task are correctly specified. Additional Data: Error Value: 2147943726

Question

We have several Task Scheduler jobs running on Windows Server 2016 that are failing with the following errors:

• Task Scheduler failed to start "\Automation\Provenir\Restart-CreditEnvironments" task for user "SVSSTX1001\amb055". Additional Data: Error Value: 2147943726.
• Task Scheduler failed to log on "\Automation\Provenir\Restart-CreditEnvironments" . Failure occurred in "LogonUserExEx" . User Action: Ensure the credentials for the task are correctly specified. Additional Data: Error Value: 2147943726..

1. I have verified service account has access and credentials are valid.
2. Attempted using different service accounts.
3. deleted and recreated task job.

Answer 1

Hello

Thank you for posting in Microsoft Community forum!

The Task Scheduler error 2147943726 you’re encountering is often caused by a change in the password for the user meant to run the scheduled task. Even though you’ve verified the service account access and credentials, the issue might still persist if the password has been changed recently.

Here are a few steps you can try to resolve this issue:

Re-assign the User to an applicative account: Most users have reported that the issue was resolved after they re-assigned the User under “Change User or Group” to the latest Active Directory information of the user. If you use an “applicative” account, it may change less frequently than a regular user account, which could provide a more lasting solution.

Update the task credentials: Go to the properties of the task. Under the General tab, click on “Change User or Group”. Enter the username in the field “Enter the object name to select”. This will ask for authentication, provide your credentials.

These are general solutions and might not work in all cases. If the issue persists, it might be due to other underlying problems such as permission issues.

Best Regards,

Wesley Li

Answer 2

Hi Wesley

Thank you for your reply, I have already tried several applicative accounts. Our applicative accounts don't rotate passwords. It works for a few days then it fails again.

Can you elaborate on what you mean by "underlying problems such as a permission issues"?

Answer 3

There are many factors involved in permissions issues, and the following points must be considered when resolving permissions-related issues:

1. Existing Permissions: Always examine the existing permissions on the relevant files or directories. Ensure that the reported issue aligns with these permissions. If necessary, you can use the chmod command to modify permissions.
2. SUID and SGID Bits: Check whether the SUID (Set User ID) or SGID (Set Group ID) bit is set. These bits affect how the file is executed. An uppercase letter indicates that the underlying permission is set.
3. Sticky Bit: The sticky bit affects a user’s ability to remove a file. Verify if the sticky bit is set.
4. ACLs (Access Control Lists): Some controls, such as ACLs, do not appear in the normal permissions. Check if an ACL is enabled on the file.

Also includes directory permissions:

• Read Permission: Allows a user to see the contents of a directory (e.g., using the ls command).
• Write Permission: Permits a user to create files in the directory.
• Execute Permission: Enables a user to enter the directory (i.e., make it their current directory).