Jump to content

Crash when starting backup after upgrade

Recommended Posts





I upgradet Retrospect 4.1 to 5.0.205 and since that time I can't backup anymore.


Everytime I want to start the backup (manual or script), Retrospect scans the SCSI


and crashes after that with an "Error 1". Using the streamer in the configure->devices section, everything works fine (scanning and changing tapes).




Hardware: G3/350, 512MB Ram, with MacOS 9.1 and a Sony TSL-A300C AIT Autoloader

Link to comment
Share on other sites

Is the error "error 1 (unknown)" or "Error type 1?"




Error type 1:


Retrospect 4.3 and Retrospect 5.0 have one major difference: Retrospect 5.0 is a Carbon application which allows it to run on OS 9 as well as OS X. Any Carbon application running on OS 9 requires the CarbonLib extension, in addition to base extensions, to launch and run. With previous versions of Retrospect, no extensions were needed to actually launch the program.




You may have programs on your machine that conflict with CarbonLib or Carbon based applications in general. It is important to update all your programs to ensure best case compatibility.




We currently do not have a list of known extension conflicts. Every system is different, and extensions that have a conflict on one system do not always have a conflict on another system.




Regarding the error Type 1, we have not seen a situation yet where the problem does not go away when booting from either the System CD or a Retrospect CD. This would indicate an extension conflict with an installed program that may not be designed to run while Carbon applications are in use.




Also, CarbonLib 1.6 and Authoring Support 1.19 are now available from Mac OS 9's Software Update control panel. You may need to be using OS 9.2.2 to upgrade.






Error 1 (unknown) on ASIP Server:


Dantz has been investigating several problems that customers have reported when backing up an AppleShare IP server with Retrospect 5.0. Reported problems include:




1) The ASIP server crashes when Retrospect 5.0 autolaunches or


is launched from an alias.




2) The ASIP server crashes at the beginning of a backup with the


Retrospect 5.0 client.




3) Retrospect returns "error 1 (unknown)" for some files backed


up from an ASIP server with the Retrospect 5.0 client.




Our investigation has revealed that these problems result from using Carbon APIs with AppleShare IP software. Problem #1 occurs when any Carbon application is launched from an alias, confirming our contention that it is not a Retrospect issue. Retrospect 5.0 uses HFS+ file system calls, as specified by Apple, which stimulate bugs in the AppleShare IP software, resulting in Problems #2 and #3.




We have reported all of these problems to Apple, but Apple's development efforts are now focused on Mac OS X Server. Without a commitment by Apple to address these problems, we have no choice but to suggest that our customers consider replacing AppleShare IP with Mac OS X Server.





Link to comment
Share on other sites


This topic is now archived and is closed to further replies.

  • Create New...