I have studied numerous sites about how to deal with Batch Jobs that fail or are stuck.
Process is basically:
Stop all Batch Jobs
Disable All Schedules
Re-create Batch Jobs
Run each Batch job
* Re-enable job schedules
I've also studied how to identify any Job Modules that have errors.
However, in 'my' case, none of the Batch Jobs moves past 'Running', whilst all modules continue to display 'Not Started', even after many hours.
It doesn't matter which Batch Job I run (although I understand the correct sequence 'should' be - DWMaintenance, MPSyncJob, Extract, Transform, Load - I have tried running jobs in this order, or any order - results are the same, the Batch job is stuck at 'Running' and the underlying modules all show as 'Not Started'.
How can I identify 'what' is stuck, or failing? (There are no errors!)
How long should I leave the job running? (I understand the ETL jobs stopped several weeks ago, so assume there is lot of catch up to do. But if I leave a job running, how can I know that it is still doing 'something', just taking a long time, or, it is stuck?)
Windows Event Viewer shows no errors.
Database shows no errors.
I don't know where else to look, or what else to look for.
As I say, anything I can find online simple explains how to stop/re-start batch jobs and/or find batch jobs/modules that have failed (error 7).
Anyone have any advice?