My ASP.NET web application works fine in VS. But when I try and deploy it on my webserver I get an error screen:
HTTP Error 500.19 - Internal Server Error. The requested page cannot be accessed because the related configuration data for the page is invalid.
Error Code 0x8007000d
Config Error
Config File \\?\C:\Domains\leas****mail.com\web.config
Config Source
-1:
0:
Any idea how I can debug this. Normally it would where in the web.config the issue is, but not in this case. I ran the file through an xml validator and there were no issues detected.
Thanks
You are using a component that defines a new section in web.config. And that component is not installed on your server. I have this problem often with the URL Rewrite for IIS module (from here) or with the .NET Chart Controls (from here) for example.
Check your web.config section by section. You'll spot the culprit...
Related
supposedly godaddy did a cache refresh, which I would not think change any basic parms or website setup but now 2 applications don't run
found this post:
0x80070021 Server Error in Application "application name"
HTTP Error 500.19 – Internal Server Error
HRESULT: 0x80070021
Description of HRESULT
The requested page cannot be accessed because the related configuration data for the page is invalid.
This problem can occur when the specified portion of the IIS configuration file is locked at a higher configuration level. To resolve this problem, unlock the specified section, or do not use it at that level. For more information on configuration locking, see How to Use Locking in IIS 7.0 Configuration.
I don't know of any config files above my app and I thought when I have specified my app directory as the app root how could there be any higher config files anyway?
unless there is some other problem cause some body can suggest. called godaddy no help there, they are suggesting some how might site is hacked which is really far fetched
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've created a "test" application below the main application on my website which is an exact duplicate of the main application - I use the /test app to test new changes before putting them in production.
After upgrading the app from .NET 3.5 to .NET 4.0, my /test application refuses to run, returning a 500.19 error from IIS. My main application (and another sub-app at the same level as /test) runs just fine.
I found a lot of references about the 500.19 error and they usually boil down to some line in the web.config that is invalid.
However, in my case the error doesn't point me to any specific line -- the error message is copied below, note that the "Config Source" section is empty.
Error Summary
HTTP Error 500.19 - Internal Server Error
The requested page cannot be accessed because the related configuration data for the page is invalid.
Detailed Error Information
Module IIS Web Core
Notification BeginRequest
Handler Not yet determined
Error Code 0x800700b7
Config Error
Config File \\?\c:\blahblahblah\test\web.config
Requested URL http://localhost:80/blahblahblah/test
Physical Path C:\blahblahblah\test
Logon Method Not yet determined
Logon User Not yet determined
Config Source
-1:
0:
Any clues would be appreciated!
Glad you're sorted now.
For me (and these guys) this error was a due to the URL Rewrite Module not having been installed - look for a 'rewrite' section in the web.config.
Nevermind... ;-)
The problem was because of a duplicate section where I forgot to add a section before the for a custom provider. (at the same time that I upgraded to .NET 4.0, I added a custom provider for encrypting sections of my web.config...)
I found the error the old-fashioned brute force way by commenting one chunk at a time in the config file until it started working...
This error might also be related to trying to run a .net 4.0 application on a IIS that has not been -iisreg with the .net 4.0 path
I get the following error when I try to access a asp.net application on my local machine. Anyone have any ideas?
HTTP Error 500.19 - Internal Server Error
The requested page cannot be accessed because the related configuration data for the page is invalid.
Module IIS Web Core
Notification BeginRequest
Handler Not yet determined
Error Code 0x80070021
Config Error This configuration section cannot be used at this path. This happens when the section is locked at a parent level. Locking is either by default (overrideModeDefault="Deny"), or set explicitly by a location tag with overrideMode="Deny" or the legacy allowOverride="false".
Config File \?\C:\inetpub\wwwroot\TravelProduct\web.config
Requested URL http://localhost:80/TravelProduct/CreateNewQuote.aspx
Physical Path C:\inetpub\wwwroot\TravelProduct\CreateNewQuote.aspx
Logon Method Not yet determined
Logon User Not yet determined
please check if you deployed your application properly : Deploying an ASP.NET Server (IIS 7)
Please check your web.config file, you must have added some configuration setting which is trying to overwrite the applicationHost.config settings.
Regards,
Vivek.
check out my answer at Handler not yet determined error
I did not realize url rewrite was not installed at the first time :)
Reinstall your server asp.net for iss using this command:
X:\WINDOWS\Microsoft.NET\Framework\v(.NET
Version)\aspnet_regiis.exe -i
This may solve your problem
I am trying to deploy a web application to a remote server over which i have no control.
If I use FTP deployment from visual studio, I manage to get the files onto the server, but when I point my browser to the server, it gives me the standand error page:
Server Error in '/' Application.
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".
Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's >configuration tag to point to a custom error page URL.
I have made shure that custom errors has mode="Off" as the text above suggests. No amount of refreshing or Cntl-F5-ing gives me anything other than the error page above.
Its most likely is that the location you have put it is not setup as an IIS Application and this is required for the .net framework application to work correctly.
As you have no control on the server you won't be able to change the IIS settings, and so dropping .net onto the server isn't quite the xcopy deployment method Microsoft pushed lots.
Please verify the virtual directory is mapped to the publish location properly. Because your question tells changing the web.config has no impact.
Probably your application on remote server isn't defined as application in IIS. This means that it can't find it 'code' resources(bin or App_Code directories) and customErrors setting is taken from parent web.config.