Thanks for your response, Brian.
I always use an account with Sysadmin permissions to connect to the SQL Docs 2 project.
I've run DBCC Check on the database and found nothing wrong internally. If I remove the offending object from the list of objects to document, it stumbles over an object further down the list. If I remove that object and it stumbles over another object yet further down the list. I've tried this about 10 times and decided that even if it did finally succeed, the resulting documentation would be missing so many items as to be quite useless.
It would be nice if SQL Doc would tell me what it's expecting to find that isn't there. It must know if there is an "object reference" in the first place. It doesn't do that, however, nor does it write this information to its log. If I knew what it was stumbling over, I could fix it, but there are just too many objects in this database to guess.
Any ideas or strategies you may have for tracking down this "missing" object would be greatly appreciated.
Thanks again, Brian.