I have a ASP.Net Core 2.2 application that I'm working on. I added a Razor page and everything was working fine.
SO, I made a change to one of the Razor pages (which I've since undone with no change) and tried to set up Visual Studio 2019 to start on that page (project properties / Debug / Relative URL). That did not go to the relative page, so I deleted it.
Now, when I attempt to navigate to that page (using the default IIS Express setting in VS2019 debug), I get the ANCM In-Process error.
Any idea what I did and how I can get back to debugging?
All the "other" pages on the site are working. Just the one I attempted to set as startup page in properties.
Got frustrated and renamed my cshtml and cs pages and it works! I've set something in the config or somewhere that causes an error when that exact file name is used.
It is hard to know your problem since it is a general error you get.What is the log in
Windows Event Log (Application)?
Have you tried to delete the applicationhost.config (in {APPLICATION ROOT}\.vs\config\applicationHost.config) and rebuild app?
Do you have problem when run application using `dotnet run` ( or selecting ProjectName from the drop down options available near the green 'run' button) instead of IIS Express?
MSDN Community Support
Please remember to click "Mark as Answer" the responses that resolved your issue.
If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.
One one in-process application is allowed per IIS application pool. Please assign the appliction '/LM/W3SVC/2/ROOT/TestFile' to a different IIS application pool.
The weird thing is: all I have to do is change the file name to 'TestFile1' and it works without error... ???!?
Hmmm. If I run the project by selecting the project name instead of IIS Express, it runs without error.
Also interesting, the applicationhost.config file had some entries that made no sense...:
SO, I deleted all those lines from the config file and my project is working again in IIS Express !!!!
All because I wanted to start debugging on a certain page and it's not clear how to set that up in a ASP.Net Core project debugging on IIS Express. Still don't know how to do that...
Anyway, thank you Xing Zou for pointing me to the solution.
Member
65 Points
892 Posts
HTTP Error 500.0 - ANCM In-Process Handler Load Failure. Only on one page
Jul 02, 2019 06:36 PM|ojm37|LINK
I have a ASP.Net Core 2.2 application that I'm working on. I added a Razor page and everything was working fine.
SO, I made a change to one of the Razor pages (which I've since undone with no change) and tried to set up Visual Studio 2019 to start on that page (project properties / Debug / Relative URL). That did not go to the relative page, so I deleted it.
Now, when I attempt to navigate to that page (using the default IIS Express setting in VS2019 debug), I get the ANCM In-Process error.
Any idea what I did and how I can get back to debugging?
All the "other" pages on the site are working. Just the one I attempted to set as startup page in properties.
TIA,
Owen
Member
65 Points
892 Posts
Re: HTTP Error 500.0 - ANCM In-Process Handler Load Failure. Only on one page
Jul 02, 2019 06:55 PM|ojm37|LINK
More information:
Got frustrated and renamed my cshtml and cs pages and it works! I've set something in the config or somewhere that causes an error when that exact file name is used.
Thoughts?
TIA,
Contributor
2220 Points
732 Posts
Re: HTTP Error 500.0 - ANCM In-Process Handler Load Failure. Only on one page
Jul 03, 2019 02:20 AM|Xing Zou|LINK
Hi ojm37,
It is hard to know your problem since it is a general error you get.What is the log in Windows Event Log (Application)?
Have you tried to delete the applicationhost.config (in {APPLICATION ROOT}\.vs\config\applicationHost.config) and rebuild app?
Do you have problem when run application using `dotnet run` ( or selecting ProjectName from the drop down options available near the green 'run' button) instead of IIS Express?
Refer to https://github.com/aspnet/AspNetCore/issues/8134
Best Regards,
Xing
Please remember to click "Mark as Answer" the responses that resolved your issue.
If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.
Member
65 Points
892 Posts
Re: HTTP Error 500.0 - ANCM In-Process Handler Load Failure. Only on one page
Jul 03, 2019 03:03 PM|ojm37|LINK
Thank you for your kind reply.
The application event log Says:
IIS Express AspNetCore Module V2 Error:
Failed to start application '/LM/W3SVC/2/ROOT/TestFile', ErrorCode '0x80004005'
AND
One one in-process application is allowed per IIS application pool. Please assign the appliction '/LM/W3SVC/2/ROOT/TestFile' to a different IIS application pool.
The weird thing is: all I have to do is change the file name to 'TestFile1' and it works without error... ???!?
Hmmm. If I run the project by selecting the project name instead of IIS Express, it runs without error.
Also interesting, the applicationhost.config file had some entries that made no sense...:
<application path="/TestFile" applicationPool="TestFile AppPool">
<virtualDirectory path="/" physicalPath="C:\Users\username\source\repos\RMP" />
</application>
AND
<location path="RMP/TestFile" inheritInChildApplications="false">
<system.webServer>
<handlers>
<add name="aspNetCore" path="*" verb="*" modules="AspNetCoreModuleV2" resourceType="Unspecified" />
</handlers>
<aspNetCore processPath="%LAUNCHER_PATH%" arguments="%LAUNCHER_ARGS%" stdoutLogEnabled="false" hostingModel="InProcess" startupTimeLimit="3600" requestTimeout="23:00:00" />
<httpCompression>
<dynamicTypes>
<add mimeType="text/event-stream" enabled="false" />
</dynamicTypes>
</httpCompression>
</system.webServer>
</location>
AND
<add name="TestFile AppPool" autoStart="true" />
SO, I deleted all those lines from the config file and my project is working again in IIS Express !!!!
All because I wanted to start debugging on a certain page and it's not clear how to set that up in a ASP.Net Core project debugging on IIS Express. Still don't know how to do that...
Anyway, thank you Xing Zou for pointing me to the solution.