Here you can find a list of some frequently encountered problems, as well as their solutions or workarounds.
Most problems can be fixed by making sure that your system is running the latest software. Before you start troubleshooting, it is advised that you make sure your product is up to date.
- 1 Cannot Connect to Embarcadero Connect
- 2 Loading Pages Takes Too Much Time
- 3 Log Error Messages
- 4 Synchronization Issues
- 5 See Also
Cannot Connect to Embarcadero Connect
Unable to Connect
If your web browser cannot establish a connection to the Embarcadero Connect server:
- Check that the URL you are trying to access is Embarcadero Connect's.
- Check that your system has a working connection to the Embarcadero Connect server.
- Check that Embarcadero Connect is running. See Starting Embarcadero Connect.
- Try increasing the maximum memory assigned to Embarcadero Connect. See Changing the Memory Limit of Embarcadero Connect.
Too Many Open Sessions
- "Too many open sessions, please contact your super user or license administrator to purchase more licenses."
If you get this error message, your Embarcadero Connect installation reached the maximum number of connections. You should ask your super user about it. If your Embarcadero Connect installation has active licenses for concurrent connections, you might be able to connect later, once someone else logs out of Embarcadero Connect. For any other type of connection, you need to purchase a license for additional connections. For more information, see Overview of Connection Licenses.
If you are a super user, you might run into this issue as well while you use the evaluation license that comes with the Embarcadero Connect. This could happen if you connect to Embarcadero Connect using more than one domain name or IP address; for example: http://localhost/, http://127.0.0.1/ and http://machinename/. Even if all those addresses point to the same server, Embarcadero Connect, you can only log in to Embarcadero Connect from one of them at a time. If you try to access http://machinename/ while you are logged in from http://localhost/ in a different web browser window or tab, you are asked for your user credentials again, and Embarcadero Connect does not let you in until you log out from http://localhost/.
Template Could Not be Loaded
- "Template could not be loaded..."
If you get this error message, you might need to restart the Embarcadero Connect server. Contact your super user.
Loading Pages Takes Too Much Time
Try increasing the maximum memory assigned to Embarcadero Connect. See Changing the Memory Limit of Embarcadero Connect.
Log Error Messages
There are some log files in the Embarcadero Connect installation folder that you can watch for error messages and warnings. Here you can see some errors that you might see registered in those log files, what the errors mean, and how to solve them.
java.lang.OutOfMemoryError: Java heap space
You need to increase the maximum memory assigned to Embarcadero Connect. See Changing the Memory Limit of Embarcadero Connect.
<date> - SyncDiagram.bat (stdout) - Could not reserve enough space for object heap
The application cannot start because there is not enough contiguous memory in the system that can be allocated for the application. For example, you are using a virtual machine and have more memory allocated to Embarcadero Connect than is available on the virtual machine.
You need to decrease the maximum memory assigned to Embarcadero Connect. See Changing the Memory Limit of Embarcadero Connect.
The default number of processes that can be set in Oracle XE is 40. If you exceed the amount of processes you may get a failure, identified in the synchronization logs as ORA-12519, TNS:no appropriate service handler found. The synchronization logs are available in the installation dir\etlvar directory.
To fix this error you can increase the number of available processes by doing the following:
- Run SQL*Plus and login as SYSTEM. You should know what password you’ve used during the installation of Oracle DB XE.
- Run the command in the SQL*Plus
“alter system set processes=150 scope=spfile;”
- Restart the database.
If you continue to get this error after increasing the number of available processes by following the above procedure, you may be using up all available processes and need to source the reason for this by examining the processes.
Connect to your database either using the sys account or by logging into your Oracle server and using a direct SQL Plus connection as the Oracle user: sqlplus / as sysdba. Note: If you are still getting errors regarding no available processes, you will have to manually kill one of the Oracle processes using the kill command. Then use these two queries to find out how many processes and sessions are currently logged:
1 select count(*) from v$process; 2 select count(*) from v$session;
For Oracle 11g, the default maximum number of processes is 150 (149 available).
Once you have confirmed that you have definitely reached the maximum number of processes, you can use this query to see what they all are and if they are active:
1 SELECT sess.process, sess.status, sess.username, sess.schemaname, sql.sql_text 2 FROM v$session sess, v$sql sql 3 WHERE sql.sql_id(+) = sess.sql_id;
Error During Install
It has been noticed that even though Connect or Portal had not been installed on a machine, the following error occurred: "Detected an existing ER/Studio Portal installation in ...\Program Files\Embarcadero\Connect 3.0. Please uninstall it first and then proceed with this installation." This error was solved by moving the following folder (it can also be renamed or deleted): C:\Program Files (x86)\Common Files\InstallShield\Universal\common\Gen1