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 Expiring Certificate for Dimensions CM on September 24 2018 - this will result in "PRG7700117E Error: Untrusted endorsing credentials" when logging into Dimensions
Expiring Certificate for Dimensions CM on September 24 2018 - this will result in "PRG7700117 E Error: Untrusted endorsing credentials" when logging into Dimensions
CMS-XML cmnproj parameter change in 5.7.1 and above - some parameter values prior to 5.7.1 will cause errors
cmnproj -actdiff output fields are: e .g. cmnproj -h:<host> -u:<user> -actdiff -p1:Proj1 -p2:Proj2 -outfields:apnrvdbqoswet -v a - Original Area b - Modified Area
CMS-XML Deploy of a Mashup removes "Record Locking" for all tables in the Mashup
To workaround this: Whenever a deploy is the done you must go into mashup administrator and switch record locking back on for the table and restart the web server ( e .g. iisreset). This is fixed in Serena Business Mashups 2008 R2.04.
CMS-XML Version Manager SSO: Default Certificates for STS, GATEKEEPER and VMSERVER expire starting June 13th 2015
, TrustedCertEntry, Valid from: Wed Jun 16 15:24:25 PDT 2010 until: Mon Jun 15 15:24:25 PDT 2015 Certificate fingerprint (SHA1): 2F:FD: E 5:CE:AE:18:55:C4:B3:79:D5:3F:CF:99:3F:0B:6 E :D6:92:3C sts
CMS-XML Potential file corruption when File Server is used by Version Manager releases prior to VM 8.1.2.2
During a mass label operation that applies a never before used label, Version Manager asks if an existing label should be overwritten, and the archive this is reported on is not referenced by multiple files in the selection set (i. e . this is not a shared archive).
CMS-XML Expiring Certificate for Dimensions CM on 13 June 2015 if you are using Dimensions CM SSO Server with CAC or SmartCard enabled
../../java/OperatingSystem/jre ( e .g. ../../java/solaris/jre)
CMS-XML HP-UX patch breaks Version Manager running in setuid mode
(i. e . the vmprofile / vmcshrc file was sourced). When in doubt, simply execute the command "pcli". If that command gives you the "libjvm.sl

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs