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 DimCM: SSO: How to create standalone SSO certificates for Dimensions CM and establish a trust with the SSO Server
This document is for Dimensions CM 14.x and later versions and/or SBM 11.3.x. SBM 11.4 does contain a newer cm.pem file which may need to be applied to the Dimensions CM Server . If using older versions of Dimensions CM, please see Knowledgebase Solution S140601 .
CMS-XML Dim14: Prevent older client installations connecting to newer server installation
If a client version is older than the server version, the client is not connected and the following message is displayed: The version of your Dimensions CM client is older than the version of
CMS-XML KM-Dim9: unavailable -3 failed to start Dimensions server process
Make sure that you do not have any old flexlm process running or anything on memory from the old flexlm version (like the DM_LICENSE variable) before you run the SLM 2.1.1 installation.
CMS-XML Dim10: How to configure the Serena License Manager and its clients for a redundant server environment with Dimensions 10.1.x
" would be replaced by whatever names you chose to replace the "this_host" part of the SERVER lines in the license file with. For older Serena products , the syntax that is used depends on the Operating System the product is running on:
CMS-XML Dim10: LDAP: Failed to connect to the Dimensions server. LDAP Error: (49) Invalid credentials, LDAP Server Error: 80090308: LdapErr: DSID-0C090334, comment: AcceptSecurityContext error, data 52e, vece, PRG4500325E Error: User authentication failed - LDAP bind to server failed
This will prompt for the old password and then the new password. If the old password is unknown, the registry.dat file will need to be rebuilt.
CMS-XML KM-Dim10: The event structure contains the old host or database name
The nodename and the DSN will also be all uppercase. If is a good idea to backup or export your pcms_sys schema before making any changes. It is also a good idea to avoid caching problems by shutting down the Dimensions servers prior to making this change.
CMS-XML Dim12: Failed to connect to the Dimensions server. ACL4502922E Error: Cannot open connection to host HOSTNAME Logon failed for user dmsys and domain . (1326: Logon failure: unknown user name or bad password.)
To fix the above, you will need to know both the old and new password for dmsys. Once this is known, you are ready to proceed:
CMS-XML Dim12.1: Error Messages: "Failed to start Dimensions server process" and no dmappsrv processes are spawned
The safest way to make sure that the information is correct is to backup the current registry.dat file, which is located in the $DM_ROOT/dfs directory, by renaming it to registry. old . Re-create it by executing the dmpasswd command as such:
CMS-XML Failures communicating with ZMF 8.1.2 Servers using older ZMF4ECL clients
“You must upgrade your ZMF for Eclipse client to version 8.1.2 before you can use it with a ChangeMan ZMF 8.1.2 or Sernet Server 8.1.2 started task .”
CMS-XML Restart of JBOSS server sends out an old notification email
When we scan the ts_notificationevents table for the itemid and tableid, as specified in the notification subject, does a record exist for the item? If not then check the ts_notificationmessages table where the message subject is similar to that of the email. If there is not a record in ts_notificationevents or ts_notificationmessages then the rogue email is likely caught in the JBOSS Server cache.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs