A connection attempt failed

Question

A connection attempt failed

Closed this issue 12 years ago · 20 comments

Hi,
I'm having this issue trying to use the .NET-MAPI-Wrapper and im sure its something simple im missing but could you possibly point me in the correct direction?

Here is the error i get when running this code.

A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond

I'm just trying to use one of your examples but im trying to figure out if i missed a setting or soemthing?

long _id = MyworkVideoId;
BrightcoveApi api = BrightcoveApiFactory.CreateApi("MyWorkReadKey");
//messing with timeout here
api.Configuration.RequestTimeout = 999999999;
BrightcoveVideo video = api.FindVideoById(_id);

This should work correct?
Thank you,
Tom

Answer 1 · 2013-04-10T20:51:17.000Z

That looks ok at a glance...

In general, you shouldn't have to mess with the timeout when performing a simple find_by_id. What sort of network are you on? My initial suspicion is that there could be a firewall causing problems in between your computer and the Brightcove network.

Do you get a response if you manually craft the URL and enter it into your browser? Try this URL: http://api.brightcove.com/services/library?command=find_all_videos&token=0Z2dtxTdJAxtbZ-d0U7Bhio2V1Rhr5Iafl5FFtDPY8E.

That's from the Brightcove API docs and will retrieve videos from their example account. If that works for you within a browser on the computer in question, then in theory so should .NET wrapper.

Answer 2 · 2013-04-10T21:04:28.000Z

Yes I am able to pull back results when using an example like that in a browser, and also thanks for the very quick response!.
I switched the token to my token and i can pull back all our videos.

Answer 3 · 2013-04-10T21:16:24.000Z

Sorry, to clarify. I can pull back information posting a link in the browser but i am still having the same problem in the .NET wrapper.

Answer 4 · 2013-04-10T21:46:21.000Z

Ok, that's interesting... The .NET wrapper should be reaching out to the Brightcove server in very much the same manner that the browser does.

Is there anything unusual about the computer on which you're testing? For instance, is it a partial trust environment? (Not sure how that would affect things, but I've never tried this code under partial trust.)

Have you customized the .NET wrapper using any of the hooks described in the wiki? Or is it basically the out-of-the-box version?

Here's a thought... is your web browser configured to work through a proxy? The browser could potentially be running through a proxy without you even being aware, if your network administrator has set up one of several auto-configuring protocols. If so, you can configure the .NET wrapper to work through a proxy, too: https://github.com/BrightcoveOS/.NET-MAPI-Wrapper/wiki/Customizing-Request-Properties

Answer 5 · 2013-04-10T21:49:54.000Z

I will try this and get back to you tomorrow, Thanks!

Answer 6 · 2013-04-10T22:05:56.000Z

oh and its the out of box version.

Answer 7 · 2013-04-10T22:31:19.000Z

It does have a proxy.
I have the name of the proxy and the port. Im afraid im a bit over my head with this though even with the example you linked me. Is that the easiest way to apply the proxy information to the code snippit I sent above?
Thanks

Answer 8 · 2013-04-10T23:12:24.000Z

Yes, you'll have to modify things in the manner described by the wiki article. It should be relatively straightforward, but I'm happy to provide some assistance if you get stuck.

https://github.com/BrightcoveOS/.NET-MAPI-Wrapper/wiki/Customizing-Request-Properties

The code that's shown there should be almost exactly what you need, though perhaps you won't need to specify credentials, and you may need to specify a port. Don't forget to instruct the API wrapper to use your custom request builder after you create the wrapper instance: api.Connector.RequestBuilder = new MyRequestBuilder(api.Configuration);

Answer 9 · 2013-04-11T14:21:03.000Z

If i do not want to build a new class but just have this as a single line in my code can i do this by putting something like api.connector.requestbuilder.(something)?

Answer 10 · 2013-04-11T14:22:14.000Z

Didnt mean to close the issue..

Answer 11 · 2013-04-11T15:36:19.000Z

The only way that currently exists to customize the manner in which the .NET wrapper connects to Brightcove's server is by writing a new IRequestBuilder. The easiest way to do that is it subclass BasicRequestBuilder as described in the wiki. If you're having trouble getting that to work, I'll provide what assistance I can.

I suppose you could alternatively try moving your operation to a different network, or ask your IT department to open a hole in the firewall for you such that you wouldn't be required to connect via a proxy.

Answer 12 · 2013-04-11T15:44:34.000Z

anyway i could discuss over email so i can show you some code snippits which i cant really show on the internet

Answer 13 · 2013-04-11T15:48:29.000Z

Sure, email me at dave at millz dot com.

Answer 14 · 2013-04-12T16:14:19.000Z

great thanks Dave!
I sent you an email

Answer 15 · 2013-04-12T17:32:29.000Z

Hi tpriscu,

I don't see any email from you. (checked spam folder, too)

Answer 16 · 2013-04-15T15:05:02.000Z

Resent email, that was my fault.

Answer 17 · 2013-04-16T16:52:59.000Z

Hi Tom,

I received your emails this time, but I'm busy at work yesterday and today. I'll try to follow up with you again in the near future.

Answer 18 · 2013-04-16T17:48:05.000Z

Thanks Dave that would be very helpful since i am currently stuck on this issue.

Answer 19 · 2013-04-16T18:14:41.000Z

Hi Dave,
I figured it out i believe.
I had to add
myRequest.UserAgent = "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; .NET CLR 2.0.50727)";

to myRequest and seems to be working now
Thanks!

Answer 20 · 2013-04-16T18:16:13.000Z

Fantastic! Glad to hear it's working.

I'm going to go ahead and close this issue. Good luck with the rest of your project :-)