I believe the different screen shots are all showing different problems.

The first is showing a problem from almost a year ago, apparently seen by a session manager. It would be good to investigate the related session. But 1 it may not be available anymore and 2 it may be totally unrelated to your current issues.

The second one is from a copy session where no agents are started because there are simply no devices availble. I would check the copy spec to know what devices are configured. Once you know that I would check that those devices are free and accessible. Maybe they are locked by other sessions (current sessions or failed sessions from the past). Or maybe they have been disabled. This seems to be something from today, so this is probably worth investigating!

The 3rd screen shot is showing sense info from debug.log reported by RMA and is showing a medium error (UNRECOVERED READ ERROR). Maybe this has lead to disablement of the device!?

Thank you so much for the reply, sir. The first one for which I have attached screenshot is happening over the last couple of years. When I try to restart a session a pop up window appear for which I am attaching the screenshot. I was wondering it is because of the tape drive driver in the device manager which the document says that it has to be removed I am also attaching those two screeshots. 

Well this is yet something else. Now you are using a device which has been removed. You need to reconfigure the device in "Devices and Media" OR you need to update your copy specification with the correct device name (which you can see in "Devices and Media").

Thank you, sir. Here are the screenshots of the configuration. Drive is dectected by the hp data protector. Destination and libraries are configured in way depicted in screenshots. 

OK what's expected here on this forum now?

Here's what I see in the screen shots.

1. In the copy spec I see no destination devices selected. I can only assume you normally have the MSL library selected there
2. The second screen shot is showing the drive configuration
3. The 3rd one is showing that no library filters are used in the object selection, which is irrelevant to this problem

Note that the logical device name in the error you shared ealier today differs from the current device configuration. That's most likely why you do not see anything selected when you pull up your copy spec right now. So all that is making sense and if you would just select the current device in the copy spec then it should work. That is if your (pysical) device is working as you seem to have a lot of troubles with that too.

Thank you so much. I am almost near solving the problem. However one last query I think why this issue happening. I am attaching screenshot.

This is really a problem with the device itself. You showed a debug.log entry before but not sure that was related to this error. You should look for a message in debug.log at exactly the time the error occurred. But this is what I said before ... you seem to have issues with the hardware itself.

Thank you so much. This is what log file displays at the time the event log message displayed device at 9/5/2024 5:30:37 error.

OK, I cannot find this sense data anywhere. Maybe the output is decimal and needs to be converted to hex (Q: 29h) and so you have a bus reset. I cannot remember. But you are uisng a DP version which is a decade old. I even cannot check anymore when it went out of support. DP9 went out of support more than 5 years ago. Also for the device, I'm missing the manual because it is too old.

I can only repeat that your hardware seems to be suffering from a lot of issues. Now, when you selected your device in the copy spec, does it run now or not???

It does, sir. Sometimes the color of the tape drive change to yellow. I am wondering why does the the destination drive got unchecked on its own in copy specs. And some the media got change into unformatted. And besides the tape drive hmi shows three of the tape statuses are not ok and maybe it is because of this.