Verified Answers


If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it!  Learn more

  • State Verified Answer
  • Replies replies
    3
  • Subscribers subscribers
    4
  • Views views
    1167
  • Users 0 members are here
  • Locked Locked
Related
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

PVCS - How to Edit Access Control Database

Robert Allen

Hello,

I recently became an admin, and received about 2 hours of training from the guy who was leaving (not his fault).

I have a user that is unable to access a project folder, but it appears he should be able to.

I am able to confirm that they are included in the user list via Admin->Security->Users... at the top level of the database.  If I select the specific project within the database, the Admin->Security menu item is unavailable (grayed out), so I cannot check directly whether this user has access to this project.  We are using Access Control Databases within this database, and I suspect that is where the problem is, but I can't figure out how to read the Access Control Database or edit it.  Is this something that I should be able to do within PVCS Version Manager stand-alone application (non-web)?

Regards,

Rob

  • 0  

    Hello Rob,

    The Admin | Security | Users menu is only activated when all of the following are true:

    1. The project (yellow folder) you selected has a black tab, indicating it has its on configuration (CFG) file.

    2. The CFG file has an ACCESSDB directive in it, resulting in that project (and its subprojects) using an alternate Access Control Database (ACDB), replacing the users & privileges that were defined at the parent level.

    3. The running Admin | Security | Users on this project is a security administrator in the alternate ACDB.

    If #1 or #2 are not true, the user will simply inherit the privileges from the parent level.

    If #1 and #2 are both true, you may not be an administrator in the subproject ACDB. In such a scenario you can use KB doc S107099 to add yourself to that ACDB file, so you can use Admin | Security | Users going forward to add/change/remove other users.

    Kind regards,

    - Richard.

  • Verified Answer

    +1 in reply to   

    Checked to make sure, and both #1 and #2 are true.  It's weird, because I can use Admin | Security | Users at the top level and on several project folders at the same level as the one that I can't.  I see that the ones I can use that menu item are using a different ACDB.  That must be the problem.

    Thanks!  I'll check with the other admins to see if they are able to get to it and hopefully update my access, so I can too.

    Regards,

    - Rob

  • 0   in reply to 

    If there are other administrators in the project ACDB, then having one of them change your privileges so you become an administrator there as well would be an easier way to solve this problem. Lacking that, use the readdb/makedb route from the KB doc.

    Kind regards,

    - Richard.

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.