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 KM-Dim7: INET Error on Login: Failed to connect to database :java.Sql.SQLException: lo exception: The network Adapter could not establish the connection
KM-Dim7: INET Error on Login: Failed to connect to database :java.Sql.SQLException: lo exception: The network Adapter could not establish the connection
CMS-XML Dim12: Failed to connect to the Dimensions server - ACL4502922E Error: Cannot open connection to host HOSTNAME - DBI0004527E DBIO: Database I/O error occurred ORA-28000: the account is locked
Logging into Dimensions, the following error message is returned: Failed to connect to the Dimensions server. ACL4502922E Error: Cannot open connection to host HOSTNAME
CMS-XML KM-Dim7: Dimensions INet Login Failure - Failed to connect to database: java.sql.SQLException: lo exception: The Network Adapter could not establish the connection
If you are using another port other than 1521 for Oracle connections , check that your Dimensions.properties file is updated with the correct port information. If the connection port for Oracle is defined as something other than the Dimensions default of 1521 and not changed or updated in the Dimensions.properties file, this error is encountered.
CMS-XML TRK: Tracker Inet Configurator gives 'Failed on connection string' message after selecting ODBC driver and entering database ID and password
3. Test for a connection using the System ODBC driver from within the Tracker Admin program on the web server. (Create or edit a Server definition and verify the user connection within the Server definition.) The values for ODBC driver, database user id, and password should display by default in Tracker 7.x.
CMS-XML Execution of the remote command failed:Connection refused: connect
Error in deploy activity log after db deploy. Make sure the deploy agent is started.
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 When opening a connection, get error "Logon Failed: File or assembly name xxxxxxx, or one of its dependencies, was not found."
This error message will occur if a database is opened using a Mariner installation that is missing custom plugins. These plugins are usually created and installed by a Serena consultant. You can verify that this is the problem by running the following query against the database.
CMS-XML Dim CM: Error "merant.adm.dimensions.exception.dbioexception failed to query database" attempting to connect to Web Client following Dimensions CM upgrade
A successful upgrade to Dimensions CM 14.4 was carried out but when a connection to Web Client was attempted the following error occurred:
CMS-XML Login failed unable to connect to the database using Agile Administrator
The problem was traced to the Windows Firewall. Once this was disabled (the company concerned had another firewall in use) the connection could be made with no further problems.
CMS-XML Dim12: Get error when deploying: PRG4500325E Error: User authentication failed
2 PRG4500325E Error: User authentication failed NET4502575E Failed to obtain a connection to database basedb@dsn on host server as user username. Launching DEPLOY job 12143328
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs