tag:blogger.com,1999:blog-7023576929606369407.post5757318627306192597..comments2023-10-31T10:47:50.956+01:00Comments on Jepson's Blog: Windows Task Scheduler error 2147942667Michael Jepsonhttp://www.blogger.com/profile/16073118583952778532noreply@blogger.comBlogger20125tag:blogger.com,1999:blog-7023576929606369407.post-17665051909006884752021-09-02T21:07:20.766+02:002021-09-02T21:07:20.766+02:00Many many years later, and this exact issue in 202...Many many years later, and this exact issue in 2021 Windows10 solved.<br /><br />Woe be the day if this blog post goes offline.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-7023576929606369407.post-76367772662259849602018-12-04T10:25:13.380+01:002018-12-04T10:25:13.380+01:00thanks a lot!
The idiot responsible for UI design ...thanks a lot!<br />The idiot responsible for UI design of Task Scheduler "Edit Action" did great job and the input box for task params and startup url could hardly be smaller.Andrejhttps://www.blogger.com/profile/13770625208527797451noreply@blogger.comtag:blogger.com,1999:blog-7023576929606369407.post-91540494144556109172018-08-14T16:45:06.611+02:002018-08-14T16:45:06.611+02:00Very crazy, got stuck with that same issue for two...Very crazy, got stuck with that same issue for two hours. Removing the path, saving it as empty, the error disappears. Once you put back the path, the task works perfectly. Thanks to you gents.Anonymoushttps://www.blogger.com/profile/14606484644750934874noreply@blogger.comtag:blogger.com,1999:blog-7023576929606369407.post-60125490998776435412015-07-30T21:22:24.719+02:002015-07-30T21:22:24.719+02:00I don't have any quotes in my "start in&q...I don't have any quotes in my "start in" field, and I tried all the suggestions, but none worked. Everything works fine until I check the "Run whether user is logged on or not" button, regardless of whether I have "Run with highest Privilges" checked.bknows2noreply@blogger.comtag:blogger.com,1999:blog-7023576929606369407.post-90653107094713679372015-06-29T17:12:08.430+02:002015-06-29T17:12:08.430+02:00Holy smokes! Removing the start in argument and t...Holy smokes! Removing the start in argument and then re-applying it works for me as well. Strange indeed.huycoolhttps://www.blogger.com/profile/02060214481377447141noreply@blogger.comtag:blogger.com,1999:blog-7023576929606369407.post-59338820715449642992015-03-20T09:13:12.899+01:002015-03-20T09:13:12.899+01:00Also happened to me by setting startup path to non...Also happened to me by setting startup path to non-existant directory :Pbottleneckednoreply@blogger.comtag:blogger.com,1999:blog-7023576929606369407.post-46065310424356393102015-01-21T21:36:47.322+01:002015-01-21T21:36:47.322+01:00Thank you for posting this. This is bizarre.
-Muk...Thank you for posting this. This is bizarre.<br /><br />-MukeshAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-7023576929606369407.post-70926383676778627472014-11-26T02:08:18.700+01:002014-11-26T02:08:18.700+01:00I found that is had nothing to do with quotes, ...I found that is had nothing to do with quotes, 'run highest privilege', or permission. It seems to be a bit of a bug in the Task Scheduler UI.<br />I added this path in the 'Start In (optional)' argument:<br />D:\scripts\DiskspaceMonitor\<br /><br />- it had not quotes, but the task would give the above error.<br />- I then removed that path from the argument, and ran it again Terrynoreply@blogger.comtag:blogger.com,1999:blog-7023576929606369407.post-65105144347274752442014-08-14T21:00:53.064+02:002014-08-14T21:00:53.064+02:00Natalee, You may want to check "run with high...Natalee, You may want to check "run with highest privileges" which worked for me.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-7023576929606369407.post-3163747951124180812014-08-04T21:54:50.179+02:002014-08-04T21:54:50.179+02:00I'm having the same problem as Stephen mention...I'm having the same problem as Stephen mentioned. I am getting this error but there aren't any quotes in the start in field and the box is checked to run when user isn't logged on. I also made sure the user has full rightsNataleenoreply@blogger.comtag:blogger.com,1999:blog-7023576929606369407.post-69983031391382588302014-07-29T21:53:32.245+02:002014-07-29T21:53:32.245+02:00someone here..need quick answer to dummy question....someone here..need quick answer to dummy question...task scheduler--setup..in ACTIONS> Program/script I have IExplore.exe<br />then Add Arguments is the Http -url- I need to point to..if this is so far correct..then does the path go in the Start in (optional field) ?? if so how is it coded..gw46https://www.blogger.com/profile/13232340233307132822noreply@blogger.comtag:blogger.com,1999:blog-7023576929606369407.post-18259973496658468092013-08-16T14:04:23.710+02:002013-08-16T14:04:23.710+02:00It should, yes. It's a member of every Adminis...It should, yes. It's a member of every Administrator group on the domain I could find.Stephennoreply@blogger.comtag:blogger.com,1999:blog-7023576929606369407.post-12531805401902881682013-08-16T11:28:04.683+02:002013-08-16T11:28:04.683+02:00Probably the error just means the file could not b...Probably the error just means the file could not be run for whatever reason.<br />Does the new account have rights to execute the file?<br /><br />Regards,<br />MichaelMichael Jepsonhttps://www.blogger.com/profile/16073118583952778532noreply@blogger.comtag:blogger.com,1999:blog-7023576929606369407.post-33694987249031511352013-08-15T22:48:26.131+02:002013-08-15T22:48:26.131+02:00I've got one- what if your "Start in"...I've got one- what if your "Start in" path doesn't have quotes? I'm trying to run a scheduled task as a new user (one dedicated to running services and scheduled tasks) and when I switch over to the new account, I get this error.<br /><br />I've changed the task to "Run whether the user is logged on or not" (as I was getting that error) but now this error is Stephennoreply@blogger.comtag:blogger.com,1999:blog-7023576929606369407.post-57812714239589240332013-03-12T19:03:10.352+01:002013-03-12T19:03:10.352+01:00Thank you *so* much for taking the time to post th...Thank you *so* much for taking the time to post this!Michaelhttps://www.blogger.com/profile/03084407498706061686noreply@blogger.comtag:blogger.com,1999:blog-7023576929606369407.post-9191448734813847622012-08-21T11:21:01.817+02:002012-08-21T11:21:01.817+02:00Thanks!Thanks!Unknownhttps://www.blogger.com/profile/12595414683835339433noreply@blogger.comtag:blogger.com,1999:blog-7023576929606369407.post-2233346310468799992012-07-04T15:08:49.152+02:002012-07-04T15:08:49.152+02:00You've saved me today. Thanks!.You've saved me today. Thanks!.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-7023576929606369407.post-2146302703834757022012-05-30T08:09:29.065+02:002012-05-30T08:09:29.065+02:00A shining example of excellent UI design. I wonde...A shining example of excellent UI design. I wonder if the people responsible have some justification for it?Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-7023576929606369407.post-41966135144238085932012-01-10T13:45:19.377+01:002012-01-10T13:45:19.377+01:00Hi Matt,
Thanks for your message. As to how I fig...Hi Matt,<br /><br />Thanks for your message. As to how I figured it out: I removed the task and the second try it worked. Only difference was the fact that I had left out the Startup path, so I knew it had something to do with that. When I added it again, it gave me the error again. A bit of research into how the Startup path is supposed to be set solved it quickly from there.Michael Jepsonhttps://www.blogger.com/profile/16073118583952778532noreply@blogger.comtag:blogger.com,1999:blog-7023576929606369407.post-85317012333704603252012-01-10T13:40:43.996+01:002012-01-10T13:40:43.996+01:00Thanks for this tip - worked like a charm. Must...Thanks for this tip - worked like a charm. Must've saved me a good few hours of howling and butt-scratching. <br /><br />How on earth did you figure this one out?Matthttp://www.nourl.comnoreply@blogger.com