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 SBM 10.1.5 database upgrade fails with "unable to connect to database"
In SBM Configurator, the "Test Connect " button will test correctly. However, when clicking the Upgrade Database link, you will get error:
CMS-XML Cannot connect to Application Repository is database name contains & symbol
The following error appears in the browser when you attempt to connect in this scenario: This page contains the following errors: error on line 109 at column 72: EntityRef: expecting ';' Below is a rendering of the page up to the first error.
CMS-XML Error: Database upgrade failed: Cannot connect to database using provided ODBC data source
Please contact Serena Support to get this resolved.
CMS-XML Cannot start Active Diagnostic (SBM Logging Services) and get error "Cannot connect to the Active Diagnostics database. Runtime configuration is currently unavailable.”
Cannot start Active Diagnostic (SBM Logging Services) and get error " Cannot connect to the Active Diagnostics database . Runtime configuration is currently unavailable.”
CMS-XML Configurator - A connection to the Application Engine database cannot be established. Do you want to start ...... services(s)? - message occurs on Apply
Configurator - A connection to the Application Engine database cannot be established. Do you want to start ...... services(s)? - message occurs on Apply
CMS-XML AE can't reestablish connection to DB at once.
AE can't reestablish connection to DB at once.
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
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. Actual Result:
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. ... After modifying the file, click Upgrade Database again in SBM Configurator. In this type configuration (SQL Server connecting via Windows Authentication), you must also add the following java option to all -renew commands:
CMS-XML Orchestration renew utility "clear" command fails to connect to database
The orchestration renew utility "clear" command will get errors of " Cannot connect to database " and " Can't fix hibernate cfg file" if the server it is being run on does not have web access or has to connect to the web through a password-protected proxy.
CMS-XML After upgrade SBM 11.4.1, unable to log into Repository or connect via Composer
Error creating bean with name 'txManager' defined in class path resource [Repository-Context.xml]: Cannot resolve reference to bean 'mySessionFactory' while setting bean property 'sessionFactory'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'mySessionFactory' defined in class path resource [ DB -Context.xml]: Invocation of init method failed; nested exception is org.hibernate.InvalidMappingException:
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs