Error 41306
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Asked by: Powershell on scheduled task fails with "The last run of the task was terminated by the user 0x41306" Windows the last run of the task was terminated by the user 0x41306 Server > Windows PowerShell General discussion 0 Sign in to vote Hi, i have created task scheduler error 0x41301 a script that i schedule to run a few times a day copying files around servers. Sometime the same script might be running task scheduler error 0x103 2-3 times at the same time. Sometimes the schedule task that runs the script failes with the error: "The last run of the task was terminated by the user 0x41306" Nobody has stopped the task. Could it be task scheduler error code 0x1 because they are running at the same time? Is weird because most of the time they don't fail and i know they run at the same time ( i set it for testing to runsimultaneously) Thanks Wednesday, April 03, 2013 2:39 PM Reply | Quote All replies 1 Sign in to vote Hi, It sounds like the Script is returning that error code for some reason. This error message is actually a code for the task
Task Scheduler 0x8004131f
scheduler (http://msdn.microsoft.com/en-us/library/windows/desktop/aa383604%28v=vs.85%29.aspx): SCHED_S_TASK_TERMINATED 0x00041306 The last run of the task was terminated by the user. So if the PC is shut down whilst the script is running, that would also cause this error. Regards, Yan Li Cataleya Li TechNet Community Support
Friday, April 05, 2013 7:52 AM Reply | Quote Moderator 0 Sign in to vote Hi, I know that is a code for task scheduler, but the thing is that the server wasn't restarted and nobody terminated the task. The tasks call 1 powershell script that moves files between servers. Is is possible that if multiple tasks call the same script at the same time it returns this error? Thanks Monday, April 08, 2013 2:08 PM Reply | Quote 0 Sign in to vote It is possible to have more than one instance of a script running. But if the script does something like "delete the logfile that is already in use by the other process", that could be the issue. What is your script doing other than hust copying files?Al Dunbar -- remember to 'mark or propose as answer' or 'vote as helpful' as appropriate. Monday, April 08, 2013 3:07 PM Reply | Quote 1 Sign in to vote Hello, I'm having the same problem with a weekly backup task on different HyperV servers. Strange thing this does not always happen on the saStart 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
Task Scheduler 0x41301 Running
Learn more about Stack Overflow the company Business Learn more about hiring developers or task scheduler error task image corrupt posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and last run result 0x0 meaning answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up https://social.technet.microsoft.com/Forums/windowsserver/en-US/207ee15a-e339-495b-a03e-6d2a32761a0e/powershell-on-scheduled-task-fails-with-the-last-run-of-the-task-was-terminated-by-the-user?forum=winserverpowershell and rise to the top Why do weekly tasks created via PowerShell using a different user fail with error 0x41306 up vote 6 down vote favorite 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 http://serverfault.com/questions/470023/why-do-weekly-tasks-created-via-powershell-using-a-different-user-fail-with-erro 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 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
Start 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://serverfault.com/questions/7638/windows-scheduled-task-fails-to-complete-with-error-code-0xc000013a company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; http://task.scheduler.error.41306.winwizards.org/ it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Windows scheduled task fails to complete task scheduler with error code 0xc000013a up vote 8 down vote favorite I'm using Windows Server 2003 and have a scheduled task that fails to complete. The task is set to run a Windows Command Script (.cmd) at 3pm each day. The script runs a program that extracts some data from a SQL Server database and uploads that data to an FTP server. The error code displayed in the "Last result" column of the scheduled tasks task scheduler error folder is 0xc000013a. A quick Google search leads to this Microsoft support page that states: The most common "C" error code is "0xC000013A: The application terminated as a result of a CTRL+C". No-one is logged in at the time the task runs, so there's no-one around to press CTRL+C. I'm not sure I understand what is being said here in the Microsoft documentation. I've checked the rudimentary things - the scheduled task is enabled, scheduled to run each day, and pointing to a file that does exist in a valid location. Interestingly, when I run this task manually (either by running the .cmd script from the command line, or by right-clicking the task and clicking "Run") the task completes successfully. What does this error code mean, and how can I get this task to run when I'm not there to force it? windows windows-server-2003 scheduled-task share|improve this question asked May 13 '09 at 4:08 Brian Willis 1,01421113 add a comment| 10 Answers 10 active oldest votes up vote 4 down vote I can't answer the question directly as I don't know specifically what the error message means (nor, therefore, how to fix it), but if I were trying to troubleshoot it I would add a few writes to a log file at strategic points in the script and then after
Scheduler Error 41306) Repair Tool Step 2: Click the "Scan" button Step 3: Click 'Fix All' and you're done! Compatibility: Windows 7, 8, Vista, XP Download Size: 6MB Requirements: 300 MHz Processor, 256 MB Ram, 22 MB HDD Limitations: This download is a free evaluation version. To unlock all features and tools, a purchase is required. Task Scheduler Error 41306 Error Codes are caused in one way or another by misconfigured system files in your windows operating system. If you have Task Scheduler Error 41306 errors then we strongly recommend that you Download (Task Scheduler Error 41306) Repair Tool. This article contains information that shows you how to fix Task Scheduler Error 41306 both (manually) and (automatically) , In addition, this article will help you troubleshoot some common error messages related to Task Scheduler Error 41306 error code that you may receive. Note: This article was updated on 2016-10-04 and previously published under WIKI_Q210794 Contents 1.What is Task Scheduler Error 41306 error? 2.What causes Task Scheduler Error 41306 error? 3.How to easily fix Task Scheduler Error 41306 errors What is Task Scheduler Error 41306 error? The Task Scheduler Error 41306 error is the Hexadecimal format of the error caused. This is common error code format used by windows and other windows compatible software and driver vendors. This code is used by the vendor to identify the error caused. This Task Scheduler Error 41306 error code has a numeric error number and a technical description. In some cases the error may have more parameters in Task Scheduler Error 41306 format .This additional hexadecimal code are the address of the memory locations where the instruction(s) was loaded at the time of the error. What causes Task Scheduler Error 41306 error? Th