I have a legacy asp.net application/site which is an amalgamation of mess from 2002 thru to present. It includes classic ASP as well as a whole lot of bad code written by all sorts of interns etc. Recently this code base has begun exhibiting performance issues and I needed a way to measure the issue and see if I can get some clues.
So as an aside when I first installed VS 2015 Community I saw the new "System Diagnostics" automatically open when I first ran one of my web applications. I thought it was cool but didn't need it right then so forgot about it. Now months later I want to go use it and I find that it doesn't work anymore, there aren't really menu options for it anymore and research into the subject says "this is for Ultimate users only"... pretty corn-fusin!!! Best I can tell it's tied to something called intellitrace and I'm out of luck.
So I am receiving an error when I run "performance profiler" on my site. My site is hosted in IIS 7.5+ using localhost. The site has been upgraded to .net 4.5.
The error is a common one. The site finishes compiling and before it begins profiling I get an error:
The web site could not be configured correctly; getting ASP.NET process
information failed. The server may not be running a version of Asp.Net
version 2.0 or greater. Requesting
‘http://localhost:85/VSEnterpriseHelper.axd; returned an error: The remote
server returned an error: (500) Internal Server Error.
It follows that up with this in the output window:
Error VSP1710: File not found: C:\_IISHosted\Project-Inside-NET45\http_localhost_85_160902.vsp
PRF0025: No data was collected.
(don't mind the port 85, I've tried it on the default port 80 as well)
I've been researching this for days. This has been a common and painful issue for people going all the way back to VS 2005 as far as I can see. I've checked and tried about everything that has been suggested in threads on this error.
My site is not in 'source control' because I've made a test copy trying to get it to work so its not a write permission issue for the web.config.
I use forms authentication in this site and have looked into adding a <location> element in the web.config for the .axd file in question but it doesn't matter. Furthermore if I setup a basic forms authentication site the profiler works and I don't need to mess with authorization, handlers, permissions, nothin... it just works.
I am using the managed pipeline mode in app pool to handle authorization using asp.net instead of IIS (as they don't play well together) it may be worth pointing out, I should go set that up in my test forms auth site (the one that works) and see if that has anything to do with the issue.
My web.config is not linking to the applicationhost (which apparently causes issues).
If I look at the IIS logs after receiving the error message I see the VSEnterpriseHelper.axd is being sent a 500.19 with a 183 sc-win32-status message which when I look it up indicates "Cannot create a file when that file already exists.".
Specifically the log entry looks like this:
date time s-ip cs-method cs-uri-stem cs-uri-query s-port cs-username c-ip cs(User-Agent) sc-status sc-substatus sc-win32-status time-taken
2016-09-02 17:58:13 ::1 GET /VSEnterpriseHelper.axd - 85 - ::1 - 500 19 183 5
So I'm at a loss trying to get this darn profiler to work. I've had trouble with it over the last 10 days. It periodically works on a site then throws up junk like this. On the site I'm currently messing with I've never gotten it to work. Things I've done that helped it work on other sites (and tried on this one as well) were:
remove IIS Express folder and let it re-create (even though I'm not using IIS Express)
clear temp asp.net files
remove child applications (sub-applications)
the aforementioned: check handlers exist in IIS, check link to appicationconfig, check permissions on web.config, put <location> authorization onto .axd file.
This has apparently been a thorny issue for a long time. There is very little current documentation about the tool and its specific peccadilloes. You get the same error message for a variety of "failure" conditions... it's very frustrating overall lol.
Does anyone have any idea what else I can do?
I think I'm going to start clearing .dll's in BIN next (as best i can) as I do have one giving a warning about using a newer version of .NET (which I've also wasted time researching and finding that it is likely an error in the framework that I need to go up an incremental version in .net to resolve)...sigh.
Thanks if anyone can help, and if not thanks for reading.
Doug