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  
Pages [Next]
  Results
CMS-XML Expiring Certificate for Dimensions CM on September 24 2018 - this will result in "PRG7700117E Error: Untrusted endorsing credentials" when logging into Dimensions
0b:3b:e3:61:b4:76:b1:41:d2:3f:ca:23:b5:2d:08: a4:06:d5:0d:c0:a6:23:29:6c: ad :b6:9c:98:04:19:
CMS-XML Dimensions CM Web Client applet certificates expire on February 25th 2017
Users unable to apply the updates before February 25th, 2017 should add the Dimensions CM server URL to the Exception Site List in the Java Control Panel on the client (Control Panel -> Java -> Security). Users of older versions not included in this list should update to a supported version and apply the corresponding hotfix or use the exception list as a workaround.
CMS-XML Source Bridge Web Client applet certificates expire on February 25th 2017
The certificate that was used to sign the Source Bridge Web Client applet expires on February 25th 2017. After this day, users will get a message similar to:
CMS-XML Click "ALERT: A57" for Java 1.7.x updates solutions for Serena web clients using the Java plug-in may randomly stop working after 14 January 2014.
Due to security enhancements that have been added to Java 7 as of update 25, the release of a new JRE on Oracle's website will automatically block certain features in the older versions of Java plug-ins that may be installed on your system. These blocked features will prevent the web client of certain Serena products from working, such as Dimensions CM and PVCS Version Manager. If you are using Dimensions CM, please see Knowledgebase Solution S140201
CMS-XML SBM 10.1.1.3 and below - default certificates expired for STS, Federation Server and SSO Gatekeeper expire on 13th June 2015
Users will not be able to connect to SBM and will see the error message: "Failed to verify signature". Please follow a link to the related solution for resolution.
CMS-XML Version Manager SSO: Default Certificates for STS, GATEKEEPER and VMSERVER expire starting June 13th 2015
and the SSO Server(STS) Detail points to an SBM SSO server, this article applies as well, though it only impact users of Version Manager Eclipse RIDE or Visual Studio RIDE integrations. If the configured Login Source is not SSO/CAC
CMS-XML Deploy of a Mashup removes "Record Locking" for all tables in the Mashup
Deploy of a Mashup removes "Record Locking" for all tables in the Mashup
CMS-XML KM-Dim10: Alert: Removing directory in project can delete non-Dimensions content from deployment area
KM-Dim10: Alert: Removing directory in project can delete non-Dimensions content from deployment area
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. ' line for every VersionManager_named license. The workaround will add additional 'INCLUDE VersionManager_named ...' lines to the users.lst file, referencing Professional_named users , which should be removed once a solution is put in place (the VM 8.0.2.3 patch; see Solution section below).
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
P2470 , or upgrade to VM 8.2 or newer. Users of older VM releases should cease using all versions of the Java 1.6 Plug-in to avoid (further) database corruption, and upgrade their Version Manager release to VM 8.2 as soon as possible.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs