morseth Posted May 29, 2003 Report Share Posted May 29, 2003 We have recently upgraded from Retrospect multi-server 6.0 to 6.5. The upgrade went very smooth, with one exception. One of the clients refuses to backup now, stating the following error mesage: "Can't access volume FCPO8001 on FirstClass, error -557 (transaction already complete)" I couldn't find much info on this particular error message, nor could I find anyone else experiencing this issue in the forums. What steps should I take to resolve this error? What causes it to begin with? The client computer is running Retrospect client version 6.5.127 Link to comment Share on other sites More sharing options...
AmyJ Posted May 29, 2003 Report Share Posted May 29, 2003 Try a clean install of the client software - uninstall / reboot / reinstall. Link to comment Share on other sites More sharing options...
morseth Posted June 3, 2003 Author Report Share Posted June 3, 2003 I gave that a try, and it seemed to only resolve the issue for the first backup of this client. It is now again reporting the -557 error as before. What exactly is theis error trying to tell me? Link to comment Share on other sites More sharing options...
AmyJ Posted June 5, 2003 Report Share Posted June 5, 2003 Rather then list the entire client in your script, try adding the individual hard drives. Does the problem go away? The development team has been investigating isolated reports of this issue. Link to comment Share on other sites More sharing options...
morseth Posted June 9, 2003 Author Report Share Posted June 9, 2003 Tried not using the "client alias" method and instead dragged the actual subvolume into the backup group, but still no difference unfortunately. This method did fix a problem on a different client of ours though, for the record. I have also noticed that it isn't just during an attempted backup of this client that I get the -557 message. If I go into the Clients tab and try to access the properties for that particular client, I get the same -557 message. The only temporary solution I have found so far is rebooting the backup client computer, but this is very impractical since it is our e-mail server. Rebooting it allows it to backup just one time, then the error returns again. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.