Folks: Entourage 10.1.4 on MacOS 10.3.2.
OK, so I had some files on an OS9 Mac on my LAN to attach to an outgoing message. Why not mount the remote Mac, navigate the "Add" dialog to those files, and so on. This appeared to work: eight files in the Attachments box, reasonable sizes. But when I went to send the message, an alert: 4363 "Unknown Error" appeared. This happened each time I tried. I sent a test message to the same addressee. The message went out instantly. Saved the original message as a draft, deal with this one tomorrow. It's now tomorrow. After some headscratching and looking around on the web with no particular success --rebuilding the database didn't seem a good bet-- I wondered, "Something wrong with the attached files?" Tried drag-saving them from the message to a local folder. Only four made it -- the remainder went missing. Hypothesis: Something was wrong with the attachments. Reconnected to the other Mac, manually copied eight files to a local folder. Deleted the existing attachments, added all eight from the local folder. The message transmitted with no problem. Problem solved. Maybe I simply didn't allow enough time for the transfers to conclude before sending the message, though I would expect this to be worked out between the app and the OS. An incomplete transfer might be anticipated and handled appropriately. Conclusion: If you get error 4363 on a transmission attempt, and you have one or more attachments, try deleting and re-attaching the file or files. Comments about this experience: 1) Giving a numerical error message is very 1980's. Does anyone recall why computers commonly gave numerical error messages way back then? 2) Displaying the message "unknown error" is worse than useless. 3) Those who suggest "rebuild your database" or "really rebuild your database (use advanced rebuild)" to people who ask for help are, by this particular evidence, no better informed than the actual recipients of the error message. I wonder if indiscriminate prescription of this generic treatment contributes to the perception that Entourage databases are more fragile than they really are. That's my firm impression. If there really are a number of potential causes and it is difficult to be more informative, how about the error message referring users to a KB article that describes what might be the causes? Thanks, Henry -- To unsubscribe: <mailto:[EMAIL PROTECTED]> archives: <http://www.mail-archive.com/entourage-talk%40lists.letterrip.com/> old-archive: <http://www.mail-archive.com/entourage-talk%40lists.boingo.com/>
