Forum Discussion
3 Replies
- Colin_WeaverModerator
Looking at every job log (for the same jb) going back to (and including) the previous full.
In every job logs expand the details and check the resources (by which we mean C:, D:, System State , SQL instance, Exchage databases, VMs etc) and compare with the job log that claims a new resource was found.
Then look at why that resource might not have been available during the presvious jobs (has a resource been bought online or moved)
- ManujackLevel 4
No encuentro ninguna relación en ninguno de los log,s tanto en el diferencial como en el completo.
Puede ser un error de la base de datos?
Gracias
- Colin_WeaverModerator
We cannot determine the cause accurately from the forums, If this continues to happen then suggest you log a formal support case (or delete and recreate the job and run a full first) - if it was a one-off then you can probably ignore it.
Related Content
- 12 years ago
- 13 years ago
- 11 years ago