Common Problems

  • 1

    Settings are lost after upgrade to Visual Studio 2017

    Rik Crompton · 1 · Last reply by Alon Amsalem

    Replication Steps:

    • Setup some CI monitors in AnyStatus
    • Update Visual Studio
    • Open Visual Studio and go to AnyStatus

    Expected result:

    • The CI Monitors should be visible

    Actual result:

    • The AnyStatus pane is empty


    This is a difficult one for me to recreate, but I *think* that my AnyStatus settings are lost after I update Visual Studio 2017.  I've noticed that the AnyStatus pane has become empty a few times recently, and it co-incides with times that I have applied an update to VS 2017.

    For Ref: I'm using VS2017 Pro

  • 1

    Any status makes vs2017 crash when opening tools->options->anystatus after install

    Kenneth Hov · 2 · Last reply by Alon Amsalem

    Any status makes vs2017 crash when opening tools->options->anystatus (never opened anystaus, just installed). If I open settings via the any status window, it works. When I tried after opening anystatus window, the I was able to open settings from the tools menu without vs2017 crash. 

  • 1

    Unauthorized Error on adding a TFS build on VS 2017

    Rik Crompton · 2 · Last reply by Alon Amsalem

    I've added AnyStatus to a fresh install of VS 2017 (15.2 (26430.13).  When I try to add a TFS build it fails with the following errors in the Output window:

    I'm using Visual Studio online:

    • URL:
    • Collection: DefaultCollection
    • Team Project: <Project Name>
    • Build Definition: <Build Name>
    • User Name & Password: as used when accessing


    [10:59:44.951] Updating "BUILD".
    [10:59:45.364] An error occurred while updating "BUILD". Exception:
    System.AggregateException: One or more errors occurred. ---> System.Net.Http.HttpRequestException: Response status code does not indicate success: 401 (Unauthorized).
    at System.Net.Http.HttpResponseMessage.EnsureSuccessStatusCode()
    at AnyStatus.BaseTfsBuildHandler.<GetBuildDefinitionIdAsync>d__2.MoveNext()
    --- End of inner exception stack trace ---

  • 0

    Have a problem? Please share it with us and we will do our best to solve it!

    Alon Amsalem · 0 · Posted
    Looking for a solution to your problem? Start by writing it here. Chances are someone has experienced it in the past and will help you resolve it.