DB Maintenance Plan fails routinely.

  • I would speculate that the host was memory constrained.

  • This issue was resolved by re-creating the job. Apparently the job itself had somehow become corrupt and that is why it was executing twice. Created a new job from scratch and this was no longer an issue.

  • Thanks for the update and solution. That shouldn't happen often, but it's good to consider removing and recreating the job.

Viewing 3 posts - 16 through 17 (of 17 total)

You must be logged in to reply to this topic. Login to reply