Find Answers

Filter Search Results
All Operating Systems:
All Products:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
  Results
CMS-XML Using Java Plug-in 1.6.0 Update 10 (1.6.0_10) or newer with Version Manager releases prior to VM 8.2 can corrupt your project database
Using Java Plug-in 1.6.0 Update 10 (1.6.0_10) or newer with Version Manager releases prior to VM 8.2 can corrupt your project database
CMS-XML VM: Known issues with Version Manager 8.0.2.0
1. Any single user cannot open more than one PDB at a time when using Professional_named licenses.
CMS-XML Potential file corruption when File Server is used by Version Manager releases prior to VM 8.1.2.2
Avoid this problem by making sure all Version Manager clients of a File Server are running VM 8.1.2.2 or newer. To explicitly prevent older VM release from accessing your Project Databases ( PDBs ), add: %if "$(PVCSVer)" <= "v8.1.2.2"
CMS-XML Version Manager SSO: Default Certificates for STS, GATEKEEPER and VMSERVER expire starting June 13th 2015
This article is applicable only if you are running Version Manager 8.4 or newer and have Project Databases configured to use the SSO/CAC Login Source. To validate, perform the following steps: Open the VM Desktop Client

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs