cancel
Showing results for 
Search instead for 
Did you mean: 

HANA Cloud Conncetor: 401 Unauthorized

Former Member
0 Kudos

Hello,

i am installed SAP Hana Cloud Connector 2 on windows platform. I am able to login but cloud connector is show the Connection Failure.

Error log:

2013 09 05 00:55:47#0-500#ERROR#org.apache.catalina.mbeans.GlobalResourcesLifecycleListener##anonymous#Start Level Event Dispatcher###No global naming context defined for server|

2013 09 05 00:55:49#0-500#DEBUG#com.sap.scc.jni##anonymous#Start Level Event Dispatcher###Load library sapscc20jni|

2013 09 05 00:55:49#0-500#DEBUG#com.sap.scc.jni##anonymous#Start Level Event Dispatcher###Init library sapscc20jni|

2013 09 05 00:55:49#0-500#DEBUG#com.sap.scc.jni##anonymous#Start Level Event Dispatcher###Library sapscc20jni is ready to use|

2013 09 05 00:55:49#0-500#INFO#com.sap.scc.rt##anonymous#com.sap.core.js.logging.bridge.OSGILogListener@6046f8df###BundleEvent STARTED|

2013 09 05 00:55:49#0-500#INFO#com.sap.scc.rt##anonymous#com.sap.core.js.logging.bridge.OSGILogListener@6046f8df###BundleEvent STARTED|

2013 09 05 00:55:51#0-500#INFO#com.sap.scc.web.component##anonymous#com.sap.core.js.logging.bridge.OSGILogListener@6046f8df###ServiceEvent REGISTERED|

2013 09 05 00:55:51#0-500#INFO#com.sap.scc.web.component##anonymous#com.sap.core.js.logging.bridge.OSGILogListener@6046f8df###ServiceEvent REGISTERED|

2013 09 05 00:55:51#0-500#INFO#com.sap.scc.web.component##anonymous#com.sap.core.js.logging.bridge.OSGILogListener@6046f8df###BundleEvent STARTED|

2013 09 05 00:55:51#0-500#INFO#com.sap.scc.web.component##anonymous#com.sap.core.js.logging.bridge.OSGILogListener@6046f8df###BundleEvent STARTED|

2013 09 05 00:56:37#0-500#ERROR#com.sap.core.connectivity.tunnel.client.ClientProtocolHandshaker##anonymous#New I/O worker #1###Invalid status of handshake response: DefaultHttpResponse(chunked: true)

HTTP/1.1 401 Unauthorized

Connection: close

Set-Cookie: BIGipServerconnectivitynotification.us1.hana.ondemand.com=745565194.27167.0000; path=/

Vary: Accept-Encoding|

2013 09 05 00:56:37#0-500#ERROR#com.sap.core.connectivity.tunnel.client.notification.NotificationClient##anonymous#New I/O worker #1###Unable to establish notification service connection to server connectivitynotification.us1.hana.ondemand.com/65.221.12.241:443|

2013 09 05 00:56:37#0-500#ERROR#com.sap.scc.ui.TunnelController##anonymous#http-bio-8443-exec-7###Tunnel Connect Failed

com.sap.core.connectivity.tunnel.core.handshake.TunnelHandshakeException: Invalid status of handshake response: 401 Unauthorized

com.sap.core.connectivity.tunnel.core.handshake.TunnelHandshakeException: Invalid status of handshake response: 401 Unauthorized

at com.sap.core.connectivity.tunnel.client.ClientProtocolHandshaker.finishHandshake(ClientProtocolHandshaker.java:88)

at com.sap.core.connectivity.tunnel.client.TunnelClientHandshaker.messageReceived(TunnelClientHandshaker.java:144)

at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:296)

at org.jboss.netty.handler.codec.frame.FrameDecoder.unfoldAndFireMessageReceived(FrameDecoder.java:459)

at org.jboss.netty.handler.codec.replay.ReplayingDecoder.callDecode(ReplayingDecoder.java:536)

at org.jboss.netty.handler.codec.replay.ReplayingDecoder.messageReceived(ReplayingDecoder.java:435)

at org.jboss.netty.handler.timeout.IdleStateHandler.messageReceived(IdleStateHandler.java:294)

at com.sap.core.connectivity.spi.logging.ThreadTaggingHandler.messageReceived(ThreadTaggingHandler.java:30)

at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:296)

at org.jboss.netty.handler.codec.frame.FrameDecoder.unfoldAndFireMessageReceived(FrameDecoder.java:462)

at org.jboss.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:443)

at org.jboss.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:303)

at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:268)

at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:255)

at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:88)

at org.jboss.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:109)

at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:312)

at org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:90)

at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178)

at org.jboss.netty.handler.execution.MemoryAwareThreadPoolExecutor$MemoryAwareRunnable.run(MemoryAwareThreadPoolExecutor.java:622)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)

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

Please help to resolve.

Thanks,

Tamizharasan.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hello,

This issue was automatically resolved.

But now i'm facing different error,

i have install HANA Cloud Connector 1.3 on SLES

it's working good. But not work after restart the server.

i have received the "Internal Server Error 500"

Thanks.

ManolV
Advisor
Advisor
0 Kudos

Hi Tamizharasan,

Which server have you restarted?

When exactly have you received the "Internal Server Error 500"? Could you please explain in more details?

Could you provide us the logs so we could inspect them?

UI logs: SCC UI --> Monitor --> LOGS --> UI Logs --> Download All

Tunnel logs: SCC UI --> Monitor --> LOGS --> Tunnel Logs --> Download All

Regards,

Manol

Answers (2)

Answers (2)

MarkusTolksdorf
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Tamizharasan,

The log shows

HTTP/1.1 401 Unauthorized

Connection: close

when trying to connect to the notification server.

As you tried using us1.hana.ondemand.com, this might be the reason. During Beta phase, only hanatrial.ondemand.com is supported. 

Best regards,

Markus

ManolV
Advisor
Advisor
0 Kudos

Hello Tamizharasan,

Is the problem still valid?

Edit: Please have a look at our official documentation where it is written that the production usage of the Connectivity service v.2 (which is still in beta version) is not allowed.

Just a hint: Hopefully, you can try the scenario in the end of this week when we expect the service to be GA.

Kind Regards,

Manol