Apache OpenOffice (AOO) Bugzilla – Issue 91727
OpenOffice fails to start from a NFS volume
Last modified: 2013-01-29 21:46:09 UTC
We store our 3rd party applications on our NFS fileserver which gets mounted on /Network/Applications on the client. When I double-click the OpenOffice.org application I get this message: The application cannot be started. The user interface language cannot be determined. I tried this in my home directory (which is also NFS mounted with the same result. It does start from the downloaded .dmg or if I copy it to a local hard disk. Other applications (Microsoft Office or NeoOffice, for example) start fine from our NFS server.
Framework issue.
I just tried it again with OpenOffice.org 3.1.1 (310m19(Build:9420)]. It still fails to launch. The Console show this message: 10/28/09 11:38:06 AM com.apple.launchd[278] ([0x0-0x354354].org.openoffice.script[87590]) Exited with exit code: 77 I am running on OSX 10.5.8 Leopard. I'll be able to test it on SnowLeopard soon.
having the same issue here using OpenOffice 3.2 on snow leopard 10.6.2.
we have a large, and growing, mac desktops, and we use NFS for most of ower applications, and this is the only one that is failing, for a very long time
*** Issue 91727 has been confirmed by votes. ***
The problem seems to be with the way mac os x handles the file extended attribute, which over nfs are saved in the ._* files. ooo's registry seems to read anything under the registry directory including those files which aren't formatted properly and it fails... A quick workaround is something like: find OpenOffice.org.app -name '._*' -delete
I've just experienced this issue (exit code 77), when running directly from my Mac HD. I was able to fix by deleting my user preferences under home/Library/Application Support/Open Office/