Timeouts, impossible to build

11 posts, 0 answers
  1. Alfonso
    Alfonso avatar
    16 posts
    Member since:
    Jun 2008

    Posted 19 Feb 2014 Link to this post

    Hello,

    I'm testing the Visual Extension for Visual Studio and allways getting timeout when building.

    We are interested in thi tool, but we always get a timeout Exception

    C:\Users\Alfonso\AppData\Local\Microsoft\VisualStudio\10.0\Extensions\ztbo1mpz.0hh\Targets\Build.targets(147,3): error : Build failed: One or more errors occurred..
    System.AggregateException: One or more errors occurred. ---> System.TimeoutException: Se excedió el tiempo de espera de la operación.

    Server stack trace:
       en #8u.#Czc.#GIc.#BXc.#qb()

    Exception rethrown at [0]:
       en System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
       en System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccess(Task task)
       en #8u.#Czc.#AXc.#qb()



    It worked one or two times, but most of the times we get the timeout error.
    The app is very simple, and the size is very low.

    Thank you.
  2. Alfonso
    Alfonso avatar
    16 posts
    Member since:
    Jun 2008

    Posted 19 Feb 2014 Link to this post

    We are trying also to build from de Windows Client, even from the in-browser Client with the same problem.

    We have also tried disabling every plugin. No matter what we do, we allways get timeout.

    Are there any problems? Is it because is a trial account?

    The error happens if we try to "Build and Deploy", but also with the Publish option.
  3. Steve
    Admin
    Steve avatar
    10941 posts

    Posted 19 Feb 2014 Link to this post

    Hi Alfonso,

    There are currently some problems when using the Visual Studio extension that could cause these timeouts, although after the update to the latest version we released yesterday, this should not happen. Or did this start to happen after updating yesterday?

    However this problem is not known/reported for the Windows or In-browser clients and I used your ImportadoDesdeVs project in attempt to reproduce the problem, but could not. Can you run a ping to platform.telerik.com with 2000 bytes of data whenever the problem starts to occur i.e. run command prompt as Administrator and type "ping platform.telerik.com -l 2000 -t" without the quotes and let it run for several minutes. Then check whether you have any packets lost and what is the %.

    If the problem is not your internet connectivity and it persists, we would appreciate if you provide session logs from FiddlerCap (with the Decrypt HTTPS Traffic option enabled). Start it prior running build & deploy (or whatever other actions you do to get the error) and save the HTTP requests to disk. Zip the sessions and upload it to this ticket.

    Regards,
    Steve
    Telerik
    Icenium is now Telerik AppBuilder, and is part of the Telerik Platform. For more information on the new name, and to learn more about the Platform, register for the free online keynote and webinar on Wednesday, February 12, 2014 at 11:00 a.m. ET (8:00 a.m. PT)
  4. Alfonso
    Alfonso avatar
    16 posts
    Member since:
    Jun 2008

    Posted 19 Feb 2014 in reply to Steve Link to this post

    It looks like a connection problem:

    Haciendo ping a platform.telerik.com [23.253.25.165] con 2000 bytes de datos:
    Tiempo de espera agotado para esta solicitud.
    Tiempo de espera agotado para esta solicitud.
    Tiempo de espera agotado para esta solicitud.

    Estadísticas de ping para 23.253.25.165:
        Paquetes: enviados = 3, recibidos = 0, perdidos = 3
        (100% perdidos),

    100% lost


    But, if i execute:
    tracert platform.telerik.com
    The trace ends correctly.
  5. Alfonso
    Alfonso avatar
    16 posts
    Member since:
    Jun 2008

    Posted 19 Feb 2014 in reply to Alfonso Link to this post

    I have tested right now, and it is working.

    I suppose it was a connection problem, it looks solved now.
    I have tried several times during the morning, so whatever was, its ok now.

    Thanks for your help.

  6. Alfonso
    Alfonso avatar
    16 posts
    Member since:
    Jun 2008

    Posted 19 Feb 2014 in reply to Alfonso Link to this post

    Exceuse me again.

    The windows client is the one that worked before.

    The Visual Extension is having the same problem.
    It has worked one or two times, before the update and after it. But most of the times it doesn't.

    As I said before, the ping operation has 100% lost, but tracert works ok.
  7. Steve
    Admin
    Steve avatar
    10941 posts

    Posted 20 Feb 2014 Link to this post

    Hi Alfonso,

    We suggest running ping in the command prompt while triggering the build in Visual Studio to see whether you get any packages lost, while the project is being transfered to our cloud server. If there are no packages lost, but you still get a timeout error in Visual Studio, please zip and upload your project to a free file share server and give us the link to download it and test with it locally.

    If the project is confidential, send it to support at icenium com and post here, so we know it is there.

    Thanks for working with us in resolving this!

    Regards,
    Steve
    Telerik
    Icenium is now Telerik AppBuilder, and is part of the Telerik Platform. For more information on the new name, and to learn more about the Platform, register for the free online keynote and webinar on Wednesday, February 12, 2014 at 11:00 a.m. ET (8:00 a.m. PT)
  8. Alfonso
    Alfonso avatar
    16 posts
    Member since:
    Jun 2008

    Posted 21 Feb 2014 in reply to Steve Link to this post

    Ok, I have sent a zip file to support with the project.
    Ticket ID: 790367

    It is a test project, and maybe the problems began when we included the Barscanner integrated plugin.
    Because I tested with other project and did build well.


    Regarding the ping, we always get 100% data loss, even when it builds correctly. I think you may have the ping operation blocked.

    Also,

    we have only 3 days of trial left. We would like to test a bit more, because we could not test it propperly because of the build timeouts. Is it possible? Thanks.

    Regards.
  9. Zdravko
    Admin
    Zdravko avatar
    657 posts

    Posted 25 Feb 2014 Link to this post

    Hi Alfonso,

    Thanks for the reply.
    I will forward your inquiry to our Sales team and will continue the conversation about AppBuilder extension issue at your other ticket ID: 790367.

    Regards,
    Zdravko
    Telerik
    Icenium is now Telerik AppBuilder, and is part of the Telerik Platform. For more information on the new name, and to learn more about the Platform, register for the free online keynote and webinar on Wednesday, February 12, 2014 at 11:00 a.m. ET (8:00 a.m. PT)
  10. Deni
    Admin
    Deni avatar
    23 posts

    Posted 06 Mar 2014 Link to this post

    Hello Alfonso,

    Apologies for the delayed response - the request got misrouted due to an internal system issue.
    I can see that you have switched to commercial version of the product so I guess that you do not need the trial extension any more. This was actually the best option since the logic of our new Platform does not allow for the trial version to be extended. Once the 30 days of Enterprise testing are over the license is automatically shifted to Starter edition.

    Feel free to get back to me if there is anything I can assist you with.

    Regards,
    Deni
    Telerik
    Icenium is now Telerik AppBuilder, and is part of the Telerik Platform. For more information on the new name, and to learn more about the Platform, register for the free online keynote and webinar on Wednesday, February 12, 2014 at 11:00 a.m. ET (8:00 a.m. PT)
  11. Alfonso
    Alfonso avatar
    16 posts
    Member since:
    Jun 2008

    Posted 07 Mar 2014 in reply to Deni Link to this post

    Thank you for your response, Deni.

    We were told in the ticket that you were finally able to reproduce the timeouts in the visual Extensión, but had no solution at the moment. We hope that you can detect and correct the problem soon, because we are working only via the Visual Studio Extensión.

    Thanks.
Back to Top