The following error was reported 2147943712

Task scheduler error 2147943712

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Answered by:

Question

I received a error when creating a basic task on a Windows 2008 server, assigning the local administrator as the account to run the task -> weather logged in or not.

It happens after I typed in the correct password in the dialog that asks for the accounts password.

An Error has occurred for the task . Error message: The following error was

reported. A specified logon session does not exist. It may have already been terminated.

Does anyone know what this message means ? It won’t let me finish the task. It also doesn’t seem to care what account I used it keeps giving me this error.

Also this system event is produced» Event id 116 Source: TaskScheduler

Task Scheduler validated the configuration for task » » , but credentials could not be stored. User Action: Re-register the task ensuring the credentials are valid. Additional Data: Error Value: 2147943712.

Answers

Please refer to this thread. It is about the same error.

This posting is provided «AS IS» with no warranties or guarantees , and confers no rights.

Microsoft Student Partner
Microsoft Certified Professional
Microsoft Certified Systems Administrator: Security
Microsoft Certified Systems Engineer: Security
Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration

All replies

Please refer to this thread. It is about the same error.

This posting is provided «AS IS» with no warranties or guarantees , and confers no rights.

Microsoft Student Partner
Microsoft Certified Professional
Microsoft Certified Systems Administrator: Security
Microsoft Certified Systems Engineer: Security
Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration

Yes that did correct it.

Computer ConfigurationPoliciesWindows SettingsSecurity SettingsLocal PoliciesSecurity Options

Policy:
Network access: Do not allow storage of passwords and credentials for network authentication [disable]

Do we know what the purpose of the policy is then ? 2003 task scheduler doesn’t care but 2008 task scheduler does. What other applications care about this setting and why would I not want to enable it, besides the 2008 task scheduler.

I also found in the 2008 task scheduler that if you have this enabled or set the [do not store password] selected on the task itself that it won’t care what the password is and will run. Actually you have to select [do not store password] if it is enabled, it’s the only way it would work. In any case isn’t this a security problem ?

Источник

Task scheduler error 2147943712

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Answered by:

Question

I received a error when creating a basic task on a Windows 2008 server, assigning the local administrator as the account to run the task -> weather logged in or not.

It happens after I typed in the correct password in the dialog that asks for the accounts password.

An Error has occurred for the task . Error message: The following error was

reported. A specified logon session does not exist. It may have already been terminated.

Does anyone know what this message means ? It won’t let me finish the task. It also doesn’t seem to care what account I used it keeps giving me this error.

Also this system event is produced» Event id 116 Source: TaskScheduler

Task Scheduler validated the configuration for task » » , but credentials could not be stored. User Action: Re-register the task ensuring the credentials are valid. Additional Data: Error Value: 2147943712.

Answers

Please refer to this thread. It is about the same error.

This posting is provided «AS IS» with no warranties or guarantees , and confers no rights.

Microsoft Student Partner
Microsoft Certified Professional
Microsoft Certified Systems Administrator: Security
Microsoft Certified Systems Engineer: Security
Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration

All replies

Please refer to this thread. It is about the same error.

This posting is provided «AS IS» with no warranties or guarantees , and confers no rights.

Microsoft Student Partner
Microsoft Certified Professional
Microsoft Certified Systems Administrator: Security
Microsoft Certified Systems Engineer: Security
Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration

Yes that did correct it.

Computer ConfigurationPoliciesWindows SettingsSecurity SettingsLocal PoliciesSecurity Options

Policy:
Network access: Do not allow storage of passwords and credentials for network authentication [disable]

Do we know what the purpose of the policy is then ? 2003 task scheduler doesn’t care but 2008 task scheduler does. What other applications care about this setting and why would I not want to enable it, besides the 2008 task scheduler.

I also found in the 2008 task scheduler that if you have this enabled or set the [do not store password] selected on the task itself that it won’t care what the password is and will run. Actually you have to select [do not store password] if it is enabled, it’s the only way it would work. In any case isn’t this a security problem ?

Источник

Powershell Script Task Schedule run as admin issue!

I have wrote a Powershell Script which deletes backup files older than 7 days. The script works fine when I run it manually though an elevated Powershell window (run as administrator). So I thought I would just create a scheduled task and run the script every morning. When creating the task I have ticked the «Run with highest privileges» box on the general tab but when I have run the task it doesn’t seem to work and I cant find any error messages about it.

Does anyone have any idea why not?

Ransomware 3.0: Prep for A New Malicious Threat Level

16 Replies

It is due to a registry setting that bars Domain accounts from running tasks.

This can be fixed by making the following change to the Registry.

