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 HP-UX patch breaks Version Manager running in setuid mode
" error shown in the first example, then you most likely are affected by the bad patch, and you should check the list of installed patches (using "swlist" or "swlist -l patch"). If the "pcli" command did not return an error, you probably just don't have your environment setup correctly to run CLI commands. To correct that problem, execute:
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
To validate , perform the following steps: ... /idp/services/Trust": Authentication failed ... /TokenService/services/Trust": Authentication failed
CMS-XML Microsoft patches KB4338815 and KB4338818 may causes services to fail with port in use errors
Microsoft patches KB4338815 and KB4338818 may causes services to fail with port in use errors
CMS-XML TTS License - "Init Extension Failed….. Failed to obtain a TTS license" - 63016
TTS License - "Init Extension Failed ….. Failed to obtain a TTS license" - 63016
CMS-XML McAfee anti-virus update breaks Version Manager by incorrectly flagging it as containing the Exploit-CVE2012-0507 Trojan
McAfee anti-virus update breaks Version Manager by incorrectly flagging it as containing the Exploit-CVE2012-0507 Trojan
CMS-XML Sample certificates in SBM expire on 16th September 2017 for SBM versions 10.1.x - you must update to avoid System Failure
Sample certificates in SBM expire on 16th September 2017 for SBM versions 10.1.x - you must update to avoid System Failure
CMS-XML Possible data loss when checking into branches following switch to NOGENERATEDELTA on existing split archives served by File Server releases prior to VM 8.3
Possible data loss when checking into branches following switch to NOGENERATEDELTA on existing split archives served by File Server releases prior to VM 8.3
CMS-XML Accessing Serena Communities via communities.serena.com may not work or may show a company other than Serena Software
may either fail or show a company other than Serena Software. This can happen if a browser accessed the communities last week and was left running.
CMS-XML SSL 3.0 Vulnerability - Poodle
This has the potential to affect any web server and thus requests to communicate with various Serena products. For customers to make sure their installations are secure there are mitigation steps they can take to secure the web servers involved. Solutions documents have been created for Dimensions CM and SBM and their numbers are listed here.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs