<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://msmvps.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Scheduled task would not run</title><link>http://msmvps.com/blogs/vandooren/archive/2009/02/25/scheduled-task-would-not-run.aspx</link><description>The scheduled task for running ntbackup on our fileserver would not run anymore. It would stop with a return code of 0x80, and nothing worthwhile in the log file or event log. It ran fine for months, apart from the occasional hickup such as having no</description><dc:language>en</dc:language><generator>CommunityServer 2008.5 SP2 (Build: 40407.4157)</generator><item><title>re: Scheduled task would not run</title><link>http://msmvps.com/blogs/vandooren/archive/2009/02/25/scheduled-task-would-not-run.aspx#1687776</link><pubDate>Wed, 15 Apr 2009 12:39:52 GMT</pubDate><guid isPermaLink="false">d67277c4-116b-43f1-b688-e9ef184ea916:1687776</guid><dc:creator>vanDooren</dc:creator><description>&lt;p&gt;In the scheduled task properties you can specify that the task has to be aborted if it runs for longer than x time. And after that it can be restarted.&lt;/p&gt;
&lt;p&gt;Bear in mind that IF the task is aborted, any processes started with it are NOT aborted.&lt;/p&gt;
&lt;p&gt;In some cases, the first thing my task does is to kill all processes normally associated with that task to avoid problems. I have one task that starts Excel to produce a report via some macros. And sometimes it fails.&lt;/p&gt;
&lt;p&gt;To avoid problems, it kills all Excel processes and instances of teh ActiveX servers that are running.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://msmvps.com/aggbug.aspx?PostID=1687776" width="1" height="1"&gt;</description></item><item><title>re: Scheduled task would not run</title><link>http://msmvps.com/blogs/vandooren/archive/2009/02/25/scheduled-task-would-not-run.aspx#1686662</link><pubDate>Fri, 10 Apr 2009 15:28:06 GMT</pubDate><guid isPermaLink="false">d67277c4-116b-43f1-b688-e9ef184ea916:1686662</guid><dc:creator>Tom</dc:creator><description>&lt;p&gt;What happens if the Task is already running when the Scheduler calls it again. &amp;nbsp;Is there a configuration setting that allows you to stop the current or delay the new task until the previous one finishes, etc.?&lt;/p&gt;
&lt;p&gt;I had the same issue as you and used a program called IsUsedBy mstsoftware.com to determine what program is using the Task. &amp;nbsp;It showed me I had 17 calls to the program that had been abandoned. &amp;nbsp;A reboot would have fixed mine as well but I would not have known.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://msmvps.com/aggbug.aspx?PostID=1686662" width="1" height="1"&gt;</description></item><item><title>re: Scheduled task would not run</title><link>http://msmvps.com/blogs/vandooren/archive/2009/02/25/scheduled-task-would-not-run.aspx#1675402</link><pubDate>Tue, 03 Mar 2009 20:46:43 GMT</pubDate><guid isPermaLink="false">d67277c4-116b-43f1-b688-e9ef184ea916:1675402</guid><dc:creator>Andy</dc:creator><description>&lt;p&gt;Thanks! &amp;nbsp;This helped me solve a problem i was having.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://msmvps.com/aggbug.aspx?PostID=1675402" width="1" height="1"&gt;</description></item></channel></rss>