Myself also, after a reboot it's been working fine. But in one of our other locations this issue has been coming up as well. I'm going to have our local guy to a reboot and that should solve this issue (again).
Did anyone find a good solution for this? We have this error as well in a brand new server with brand new tapes. But only on Wednesday. It's been driving me nuts!!
Sam
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.