Jump to content

9.2.2 ASIP 6.3 Crashes on Retro Start-Up


Recommended Posts

While I'm waiting for a resolution of an issue involving Firewire drives (crashes during back-ups) I installed the Retro 5.0.201 update.....thinking it MAY help.

 

 

 

What I see is a crash EVERY time I start up Retrospect. There seem to be times when I'll get it to run but now it seems to happen constantly.

 

 

 

Please help!!!!

Link to comment
Share on other sites

  • 2 weeks later...

*UPDATE*

 

 

 

Some customers have reported problems when backing up AppleShare IP servers with both Retrospect 4.3 and 5.0.

 

 

 

There is one problem reported with Retrospect 5.0 running on an ASIP server, where Retrospect is definitely not the cause:

 

 

 

The ASIP server crashes when Retrospect 5.0 autolaunches or is launched from an alias.

 

 

 

We have identified this to be a problem between Mac OS 9 and the ASIP software that may occur when any Carbon-style application is launched from an alias. We have duplicated this behavior using other Carbon applications, and we have reported the issue to Apple.

 

 

 

Other reported problems currently under investigation include:

 

 

 

Retrospect 4.3 running on an ASIP server asserts failure or hangs during the backup's copy phase.

 

 

 

The ASIP server locks up when the first user logs in following a backup of the server with the Retrospect 4.3 client.

 

 

 

The ASIP server crashes at the beginning of a backup with the Retrospect 5.0 client.

 

 

 

Retrospect returns "error 1 (unknown)" for some files backed up from an ASIP server with the Retrospect 5.0 client.

 

 

 

Due to the complexity of the AppleShare IP software and the difficulty in reliably reproducing these behaviors in a controlled environment, Dantz has been unable to establish that Retrospect is the cause of these problems. As such, we have opened a developer support case with Apple to determine the root cause of these issues.

 

 

 

We consider this to be a matter of the highest priority, and we will provide additional information on these issues as soon as we have anything significant to report.

 

 

 

Thank you,

 

 

 

Dantz Technical Support

 

 

Link to comment
Share on other sites

Many thanks, but......

 

 

 

I just tried the idea that Retrospect has a Start-Up problem with the alias....not the program. I quit the application and tried opening it directly by double-clicking the program, not an alais. It opened fine the first time, but locked (the same way my alias has) the second time. Looks like it's more than an alias problem from here.

 

 

 

sigh......

Link to comment
Share on other sites

I'm upgrading to OSX next week in hopes of solving it.

 

 

 

On another note, I've also had serious problems not being able to back-up a Firewire Drive tower for months and no one is replying. Will that be solved as well??

 

 

 

If you'll review my other posts, you'll see what the issues are...

 

 

 

I have used Retro for years but am NOT a happy camper in 2002.....

Link to comment
Share on other sites

  • 1 month later...

Hello,

 

 

 

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.

 

 

 

Sincerely,

 

 

 

Dantz Development

 

Technical Support

 

www.dantz.com

Link to comment
Share on other sites

Archived

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

×
×
  • Create New...