Find Answers

Filter Search Results
All Operating Systems:
All Products:
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
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:D 5 :3F:CF:99:3F:0B:6E:D6:92:3C sts
CMS-XML MCLG: Getting Collage ready for the new USA 2007 Daylight Saving Time rules
Beginning in 2007, the start and end date of Daylight Savings Time (DST) will change in the United States (see ). Daylight Savings Time will begin March 11, 2007 (the second Sunday in March) instead of April 1 (the first Sunday of April). Daylight Savings Time will end November 4, 2007 (the first Sunday of November) instead of October 28 (the last Sunday in October).
CMS-XML Urgent notice for users of both SBM and Dimensions CM with SSO who are considering the upgrade to SBM 2009 R4
The Single Sign On (SSO) component included in the SBM 2009 R4 release is incompatible with SSO components included within the released version of Dimensions CM 2009 R2 and CM 2009 R1. Users of SSO between SBM and Dimensions CM, must first patch CM to patch level 2009 R2.05 or later, or upgrade to the major release CM 12.1, before upgrading to SBM 2009 R4. The CM patch 2009 R2.05 and the release CM 12.1 will be available during March 2011.
CMS-XML VM: Known issues with Version Manager
1. Any single user cannot open more than one PDB at a time when using Professional_named licenses. In a simple scenario, you install named licenses and assign them to developers. One of the developers starts the VM desktop client and opens a PDB. Next, that developer attempts to open a second PDB, using the identical
CMS-XML VM I-Net Web Client applet certificates expire on February 25th 2017
This patch is available from KB doc P2786 . The recommended solution for users of older VM 8.5.x releases is to first install the VM 8.5.3 patch, available from KB doc P2757 , then install VM 8.5.3 Patch 004. The recommended solution for users of pre-VM 8.5 releases is to first upgrade to VM 8.5.0, then install the VM 8.5.3 patch and finally install VM 8.5.3 Patch 004.
CMS-XML SBM and below - default certificates expired for STS, Federation Server and SSO Gatekeeper expire on 13th June 2015
The first related link is good for all 10.1.x installs. The second related link contains an executable that will generate new SSO certificates for all versions and earlier.
CMS-XML Cross-Site Scripting (XSS) vulnerability in Version Manager Web Client (VM I-Net)
If you are running VM 8.5.0, please download the patch from KB article P2710 . If you are running VM 8.4.6, please download the patch from KB article P2709 . Users of older VM releases should upgrade to either of these versions first .
CMS-XML Do NOT Run vsplit -u (unsplit) on Archive Paths that Contain Double-Byte Characters on pre- releases
WARNING! Do NOT Run vsplit -u on Archive Paths that Contain Double-Byte Characters using Version Manager releases prior to result in data loss. To split archives containing double-byte characters in the path, please make sure you first upgrade to VM or beyond.
CMS-XML Serena License Manager: HotFix for SLM 2.2.0 to remediate two security vulnerabilities in FlexNet Publisher
Although the vulnerability is said to exist in all releases of FlexNet Publisher, and therefore all releases of SLM, a fix is only available for the latest code base, which is why Serena can only provide a solution for SLM 2.2.0. Users of older SLM releases should first upgrade to SLM 2.2.0 if they want to deploy the fixes in SLM
CMS-XML ALERT - possible Oracle data loss if upgrading from TeamTrack directly to SBM 2008 2.03, 2.04, 2.05 or 2009 R1
then it is likely that you will experience data loss on the database upgrade. Workaround: When upgrading from TeamTrack the Unicode Upgrade Utility is a one-off utility run so to avoid this issue upgrade your database to 2008 R2 first and only then apply the patch or upgrade to 2009 R1( first GA build - no longer available for download).
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs