Launch failure: null

[Art Blount]

From time to time we experience job failures that return "Error Occurred" job statues. When opening the Output tab the content displays "Launch failure: null.

Has anyone experienced this issue, if so what step have you taken to resolve?

Master version - 6.02.179

Plugin(tes-6.0) - 6.0.2.180

[Derrick Au]

Hi ablount1115,

How is your Tidal job setup? An error occurred is a pre-execution error preventing Tidal job from launching the job at agent. Verify job definition for the following: command, working directory/environment paths, runtime user, and agent are valid.

[Art Blount]

Hi Auderrick,

The jobs that return Launch:null run on the JDE Adapter. We have been exeperiencing this issue for some time now. We have many jobs that repeat every 10 to 30 minutes and one occurence of the job will report Launch: null. If you resubmit the job it runs fine or the next occurrence of the same job will execute without any errors. Agent, runtime users are active and valid and no changes are being made to the jobs.

[Derrick Au]

Hi,

I am not familiar with the JDE Adapter, have you tried checking into the adapter logs and see if anything stands out?

BR,

Derrick Au