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 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 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 VM: The instruction at "hex_address" referenced memory at "hex_address". The memory could not be 'read'.
c:\> set ISLVINI The output should be similar to ISLVINI=c:\ pvcs If the ouput is 'Environment variable ISLVINI not defined' or similar, then you may need to setup an ISLVINI environment variable on your workstation.
CMS-XML PCLI get command on UNIX client throws "could not read the information stored in the archive" error, but the desktop client GUI running on the same system has no problems getting this file
SetUID mode: set, SetGID mode: set , User: pvcs , Group: pvcsgrp vmsetsuid found no problems
CMS-XML VM: ''unable to read ...\pvcsproj.ser reached end of file''
The user who had the following configuration experienced the errors Windows NT version 4.0, service pack 6, build 1381 PVCS Version Manager version 6.7.11, build 915.12
CMS-XML Problem: #1537 User Cannot Prevent VB 4.0 from Checking-Out Read-Only copies of Project Files.
User has set the "Get latest Checked in versions of project files when opening a project?" option in the Add-Ins/ PVCS /Options dialog box to either "NO" or "ASK". Yet, when he/she opens a project, read-only files get checked-out automatically anyway.
CMS-XML 'CMNALLIO unable to read/write logfile' during admin update
'CMNALLIO unable to read /write logfile' during admin update
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs