Jump to content

ASIP 6.3 Crash Workaround


Recommended Posts

I have found a workaround for the Appleshare IP crash problem - at least one that works for me. I discovered that it was not ASIP per se that was the problem, but rather ASIP filesharing. When I turned off filesharing, the backup proceeded with no problems.

 

 

 

Given the way I saw the crashes happen (sometimes an immediate crash, sometimes no crash for a minute or two), here's what I think is going on. The backup starts just fine, but then if someone makes a file access while the backup is happening, the crash occurs. Without filesharing on, this can't happen.

 

 

 

Now I understand that some have fileservers that have to be up all the time, but it's a workaround, not a solution.

 

 

 

The real pain is that the stop and start have to be done by hand, at least I think so. I haven't been able to find any AppleScript way to turn filesharing on and off. Anyone know of a way?

 

 

 

Don Carlile

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

  • 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

I cannot agree with that analysis.

 

 

 

Version 4.x of retrospect used to work fine with ASIP. Why not get the 4.x client to work with the 5.x server. This is more a marketing issue than a technical issue. There may be a bug in Apple Carbon libraries on ASIP but this library is not required to write software on ASIP, especialy that you had a working version before.

 

 

 

Pierre Frisch

Link to comment
Share on other sites

The 4.x client does work with the 5.x server.

 

 

 

As long as you have paid to upgrade your licenses to 5.0 for your application and clients, the Retrospect server will log in clients running 5.x software OR 4.x software. The only requirement is that they are TCP/IP clients.

 

 

 

If you revert to the 4.x client and this is successful, that's perfectly fine.

Link to comment
Share on other sites

In reply to:

Version 4.x of retrospect used to work fine with ASIP.


 

But Version 5.x of Retrospect does not.

 

 

 

It's not about the client software, which is only a communication channel between the Retrospect application and the remote computer.

 

 

 

As I read the statement it is because for 5.x Dantz used the up-to-date API's that Apple guidlines said to use. But those modern programing calls (sometimes) fail when communicating with the hack job that is (and always has been) AppleShareIP.

 

 

 

Dave

Link to comment
Share on other sites

Archived

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

×
×
  • Create New...