Find Answers

Filter Search Results
All Operating Systems:
All Products:
All Solution Types:
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
CMS-XML How To: - Version Manager and/or System Administrator wants to setup archive directories so that user do not have delete rights on an NT Server
This policy should result in a minimal amount of data loss and/or down-time.
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
Please do not perform any operations that will update the repository (Put, AddFiles, etc.) while this variable is in effect unless you are certain the repository is File Server-based. ... as the user who installed Version Manager (a.k.a. the setuid user) or as a system administrator .
CMS-XML After making an archive update, user gets: Serena PVCS Version Manager could not read the information stored in the archive ""
As a result the actual archive was not changed, so there is no permanent damage, but the archive change the user tried to make has been lost.
CMS-XML VM Server Error: "Could not find directory. Check-in <workfile> Archive: <archive> File: <archive> Work Item: <file>"
I had him change this directory to one that granted him full access. It appears that the Start-In directory effect the put operation whether there is an event trigger defined or not. In UNIX environments, the "Start-In" directory would be the directory from which VM is launched.
CMS-XML Problem: Keyword Expansion produces unexpected results if the archive directory contains a Dollar character
No data is lost but the effect is not pretty and may lead to very long lines of text.
CMS-XML Software Error: PVCS Answerline #517 The command line option -# does not result in proper output of info.
PROBLEM: The GUI writes Diagnostic = n, where n is 0 by default, to
CMS-XML VM 8.5.x: Configure Project shows "The LDAP connection information is not valid. Please correct." when trying to save changes
When using Configure Project in VM 8.5 on an Project Database that is configured to use LDAP authentication, trying to save changes via Apply or OK can result in the error:
CMS-XML Trying to open a project database gives "System Error: pvcs.fsclientapi.ProjectFileAPI.jniGetClientPathMapsAllInfo()[Ljava/lang/String;"
After installing the 8.4.6 patch, attempts to open a Project Database from the desktop client GUI result in the following error ( Details expanded): If the GUI is running in console mode, the error is shown there as well: Serena PVCS Version Manager (VMGUI) v8.4.6.0 (Build 037) for Windows NT/80x86
CMS-XML After upgrading the VM server to release 8.5.0, File Server clients using SSL randomly report "error:14094410:SSL routines:SSL3_READ_BYTES:sslv3 alert handshake failure" Detail: SSL connect failed in tcp_connect()."
Following this error, the client can no longer read data from the File Server, resulting in errors indicating that Archive files, Configuration files, Access Control Databases or Project .ser files cannot be read.
CMS-XML Version Manager patch for 8.1.3
Running vsplit -u on Archive Paths that Contain Double-Byte Characters Causes Data Loss [DEF102167; DEF100974] If the path to an archive , or the archive name itself, contains double-byte characters, attempting to unsplit the archive will result in data loss. This has been fixed.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Product Demos

Dimensions CM: Working with items, part 1 (demonstration)
This Dimensions CM demonstration shows you how to perform impact analysis to determine which files are affected by specific changes

Additional Assistance

  • Submit a Case Online
  • FAQs