cancel
Showing results for 
Search instead for 
Did you mean: 

Job started but empty log files and no job execution

MarcusZwirner
Product and Topic Expert
Product and Topic Expert
0 Kudos
561

Hi experts,

from time to time we observe a very strange behavior of Data Services.

When we start a batch job (it doesn’t matter if the job is started from the Designer or via command line) it happens occasionally that the job seems to be started, i.e.

  • in the Designer the execution window opens with the trace log,
  • in the server_eventlog_<date>.txt the job start is logged (“Starting job …” and “ … is kicked off”),
  • the three log files (trace, monitor and error) are created,

but nothing else happens, i.e.

  • in the Designer the execution window with the trace log remains empty,
  • the three log files (trace, monitor and error) remain empty,
  • the job is not executed (the data is not processed)
  • the job is not displayed in the Management Console
  • no error is thrown or logged.

This happens incidentally (sometimes once every one or two month, sometimes several times a week, …). And we couldn’t identify any sort of pattern so far. It is independent of the Data Services release (we saw it with different SPs and we are now on the latest version 4.2 SP12 patch 3) and it happens even if we use the Designer directly on the Windows server where the job server runs.

If we start the same job with the same settings shortly after once again, it runs without any problems.

Did anyone observe a similar behavior?

Any ideas what could be the root cause or trigger?

Thanks a lot and best regards
Marcus

Accepted Solutions (0)

Answers (0)