• This wound up being an issue with the D: dependency. The original configuration was changed at one point to add a new, larger volume which replaced the old D: but the dependency was still pointing to the old drive. this is because the old drive was still in existence but had the drive letter changed. Once I added a new resource for the correct volume and added it to the sql server as a dependency i was able it resolved the issue.