AFP, error code 50 and database (Entourage) documents

Question

Level 1

0 points

AFP, error code 50 and database (Entourage) documents

We see some strange behavior lately: we have Novell servers in aur institute (University, with latest updates applied) to which we connect via AFP. The problem is, copying some documents from the finder returns an error 50. Mostly (but not exclusively) databases documents (like databse of Entourage 2004 or backup databases from SOHONotes 6.3) return the error. Creating e.g. a new Word document, saving to the finder and copying to AFP volume retrurns NO error! (same is true for .xls). The behavior seems to be erratic: copying a document from AFP volume to finder, then deleting the original and copying back works for certain documents, for other not... Even more strange: on some days we can copy these documents (automatic backup to distant volume), on some others not...
What we tried until now: runnig Applejack (all tasks including cleaning caches and VM) in single user mode, renaming documents, numerous log-outs and reboots ⚠, rebuilding database(s), .... Making .zip or .dmg from the incriminated documents does not wort either...
Interestingly manually creating a backup from SOHONotes at destination (directly on AFP volume) works without problem...
Anybody with the same problem, or even a solution???

G4 1GHz DP, 1.5 GB RAM Mac OS X (10.4.10)

Posted on Jul 18, 2007 6:09 AM

Reply

Answer 1

Best reply

a brody

Level 10

82,925 points

Jul 18, 2007 6:25 AM in response to GTM

An error 50 can be a read/write error. It may be your mounted volumes aren't solidly connected at all times, so a program might have problems reading and writing to those network mounts. It is best in such scenarios to operate on your files locally, and use networking just for "sneakernet" and backup purposes.

Reply

Answer 2

GTM Author

Level 1

0 points

Jul 18, 2007 6:33 AM in response to a brody

It is best in such
scenarios to operate on your files locally, and use
networking just for "sneakernet" and backup purposes.

Thanks for the suggestion. The problem is: it is exactly the way I am using aour AFP volumes!! The corollary being, that if I cannot beam up my backups, they are of very little use... I always work locally and have chronosync programmed to copy all changed files at the end of the day...

G4 1GHz DP, 1.5 GB RAM Mac OS X (10.4.10)

Reply

Answer 3

a brody

Level 10

82,925 points

Jul 18, 2007 6:36 AM in response to GTM

I suggest isolating the issue on the network hardware.

Reply

Answer 4

a brody

Level 10

82,925 points

Jul 18, 2007 7:35 AM in response to a brody

I might also add, I'd start to migrate away from Entourage, it is very weak when it comes to data integrity. While it has a database rebuild program, it puts all your eggs in one basket more so than any other program. See my FAQ* on how to migrate:

http://www.macmaps.com/entouragemigration.html

* Links to my pages may give me compensation.

Reply

Answer 5

GTM Author

Level 1

0 points

Jul 19, 2007 5:49 AM in response to a brody

We finally traced the problem back to quotas on the NetWare AFP volume: approaching the limit (i.e. being 300 MB near the limit!) caused havoc on the transfer. Strange is, that files as small as 5 MB could not be copied (temporary data created by finder??). Setting a new higher limit resolved the problem...

Reply