Eclipse Repository not Logging On

[Former Member]

p13439331trial

I can access and develop just fine via the workbench, but I can no longer 'Log On' to the 'Repository' view of this within Eclipse.  I had been able to log on in Eclipse for several days but this stopped working a few days ago.

I don't know if this is the correct route for this problem, so please advise as to how I can access my instance in Eclipse.

Thanks

[alexander_silgidjian · Accepted solution]

Hi Kelvin,

Would you open the HANA Instances account page  (https://account.hanatrial.ondemand.com/cockpit#/acc/p13439331trial/dashboard) and check your HANA system state?

Kind Regards,

Alex

[Former Member · Accepted solution]

That connects up just fine, and shows Overall Health with a green light and 'OK'. I have 1 application showing and that all works.

I can uninstall Luna and re-install again, I'm not aware of any potential port conflicts and 30015 is not in use.

Thanks

[alexander_silgidjian · Accepted solution]

Hi Kelvin,

Did you resolve the issue?

Btw you do not need to reinstall, you can just switch the workspace in order to start with clean setup.

Kind Regards,

Alex

[Former Member · Accepted solution]

Thanks for the advice Alex, I switched workspace, re-connected to my HANA instance and was able to resume.

[Former Member]

...the progress bar moves across half way and 'sticks' - not locked up but not advancing either!

[former_member185231]

Hi Kevin,

can you check the log file of eclipse for errors that are logged at the time when you reproduce the issue.

This will help it to understand what goes wrong.

The log file is inside your workspace/.metadata folder and is named .log

Best regards,

Dobri

[Former Member]

This is an extract from the log after I choose 'Log On': !ENTRY com.sap.ndb.studio.backup 4 4 2014-12-02 19:08:13.330 !MESSAGE Could not open connection to 'JTF localhost 00' !STACK 0 java.util.concurrent.ExecutionException: com.sap.ndb.studio.jdbc.JDBCConnectionStatus: Database connection is not available; see error log at java.util.concurrent.FutureTask.report(Unknown Source) at java.util.concurrent.FutureTask.get(Unknown Source) at com.sap.ndb.studio.backup.BackupConnectionHandler.openConnection(BackupConnectionHandler.java:166) at com.sap.ndb.studio.backup.BackupConnectionHandler.getConnection(BackupConnectionHandler.java:132) at com.sap.ndb.studio.backup.BackupWorkbenchAdapter$2.call(BackupWorkbenchAdapter.java:154) at com.sap.ndb.studio.backup.BackupWorkbenchAdapter$2.call(BackupWorkbenchAdapter.java:1) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: com.sap.ndb.studio.jdbc.JDBCConnectionStatus: Database connection is not available; see error log at com.sap.ndb.studio.jdbc.JDBCPlugin.createConnection(JDBCPlugin.java:300) at com.sap.ndb.studio.jdbc.JDBCPlugin.createConnection(JDBCPlugin.java:326) at com.sap.ndb.studio.backup.BackupConnectionHandler$2.call(BackupConnectionHandler.java:160) at com.sap.ndb.studio.backup.BackupConnectionHandler$2.call(BackupConnectionHandler.java:1) ... 4 more Caused by: com.sap.db.jdbc.exceptions.JDBCDriverException: SAP DBTech JDBC: Cannot connect to jdbc:sap://localhost:30015 [Cannot connect to host localhost:30015 [Connection refused: connect], -813.]. at com.sap.db.jdbc.exceptions.SQLExceptionSapDB.createException(SQLExceptionSapDB.java:230) at com.sap.db.jdbc.exceptions.SQLExceptionSapDB.createException(SQLExceptionSapDB.java:214) at com.sap.db.jdbc.exceptions.SQLExceptionSapDB.generateDatabaseException(SQLExceptionSapDB.java:197) at com.sap.db.jdbc.Driver.connect(Driver.java:192) at com.sap.ndb.studio.jdbc.JDBCConnection$1.run(JDBCConnection.java:157)

[Former Member]

Thanks for your help Dobromir, hope this provides a clue!

Regards

Kelvin

[former_member185231]

Hi Kevin,

It look like the tunnel was not opened and JDBC driver cannot establish a connection.

When once the System is added - the tunnel for this system always use one and the same ports. If those ports are now occupied then the connection cannot not be established. My proposals to you are the following.

First check does the port 30015 is free. If it is occupied by something else, just free it before logon to the system.

If this do not help, you can remove and then add again your system. If the ports are free the new system instance will reuse them (will keep its instance number) and the workspace will be linked again to this new system.

HTH,

Dobri

[Former Member]

I will try the re-install

Thanks