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 Location of 'ChangeMan.INI' file
DS 5.7.2 - the location of ChangeMan.ini file is at 'C:\Documents and Settings\ username \Application Data\Serena' where username is the login of the user to the network DS 5.7.2 the location of ChangeMan.ini file is at 'C:\Documents and Settings\username\Application Data\Serena' where username is the login of the user to the network
CMS-XML Version Manager SSO: Default Certificates for STS, GATEKEEPER and VMSERVER expire starting June 13th 2015
... SSO/CAC Login Source. ... Configure Project: Login Source ... if the selected Login Source is SSO ... ... If the configured Login Source is SSO ... ... If the configured Login Source is SSO ... ... If the configured Login Source is not ... ... can no longer login to Version Manager ... SSO/CAC Login Error: Connection exception using SSLCLIENTAUTHURL "http://ServerName ... /idp/services/Trust": Authentication failed SSO/CAC Login Error: Connection exception using SSLCLIENTAUTHURL "http://ServerName ... /TokenService/services/Trust": Authentication failed
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. user id as used with the first PDB. That developer will now be denied access to this PDB (and subsequent ones) with an error stating that the login account was unable to obtain a license.
CMS-XML Unable to login or promote or deploy after Sept. 11 2012 due to certificate expiry issue
Unable to login or promote or deploy after Sept. 11 2012 due to certificate expiry issue
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 Notification Server hangs or crashes so notifications no longer go out in 2009 R4 - DEF198769
Notification Server hangs or crashes so notifications no longer go out in 2009 R4 - DEF198769
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
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs