'Validate Response Code' results in '503 - Service Unavailable'

Locked 'Validate Response Code' results in '503 - Service Unavailable'

  • jueves, 14 de junio de 2012 10:43
     
     

    I've been running tests lately and am trying to get the performance counts working (which still don't work by the way)

    We are running a website and have three different locations:

    1. Test
    2. Acceptance
    3. Production

    The tests were working fine until we changed something in the open ports. Since then we were getting this error when testing the acceptance server. It is still working fine for the test server.

    In the details of the test it says:

    Response URL | Passed
    Response Time Goal | Passed
    Validate Response Code | 503 - Service Unavailable'

    We reversed our changes, but without any affect so far.

    When checking netstat -a the ports are still open and established. The controler still mentions all agents as ready, so it's not the connect to or from the agents. The website are all accessible in the browsers, on the server and on the agents.

    When trying to access:  http://servername:8080/services/v1.0/ServerStatus.asmx?op=CheckAuthentication
    I get: Internet explorer cannot display the webpage"
    Network diagnostics gives: "The remote device or resource won't accept the connection"

    I have no /TFSserver user account, but never had one when it all worked.

Todas las respuestas

  • viernes, 15 de junio de 2012 2:06
     
     

    Can you run fiddler to capture the trace when the web test is run and compare it with the trace when you manually run the scenario in browser.

    Thanks,

    Anuj


    http://www.anujchaudhary.com

  • viernes, 15 de junio de 2012 9:55
     
     

    Thanks for your reply. For some strange reason I'm no longer getting the error. I check whether the tech-guys changed something, but they didn't. Although this seems positive, it adds a reliability issue as it could happen again.

    I still tried the fiddler option, which I already had installed. It gives results when I execution the scenario manually, but it doesn't return any values when Visual Studio runs a test. This is a shame, because I really would like to have confirmation that the test is actually running, aside from a notification 'test running'. Any changes I could make?

    The issue with the performance counters is still there:
    Exception LoadTestCounterCategoryNotFoundException 1 The performance counter category 'Memory' cannot be accessed on computer 'X' (Access is denied) ; check that the category and computer names are correct.

    The connection is good. Perf Mon is running and my account is local admin. We will be trying the same soon with a domain admin user, maybe it helps. I will update this post if so.

  • lunes, 18 de junio de 2012 5:48
    Moderador
     
     

    Thanks for Anuj’s help.

    Hi vegter,

    Thank you for posting in the MSDN forum.

    Thanks for your reply. For some strange reason I'm no longer getting the error.

    About the previous issue, do you mean that it works well now? If so, I will mark your reply as the answer and close this thread.

    Exception LoadTestCounterCategoryNotFoundException 1 The performance counter category 'Memory' cannot be accessed on computer 'X' (Access is denied) ; check that the category and computer names are correct.

    About the new issue, if possible, you could post a new thread for it, in this way, our discussion here will not deviate too much from the original issue. This will make answer searching in the forum easier and be beneficial to other community members as well.

    In addition, I did some research about the new issue, Ed wrote a blog about the similar issue, when we use a test controller, the user account is the account the controller service is running as. For detailed information, see “Reading Performance Counters on Vista and Server 2008 Machines”. Hope it could help.

    Best Regards,


    Jack Zhai [MSFT]
    MSDN Community Support | Feedback to us

  • martes, 19 de junio de 2012 6:29
     
     Respondida

    The issue is indeed fixed and the error hasn't occured since. Thanks, I will open a new thread for the performance counter issue.

  • martes, 19 de junio de 2012 9:50
    Moderador
     
     

    The issue is indeed fixed and the error hasn't occured since. Thanks, I will open a new thread for the performance counter issue

    I mark you reply as the answer, thanks for your understanding.J

    Have a nice day,


    Jack Zhai [MSFT]
    MSDN Community Support | Feedback to us