Find Answers

Filter Search Results
All Operating Systems:
All Products:
All Solution Types:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML How To: #662 PB 4.0: Minimum AccessDB privileges to run the PB interface
How To: #662 PB 4.0: Minimum AccessDB privileges to run the PB interface
CMS-XML How To: INT APPROVED: #502 PB 4.x/5.x using the non-SCC interface: Can I use conditional constructs in MASTER.CFG? (AccessDB)
How To: INT APPROVED: #502 PB 4.x/5.x using the non-SCC interface: Can I use conditional constructs in MASTER.CFG? ( AccessDB )
CMS-XML How To: Provide Project-level Security
I set my ACCESSDB in the project.cfg file.
CMS-XML User Error: #427 OPTIONS|SECURITY GPF - USER, GROUP AND PRIVILEGE WITH SAME NAME
PROBLEM : User had a defined a USER, GROUP and PRIVILEGE in the AccessDB with the same name causing a GPF during a Options|Security| process.
CMS-XML Error: Internal error #98, PVCSQueryConfiguration
2. Make sure that you don't have two instances of VM DLLs. 3. If an AccessDB is defined, make sure that the user has sufficient privileges in it. Keywords: PVCS_E_CANT_OPEN_VCONFIG_FILE
CMS-XML Problem: Tracker vmi closes when a new file is checked in.
also try commenting out the accessdb for a test to see if the user is not listed in the accessdb .
CMS-XML VM: Setting up ACDBs on subprojects using command line
Create a subproject CFG file containing the one line, having the directive: ACCESSDB = PathToSubprojectACDB Run the PCLI command:
CMS-XML Error: "The Access Control Database Is Corrupted" or "Cannot perform action on archive"
When a user tries to check out get this error (read or writable with lock): This possibly means that in the Privilege name used inside the accessdb has a space in it: Example: "PROD LEAD" OR
CMS-XML VM: Error: pvcs.exception.PvcsSecurityException: No Access
The ACDB file does not exist in the location that is defined by the ACCESSDB directive in the subproject's Configuration file. This would affect all users.
CMS-XML About: VM6.5: Copying a 6.0 project to a 6.5 project database doesn't copy the access control database
If the original configuration file for the 6.0 project doesn't have the ACCESSDB directive, but is inheriting it from the 6.0 master project, then the access control database will not be copied. A new access control database will be created for the 6.5 project with the only user being the user who copied the project.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs