Can't read file

[ckatzuc]

After updating to version 5 (running on OS 9.1 backing up and Appleshare IP server running OS 9.0.4) I get numerous "Can't read file "name" error 1 (unknown)" messages - over 100. Previously, 4.3 backed all of these up with no problems.

 

 

 

In addition, if I try to back up the full server instead of just my documents folders - the server crashes every time.

 

 

 

Any ideas would be appreciated. I've tried searching the support site for that error number - it's basically useless.

 

 

 

Thanks,

[Guest]

Dantz is aware of and actively investigating this issue.

 

 

 

See the threads on ASIP hangs and crashes.

 

 

 

Thanks,

 

 

 

Irena Solomon

 

Dantz Tech Support

[Guest]

*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

 

 

[Guest]

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

[vlherring]

I finally gave up backing up to CD-Rs because the alleged compatibility on Dantz site did not exist - went to LaCie FW HD instead and all or almost all is working fine =- Normal back up being done but this is a problem that has existed long before = pretty consistently (every time I back up) I have the same 54-56 errors... "can't read file, error -1, unknown path" - which is wierd since it's successful in backing up the other ones == what are not being backed up are jpgs in iPhoto library = the same as the other backed up jpgs.

 

 

 

And they are on the resident volume. In other words, I am using my 800 mhz iMac, lots of ram, Retro 5 to back up that and Cube over network and getting the same 54=56 items that won't back up. Some of them say 'different modification date' but not always.

 

 

 

Any thoughts on that???