|
Posted by Roger Abell [MVP] on January 18, 2006, 6:28 pm
Please log in for more thread options The tightening of permissions on application install areas began
with the release of W2k and tightened further with release of XP
and again with W2k3.
I am not familiar with your application architecture, as to where
and how users access the application. But, I would check how
the NTFS permissions are set (on the containing folder and on
the file itself also in case it is not inheriting), and if the access
is by a share over the network then also check the share level
permissions. The first is in the security tab in the properties of
the filesystem object, the second (share level) is under the
Permissions button on the Sharing tab for the shared folder
(again, in the properties of the underlying filesystem object).
Pay close attention to what groups have grants, and then
determine whether the new account that have issue are in
the groups as is so for the older account that have no problem.
--
Roger
>I suspect you are correct. Am I right in suspecting this
> is not then a server security issue, but a local
> security issue on the XP machine?
>
> Dbase does keep the vdb.ini in the BIN directory.
>
> Also until the recent security updates to Server and XP
> all domain users who were using the program had, and
> continue to have, no trouble. This is only a problem for
> new domain users added recently.
>
> Are you saying that by creating a share to the local
> application directory (containing the ini and the exe)
> and adding modify rights it should work? I've tried this
> by giving everyone permission, and it did not work.
>
>
> mvpNoSpam@asu.edu says...
>> You issue may be as simple as Users group having only Read/Execute
>> (not Modify) granted on the application's files. If so this is due to
>> the
>> application not following the specifications for a well-behaved (logo
>> certifiable) application which require that modifiable data be stored in
>> the correct areas and not with the program's binaries.
>>
>>
|