Open the Registry on the server and navigate to HKEY_LOCAL_MACHINESystemCurrentControlSetControlLsa

Change the ‘REG_DWORD’ with ValueName ‘disabledomaincreds’ to a Value to “0

(If this ‘REG_DWORD” does not exist then create as above)

(Had this issue on W2008R2)

If you’re running it in Task Scheduler there is a Last Run Result column, what’s the code in that column?

What account are you using to execute (yours/service account)?

If a service account does it have the permissions to access/modify the target folder (had this issue with a report script I ran last week)?

1. Error: 2147943712
It is due to a registry setting that bars Domain accounts from running tasks. (See above to fix)

2. Error: 2147944309
This is due to account being locked out

3. Error: 2147943726
This error occurs when the Task is already running. You can change this by editing the task properties and changing the action when the task tries to start and is already running:

Hi everyone thanks for your help.

The last run result shows «(0x41301).

I am running it from my account at the moment, I may change to service account once I know it is working properly.

I have run the script manually now to check it works so have shot myself in the foot a little bit in terms of testing, unless I amend the script to do something else but I don’t really want to do that at the moment.

Hi everyone thanks for your help.

The last run result shows «(0x41301).

That means its still running

says completed in the task history.

Try following this through, see if it works then;

0 or 0x0: The operation completed successfully.
1 or 0x1: Incorrect function called or unknown function called.
2 or 0x2: File not found.
10 or 0xa: The environment is incorrect.
0x41300: Task is ready to run at its next scheduled time.
0x41301: Task is currently running.
0x41302: Task is disabled.
0x41303: Task has not yet run.
0x41304: There are no more runs scheduled for this task.
0x41306: Task is terminated.
0x8004130F: Credentials became corrupted (*)
0x8004131F: An instance of this task is already running.
0x800704DD: The service is not available (is ‘Run only when an user is logged on’ checked?)
0xC000013A: The application terminated as a result of a CTRL+C.
0xC06D007E: Unknown software exception.

Do you have a termination setting in the settings or on your trigger? Sounds like task scheduler still sees the event as running.

As for amending the script you could just add a simple statement at the end that writes to a file (maybe call it log/debug). Have it write the time and date it ran. Can always comment out once you get it working that way you have a test if anything goes sideways later.

Good habit when writing scripts.

then just add # add start to comment out.

What I do to troubleshoot these situation is set the task to «Run only when user is logged in» and then manually trigger it. The console window will now appear and you can see the error that is happening. you might want to add a pause at the end so you can see it:

Also, I wrote up how to run Powershell jobs in task scheduler, that might help too:

Awesome. You just solved (4) days of frustration for me in trying to get a PowerShell script to run as a Scheduled Task.

This worked for me also.

Same for me.
Thanks Francis193

Your solution worked for me. Thank you! I have been busting my hump on this one for a few hours.

However I do want to add that I had to slightly modify the settings. Under step 7 I had to change my arguement to «./install.ps1» instead of «.install.ps1» (install.ps1 is my file name as opposed to yours which was «migration». Is there a reason why I needed to use «/» instead of a «»?

I have added the script via Taskschedular as well, when I run as administrator manually via powershell, it is working but not as taskschedular. Please, help.

I checked the folder has full permission to the account, I’m using.

This topic has been locked by an administrator and is no longer open for commenting.

To continue this discussion, please ask a new question.

Read these next.

Laptop deployments

Hi all,I am looking for suggestions for laptop deployment software please. We usually build maybe one or two laptops a month, but we have a mass laptop roll out coming up to replace aging hardware so rather than spend time configuring each laptop, I’d li.

Spark! Pro series — 11th January 2023

Today in History: 1922 The First Insulin Injection as a Treatment for DiabetesAs of 2020, the CDC estimates that just over one in ten Americans has diabetes, a chronic condition that can have serious, life-threatening complications if left untreated.Diabe.

SQL Injection.

Hi all,We have a super old legacy application built in asp, running on IIS with a SQL 2012 backend database and I have been asked to look at it as the business owner suspects its time to upgrade.We connect to it on http://cnameofapplicationDoes not even u.

Intermittent ping, wifi, printers

Hi,We have been having intermittent problems for over a month. I have limited networking experience. We are running Windows 2008 R2 servers in VMWare sessions. DC1 is our domain, DHCP and DNS server. At least twice a day, we will have problems: .

System-Root Full — 5230 Appliance

Before I begin, I know this appliance is EOL, but I need to keep it around for historical reasons. I have already reached out to support, they can’t help. I also have posted this on the VOX Community I have an issue with my 5230 appliance (I know it’s .

Источник