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 After making an archive update, user gets: Serena PVCS Version Manager could not read the information stored in the archive ""
After making an archive update, user gets: Serena PVCS Version Manager could not read the information stored in the archive ""
CMS-XML Error: Version Manager could not read the configuration file "..\master.cfg". Please contact your PVCS Administrator for further assistance.
Error: Version Manager could not read the configuration file "..\master.cfg". Please contact your PVCS Administrator for further assistance.
CMS-XML VM 8.x: Add Workfile with Chinese characters in the filename, got the error => Serena PVCS Version Manager could not read the information stored in the archive "...?..."
VM 8.x: Add Workfile with Chinese characters in the filename, got the error => Serena PVCS Version Manager could not read the information stored in the archive "...?..."
CMS-XML PCLI ScanPDB does not detect PvcsID error / How to fix "Unable to read pvcsid file" error
PVCS Version Manager 8.0.2.0
CMS-XML VM I-Net: Unable to read "\pvcsroot.ser". Use nonce "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx".
PVCS Version Manager 8.4.2
CMS-XML Incorrect error "Unable to read File Server configuration information from ...\servers.ini. The path may no longer be valid, or you may not have permissions to read this file."
PVCS Version Manager 8.1.2
CMS-XML Unable to read "...\pvcsproj.ser". null - java.io.EOFException
at java.io.ObjectInputStream.<init>(ObjectInputStream.java:280) at pvcs .suite.io.file.PersistObjectInputStream.<init>(PersistObjectInputStream.java:42) at pvcs.suite.io.file.PersistObjectInputStream.newInputStream(PersistObjectInputStream.java:56)
CMS-XML VM GUI: right-click -> Properties on a file whose archive cannot be read should still show archive path
PVCS Version Manager 6.6.00
CMS-XML Version Manager could not open the access control database, "ACDB Path". Please contact your PVCS administrator for further assistance.
When not using a VM File Server and using a desktop client, make sure the end-user at least has read permissions to the ACDB path. If the path involves a mapped drive, make sure the end-user has this drive mapped.
CMS-XML PVCS VM GUI on UNIX/Linux cannot run in setuid mode when tunneling X11 (X-Windows) through SSH (Secure shell)
Setuid mode is a way for Version Manager to ensure all read and write operations for the repository (i.e. the files contained in the project databases) are performed by a single user ID, typically named " pvcs ". Doing so allows access to the repository to get locked down to just that user ID, preventing unauthorized modifications to individual files in the repository outside using Version Manager applications. By default, Version Manager on UNIX/Linux installs with setuid mode enabled.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs