The databases are still attached; however, they have no "objects" under them (i.e., no tables, views, programmability...basically the "plus sign" is no longer there, only the database name.) I will contact the developers who used these databases to find out why this happened. The developers have full access to the objects on this server as it is strictly development use, so this not a critical issue.

This may have been a better "Newbie" post, based on my lack of understanding on how the databases ended up in this state. I've never seen databases with no objects associated, and the fact that these are the only databases causing the plan failure makes them intriguing.

In any event, thank you for the information. I will find out if the databases can be detached and archived and see if that removes them from the T-SQL backup script and corrects the failure of the maintenance plan job.

K