Intel macs consistently crash in AFP open/save dialog

Question

Hi.
We are experiencing a problem whereas we cannot open or save any documents on our intel macs from the 10.4.8 xserve. The intel macs will crash the application trying to open or save, even while just browsing the directory structure on the server from within the open or save dialog boxes. The shares are mounted with AFP. When mounting with SMB, things are better in that open and save will work, but printing now crashes the intel macs.
If we copy the files on to the intel mac and open them locally, everything is fine. However, such is the collaboration on projects in my company that we must have work with the files on the server, lest everything become a mess. I have found that it is while browsing folders on the server that contain old files with resource-forks that this happens. We cannot remove these files, as they are often the basis for our work. (for instance, we convert old quark files to indesign).
The trouble is: This is consistent behaviour for all our new intel macs. The trouble apps are MS Office 2004 and Adobe CS2, though there could be others, I have not tested. Also, the problem can be reproduced on other xserves with folders with resource forks in them and intel macs and AFP-file sharing.
I cannot possibly be the only one experiencing this? Has anyone else been through this and found a solution?
The server is an xServe g4 with 10.4.8

Answer 1

I have not had any crashes locally when browsing a fileshare on an Intel Xserve running 10.4.8 , however the Standard Operating Procedure there is not to work directly off the server (no network home dirs either).
Quark doesn't support it (not unless you use QPS), nor does Adobe (only if you use VersionCue or one other of their products), they don't.
I saw someone crash the AFP server process (when the server was a different machine, running an earlier version of 10.4 server) when ignoring the SOP and trying to save directly to the fileshare using Office v. X. A reinstall of the application applying all updates fixed that, but so did following the SOP.
Issues with Office apps & trying to work directly off a fileshare have long plagued many people.
I am not surprised at all that trying to open or save directly off a fileshare, using Office which will be running under Rosetta, could cause even more problems.
Please understand that you will be pursuing workarounds at best.
Out of many hints others have given for this issue, one was: make sure the group listed for the .TemporaryItems has r+w permission(s).
Make sure your user is in that group.
chmod 1770 .TemporaryItems
Also check your Word prefs and be sure that autosave is saving to a local directory on your own machine.