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 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
1. Run Application Repository 2. Recycle your Database server so that all connections are dropped 3. Notice that error messages will start appearing in the log regarding lost connections from common scheduler.
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"
comp/env/jdbc/serenaAdminDsn' java.sql.SQLException: Cannot open database "SBM_App_Repository" requested by the login. The login failed.
CMS-XML Connection to Oracle fails in Configurator when using Update From Database
If you attempt to connect to the an Oracle database using different user accounts on separate SBM servers, the Update From Database operation fails, and an error appears.
CMS-XML SBM 10.x database upgrade to SBM 11.x gives error "Failed to upgrade Orchestration Engine database. Connection to the Application Engine server has timed out."
SBM 10.x database upgrade to SBM 11.x gives error "Failed to upgrade Orchestration Engine database. Connection to the Application Engine server has timed out."
CMS-XML Intermittent errors when accessing items or listing report - Error: The connection is broken and recovery is not possible
This is a regression from 11.2 Intermittent errors when accessing items or listing reports in SBM User Workspace and Work Center with the following message - " Database Exception in CHtmlPage_Process::OpenPage() with tag OpenEx
CMS-XML SBM 10.1.5 database upgrade fails with "unable to connect to database"
Unable to Connect to Database. Invalid connection string.
CMS-XML Database Upgrade -- SBM Upgrade Fails
Click the upgrade link to upgrade your AE database (or do the upgrade in the SBM System Administrator in pre 10.1.3. Be sure to verify your connection information in System Administrator)
CMS-XML Orchestration Engine renew errors when using SQL Server with Windows Authentication - Can't create connection to the database ... I/O Error: SSO Failed: Native SSPI library not loaded. Check the java.library.path system property
This issue occurs when upgrading the Orchestration Engine database to SBM 11.0 while using SQL Server and Windows Authentication. To work around this problem: Add following option to "...\Serena\SBM\Common\Misc\renew\renew_redeploy.bat":
CMS-XML SBM 10.x database upgrade to SBM 11.x gives error "One or more deployment failures were encountered during the database upgrade process"
Skipping deployment of 'ENV NAME' environment for user 'NAME' due to calculation apps error. For help with these errors, see KB S141698 Cannot deploy BPEL definition for process model alf/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/ - Connection refused: connect
CMS-XML "xact abort" in SQL Server causes table creation to fail
Enabling the "xact abort" setting in the Connections options of the Server Properties in SQL Server will prevent primary tables from being created when doing a Copy Database or deploy.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs