CODEWITHSUNDEEP
asp.netiisprofiler
Christopher Bai
Christopher Bai

Reputation: 391

The web site could not be configured correctly; getting ASP.NET process information failed. Requesting

I made a website using the asp.net 4.0. I have deployed it to my local IIS. Need to do profiler in Visual Studio 2010. When I click the run profiler button I get the error like below.

"The web site could not be configured correctly; getting ASP.NET process information failed. Requesting 'http://xxx/VSEnterpriseHelper.axd' returned an error: The remote server returned an error: (500) Internal Server Error."

What's getting wrong? I to solve this problem.

Upvotes: 22

Views: 6139

Answers (4)

Maksim Ramanovich
Maksim Ramanovich

Reputation: 621

For me the problem was in the location tag:

<location path="." inheritInChildApplications="false">

The Profiler ignored it during Web.config modifications and added duplicate sections that were already defined within the location tag. Therefore resulting Web.config was considered as broken by IIS and 500 error was being returned.

Common approach how to determine a root of the issue: when the Profiler modified the config and before the exception thrown (about 1 second) you can see modified Web.config in your project folder (next to newly created backup of the original file). At this time you need to "catch" (copy & paste) modified Web.config and then use it as regular configuration file in your project. Now when you open your project in browser, IIS will show what exactly is wrong (details of the "500" exception).

Upvotes: 1

Rachel Fishbein
Rachel Fishbein

Reputation: 858

I had the same issue. The problem was in web.config. After I fixed it, I did not get this error anymore.

Upvotes: -6

type.parse
type.parse

Reputation: 21

In the web.config changing the attribute of the appSettings from "configSource" to "file" worked for me.

<appSettings configsource="..."> to <appSettings file="...">

Upvotes: 0

David W
David W

Reputation: 10184

This issue can occur if the target site is using an external settings file.

You might review the bugreport on this issue someone filed at connect.microsoft.com

Possible problem cause w/Profiler, IIS

Upvotes: 6

Related Questions