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 VM: SSO Login fails with error "Failed to verify signature"
An attempt to login to Version Manager that is configured to use an SSO server fails . The login page shows the error Failed to verify signature
CMS-XML After upgrading to VM 8.6.1 or newer, HTTPS connections to the File Server may fail with SSL routines:ssl3_get_server_certificate:certificate verify failed
After upgrading to VM 8.6.1 or newer, HTTPS connections to the File Server may fail with SSL routines:ssl3_get_server_certificate:certificate verify failed
CMS-XML VM 8.5 - The command "vmlinklibs -verify" always fails on Linux for the file libjsig.so
As of VM 8.5, the command vmlinklibs - verify always throws at least one error on Linux for the file libjsig.so Example:
CMS-XML Check in of an unchanged file can break ability to run a journal file report on locked files
In the Project Configuration, under Archive -> Locking, ensure that "Remove lock on unchanged revision" is set. Check out a file and check it back in, unchanged: Version Manager will unlock the revision instead of checking in a new revision. The journal file shows a correct entry, but the journal file processor (Show Journal) cannot handle it, as it expects to find a "put -r" entry to indicate a revision was checked in, but doesn't find one.
CMS-XML VM 8.6.1+: Web Client shows SSLHandShakeException PKIX path building failed when trying to login to SBM to use Associate Issue
When using the Associate Issue feature during a Check-out or Check-in operation, VM I-Net Web Client users may see the following error:
CMS-XML "WSDoAllReceiver: The timestamp could not be validated" error on login, or deploy log in composer
When attempting to login using an SSO server, users may get the error: ERROR -- Failed to obtain security token: WSDoAllReceiver: The timestamp could not be validated
CMS-XML VM I-Net: file association with SBM issue may fail for reasons that are not clear
While trying to check -in a revision with an SBM issue association, the check-in itself succeeds but is followed by the error: Failed association with ##### where ##### is the issue number.
CMS-XML On Unix environment, when AddWorkFile fails, the archive gets created with no revisions and doesn't get deleted if using File Server with split on create
On Unix only, when an AddWorkFile action fails , the archive gets created with no revisions if the user lacks the privilege to check -in or assign the default promotion group to the initial revision. The empty archive gets deleted on a pdb accessed through a File Server but when using a Fileserver pdb with SPLIT ON CREATE enabled, the revision library component is left undeleted.
CMS-XML VM I-Net: Java 7 Update 21 and Java 6 Update 45 break ability to use file explorer on end-user's PC
After installing Java 7 Update 21 or Java 6 Update 45, users trying to browse a location on disk by pressing the ellipsis button [...] from an Add Workfiles, Get, Check Out or Check In dialog will find that the file browser dialog does not come up. In Java console, the following error is displayed:
CMS-XML Checkout or Get by a Version Label which starts with a number will give the error: "Could not find a revision named [LabelName] in the archive [ArchivePath]"
When performing a Check Out or Get by Version Label using a label with the same layout as a Revision Number (#.#, #.#.#, etc.), or, when running a VM release prior to 8.1.1, using a label that just starts with a number, the operation fails with the error: Could not find a revision named LabelName in the archive
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs