Find Answers

Filter Search Results
All Operating Systems:
All Products:
All Solution Types:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML VM 8.5.3: Patch for Version Manager 8.5
... so there is no need to install ... patches if they are not presently installed. ... 3.0 unable to obtain a ... ... .0 installer will not have offered this ... Studio because it could not recognize these newer VS ... If you do not have Eclipse installed ... ... so there is no need to install ... patches if they are not presently installed. ... 3.0 unable to obtain a ... ... .0 installer will not have offered this ... Studio because it could not recognize these newer VS ... If you do not have Eclipse installed ... 1.1.3 Desktop Client no longer supports right-click context menu to copy and paste label names (Windows specific) [DEF258878]
CMS-XML Meritage -Meritage fails when Tomcat is configured to accept SSL connections only.
11. At this point you should get a Security Warning that explains the CA server.domain.com cannot be validated. Click Yes to accept the certificate.
CMS-XML How To: #358 VM hangs at startup on a Novell lanworkplace tcp/ip connection to AIX/UNIX/NFS
Windows File Manager does not have a problem navigating through the drives. Other network applications also recognize the drive at the mounted point and have no problem.
CMS-XML After upgrading to VM 8.6.1 or newer, HTTPS connections to the File Server may fail with SSL routines:ssl3_get_server_certificate:certificate verify failed
In the default configuration that means neither self-signed certificates, nor certificates signed by an internal CA, are accepted anymore. Internal Certificate Authorities can
CMS-XML PCLI repeatedly requests the same license, causing the SLM License Server to (temporarily) fail for all users
Under certain circumstances it is possible for PCLI to flood the License Server with repeated request for the same User@Host combination. Even though this will only use a single license on that server, the sheer number of requests can effectively make SLM server stop working by using up all the available TCP ports on the operating system running SLM. Without available ports, SLM server clients (and clients of any other server process running on the OS) can no longer establish a new TCP connection .
CMS-XML VM I-Net server may lock up with Resource Locked by Session errors when using LDAP login with referrals
The issue may be triggered by someone mistyping their username, forcing the referral logic to kick in. At this point the primary LDAP server can tell Version Manager which additional LDAP servers it should query in an attempt to locate the user. If one of these non-primary LDAP servers accepts the connection but does not send a response, the VM I-Net server is effectively locked up until either:
CMS-XML SLM: How to access the Serena License Manager through a firewall / What TCP ports are used by the Serena License Manager?
In your environment SLM may needs to run on different ports, or fixed ports may be needed to either: Access SLM through a firewall, requiring specific ports to be opened Allow SLM clients to specify a port in the license server connection string
CMS-XML VM shows SSO Login Error: Connection exception using TOKENSERVERURL "http://ServerName:8085/TokenService/services/Trust": Transport error: 404 Error:
A fix for this issue is available as of VM 8.6.2, which also recognizes the changed response sent by the newer SSO server. Users of older VM releases can manually edit the affected Project Database configuration files (*.cfg) in a text editor, replacing /TokenService/services/Trust with /idp/services/Trust
CMS-XML Using SourceBridge from the VM I-Net Web Client when the connection to the SBM server uses HTTPS (Secure Sockets Layer - SSL)
If you would like, you can use the attached Java application TestHTTPS to verify that the JRE keystore now accepts the HTTPS-based URL for the SBM / TeamTrack / Tracker server. To run the application, save the file TestHTTPS.class
CMS-XML VM 8.6.x : is LDAP Channel Binding and LDAP Signing supported?
Recommendation is to follow Microsoft guides to reject clear-text and SALS connections (port 389) and only accept LDAPS connections (port 636). Information on configuring PVCS VM to use LDAPS can be found in KB doc S139658 .
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Product Demos

Title: Dimensions CM: Deploying Emergency Fixes (demonstration)
This demonstration shows you how to deploy an emergency fix to a live production environment in Dimensions CM. You will learn how to promote requests to any stage in the Global Stage Lifecycle, promote and deploy in the same operation, and browse deployment areas.
Title: Dimensions CM: Deploying Requests (demonstration)
This demonstration shows you how to deploy requests in Dimensions CM. You will learn how to promote requests to the next stage in the Global Stage Lifecycle, deploy requests by
Title: Dimensions CM: Scheduling Deployment (demonstration)
This demonstration shows you how to schedule a deployment in Dimensions CM. You will learn how to set a deployment sequence, schedule a deployment, and use the Queue tab in the Deployment view

Additional Assistance

  • Submit a Case Online
  • FAQs