Kbase 20835: Appserver Access Rights
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
6/21/2002 |
|
SUMMARY:
This solution discusses access rights to the Progress AppServer. The rights are inherited from the owner of the ADMINSERVER/NAMESERVER.
EXPLANATION:
When you try start an AppServer, the access rights to the required files are based on inheritance from the user who started the AdminServer. For example, if a .pf file is on a mapped or shared device, the access rights to that .pf file come from the owner of the AdminServer, not necessarily from the user who attempts to start the AppServer.
To test this functionality, start the AdminServer/NameServer as "system account" and attempt to start an AppServer with a different user name. The AppServer should fail because you do not have the
appropriate access rights.
As a case and point, assume that you have created a .pf file that resides on a mapped or shared resource to be used as a common .pf file:
When a different user attempts to start an AppServer with the
"common" .pf file, that user gets an error that indicates the
AppServer cannot start. In order for this user to use the common
.pf file, the user must be in the same user group as, or have
equivalent rights to the .pf file you created.
When this situation occurs, the user who is trying to start the
AppServer might see a Progress (8113) with an errno = 13 error,
followed by text that indicates the system is unable to open the
.pf file.
The errno 13 indicates that the data in the .pf file is invalid,
yet when the same .pf file is used on a local drive, the
AppServer can be started.
SOLUTION:
Make sure that the user who is attempting to start the AppServer has access rights to the resource where the common .pf file resides.