Solved: Lost access to my HCP system

Former Member · ‎05-19-2014

Hi there,

Anyone has experience with losing access to their HANA system. In the cockpit it looks like this

If i try to use NEO to connect i get this log:

2014-05-19 09:52:08,356 INFO [main] com.sap.jpaas.infrastructure.console.CommandManager: Starting execution of command [open-db-tunnel]

2014-05-19 09:52:08,360 INFO [main] com.sap.jpaas.infrastructure.console.CommandManager: Command [open-db-tunnel] init() finished for [1] ms

2014-05-19 09:52:08,375 INFO [main] com.sap.core.tunnelcommands.framework.executor.CommandTunnelRequestExecutor: CommandTunnelRequestExecutor.executeRequest() called for command [open-db-tunnel] (version: 0.27.0)

2014-05-19 09:52:11,116 ERROR [main] com.sap.core.tunnelcommands.framework.executor.DefaultResponseConsumingStrategy: An internal server error occurred.

2014-05-19 09:52:11,116 ERROR [main] com.sap.core.tunnelcommands.framework.executor.DefaultResponseConsumingStrategy: request URI: https://services.hanatrial.ondemand.com/services/v1/instances/s0007822117trial/persistence/v2/dbtunn...

2014-05-19 09:52:11,116 ERROR [main] com.sap.core.tunnelcommands.framework.executor.DefaultResponseConsumingStrategy: statusCode: 500 Internal Server Error

2014-05-19 09:52:11,116 ERROR [main] com.sap.core.tunnelcommands.framework.executor.DefaultResponseConsumingStrategy: contentType: text/plain

2014-05-19 09:52:11,117 ERROR [main] com.sap.core.tunnelcommands.framework.executor.DefaultResponseConsumingStrategy: content: Existence of database user/schema for ID itelligence could not be checked in the underlying DBMS system due to an error. Contact HCP support if the error persists.

Reason: Existence check for user/schema 'NEO_CYYKURTLZAYQSV3NJOCJV363S' on DB server 'JN5' failed with SAP DBTech JDBC: Cannot connect to jdbc:sap://vadbjn5.nwtrial.od.sap.biz:30015/ [Cannot connect to host vadbjn5.nwtrial.od.sap.biz:30015 [Connection refused], -813.].

Stack trace: com.sap.core.dbaas.registry.DbAreaRegistryException: Existence check for user/schema 'NEO_CYYKURTLZAYQSV3NJOCJV363S' on DB server 'JN5' failed with SAP DBTech JDBC: Cannot connect to jdbc:sap://vadbjn5.nwtrial.od.sap.biz:30015/ [Cannot connect to host vadbjn5.nwtrial.od.sap.biz:30015 [Connection refused], -813.].

at com.sap.core.dbaas.registry.internal.DbAreaRegistry.userExists(DbAreaRegistry.java:1227)

at com.sap.core.dbaas.registry.internal.DbAreaRegistry.getOrCreateDbDeveloperUser(DbAreaRegistry.java:1124)

at com.sap.core.dbaas.servicecommands.CommandDbTunnel.openDbTunnel(CommandDbTunnel.java:138)

at sun.reflect.GeneratedMethodAccessor89.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:597)

at org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:173)

at org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:89)

at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:133)

at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:82)

at org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:58)

at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)

at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)

at java.util.concurrent.FutureTask.run(FutureTask.java:138)

at org.apache.cxf.workqueue.SynchronousExecutor.execute(SynchronousExecutor.java:37)

at org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:106)

at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:243)

at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:110)

at org.apache.cxf.transport.servlet.ServletDestination.invoke(ServletDestination.java:98)

at org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:423)

at org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:139)

at org.apache.cxf.transport.servlet.AbstractCXFServlet.invoke(AbstractCXFServlet.java:142)

at org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:179)

at org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPut(AbstractHTTPServlet.java:120)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:758)

at org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:159)

at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)

at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)

at com.sap.core.communication.server.CertValidatorFilter.doFilter(CertValidatorFilter.java:321)

at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)

at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)

at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)

at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)

at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:501)

at com.sap.security.auth.service.webcontainer.internal.Authenticator.invoke(Authenticator.java:192)

at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)

at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98)

at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950)

at com.sap.core.tenant.valve.TenantValidationValve.invokeNextValve(TenantValidationValve.java:221)

at com.sap.core.tenant.valve.TenantValidationValve.invoke(TenantValidationValve.java:103)

at com.sap.js.statistics.tomcat.valve.RequestTracingValve.invoke(RequestTracingValve.java:24)

at com.sap.core.js.monitoring.tomcat.valve.RequestTracingValve.invoke(RequestTracingValve.java:27)

at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)

at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408)

at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1040)

at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:607)

at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:313)

at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)

at java.lang.Thread.run(Thread.java:743)

Caused by: com.sap.db.jdbc.exceptions.JDBCDriverException: SAP DBTech JDBC: Cannot connect to jdbc:sap://vadbjn5.nwtrial.od.sap.biz:30015/ [Cannot connect to host vadbjn5.nwtrial.od.sap.biz:30015 [Connection refused], -813.].

at com.sap.db.jdbc.exceptions.SQLExceptionSapDB.createException(SQLExceptionSapDB.java:219)

at com.sap.db.jdbc.exceptions.SQLExceptionSapDB.createException(SQLExceptionSapDB.java:203)

at com.sap.db.jdbc.exceptions.SQLExceptionSapDB.generateDatabaseException(SQLExceptionSapDB.java:186)

at com.sap.db.jdbc.Driver.connect(Driver.java:192)

at com.sap.db.jdbcext.DataSourceSAPBase.openPhysicalConnection(DataSourceSAPBase.java:350)

at com.sap.db.jdbcext.DataSourceSAP.getConnection(DataSourceSAP.java:39)

at com.sap.core.dbaas.schema.util.ConnectionProvider.getConnection(ConnectionProvider.java:42)

at com.sap.core.dbaas.schema.util.JdbcExecutor.executeForConnectionProperties(JdbcExecutor.java:46)

at com.sap.core.dbaas.schema.util.JdbcExecutor.execute(JdbcExecutor.java:32)

at com.sap.core.dbaas.schema.util.JdbcExecutor.executeQueryHasResult(JdbcExecutor.java:72)

at com.sap.core.dbaas.schema.internal.hana.AbstractHanaSchemaManager.userExists(AbstractHanaSchemaManager.java:105)

at com.sap.core.dbaas.registry.internal.DbAreaRegistry.userExists(DbAreaRegistry.java:1225)

... 49 more

2014-05-19 09:52:11,119 INFO [main] com.sap.jpaas.infrastructure.console.CommandManager: Command [open-db-tunnel] cleanup() finished for [0] ms

2014-05-19 09:52:11,125 FATAL [main] com.sap.jpaas.infrastructure.console.ConsoleClient: ERROR: An internal server error occurred.

Existence of database user/schema for ID itelligence could not be checked in the underlying DBMS system due to an error. Contact HCP support if the error persists.