• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 7283
  • Last Modified:

Server 2008 Task Scheduler Last Run Result 0xE0434F4D

Since upgrading to Server 2008 we've been experiencing issues with one of our .NET applications that we use for a client. This website summarizes exactly what our symptoms are - we are able to manually run the scheduled task but when we leave it scheduled it fails to run.

Any ideas or work-arounds to make this application run via scheduled tasks that doesn't involve the company that programmed the proprietary software to re-code things? (they don't seem to be the best at responding to bugs)

1 Solution
David Johnson, CD, MVPOwnerCommented:
You might want to look at this:http://social.technet.microsoft.com/Forums/hu/winserverManagement/thread/776d6be1-8d2b-44d1-be22-9927c904200a

The solution is a specific hotfix http://support.microsoft.com/kb/940345

Another possible solution: Just set working directory into the action tab for you task. Maybe you using parameters for you programm, all files must be in the directory at the same level

Featured Post

Never miss a deadline with monday.com

The revolutionary project management tool is here!   Plan visually with a single glance and make sure your projects get done.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now