DR Watson Caused By NT Not Finding A Backup Device?

Hello:

We have, on a devlopment server, running a long_running transaction for
almost two days. It was still running. This morning I decided to look at
three of two backup devices under EM to see if any backups were made to
these devices during the last couple of days on a de,mand basis by anyone.
The first one had a backup and the second and third device did not.
Somehow, and for some unexplained reason, the following message was put
into the MSSQL error log (and pretty much the same message went into the NT
event viewer).

----------------------------------------------------------------------
99/02/23 10:05:45.81 kernel dbsvolopen: Backup device
'E:MSSQLBACKUPEaglePro2_run02.DAT' failed to open, operating system
error = 2(The system cannot find the file specified.)
99/02/23 10:05:48.48 kernel dbsvolopen: Backup device
'E:MSSQLBACKUPEaglePro2_run02.DAT' failed to open, operating system
error = 2(The system cannot find the file specified.)
99/02/23 10:05:49.17 kernel dbsvolopen: Backup device
'E:MSSQLBACKUPEaglePro2_run03.DAT' failed to open, operating system
error = 2(The system cannot find the file specified.)
---------------------------------------------------------------------

This error, I beleive, caused DR watson to kick off and we could only sopt
it and revive the long running transaction by rebooting the machine, of
course thus requiring us to restart the lon_running transaction.

It look like NT couldn't find the backup device and therefore activated the
drwatson executible or so it seems to me.

Has anyone experienced this error before? IS it caused by NT? Or that
perhaps a certain threshhold was reacched on NT and drwatson kicked in?Any
other ideas?

Any information that can be provided would be GREATLY appreciated. THanks.

David Spaisman