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 Vss2vm conversion does not migrate all the revisions
PVCS Version Manager 8.3
CMS-XML VM: How to "migrate" from VM 6.5 to VM 6.6.
1) IF the customer installs VM 6.6 into EXACTLY the same directory and EXACTLY the Program Group, there may be a PVCS Version Manager 6.5 icon. This icon will launch VM 6.6. Simply delete the offending Program Group Item.
CMS-XML PVCS(J): Some double-byte characters cannot be used for file/folder/project names in File Server-based Project Databases
_normal"><font color="black" face="Verdana" size="2"><span style="font-size: 10pt;"><img src="http://knowledgebase.serena.com/library/KNOWLEDGEBASE/ Migrated /kbimages/5007748/1.GIF" border="0" /></span
CMS-XML VM: How to use a pre-generated SSL certificate that includes the private key with Tomcat in the PVCS Version Manager Web Application Server
The JKS keystore uses a proprietary format. It is recommended to migrate to PKCS12 which is an industry standard format using "keytool -importkeystore -srckeystore C:\ pvcs \vm8630\vm\common\tomcat\conf\serena.keystore -destkeystore C:\ pvcs \vm8630\vm\common\tomcat\conf\serena.keystore -deststoretype pkcs12".
PDF MERANT PVCS VM for Visual C++
8 Select the following options:  Based on existing 5.3/6.0 workfile hierarchy option Migrate SCC Project check box
PDF MERANT PVCS VM Implementation Guide for PowerBuilder
8 Select the following options:  Based on existing 5.3/6.0 workfile hierarchy option Migrate SCC project checkbox
CMS-XML Provide a way to enable pcli Get -ce by default, to ease migration from pre-VM 8.6.0.
PVCS Version Manager 8.6
CMS-XML VSS2VM: When running a migration and the VSS project structure is nested ~11+ levels deep the migration gives Java Hotspot errors
# Problematic frame: # C [2 pvcs .dll+0x10a37] # An error report file with more information is saved as hs_err_pid32748.log
CMS-XML Migrating projects already in Version Manager to VS2005 / VM 8.1.3 Rich Integration
Migrating projects already in Version Manager to VS2005 / VM 8.1.3 Rich Integration
CMS-XML VM: Migrating 5.3/6.0 Projects that contain multiple archives with the same name into VM 6.5/6.6
VM: Migrating 5.3/6.0 Projects that contain multiple archives with the same name into VM 6.5/6.6
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs