Issue 9066 - Soffice.exe fails to load when user is in 'Restricted User' group
Summary: Soffice.exe fails to load when user is in 'Restricted User' group
Status: CLOSED NOT_AN_OOO_ISSUE
Alias: None
Product: General
Classification: Code
Component: ui (show other issues)
Version: current
Hardware: PC Windows 2000
: P3 Trivial (vote)
Target Milestone: AOO Later
Assignee: thorsten.martens
QA Contact: issues@framework
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-11-08 04:03 UTC by Unknown
Modified: 2004-03-22 09:31 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description Unknown 2002-11-08 04:03:07 UTC
with every restricted user on any of the machines, soffice.exe performs an 
illegal function, causing the program to not load.  this is bad...  only admins 
and powerusers are allowed to write!
Comment 1 stx123 2003-02-17 09:52:27 UTC
moving to component framework
Comment 2 stx123 2003-02-17 09:53:04 UTC
moving to subcomponent ui and  Reassign issue to owner of selected
subcomponent
Comment 3 thorsten.martens 2003-03-10 13:17:23 UTC
When installing OO644 as restricted user, this problem doesn´t occur
and isn´t reproducible. Please specify the version ("current" doesn´t
say much !). Give more information about the type of installation (eg.
net/workstation - or single user installation). Who has done the
installation ? Administrator or User ? Is there a special character
within the installation path or the username ? 
Comment 4 Unknown 2003-05-09 08:44:55 UTC
Issues 11946 and 11685 shown as enhancement requests would appear to
relate to this issue.  In issue 11685 developer release 644m3 is
indeed reported as being well behaved with respect to the multi-user
windows platforms (NT/2000/XP), subsequent ones apparently again
caused problems.

I administer 40 workstations, some linux, the rest win2k (as well as a
number of linux webservers and a win2k domain controller).  There are
many users, changing every few months.  **Having each [unprivileged]
user install OO in their own directory is unworkable**.

The only feasible solution is to install OO as the Administrator.   I
have installed OO 1.0 on a trial machine and am encouraging users to
try it out.  

At the moment this trial is a failure.

Have accepted the file associations for the MS .doc etc so that users
documents show up as OO icons, and will automatically invoke OO writer
or such on double-clicking.

Workarounds to install problems:  
Have manually put the .lnk files created in the Administrator's
personal copy of the start menu into the "All Users" folder so that
everyone has access to these.  Write access for "Everyone" given to
the directory where the binaries are installed (**not good**).  

However before each new user runs OO for the first time it appears
they have to run the Setup program in repair mode, perhaps to write
the environment.  This requires the installation package to be left on
the machine.  They then have to click 20-30 times "Ignore" on an error
dialog regarding registration of the .dll's (normal users dont have
registry key write priv's).  After this they can run OO.

They still have to manually change their defaults paths for Documents
and Temp to their own "My Documents" folder, or it will write these
into the installation directory.

Any fixes for this gratefully received as I would like to see a much
broader uptake of OO amongst my windows users (I use it under linux
and the multi-user issues there seem to be well solved).
Comment 5 thorsten.martens 2003-05-15 13:28:16 UTC
Please consult the setup-guide to get more knowledge about how to use
a OO/StarOffice network/client setup. 
Comment 6 thorsten.ziehm 2003-05-21 17:06:45 UTC
This task is 'resolved invalid' and will be closed now.
If you have more details to reproduce the task, please reopen it.
Comment 7 thorsten.martens 2004-03-22 09:31:02 UTC
.