Not able to run performance tests
I am running the August CTP and I receive the following error whenever I try to run performance tests against an ASP.NET application:
"The web site could not be configured correctly; getting ASP.NET process information failed. Requesting 'http://localhost/EffortTrackingWeb/VSEnterpriseHelper.axd' returned an error: The remote server returned an error: (500) Internal Server Error."
I'm running on WinXP SP2 with IIS 5.1. The website works when I am not running a performance test. The error occurs when trying either sampling or instrumentation, .NET objects or not. The output window contains the following error: PRF0017: Can't launch server for 'http://localhost/EffortTrackingWeb'.
Any ideas why this may not be working? If necessary I can provide remote desktop access to the machine.
Thanks!
Jeff
Hi Jeff,
You said you already made sure that you can see the website in the browser, right?
Then try to change the web.config file (if you have one), and removve the xmlns attribute and see if it works. In the meantime, I will check Auguest CTP tomorrow and if needed I can TS to your machine and figure out what's going on.
-Munjal
There are a few things you can check:
1. The web site opens in the browser. Sometimes, default.aspx is not added to the default documents, and hence the URL like http://localhost/WebSite1/ do not open fine, but http://localhost/WebSite1/default.aspx opens fine.\
2. If you have a web.config file, try removing the xmlns attribute and see if it works
If these do not solve your problem, can you answer the following for me to figure out what's going on?
- Is this IIS/Cassini?
- How did you create a performance test?
- Is it sampling/instrumentation/both?
-Munjal
Yes, it was. Sorry I didn't post it. The key thing here is that you must disable the threshold tests. When you initially create a test a timeout threshold is part of the default settings. however, when you are running the tests standalone on a development platform, it usually isn't as powerful as a production platform. Because of this, the threshold causes numerous (in my case, all) tests to fail. When the initial threshold failure occurs the step that was supposed to run is essentially skipped. In my case this means that certain values were not getting set.
Removing the threshold solved the issue.
Jeff
Whoops, wrong problem (I had several). The latest release (release candidate), everything is working fine. I found that I had no problems when deploying directly to a test machine (instead of in the development environment) and using a controller and agents.
Jeff
Found a solution for my problem... We have anonymous access blocked in the web.config, and for some reason there is a difference between running the application and profiling the application when it comes to access rights. Instead of going to the Forms authentication it just gives that error message. By allowing anonymous access during profiling the problem disappeared... So it's a possible workaround for those who have problems.
/Kjell
