Community
Participate
Working Groups
Defect reproducible only with Win 2000 Server. Eclipse installed by user in Administrator group in c:\program files\eclipse. Eclipse started & default workspace selected, set as default to always open & populated with various resources - java proj, 2 text files. Log out. User in low-level User group, which does not have rights to Modify c:\program files (but does have Execute rights) starts Eclipse. Error message, caption "Eclipse" message "An error has occured. See the log file c:\program" Note the "c:\program" truncation. Access to admin-created workspace should not be allowed, but should prompt for alternate workspace name.
Used Eclipse JDT SDK Build 200406251208
The first time you run eclipse, the configuration is created in "c:\program files\eclipse\configuration". This area is used to store the values presented in the workspace chooser (c:\program files\eclipse\configuration\org.eclipse.ui.ide). When the low-level user runs this eclipse, the configuration area is being found (this is a good thing because this way everybody shares the same manifest files and other runtime things) and the workspace chooser is populated with the info available (which is not interesting in your case). In order to set up your shared install of eclipse, simply run: eclipse -initialize This will generate all the config files and stuffs but it will not create a workspace and therefore the config.ini will be clean to that respect.
Created attachment 14180 [details] log This is the log file that I got when I changed my windows configuration directory (and all sub-folders) to read only and then tried to start eclipse. The stack shows that execution didn't get as far as the IDEApplication, the root problem is somewhere inside the runtime. There's an 'Access Denied' from near Locker_JavaNio.java:30. This surprised me because I thought that if the runtime could not read the configuration directory then it would use some user-local configuration area instead. Perhaps that is only if the user has properly setup their shared install (which I intentionally did not do in this case). The interesting thing (at least to me) is that although the config area was marked read-only AND although eclipse failed to launch because the config area was read only; my log file got written into the configuration directory.
Moving back to pascal since the error is happening before the workspace launcher code is executed. I've also changed the title to match the error that I attached in comment 3.
Several improvements have been done in this area, could you try with the 3.0.1 candidate.
Please reopen when you can provide the information requested in comment 5.
tester who originally reported bug does not respond. Assumed fixed.
As of now 'LATER' and 'REMIND' resolutions are no longer supported. Please reopen this bug if it is still valid for you.
