locked
No Error Details Link on Error Log with Agents - With a 500 Internal Server Error RRS feed

  • Question

  • I am running a small loadtest and recieving 500 Internal Server errors occasionally, however, there is no place to click details on the error log.  There is a view link under the stack for failed requests afterwards, however these requests where expected after the 500 errer.  So what determines if there will be a view link under Stack or Details for a particular request.  And is there a way to better log an instance (like when you run a single webtest) for each of the users in a load test.  It looks like there is for 2010, but not 2008 (which I am using).  The small load test I'm running has 5 conncurent users with 5 agents (1test/agent) and only 1 agents fails (gets the 500 internal service error) occasionally.  The inconsistant results seem to make it harder to debug.  I have the % of new users set to 100, and use a csv file to import 5 different users logging in.  Also, I cannot regenerate the 500 error if I do a single webtest run, it only occurs in a load.
    Thursday, July 16, 2009 2:41 PM

Answers

  • Hello NickN87,

    Based on your description, there are some errors including the 500 Error.

     

    Generally, 500 Internal Server Error indicates a failed request which could be caused by your webtest, load on the server,etc. I suggest you solve other errors first to see if this error remains.

     

    The following articles will be helpful for your troubleshooting:

    ·          Debugging errors in Load Test

    ·          How to debug a Web Test


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    Send us any feedback you have about the help from MSFT at fbmsdn@microsoft.com.
    Monday, July 20, 2009 5:22 AM
    Moderator

All replies

  • I was able to get a detail window to come up after a few runs; there is a localization error, says "The process cannot access the file 'f:\inetpub\wwwroot\...\Main.asp.xml because it is being used by another process."

    I would take a guess this is a race condition.
    Friday, July 17, 2009 12:39 PM
  • Hello NickN87,

    Based on your description, there are some errors including the 500 Error.

     

    Generally, 500 Internal Server Error indicates a failed request which could be caused by your webtest, load on the server,etc. I suggest you solve other errors first to see if this error remains.

     

    The following articles will be helpful for your troubleshooting:

    ·          Debugging errors in Load Test

    ·          How to debug a Web Test


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    Send us any feedback you have about the help from MSFT at fbmsdn@microsoft.com.
    Monday, July 20, 2009 5:22 AM
    Moderator