Home/ Questions/Q 9394
Next
Answered
computing
  • 0
Asked: 2021-12-01T11:55:40+00:00 In:

Solved Scheduled Task Stops Running

  • 0

Hello,

I have an EXE that I created using Visual Studio Professional 2010. When I run it manually it runs fine but when it runs in Scheduled Tasks it will run for a while but eventually fails with error code 0XE0434F4D. I know that it runs for some time because it does produce the expected output file, however the file is incomplete.

The file runs fine on a Windows Server 2003 system (this is where it was originally created).

The problem is happening on a Windows Server 2008 SP1 machine. The process queries the SQL server backend of the WSUS server that’s installed on the same machine (local).

I’ve ensured that all dirs and files involved have full authority for the ID that’s running the task.

Any ideas what could be causing it to run for a while and then fail?

Thank You,

Rakesh T.

Share

    1 Answer

    1. Best Answer
      I fixed this by re-compiling the VB script in .NET Framework 3.5. It must have been created in a previous version which was incompatible with our new WSUS servers.
      • 0