locked
ListPools timeout RRS feed

  • Question

  • Hello

    I am doing the tutorial : http://azure.microsoft.com/en-us/documentation/articles/batch-dotnet-get-started/
    But the call to IPoolManager.ListPools fails with :
    - AggregateException : One or more errors occurred.
    - (Inner) BatchException : The client could not finish the operation within specified timeout.

    Any advice ?

    I am in an enterprise corporate network.
    I have set my proxy credentials to avoid a WebException : The remote server returned an error: (407) Proxy Authentication Required.

    Thanks in advance for your help

    Vianney

    Friday, October 31, 2014 11:57 AM

Answers

  • If you are on step 12 then one thing to do is change a line in step 9:

    private const string Uri = "http://batch.core.windows.net";

    to

    private const string Uri = "https://batch.core.windows.net";

    (use httpS not http).

    The tutorial page will be republished today with some corrections.  This is a critical one.

     

    I cannot say this will fix your problem, but it is a necessary step to get the sample working.

    Do any calls work?  ListWorkItems, ListCertificates?  You could even try any get with dummy data and see if you get a rational 404 instead of a timeout...

    If you follow the example I posted earlier in using ToString() on the BatchException, the text will probably include your account name (it is part of all of our REST URIs but can be crossed out or omitted here)... your key (secret) is not disclosed by any ToString(). The full exception can help us in many cases.

    • Marked as answer by Vianney Friday, October 31, 2014 9:08 PM
    Friday, October 31, 2014 4:10 PM

All replies

  • If you are on step 12 then one thing to do is change a line in step 9:

    private const string Uri = "http://batch.core.windows.net";

    to

    private const string Uri = "https://batch.core.windows.net";

    (use httpS not http).

    The tutorial page will be republished today with some corrections.  This is a critical one.

     

    I cannot say this will fix your problem, but it is a necessary step to get the sample working.

    Do any calls work?  ListWorkItems, ListCertificates?  You could even try any get with dummy data and see if you get a rational 404 instead of a timeout...

    If you follow the example I posted earlier in using ToString() on the BatchException, the text will probably include your account name (it is part of all of our REST URIs but can be crossed out or omitted here)... your key (secret) is not disclosed by any ToString(). The full exception can help us in many cases.

    • Marked as answer by Vianney Friday, October 31, 2014 9:08 PM
    Friday, October 31, 2014 4:10 PM
  • It works fine with https. Thanks for your quick answer.
    BTW I saw a couple of errors in the tutorial.
    I was preparing a pull-request to fix the documentation.
    Friday, October 31, 2014 9:10 PM