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 After installing Microsoft Windows patch KB3172605 on a client PC, Internet Explorer can no longer access Tomcat-based servers via HTTPS (ports 8443/8444)
This page can’t be displayed Make sure the web address https://ServerName :8443 is correct.
CMS-XML Do NOT Run vsplit -u (unsplit) on Archive Paths that Contain Double-Byte Characters on pre-8.1.3.1 releases
WARNING! Do NOT Run vsplit -u on Archive Paths that Contain Double-Byte Characters using Version Manager releases prior to 8.1.3.1. result in data loss. To split archives containing double-byte characters in the path, please make sure you first upgrade to VM 8.1.3.1 or beyond.
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 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 MCLG: How will the new USA 2007 Daylight Saving Time rules impact Collage?
After the DST time change, you should review all of your scheduled activites to make sure there are not any new conflicts. As an example, let's say that you have a deploy that runs every 4 hours at 11:00, 3:00, and 7:00. The night before the DST time change, the 11:00pm deploy will run.
CMS-XML Version Manager SSO: Default Certificates for STS, GATEKEEPER and VMSERVER expire starting June 13th 2015
This article is applicable only if you are running Version Manager 8.4 or newer and have Project Databases configured to use the SSO/CAC Login Source. To validate , perform the following steps: Open the VM Desktop Client
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.
CMS-XML ALERT - possible Oracle data loss if upgrading from TeamTrack directly to SBM 2008 2.03, 2.04, 2.05 or 2009 R1
If you are an Oracle TeamTrack customer and looking to upgrade directly to Serena Business Mashups 2008 2.03, 2.04, 2.05 or 2009 R1 then there is a potential for data loss. Please check the following criteria:
CMS-XML Potential file corruption when File Server is used by Version Manager releases prior to VM 8.1.2.2
A Checkout or Get operation may yield revision contents of another file. This can only happen if you have unsplit archives.
CMS-XML Expiring Certificate for Dimensions CM on 13 June 2015 if you are using Dimensions CM SSO Server with CAC or SmartCard enabled
You will only see messages concerning certificate expiration if the Dimensions CM server is configured to use SSO with CAC or SmartCard enabled. The simplest way to check this is to look for the following variables in the Dimensions CM server dm.cfg file.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs