error -557 ( transaction already complete) and Retrospect engine crashing

[gregwelch]

Hello.

 

I am running Retrospect 8.1.626 on an Mac Mini (2009, Intel) running OS X Server 10.6.2. With a proactive backup of one client in particular (it seems) I am seeing frequent occurrences of "error -557 ( transaction already complete)", and (perhaps related, or not...) subsequent crashes of the Retrospect Engine, requiring a reboot to get it restarted. The crash logs indicate the same error every time: EXC_BAD_ACCESS (KERN_PROTECTION_FAILURE) way down in libSystem.B.dylib. The client in question is an Intel Core 2 duo iMac running also running 10.6.2 ("client" OS, not Server). The backup is a "file" backup to a brand new (recently formatted) external 2TB Firewire 800 drive.

 

I have done a complete removal of Retrospect (including config files, logs, etc.), re-installation, and manual recreation of my scripts (a couple of copy and proactive backup scripts). I have checked the disks on the client mac, etc. but can't seem to find a problem.

 

I have searched the web and the forums and cannot find anything that seems relevant, aside from some other mentions of 8.1.626 crashing and some question of stability under OS X Server.

 

Anyone know what the "error -557 ( transaction already complete)" error is? The list of error codes on line does not appear to have any associated KB articles.

 

I apologize in advance if I'm missing something (I have tried to look), and would be grateful if anyone has suggestions for further debugging, etc.

 

Thanks.