Thanks for your suggestions; the problem was resolved but it went a little deeper that this. Your suggestions were right on the money, and worth every penny I might add. ;)
After powering down the server and both attached libraries, re-seating all cables (both ends) and applying the latest driver library driver update, I did have to delete the robotic library definitions and after rebooting the server the Library devices were once again recognized and without the phantom tape identified in the drive. The devices were then re-labeled as they we re-numbered sequentially; First Library 1, First Tape Drive 2, Second Library 3, Second Tape Drive 4, and then re-associated the devices to the job profiles per media set and life is good again in the land of archival.
The two libraries were identical, but one was set for emulation mode and the other was not. This caused two drivers to be loaded and one was a little older than the second. I guess when the tape failed, the drive did not know how to recover.
Thanks for your assistance.
I wish everyone had as good a result as I have had with Ver 11.
Keep up the good work.