cancel
Showing results for 
Search instead for 
Did you mean: 

HCP destination - error while testing the connection

11-14-2016 6:47 AM
4552 views 20 comments
SAP Managed Tags
Subscribe

Dear all,

I am getting attached error while clicking the test connection button after configuring the destination for northwind in my HCP trial account. Could somebody please help me to overcome the same.

Error Description:

Failure reason: "Read timed out (local port 57637 to address 10.117.12.167 (vsa1630636.nwtrial.od.sap.biz), remote port 8080 to address 10.117.18.16 (sgw-a1s-03-int.od.sap.biz))"

Regards,
Gibu.

Accepted Solutions (0)

Answers (7)

Answers (7)

Former Member

I am having the same issue. Have you been able to resolve?

moyalynne
Active Contributor

Hi all;

This issue is now fixed. Thanks very much for your patience and reporting this, and sorry for the inconvenience.

Thanks also to Simon Kemp on twitter for alerting us to the fix.

best,

-m

Former Member
0 Likes

Thank you for your effort. It's a high appreciate if you could tell us what has happened and how to fixed it. Thank you all the same.

former_member264217
Participant
0 Likes

Hi Moya Watson,

Currently I am facing the same connection issue on destination for northwind service. Can u help to resolve this issue.

Failure reason: "Read timed out (local port 41560 to address 10.117.12.251 (vsa2280624.nwtrial.od.sap.biz), remote port 8080 to address 10.117.18.16 (sgw-a1s-03-int.od.sap.biz))"

Thanks in advance.

Regards

Sukhram Bhamboo

Former Member
0 Likes

Hi Moya

I am able to access northwind service, when trying to connect to our netweaver gateway development server we are getting similar error, please guide us with the steps required to configure our development server.

Failure reason: "Read timed out (local port 48098 to address 10.117.12.178 (vsa3770046.nwtrial.od.sap.biz), remote port 8080 to address 10.117.18.16 (sgw-a1s-03-int.od.sap.biz))"

Regards

Subhash

moyalynne
Active Contributor
0 Likes

Hi Subhash -- thanks for reaching out and for doing a search first! The issue above was temporary however, and I'm unfortunately not directly on the team and unable to help resolve personally -- was just passing along info that it was fixed.

The best way to get the right experts to look at this issue is to create a new question -- if you've already done that, let me know and I can try to ping the people who can help.

thanks much and hope you get it running soon;

-m

Former Member

Experienced same issue when checking connection with message shown here:

Failure reason: "Read timed out (local port 59093 to address 10.117.12.167 (vsa1630636.nwtrial.od.sap.biz), remote port 8080 to address 10.117.18.16 (sgw-a1s-03-int.od.sap.biz))" Close
moyalynne
Active Contributor
0 Likes

Yes, we see the same issue still is unresolved. We're tracking it internally. thanks!

Former Member

Still now the issue hasn't been fixed, how's it going ? Is there some problem on the user authorised?

moyalynne
Active Contributor
0 Likes

A few teams have been working on this internally. Will keep you posted here. Thanks and apologies.

Former Member
0 Likes

Thank you for your feedback. I wish this issue will be fixed soon that I can continue my happy experience on this new

platform.

moyalynne
Active Contributor

Apologies for the issues -- we were tracking a problem with the OData provisioning service but now that's back up, users are still experiencing timeouts. We've raised the issue internally. Stay in touch

former_member272302
Discoverer
0 Likes

Thanks for the update. Will wait for sap to reslove the issue.

Former Member

Any update Moya?

moyalynne
Active Contributor

We are still tracking internal tickets and there is not yet any resolution. Apologies for the inconvenience!

Former Member

I have this issue also, maybe there is a problem about SAP database proxy error. If any progress, pls. kindly tell me. Thank you!

moyalynne
Active Contributor
0 Likes

From what I can tell of the internal conversations, it does seem to be proxy related. Team is working on it so please stay tuned - and apologies again.

former_member272302
Discoverer
0 Likes

Yes it's working fine now.Thanks to who ever worked on this to resove the issue.

0 Likes

can you share how the issue is fixed

Former Member
0 Likes

Hi, did you manage to get any resolution to this?