Error Code 41306
Contents |
Studio 2015 products Visual Studio Team Services Visual Studio Code Visual Studio Dev Essentials Office Office Word/Excel/PowerPoint Microsoft Graph Outlook OneDrive/Sharepoint Skype Services Store Cortana Bing task scheduler error code 0x1 Application Insights Languages & platforms Xamarin ASP.NET C++ TypeScript .NET - VB, task scheduler error 0x41301 C#, F# Server Windows Server SQL Server BizTalk Server SharePoint Dynamics Programs & communities Students Startups Forums MSDN task scheduler error 0x103 Subscriber downloads Sign in Search Microsoft Search Windows Dev Center Windows Dev Center Explore What’s new for Windows 10 Intro to Universal Windows Platform Coding challenges Develop for accessibility Build
The Last Run Of The Task Was Terminated By The User 0x41306
for enterprise Windows Store opportunities Docs Windows apps Get started Design and UI Develop API reference Publish Monetize Promote Games Get started UI design Develop Publish Desktop Get started Design Develop API reference Test and deploy Compatibility Windows IoT Microsoft Edge Windows Holographic Downloads Samples Support Why Windows Dashboard Explore What’s new for Windows 10 Intro to Universal Windows 0x41306: task is terminated. Platform Coding challenges Develop for accessibility Build for enterprise Windows Store opportunities Docs Windows apps Get started Design and UI Develop API reference Publish Monetize Promote Games Get started UI design Develop Publish Desktop Get started Design Develop API reference Test and deploy Compatibility Windows IoT Microsoft Edge Windows Holographic Downloads Samples Support Why Windows Dashboard System Administration Task Scheduler Task Scheduler Reference Task Scheduler Reference Task Scheduler Error and Success Constants Task Scheduler Error and Success Constants Task Scheduler Error and Success Constants Task Scheduler Scripting Objects Task Scheduler Interfaces Task Scheduler Structures and Unions Task Scheduler Enumerated Types Task Scheduler Schema Task Scheduler Error and Success Constants Schtasks.exe TOC Collapse the table of content Expand the table of content This documentation is archived and is not being maintained. This documentation is archived and is not being maintained. Task Scheduler Error and Success Constants If an error occurs, the Task Scheduler APIs can return one of the following error codes as an HRESULT value. The constants that begin with SCHED_S_ are success constants, and the
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company task scheduler operational codes Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs
0x8004131f An Instance Of This Task Is Already Running
Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just
Task Scheduler Return Code 0
like you, helping each other. Join them; it only takes a minute: Sign up Where can I find the Windows Task Scheduler exit codes list? up vote 0 down vote favorite All I have found about the https://msdn.microsoft.com/en-us/library/windows/desktop/aa383604(v=vs.85).aspx Windows Task Scheduler results are short details about just a few codes. Does anybody knows about a complete list? For example, I have not been able to locate anything about the error code 0xFF. EDIT:For example, if I add this task (for testing a command line program called "Notifu"): schtasks /create /tn "NotifuTest" /tr "d:\Temporal\Notifu\notifu64.exe /m 'Test'" /sc minute /mo 1 /sd 10/10/2010 /ru "SYSTEM" The same command has been verified working by command-line. http://stackoverflow.com/questions/22494333/where-can-i-find-the-windows-task-scheduler-exit-codes-list This is the result (sorry, my Windows is in spanish); note the 0xFF (the program seems to be executing, but with no results: windows scheduled-tasks exit-code schtasks.exe share|improve this question edited Mar 19 '14 at 10:50 asked Mar 19 '14 at 1:14 Sopalajo de Arrierez 7061822 1 Where do you see these error codes? Windows Task scheduler usually runs other things (batch scripts, command line programs etc.), and these are the things that will have documentation on result codes. –Nick.McDermaid Mar 19 '14 at 1:43 Added extra info to original post, @ElectricLlama. Thanks. –Sopalajo de Arrierez Mar 19 '14 at 10:51 1 Yes, as mentioned below, notifu.exe has returned 0xFF (255) and windows scheduler is just echoing that. What does the notifu documentation say that means? If you can enable a log for notifu, you should do it and check the log. –Nick.McDermaid Mar 19 '14 at 12:07 add a comment| 3 Answers 3 active oldest votes up vote 4 down vote accepted Process exit codes are process specific. By convention a value of zero indicates success. The only reserved value is STILL_ACTIVE which has value 259. That is returned by GetExitCodeProcess when the process is still active. To understand what the values mean you will have to consult the documentation of the process in question. share|improve thi
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the http://stackoverflow.com/questions/14378951/why-do-weekly-tasks-created-via-powershell-using-a-different-user-fail-with-erro company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Why do weekly tasks created via PowerShell using a different user fail with error 0x41306 up vote 8 down vote task scheduler favorite 2 We have some scripts that create scheduled jobs using PowerShell as part of our application. When testing them recently, I noticed that some of them always failed immediately, and no output is ever produced (they don't even appear in the Get-Job list). After many days of tweaking, we've managed to isolate it to any jobs that are set to run weekly. Below is a script that creates two jobs that do task scheduler error exactly the same thing. When we run this on our domain, and provide credentials of a domain user, then force both jobs to run in the Task Scheduler GUI (right-click -> Run), the daily one runs fine (0x0 result) and the weekly one fails (0x41306). Note: If I don't provide the -Credential param, both jobs work fine. The jobs only fail if the task is both weekly, and running as this domain user. I can't find information on why this is happening, nor think of any reason it would behave differently for weekly jobs. The "History£ tab in the Task Scheduler has almost no useful information, just "Task stopping due to user request" and "Task terminated", both of which have no useful info: Task Scheduler terminated "{eabba479-f8fc-4f0e-bf5e-053dfbfe9f62}" instance of the "\Microsoft\Windows\PowerShell\ScheduledJobs\Test1" task. Task Scheduler stopped instance "{eabba479-f8fc-4f0e-bf5e-053dfbfe9f62}" of task "\Microsoft\Windows\PowerShell\ScheduledJobs\Test1" as request by user "MyDomain\SomeUser" . What's up with this? Why do weekly tasks run differently, and how can I diganose this issue? This is PowerShell v3 on Windows Server 2008 R2. I've been unable to reproduce this locally, but I don't have a user set up in the same way as the one in our production domain (I'm working on this, but I wanted to post this ASAP in the hope someone knows what's happening!). Import-Module PSSchedule