org.quartz.JobPersistenceException: Failed to obtain DB connection from data source 'myDS': java.sql.SQLException: Could not retrieve datasource via JNDI url 'java:serenaAdminDsn' org.jboss.util.NestedSQLException: Could not create connection ; - nested throwable: ( java.sql.SQLException : I/O Error : DB server closed connection .); - nested throwable: (org.jboss.resource.JBossResourceException:
When attempting to log into Dimensions CM, the following error is occurring: Failed to connect to the Dimensions server . ACL4502922E Error: Cannot open connection to host HOSTNAME
Logging into Dimensions, the following error message is returned: Failed to connect to the Dimensions server . ACL4502922E Error: Cannot open connection to host HOSTNAME
1) Is the Oracle listener on port 1521? 2) Is the Oracle SID on the server the same as the Oracle Service Alias? 3) Is the Oracle server on the same machine as the Dimensions server?
Edit the value in the " Database Hostname" to be the server name (or IP address) of the server hosting the Oracle Database (in some cases the server name will need to be the fully qualified server name).
After turning on SDP trace (DM_SDP_TRACE) on the Dimensions server, it shows the dmappsrv process failed with this error : MsgStrAdd2: DBI0004527E DBIO: Database I/O error occurred ORA-12154: TNS : l'identificateur de connexion indiqué n'a pas pu êre résolu
Your eRMserver.log has the following error entry “ java.sql.SQLException : [your host name] Could not locate entry in sysdatabases for database 'Serena'. No entry found with that name. Make sure that the name is entered correctly.”
When the user tries to connect to Dimensions using the Dim Client, they receive error : Failed to connect to the Dimensions server . ACL4502922E Error : Cannot open connection to host xxxxxxxxxxxxx Failed to start Dimensions server process Event viewer shows the following errors : ... Turning on trace logging, the DMAPPSRV log will show the following errors : DBI0004527E DBIO: Database I/O error occurred ... Error : Unable to connect to database "xxxxxxxxxxxxxxx"
By doing this no connection is made to the database in order to scan for new client upgrades and as a result the dmupgradesrv.exe ... The error messages above are caused by other Dimensions CM Client installations polling the server to see if there are any updates, and these connection attempts fail because the dmupgradesrv.exe ... If you have listener trace active on the server you can see the connection attempts in the DMPOOL log but at the system level they appear in the Windows Application Event Log as errors .
