Any chance that you have more than one session with the same userid
logged into the Sunray server at one time? Openoffice doesn't like this
as it assumes that only one instance will be writing to the .openoffice
config files.
I realize that this doesn't explain why 3.2 worked and 3.3 doesn't, but
perhaps some part of the .openoffice read/write code is more brittle in
the new version?
If this turns out to be your problem, we worked around a different issue
related to multiple same-user Openoffice sessions by including the
$SUN_SUNRAY_TOKEN value in the argument passed to the Openoffice
"-env:UserInstallation=" option (e.g. -env:UserInstallation=file://<path
including $SUN_SUNRAY_TOKEN>"). This ensures a unique OO config
directory for each userid/Sunray pair, but of course it means that
config isn't global for each userid across different Sunrays.
Sean Walmsley
On 07/22/11 06:25, Kevin Doyle wrote:
Hi
I have recently upgraded to SRSS 4.2 and Openoffice 3.3 We run Solaris
10 on SunRay servers
before the upgrade things ran fine. After the upgrade Openoffice crashes
a few times per day The solution is to
remove the .openoffice directory in the users home directory. However this
problem happens again a few days later and once again I remove the
.openoffice
directory.
Question does anyone else have the same problems with Openoffice 3.3 ?
and found a solution ?
I am thinking of downgrading back to 3.2
Many thanks
Kevin
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
