I have an ASP.NET Core app that runs great in IIS Express. Similarly, if I launch the app from the command line via dotnet run, everything works smoothly:
C:CodeSandboxIisTestAppIisTestApp>dotnet run
Using launch settings from C:CodeSandboxIisTestAppIisTestAppPropertieslaunchSettings.json...
Hosting environment: Production
Content root path: C:CodeSandboxIisTestAppIisTestApp
Now listening on: http://localhost:5000
Now listening on: https://localhost:5001
Application started. Press Ctrl+C to shut down.
If I try to target local IIS, I get the following error:
Unable to start process C:Program Filesdotnetdotnet.exe. The web server request failed with status code 500, Internal Server Error. The full response has been written to C:Users{my user name}AppDataLocalTempHttpFailure_08-05-50.html.
The HTML file contains this information:
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 0x8007000d
Config Error
Config File ?C:CodeSandboxIisTestAppIisTestAppweb.config
Requested URL http://localhost:80/IisTestApp
Physical Path C:CodeSandboxIisTestAppIisTestApp
Logon Method Not yet determined
Logon User Not yet determined
Note: in case it’s not obvious from that message, this is a minimal repro of my problem, not the actual app
Most of what I see online says that the error code 0x8007000d indicates that I don’t have the .NET Core Windows Server Hosting component (AspNetCoreModule), but I definitely have installed that:
I can also see it in the main «Modules» page of IIS, and verified that the file it points to actually exists:
Strangely, if I try to go to the Modules page for this specific site, I get the same error message as the web page:
There was an error while performing this operation.
Details:
Filename: ?C:CodeSandboxIisTestAppIisTestAppweb.config
Error:
This hosting module version (2.1.8) matches generally what I have installed:
C:Users{my user name}>dotnet --list-sdks
2.1.202 [C:Program Filesdotnetsdk]
2.1.504 [C:Program Filesdotnetsdk]
C:Users{my user name}>dotnet --list-runtimes
Microsoft.AspNetCore.All 2.1.4 [C:Program FilesdotnetsharedMicrosoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.1.8 [C:Program FilesdotnetsharedMicrosoft.AspNetCore.All]
Microsoft.AspNetCore.App 2.1.4 [C:Program FilesdotnetsharedMicrosoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.1.8 [C:Program FilesdotnetsharedMicrosoft.AspNetCore.App]
Microsoft.NETCore.App 2.0.9 [C:Program FilesdotnetsharedMicrosoft.NETCore.App]
Microsoft.NETCore.App 2.1.8 [C:Program FilesdotnetsharedMicrosoft.NETCore.App]
And what my test app is targeting:
<Project Sdk="Microsoft.NET.Sdk.Web">
<PropertyGroup>
<TargetFramework>netcoreapp2.1</TargetFramework>
</PropertyGroup>
<ItemGroup>
<PackageReference Include="Microsoft.AspNetCore.App" />
<PackageReference Include="Microsoft.AspNetCore.Razor.Design" Version="2.1.2" PrivateAssets="All" />
</ItemGroup>
</Project>
Despite all that, I think the problem really is related to IIS and that hosting component! Here is the (very default) web.config that is generated with the project template:
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<location path="." inheritInChildApplications="false">
<system.webServer>
<handlers>
<add name="aspNetCore" path="*" verb="*" modules="AspNetCoreModule" resourceType="Unspecified" />
</handlers>
<aspNetCore processPath="binIISSupportVSIISExeLauncher.exe" arguments="-argFile IISExeLauncherArgs.txt" stdoutLogEnabled="false">
<environmentVariables />
</aspNetCore>
</system.webServer>
</location>
</configuration>
Note: I still get the same error message if I hardcode the full path in the processPath, or use . relative pathing
If I remove the <aspNetCore> node, I get a different error:
HTTP Error 502.3 — Bad Gateway
There was a connection error while trying to route the request.
Detailed Error Information:
Module AspNetCoreModule
Notification ExecuteRequestHandler
Handler aspNetCore
Error Code 0x80070490
Requested URL http://localhost:80/IisTestApp
Physical Path C:CodeSandboxIisTestAppIisTestApp
Logon Method Anonymous
Logon User Anonymous
The point being that the AspNetCoreModule throws the error this time, so it is being loaded and running some code.
Publishing to a separate folder and manually setting up the site in IIS (rather than relying on the default Visual Studio behavior of create an IIS website pointed at the «bin» folder) results in the same error message, although I get a slightly different aspNetCore node in the generated web.config file:
<aspNetCore processPath="dotnet" arguments=".IisTestApp.dll" stdoutLogEnabled="true" stdoutLogFile=".logsstdout">
<environmentVariables />
</aspNetCore>
What is causing IIS to fail to run this application?
I have tried re-installing .NET Core (SDK, runtime, and hosting component) but it did not help.
I also noticed several posts that mention installing the URL Rewrite module for IIS corrects this error (notably this: HTTP Error 500.19 — IIS 7.5 Error 0x8007000d). My web.config doesn’t mention that module, but I tried installing it in case the AspNetCoreModule uses it under the covers. This did not help in my situation.
User246821057 posted
I am having problems installing Drupal 7.0. However I think it is an IIS problem.
When I execute the install program: http:\mywebDrupal-7.0install.php I get an error 500.19 Internal Server error.
‘The requested page cannot be accessed because the related configuration data for the page is invalid’
The detail of the error are:
Detailed Error information:
Module: IIS Web Core
Notification: Begin Request
Handler: Not yet determined
Error Code: 0x8007000d
Requested URL:
http://localhost/myweb/drupal-7.0/install.php
Physical path: c:inetpubwwwrootmywebdrupal-7.0install.php
Login Method: Not yet determined
Login User: Not yet determined
Config Error
Config File: \?
C:inetpubwwwrootmywebdrupal-7.0web.config
Config Source:
-1:
0:
Drupal has its own web.config file (listed below). If I edit it to introduce a deliberate error (mis-matching tags) the two lines in error and an explanation of the error is shown under the ‘Config source’ heading.
If I comment out everything except the configuration and system.webserver tags I get the same error (Config source -1: 0:).
Editing out more, or deleting this web.config file I get the error 404 Not found.
I am running IIs7 on Windows 7 Ultimate and granted full permission to the inetpub folder according to the post by Thomad on http://forums.iis.net/t/1147354.aspx.
The error message suggests that the error is on lines -1 and 0. I have run the drupal web.config file through an XML verifier/syntax checker and it checks out ok. There is nothing before the <?xml tag, and nothing after the last closing tag.
Can you help please!
Web.config: (in the c:inetpubwwwrootmywebDrupal-7.0 folder)
<?xml version=»1.0″ encoding=»UTF-8″?>
<configuration>
<system.webServer>
<!— Don’t show directory listings for URLs which map to a directory. —>
<directoryBrowse enabled=»false» />
<rewrite>
<rules>
<rule name=»Protect files and directories from prying eyes» stopProcessing=»true»>
<match url=».(engine|inc|info|install|make|module|profile|test|po|sh|.*sql|theme|tpl(.php)?|xtmpl)$|^(..*|Entries.*|Repository|Root|Tag|Template)$» />
<action type=»CustomResponse» statusCode=»403″ subStatusCode=»0″ statusReason=»Forbidden» statusDescription=»Access is forbidden.» />
</rule>
<rule name=»Force simple error message for requests for non-existent favicon.ico» stopProcessing=»true»>
<match url=»favicon.ico» />
<action type=»CustomResponse» statusCode=»404″ subStatusCode=»1″ statusReason=»File Not Found» statusDescription=»The requested file favicon.ico was not found» />
</rule>
<!— Rewrite URLs of the form ‘x’ to the form ‘index.php?q=x’. —>
<rule name=»Short URLs» stopProcessing=»true»>
<match url=»^(.*)$» ignoreCase=»false» />
<conditions>
<add input=»{REQUEST_FILENAME}» matchType=»IsFile» ignoreCase=»false» negate=»true» />
<add input=»{REQUEST_FILENAME}» matchType=»IsDirectory» ignoreCase=»false» negate=»true» />
<add input=»{URL}» pattern=»^/favicon.ico$» ignoreCase=»false» negate=»true» />
</conditions>
<action type=»Rewrite» url=»index.php?q={R:1}» appendQueryString=»true» />
</rule>
</rules>
</rewrite>
<httpErrors>
<remove statusCode=»404″ subStatusCode=»-1″ />
<error statusCode=»404″ prefixLanguageFilePath=»» path=»/index.php» responseMode=»ExecuteURL» />
</httpErrors>
<defaultDocument>
<!— Set the default document —>
<files>
<remove value=»index.php» />
<add value=»index.php» />
</files>
</defaultDocument>
</system.webServer>
</configuration>
I am replicating web application deployment and found several issues related to HTTP Error 500.19. My machine is running Windows 7 while the working development is using Windows 8. We’re developing our Web Application using Visual Studio 2010.
First, I got error code 0x80070021, similar as posted here.
I update my web.config according to the accepted answer and then I got following error code (which is similar as posted here).
HTTP Error 500.19 - Internal Server Error
Error Code 0x8007000d
Config Source -1: 0:
I have read the symptoms definition in Microsoft support page and cause of the error is:
This problem occurs because the ApplicationHost.config file or the Web.config file contains a malformed XML element.
and the solution is
Delete the malformed XML element from the ApplicationHost.config file or from the Web.config file.
However, the web.config that I used is working perfectly in the original development environment.
Here is what I have checked and tried so far:
- Install ASP.NET by calling aspnet_regiis -i
- Set my application to use different application pool (ASP.NET v4.0, .NET v4, etc)
- ApplicationHost.config file is still using default from Windows 7.
This is part of my Web.Config
<system.webServer>
<section name="handlers" overrideModeDefault="Allow" />
<section name="modules" allowDefinition="MachineToApplication" overrideModeDefault="Allow" />
<validation validateIntegratedModeConfiguration="false" />
<modules runAllManagedModulesForAllRequests="true">
</modules>
<handlers>
<remove name="UrlRoutingHandler" />
<add name="ReportViewerWebControlHandler" preCondition="integratedMode" verb="*" path="Reserved.ReportViewerWebControl.axd" type="Microsoft.Reporting.WebForms.HttpHandler, Microsoft.ReportViewer.WebForms, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />
</handlers>
<urlCompression doStaticCompression="true" doDynamicCompression="false"></urlCompression>
<directoryBrowse enabled="true" />
<defaultDocument>
<files>
<add value="Logon.aspx" />
</files>
</defaultDocument>
</system.webServer>
I have read similar/duplicates/closed posts (around 13) posts in stackoverflow, tried all except the answer related to Ajax (is it related) and still have no clue on what the error is.
Does anyone one how to fix this error? (And if possible, a comprehensive lists of things need to be checked so we can reduce similar posts like this.) I am ready to provide more details.
I am replicating web application deployment and found several issues related to HTTP Error 500.19. My machine is running Windows 7 while the working development is using Windows 8. We’re developing our Web Application using Visual Studio 2010.
First, I got error code 0x80070021, similar as posted here.
I update my web.config according to the accepted answer and then I got following error code (which is similar as posted here).
HTTP Error 500.19 - Internal Server Error
Error Code 0x8007000d
Config Source -1: 0:
I have read the symptoms definition in Microsoft support page and cause of the error is:
This problem occurs because the ApplicationHost.config file or the Web.config file contains a malformed XML element.
and the solution is
Delete the malformed XML element from the ApplicationHost.config file or from the Web.config file.
However, the web.config that I used is working perfectly in the original development environment.
Here is what I have checked and tried so far:
- Install ASP.NET by calling aspnet_regiis -i
- Set my application to use different application pool (ASP.NET v4.0, .NET v4, etc)
- ApplicationHost.config file is still using default from Windows 7.
This is part of my Web.Config
<system.webServer>
<section name="handlers" overrideModeDefault="Allow" />
<section name="modules" allowDefinition="MachineToApplication" overrideModeDefault="Allow" />
<validation validateIntegratedModeConfiguration="false" />
<modules runAllManagedModulesForAllRequests="true">
</modules>
<handlers>
<remove name="UrlRoutingHandler" />
<add name="ReportViewerWebControlHandler" preCondition="integratedMode" verb="*" path="Reserved.ReportViewerWebControl.axd" type="Microsoft.Reporting.WebForms.HttpHandler, Microsoft.ReportViewer.WebForms, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />
</handlers>
<urlCompression doStaticCompression="true" doDynamicCompression="false"></urlCompression>
<directoryBrowse enabled="true" />
<defaultDocument>
<files>
<add value="Logon.aspx" />
</files>
</defaultDocument>
</system.webServer>
I have read similar/duplicates/closed posts (around 13) posts in stackoverflow, tried all except the answer related to Ajax (is it related) and still have no clue on what the error is.
Does anyone one how to fix this error? (And if possible, a comprehensive lists of things need to be checked so we can reduce similar posts like this.) I am ready to provide more details.
In general, a 500.19 error happens due to invalid configuration data. The IIS configuration system will almost always point to the source of the problem. At the same time, sometimes it is important to examine the “Error Code” field which symbolizes the cause of problem.
Here’s an example of how a 500.19 error appears on an IIS 7.0 server:
Let’s talk about some of the causes for 500.19 errors. We will use the ERR.exe tool for looking up the associated error codes (MSDN says it’s for Exchange error codes but it works for Win32 error codes and many more.) To use ERR.exe tool and find what an HRESULT error code corresponds to, navigate to the folder where err.exe resides and run command: ERR ErrorCode
Note: Make sure to backup your applicationHost.config file before editing it manually, to avoid any further issuesJ. You can find the detailed instructions here
***************************************
Scenario 1
Error Message:
HTTP Error 500.19 — Internal Server Error
Description: The requested page cannot be accessed because the related configuration data for the page is invalid.
Module: StaticCompressionModule
Notification: MapRequestHandler
Handler: StaticFile
Error Code: 0x800700c1
Requested URL: http://localhost/
Physical Path: C:inetpubwwwroot
Logon Method: Anonymous
Logon User: Anonymous
Reason:
The Error Code in the above error message is “0x800700c1” which when translated through ERR.EXE, is
# %1 is not a valid Win32 application.
Solution:
This error normally indicates an attempt to use EITHER
Ø 32-bit executable from a 64-bit process
OR
Ø A corrupt executable
Hence the solution is to make sure that the listed module’s bitness (32bit/64bit) matches the bitness of the application Pool.
***************************************
Scenario 2
Error Message:
HTTP Error 500.19 — Internal Server Error
Description: The requested page cannot be accessed because the related configuration data for the page is invalid in the metabase on the Web server.
Error Code: 0x800700b7
Notification: BeginRequest
Module: IIS Web Core
Requested URL: http://localhost/
Physical Path: C:inetpubwwwroot
Logon User: Anonymous
Logon Method: Anonymous
Handler: StaticFile
Config Error: Cannot add duplicate collection entry of type ‘add’ with unique key attribute ‘name’ set to ‘header’
Config File: \?C:inetpubwwwrootweb.config
Config Source:
21: <customHeaders>
22: <add name=»header» value=»text/plain» />
23: </customHeaders>
Reason:
This problem essentially happens if there is a duplicate entry for the configuration section setting at a higher level in the configuration (i.e. in parent site/folder’s web.config or applicationHost.config file). The error message itself points out the location of duplicate entries.
Solution:
One should look in the site’s config file and compare it with applicationHost or web.config file at a higher level to check for duplicate entries as pointed by the error message. You can either remove this entry to make the server run again, or make the entry non-duplicate by changing the collection key.
For example, the above error message was because of the same custom header defined at the IIS root level (applicationHost.config) and at the Default Website (web.config). To solve this, we can
1. Remove this entry from web.config file : <add name=»header» value=»text/plain» />
OR
2. Add remove OR clear element before this add element:
<remove name=»header»/>
OR
<clear />
***************************************
Scenario 3
Error Message:
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: 0x8007000d
Config Error: Configuration file is not well-formed XML
Config File: \? C:inetpubwwwroot web.config
Requested URL: http://localhost/
Physical Path: C:inetpubwwwroot
Logon User: Not yet determined
Logon Method: Not yet determined
Config Source
3: <system.webServer>
4: </handlers>
5: <remove name=»StaticFile»/>
Reason:
That error message goes on to say what exactly is bad about your configuration file, hence you should refer the “Config Error” and “Config Source” sections. This problem occurs because the ApplicationHost.config file or the Web.config file contains a malformed or unsupported XML element.
Solution:
Delete the malformed XML element from the ApplicationHost.config file or from the Web.config file as indicated by the error message.
There are couples of instances that we have come across where the error code remains 0x8007000d, but the cause of issue was interesting.
In one scenario, we had a virtual directory pointing to a UNC share content. This same above 500.19 error was caused because of wrong password specified in the “Connect as..” setting. So make sure to provide the right credentials under “Connect as..” .
Another instance where the error code remained “0x8007000d” but the “Config Error” didn’t complain the mal formed XML, rather was about Configuration section encryption.
HTTP Error 500.19 – Internal Server Error
The requested page cannot be accessed because the related configuration data for the page is invalid.
Module : ConfigurationValidationModule
Notification: BeginRequest
Handler : PageHandlerFactory-Integrated
Error Code: 0x8007000d
Config Error: Configuration section encryption is not supported
Config File: \?C:inetpubwwwrootaspnetweb.config
Requested URL: http://localhost/
Physical Path: C:inetpubwwwroot
Logon User: Not yet determined
Logon Method: Not yet determined
<identity configProtectionProvider=»RsaProtectedConfigurationProvider»>
<EncryptedData Type=http://www.w3.org/2001/04/xmlenc#Element
As the error suggests, the error is because IIS7 configuration system only supports per-attribute encryption; it does not support per-section encryption. For more details, refer Section level encryption of ASP.NET settings in IIS 7
***************************************
Scenario 4
Error Message:
HTTP 500.19 — Internal Server Error
Module: IIS Web Core
Notification: BeginRequest
Handler: Not yet determined
Error Code: 0x8007010b
Config Error: Cannot read configuration file
Config File \?C:inetpubwwwrootaspnetweb.config
Logon Method: Not yet determined
Reason:
ERROR CODE: 0x8007010b translates to “ERROR_DIRECTORY — The directory name is invalid.”
Solution:
As the error indicates, IIS is not able to find the content directory. For this error, we can run Process Monitor OR use Failed Request Tracing to get the Directory name where it fails. And then verify if that directory name/path is valid or not. If it does exist, then verify the NTFS permissions on that directory for account that is being used to access it.
We have seen this error when the site content is pointing to some Non-NTFS File system. In such cases, it is advisable to test it by placing the content on a Windows/NTFS share.
***************************************
Scenario 5
Error Message:
HTTP Error 500.19 — Internal Server Error
Description: The requested page cannot be accessed because the related configuration data for the page is invalid.
Error Code: 0x8007052e
Notification: BeginRequest
Module: IIS Web Core
Requested URL: http://localhost/
Logon User: Not yet determined
Logon Method: Not yet determined
Handler: Not yet determined
Config Error: Cannot read configuration file
Config File: \?UNCisha2003wwwrootweb.config
Reason:
The error code in this 500.19 error message is 0x8007052e which indicates:
ERROR_LOGON_FAILURE — Logon failure: unknown user name or bad password.
Solution:
To resolve this error, follow the steps given in the KB 934515
***************************************
Scenario 6
Error Message:
HTTP Error 500.19 — Internal Server Error
The requested page cannot be accessed because the related configuration data for the page is invalid. Module DynamicCompressionModule
Notification SendResponse
Handler StaticFile
Error Code 0x8007007e
Requested URL http://localhost:80/
Physical Path C:inetpubwwwroot
Logon Method Anonymous
Logon User Anonymous
Reason:
Error Code 0x8007007e is:
ERROR_MOD_NOT_FOUND — The specified module could not be found.
This problem occurs because the ApplicationHost.config file or the Web.config file references a module that is invalid or that does not exist. To resolve this problem: In the ApplicationHost.config file or in the Web.config file, locate the module reference or the DLL reference that is invalid, and then fix the reference. To determine which module reference is incorrect, enable Failed Request Tracing, and then reproduce the problem.
For above specific error (mentioned in this example), DynamicCompressionModule module is causing the trouble. This is because of the XPress compression scheme module (suscomp.dll) which gets installed with WSUS. Since Compression schemes are defined globally and try to load in every application Pool, it will result in this error when 64bit version of suscomp.dll attempts to load in an application pool which is running in 32bit mode.
This module entry looks like:
<scheme name=»xpress» doStaticCompression=»false» doDynamicCompression=»true»
dll=»C:Windowssystem32inetsrvsuscomp.dll» staticCompressionLevel=»10″
dynamicCompressionLevel=»0″ />
Hence to get rid of this problem:
Ø Remove/Disable the XPress compression scheme from the configuration using the command below:
%windir%system32inetsrvappcmd.exe set config -section:system.webServer/httpCompression /-[name=’xpress’]
OR
Ø Add an attribute of «precondition= «64bitness» for this module entry so that it loads only in 64bit application pools
Refer this blog for more details on Preconditions in IIS7
OR
Ø Use a 32bit version of suscomp.dll
***************************************
Scenario 7:
Error Message:
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 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:inetpubwwwrootweb.config
Requested URL http://localhost:8081/
Physical Path C:inetpubwwwroot
Logon Method Not yet determined
Logon User Not yet determined
Config Source
144: </modules>
145: <handlers>
146: <remove name=»WebServiceHandlerFactory-Integrated»/>
Reason:
ERROR CODE: 0x80070021 is
ERROR_LOCK_VIOLATION The process cannot access the file because another process has locked a portion of the file.
Solution:
There are usually a few more lines in that error response that points to the exact line in the config file (and hence the locked section) that has the problem. You will either have to unlock that section or not use it in your application’s web.config file.
For e.g., one can lock/unlock handlers/modules sections by either
Ø use appcmd.exe
%windir%system32inetsrvappcmd unlock config -section:system.webServer/handlers
%windir%system32inetsrvappcmd unlock config -section:system.webServer/modules
OR
Ø manually change value from «Deny» to «Allow» for below settings in %windir%system32inetsrvconfig applicationHost.config
<section name=»handlers» overrideModeDefault=»Deny» />
<section name=»modules» allowDefinition=»MachineToApplication» overrideModeDefault=»Deny»/>
You can also configure the locking via IIS manager UI.
For more details refer: Locking in IIS 7.0 Configuration
In above error message, the error occurred on the handlers section at:
<remove name=»WebServiceHandlerFactory-Integrated»/>”
This usually indicates that ASP.NET is either not installed or has corrupted/incomplete installation because installation of asp.net unlocks that section. Hence if this is the case, one should install asp.net feature from Server Manager (Under Web Server Role in Windows Server 2008 and in Program Features-> Application server in Vista/Windows7). This KB929772 talks about the ASP.NET installation failure reason.
***************************************
Scenario 8
Error Message:
HTTP Error 500.19 — Internal Server Error
Description: The requested page cannot be accessed because the related configuration data for the page is invalid.
Error Code: 0x80070005
Notification: BeginRequest
Module: IIS Web Core
Requested URL: http://localhost
Physical Path: C:Inetpubwwwroot
Logon User: Not yet determined
Logon Method: Not yet determined
Handler: Not yet determined
Config Error: Cannot read configuration file
Config File: \? C:Inetpubwwwrootweb.config
Reason:
The error code 0x80070005 is:
E_ACCESSDENIED — General access denied error
The “Config error” portion of the error may indicate this too, via message: “Config Error Cannot read configuration file due to insufficient permissions ”
Solution:
Grant Read permission to the IIS_IUSRS group for the ApplicationHost.config file or for the Web.config file indicated in the error message. Even if there is no config file at that location, the worker process identity (and/or the IIS_IUSRS group) needs at least Read access to the directory so that it can check for a web.config file in that directory. If it’s a UNC share, you need to either run your app-pool as an account that has sufficient permission to the UNC share or configure the virtual directory with a user that has sufficient permission to the share.
If you still see the issue, run the Process Monitor tool, reproduce the error and look for “Access Denied” in the “Result” column. You can then configure the required permissions accordingly.
Other Related Articles:
Troubleshooting HTTP 401.3 errors (Access denied) with Process Monitor
Troubleshooting common permissions and security-related issues in ASP.NET
***************************************
Scenario 9
There’s one intermittent 500.19 error we’ve observed while using Shared Configuration with multiple web servers in a load balanced environment and the configuration files stored on a common UNC file share. In this scenario, if the file share content goes offline, the web server will stop responding. Furthermore, when the file share comes up again, the web server will still not detect it and will fail with a 500.19 error. In order to recover from this situation, you must restart IIS. The solution to this problem is described in this KB
***************************************
Other references:
Error message when you visit a Web site that is hosted on IIS 7.0: «HTTP Error 500.19 – Internal Server Error»
You receive an error message when you try to view a Web page from a Web site that uses pass-through authentication in Internet Information Services 7.0
Troubleshoot IIS7 errors like a pro
I need help for a client and am willing to pay a professional if need be. I just opened an account with a web host and had the developer upload the site and we are getting an error while accessing the site. We are running IIS 7.5 and getting
a 500.19 error code 0x8007000d pointing to the web.config file.
Here is the contents of the web.config file. We are getting an error pointing to line 54 which is the </system.web> which is 6 lines from the bottom of the file.
PLEASE if you have any suggestions or fixes, let me know how to do this. If you would like to contact me my email is mike@tuprox.com. Much thanks in advance!
<?xml version=»1.0″ encoding=»UTF-8″?>
<!—
For more information on how to configure your ASP.NET application, please visit
http://go.microsoft.com/fwlink/?LinkId=169433
—>
<configuration>
<connectionStrings>
<add name=»ApplicationServices»
connectionString=»data source=.SQLEXPRESS;Integrated Security=SSPI;AttachDBFilename=|DataDirectory|aspnetdb.mdf;User Instance=true»
providerName=»System.Data.SqlClient» />
</connectionStrings>
<system.web>
<compilation debug=»true» targetFramework=»4.0″ />
<authentication mode=»Forms»>
<forms loginUrl=»~/Account/Login.aspx» timeout=»2880″ />
</authentication>
<customErrors>
<configuration>
<system.web>
<customErrors mode=»RemoteOnly» defaultRedirect=»mycustompage.htm»/>
</system.web>
</configuration>
<membership>
<providers>
<clear/>
<add name=»AspNetSqlMembershipProvider» type=»System.Web.Security.SqlMembershipProvider» connectionStringName=»ApplicationServices»
enablePasswordRetrieval=»false» enablePasswordReset=»true» requiresQuestionAndAnswer=»false» requiresUniqueEmail=»false»
maxInvalidPasswordAttempts=»5″ minRequiredPasswordLength=»6″ minRequiredNonalphanumericCharacters=»0″ passwordAttemptWindow=»10″
applicationName=»/» />
</providers>
</membership>
<profile>
<providers>
<clear/>
<add name=»AspNetSqlProfileProvider» type=»System.Web.Profile.SqlProfileProvider» connectionStringName=»ApplicationServices» applicationName=»/»/>
</providers>
</profile>
<roleManager enabled=»false»>
<providers>
<clear/>
<add name=»AspNetSqlRoleProvider» type=»System.Web.Security.SqlRoleProvider» connectionStringName=»ApplicationServices» applicationName=»/» />
<add name=»AspNetWindowsTokenRoleProvider» type=»System.Web.Security.WindowsTokenRoleProvider» applicationName=»/» />
</providers>
</roleManager>
</system.web>
<system.webServer>
<modules runAllManagedModulesForAllRequests=»true»/>
</system.webServer>
</configuration>
|
|||
| Prefuse
11.06.15 — 16:41 |
Добрый день! Из 1С база публикуется, но при переходе в браузере на http://localhost/crm/ ругается:
Ошибка HTTP 500.21 — Internal Server Error В чем может быть причина? |
||
| Biker
1 — 11.06.15 — 16:44 |
зачем на 32 разрешение, платформа на сервере какая 32 или 64? |
||
| Prefuse
2 — 11.06.15 — 16:45 |
(1) 32 битная. все файлы 1с в C:Program Files (x86) |
||
| Господин ПЖ
3 — 11.06.15 — 16:49 |
(1) потому что прокладка в 1с 32-битная |
||
| Господин ПЖ
4 — 11.06.15 — 16:50 |
в инструкции слишком много работы «руками»… платформа опубликует все сама — надо ее запустить от админа |
||
| Prefuse
5 — 11.06.15 — 16:55 |
(4) Запускаю от ярлык 1с имени Администратора, публикую. Захожу в браузер, ты же фигня. |
||
| Prefuse
6 — 11.06.15 — 16:58 |
(5) Вот что еще пишет в браузере, может ктото понимает: |
||
| Господин ПЖ
7 — 11.06.15 — 17:00 |
попробуй iis переставить и добавь модулей в него >однако установка ASP.NET не выполнена или выполнена не полностью. |
||
| Господин ПЖ
8 — 11.06.15 — 17:00 |
чего-то не хватает |
||
| Prefuse
9 — 11.06.15 — 21:34 |
(8) Спасибо! переустановили, заработало. |
||
| Prefuse
10 — 11.06.15 — 21:40 |
(9) С половиной проблемы разобрался: |
||
| Prefuse
11 — 11.06.15 — 21:43 |
(10) Осталось понять почему внешнему ip не заходит, 404 ошибка |
||
| floody
12 — 11.06.15 — 22:00 |
Апач не предлагать? Всё не читал. |
||
|
Prefuse 13 — 11.06.15 — 22:07 |
(12) с Апача все начиналось, не удалось его поднять, служба ни в какую не хотела стартовать. решили стандартными средствами пойти( |
ВНИМАНИЕ! Если вы потеряли окно ввода сообщения, нажмите Ctrl-F5 или Ctrl-R или кнопку «Обновить» в браузере.
Тема не обновлялась длительное время, и была помечена как архивная. Добавление сообщений невозможно.
Но вы можете создать новую ветку и вам обязательно ответят!
Каждый час на Волшебном форуме бывает более 2000 человек.