Find Answers

Filter Search Results
All Products:

Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML Database connectivity fails when database password is pending expiration
Also, SBM Configurator shows " FAILED " when testing the db connection . To get around the issue, the database password must be reset. When the password isn't expired yet, a warning shouldn't interfere with connectivity.
CMS-XML RM - SBM Sync engine fails in there is not DB connection
RM - SBM Sync engine fails in there is not DB connection
CMS-XML Static Diagnostics Notification Server and Mail client database connection fails if TLS 1.0 is disabled
The Notification Server and Mail client database connection test fails with the error: Notification Server and Mail Client database connection Result : Failed
CMS-XML Server.log error "Failed to obtain DB connection" and "Connection refused" and "Could not retrieve datasource" and "Destroying connection that could not be successfully matched" and "Connection error occurred" and "Destroying connection that is not valid"
The common log will also show the orchestration running. However, the web service calls to SBM (using sbmappservices72, for example) will fail . A summary of the errors in the server.log
CMS-XML Common Scheduler shuts down if DB server is cycled - Failed to obtain DB connection from data source 'myDS': java.sql.SQLException: Could not retrieve datasource via JNDI url 'java:serenaAdminDsn' ... Could not create connection
The following messages will appear in server.log (or maybe Mashupmgr.log) and all activities will fail to run.
CMS-XML semi-colon character in database passwords truncates password
Reopening configuration and the password is shorter and DB connection test fails is the password contains a semi-colon for common logger
CMS-XML SBM 10.1.5.2 loses spaces in database names
If one or more of the SBM Databases are configured to use a name, which contains spaces then upgrading this configuration to 10.1.5.2 will strip the space characters from the database names rendering them unusable. For example if the Common Log database is named "CL DB" it will be renamed to "CLDB" after applying the configuration which then in turn means the DB connection will fail .
CMS-XML Problem with notification server diagnostic tests when there is a Tomcat cluster configured.
05/30/2018 15:36:12 Warning The remote server returned an error: (404) Not Found. 05/30/2018 15:36:12 Information Running test: 'Notification Server and Mail Client database connection ', result: Failed 05/30/2018 15:36:12 Information Running test: 'Notification Server connectivity', result: Success
CMS-XML Dim10: Using DMCLI with a PAM-enabled server
Database Connection : dim10 PRG4500367E Error: User authentication failed Doing PAM Authentication for user "user1" - "Authentication failed " on host SERVERNAME PRG4500325E Error: User authentication failed Doing PAM Authentication for user "user1" - "Authentication failed " on host SERVERNAME ACL4500326E Error: User authentication failed when connecting to host SERVERNAME User authentication failed
CMS-XML Dim 10: Dmcli- If password is more than 8 chars using LDAP authentication gives error
When using a password greater than 8 characters with LDAP authentication, then It gives error 'Error: User authentication failed - LDAP bind to server failed ' ... Database Connection : dim10xp ... PRG4500325E Error: User authentication failed - LDAP bind to server failed ACL4500326E Error: User authentication failed when connecting to host or-supernova User authentication failed ... Database Connection : dim10xp
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs