"Access is Denied" Error Message

  • Thread starter Thread starter =?iso-8859-1?Q?Fran=E7ois?=
  • Start date Start date
?

=?iso-8859-1?Q?Fran=E7ois?=

I have installed an application from CD under the computer
administrator account. When I am logged in the computer
administrator account, I am able to start the application
with no problems. However, when I log in as a "normal"
user and try to start the application, I get the following
error message:

Operating System Error.
Access is denied.
ID: eWin: 5/ cFil: 24

I have tried to give full privileges on the folder
containing the application files to the "normal" user
account, but to no avail. Uninstalling the software and re-
installing it hasn't helped either. It is however
interesting to note that on startup of the application
after the second install, the application did not ask me
for a license key, as if it was able to reference the key
from the first install.

File volume is NTFS. All privileges on the folder /
children appear to be fine.

Any insights?
 
François said:
I have installed an application from CD under the computer
administrator account. When I am logged in the computer
administrator account, I am able to start the application
with no problems. However, when I log in as a "normal"
user and try to start the application, I get the following
error message:

Operating System Error.
Access is denied.
ID: eWin: 5/ cFil: 24

I have tried to give full privileges on the folder
containing the application files to the "normal" user
account, but to no avail. Uninstalling the software and re-
installing it hasn't helped either. It is however
interesting to note that on startup of the application
after the second install, the application did not ask me
for a license key, as if it was able to reference the key
from the first install.

File volume is NTFS. All privileges on the folder /
children appear to be fine.

Any insights?
Most applications weren't designed for this type of multi-user environment.
Such applications need to be installed in each specific user's account to
whom you wish to grant access.

First, be sure the account to which you wish to grant access is set to
administrator and not limited. Install the applications to the same folder
in which it was originally installed. This will look the same as one
install on your hard drive but create the pointers necessary for this user
to have access to the application.

Once the installation is complete, you can return the account to its limited
status if that is what you want and the user should still have access.
 
Michael:

Thanks for your reply. I have completed what you have
suggested and it was successful, up to a point. When I
started up the application with administartor rights given
to the user, it came up fine. When I reverted the user to
his "normal" privileges, ,the same error message began to
appear. It appears that I can only run the application as
an administrator, although that is clearly notintended to
be the case.

Any other suggestions?
 
Clearly this application has having a problem with this environment. Do you
have the latest version of this application, have you checked for patches,
updates and compatibility with XP?

If you are using XP Pro, you might try using the Group Policy Editor to give
the user rights to access the application. For information about the Group
Policy Editor, check the following Knowledge Base Article:
http://support.microsoft.com/default.aspx?scid=kb;en-us;307882

--
Michael Solomon MS-MVP
Windows Shell/User
Backup is a PC User's Best Friend
DTS-L.Org: http://www.dts-l.org/

Michael:

Thanks for your reply. I have completed what you have
suggested and it was successful, up to a point. When I
started up the application with administartor rights given
to the user, it came up fine. When I reverted the user to
his "normal" privileges, ,the same error message began to
appear. It appears that I can only run the application as
an administrator, although that is clearly notintended to
be the case.

Any other suggestions?
 
hi, this is something i encounter regularly.
In my experience, the problem is usually permissions - NTFS or registry.
Sysinternals, now owned by Microsoft, have excellent tools for this purpose : FileMon and RegMon.
Both free tools, they have in common that they can monitor what your unwilling app is trying to do.
One tool monitors access to your registry, the other monitors activity on files.
In both cases, you will look for access failures.

You can find them here, along with a huge load of essentials for a sysadmin.
http://www.microsoft.com/technet/sysinternals/Processesandthreadsutilities.mspx

Hope this helps.
 
Last edited:
Back
Top