The Issue
I have cloned down an exiting web forms project and when I try to build, I get the error;
HTTP Error 500.19 - Internal Server Error
The requested page cannot be accessed because the related configuration data for the page is invalid.
Below this error, the "Detailed Error Information:" section provided a config file path that seems to point to the correct place, accept to the machine of the previous contributor of the solution.
Below is the approach I took to try resolving this issue
Initially, from this, I tried finding out where this incorrect file path is coming from but came across nothing even vaguely relative so I tried googling the error itself.
I came across this question:
How do I resolve "HTTP Error 500.19 - Internal Server Error" on IIS7.0
An answer provided by Bruce mentioned to:
"Check the directory and see if that user has appropriate rights to
it".
In an attempt to do this, I had a quick google and same across the following question: The requested page cannot be accessed because the related configuration data for the page is invalid error
From intermension's answer, I gathered that it was "ApplicationPoolIdentity" that was not assigned the correct permissions so in ettempting to resolve this, I visited the following link. IIS7 Permissions Overview - ApplicationPoolIdentity
I followed Jon Adams' steps successfully as shown here:
This was unsuccessful and I'm unsure of where to go now.
Thank in advance! :)
You can follow there steps:
Check which application pool your website is using
Change it to use ApplicationPoolIdentity if it is not.
Go to your website directory and search for Application Pool Identity user which has format IIS AppPool{AppPool Name} e.g. IIS AppPool\DefaultWebsite and give it read permissions
In IIS Manager select your website in the left pane and then in right pane double click the HandlerMappings icon to ensure that handlers list show up.
Related
I have a problem which is similar to this one, but not quite.
We have a solution with two Azure Web Apps, built and deployed by Visual Studio Online. It has been working just fine for a few months, but suddenly all requests end in a 401.72 response:
HTTP Error 401.71 - Unauthorized You do not have permission to view
this directory or page.
Most likely causes: The authenticated user does not have access to a
resource needed to process the request.
Things you can try: Create a tracing rule to track failed requests for
this HTTP status code. For more information about creating a tracing
rule for failed requests, click here.
Detailed Error Information: Module EasyAuthModule_32bit
Notification AuthenticateRequest Handler
ExtensionlessUrlHandler-Integrated-4.0 Error Code 0x80004005
Requested URL https://[appname]:80/ Physical Path
D:\home\site\wwwroot Logon Method Not yet determined Logon User
Not yet determined
More Information: This is the generic Access Denied error returned by
IIS. Typically, there is a substatus code associated with this error
that describes why the server denied the request. Check the IIS Log
file to determine whether a substatus code is associated with this
failure. View more information »
Microsoft Knowledge Base Articles:
As far as I can figure out, no relevant configuration changes has been done.
Restarting the Web App and redeploying the solution didn't solve the problem
As it happens, we were due to recreate the environment anyway, and after this was done, the same deployment setup (with updated target) deployed successfully and it's working fine on the new Web App intsance.
Even if we now have a working environment, we'd really like to know what happened, so we can be sure it doesn't happen again.
Can anyone shed any light on this?
You had easy auth turned on. Do you expect it to be turned on? That appears to be causing the issue.
If you don't intend for it to be on, please turn it off via either portal (old|new) by navigating to your Web App and finding it in your settings.
If you do intend for it to be on, you need to check your configuration to make sure you've properly set up AAD. Maybe the App Configuration within AAD has changed?
If neither of those things helps, let me know.
I tried creating new web applications...
I have been using VS 2010 for developing website
I make use of wsp builder to package all my dlls, pages, scripts and images into a solution package and deploy it in the web applications.
I am trying to get a MVC Web App running in my IIS. Unfortunately, I am absolutely stuck on this error:
HTTP Error 500.19 - Internal Server Error
The Request page cannot be accessed because the related configuration data for
the page is invalid.
Module: IIS Web Core
Notification: Unknown
Handler: Not yet determined
Error Code: 0x80070005
Config Error: Cannot read configuration file due to insufficient permissions
Config File: \\?\C:\Users\dev.fuji\Desktop\Mywebiste\web.config
Request URL: http://xxx.xxx.xxx.xxx
Logon Method: Not yet determined
Logon User: Not yet determined
Config Source
-1:
0:
I am not quite sure what else to do. Why I got this error, I search even youtube but everyone get it worked but why not me.. I do almost exactly they done.
MAYBE** because before this the server already done by someone else in my place... I new worker in my it department...so I miss the installment part in video.. Is that what make the error? Do I have to reinstall my iis??
If anyone has any information or would be able to help me work through this it would be much appreciated. Thanks!
Your config file shouldn't be located on the dev desktop.. it should be within your website, and that website should be located somewhere within IIS (default location is c:\inetput\wwwroot\). Start there, if you have any questions, I'd say give this URL a shot first: http://www.iis.net/learn/get-started/getting-started-with-iis/create-a-web-site
I'm having the classic (dare I say typical?) error on the ASP.NET production server, which tells me that I can't view errors. Below the error displayed below, are things I've already tried.
In IIS Manager (6.0), the application is located under one of the web sites in "Web Sites". It is indeed a web application, as opposed to a virtual directory (it has that gear icon).
When trying to view the error from the localhost (i.e. the server itself), it doesn't find the application on its path, even though the root web site works just fine from localhost. It is clearly not a firewall issue because first of all, the firewall is turned off, and second because the root web site works fine from localhost. Heck, I even tried connecting through telnet and that worked fine and dandy too, so it is most certainly and very clearly not a firewall issue.
Basically, I just need to view the error at all. I won't have to fix this problem if I can just see the error and fix it, because obviously there is something wrong in the code itself... I just don't know what, because IIS/.NET won't tell me.
Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.
Details: To enable the details of this specific error message to be viewable on remote machines, please create a tag within a "web.config" configuration file located in the root directory of the current web application. This tag should then have its "mode" attribute set to "Off".
So what I've already tried is what the error message itself suggests by setting the customErrors thing to "Off". In fact, it always was on "Off" so I didn't have to change anything. I've made sure that the web.config XML is valid.
Another common reason for this error is that the .NET run-time is set to version 1.1, not 2.0. I've also made sure that this is correctly configured to 2.0.
I'm running it in an independent application pool, meaning that there are no other applications at all, much less 1.1 applications, on the same application pool.
I've made sure that EVERYONE can do ANYTHING to the files and directories in the application itself. I understand the security ramifications here, I'm just trying to get it working at all, and then I'll constrain the access rights afterward, one step at a time. But in any case, everyone can read those files.
Any help deeply appreciated. Thank you in advance.
The error is a .NET framework error so it finds the app, but there is a configuration error. What you could do is add some event logging code in APplication_Error handler in global.asax to trap these errors, or turn on health monitoring (<healthMonitoring enabled="true" />), which by default will log ASP.NET framework errors to the event log.
HTH.
Never got this working until I changed the application from a "sub-application" (I don't know the proper terminology) to an independent website with its own hostname. ASP.NET works in mysterious ways.
I have been trying to configure a small website on a Windows Server 2008 running IIS 7. Unfortunately, when trying to load the website I keep getting the error: Server Error 401 - Unauthorized: Access is denied due to invalid credentials.
The permissions on the website folder include read, write, and execute for user ASP.NET v4.0. I even clicked "Check names" before adding the user to folder, to make sure that I spelled everything correctly. But the error continues to show. Also, I noticed that everything works okay if I add "Users" to the permissions for the folders containing the website, but I don't see why this should be necessary. I only want to give ASP.NET v4.0 access to the folder.
Some other noteworthy points include that I'm using the ASP.NET v4.0 application pool, that the managed pipeline is integrated, and that load user profile is set to true.
If anyone has any ideas, I'd appreciated the help. I'm stumped!
EDIT: Does it matter that the website is on the d: drive? I just assumed this wasn't important...
I find I always need to give IIS_IUSRS access.
I'd recommend you to use the Process Monitor to detect which user is actually accessing the file.
Here you'll find an explanation about how to achieve that.
Open IIS7 on the server. Highlight the site, and double-click on the Authentication icon in the Security Section. Check that Anonymous Authentication is enabled.
Some troubleshooting links for this particular issue:
http://support.microsoft.com/kb/902160
http://support.microsoft.com/kb/907273
I don’t know anything about deploying a website, so I probably made some stupid mistake.
Anyways, I opened IIS 7 manager, created new virtual directory ( via Add Application ) and pointed it to physical directory where Visual studio saved my Web project. But when I tried to request an .aspx page, browser reported the following error (I won’t post the whole error, but just the interesting bits):
Handler: Not yet determined
Config Error: Cannot read configuration file due to insufficient permissions
Logon User: Not yet determined
A) why is handler not yet determined? As far as I know, IIS7 does have Asp.Net handler registered?!
B) Why wouldn’t IIS have sufficient permissions? Does that mean I should give IIS higher privileges? Or does Asp.Net runtime have insufficient permissions?
C) Could the error also be due to the fact that perhaps it expected the user to authenticate itself? I’m assuming this due to Logon user not yet being determined?
D) And finally, any ideas how to make it work?
thanx
error code:0x8007000d
I started playing with permissions and all the stuff about access issues to web.config or applicationhost.config anyway those did not change the error.
while I was playing with my web.config I deleted rewrite tags from my config file and error changed. then I installed "web platform installer" and installed url rewrite module for IIS and played with some configuration now my site is working. it took about one day to find out this issue I hope it helps someone.
Does the identity of your IIS application pool have sufficient rights to access the folder that is hosting your site?