Umbraco 7 with child web-api application, unable to access CMS
Morning all, With umbraco 6. I've been able to add child applications under an Umbraoc install. The inheritance of the parent web config details has been prevented by wrapping <system.web>, <system.webserver> and <system.web.webPages.razor> with the <location path="." inheritInChildApplications="false" > element.
I've applied the same principles to an Umbraco 7.2.1 install framework 4.5 (IIS 7). Wrapping the <system.web>, <system.webserver> with the <location> element. The child application is a web-api project framework 4.5.
The Umbraco site works, the child application works. When I access the CMS, I get the folowing error:
HTTP Error 500.22 - Internal Server Error
An ASP.NET setting has been detected that does not apply in Integrated managed pipeline mode.
It mentions several steps to try. The http modules section is in <system.web> and <system.webserver>. The validation validateIntegratedModeConfiguration attribute is set to false.
Has anybody come across this before? Is this the correct way to allow a child application to exist under an Umbraco application?
I've fixed this issue. The solution is to comment out the content of <httpModules> section in <system.web>. The same modules are mapped in the <system.webserver> section.
I just wanted to get on the record here and say that I've spent a ton of time on this.
Instead of removing the <httpModules> section, move the <validation> tag out of the <location> and in to the more-global space (probably <configuration>).
Thanks for your answer. It worked perfect. I just upgraded 7.1.4 to 7.2.4 and my applications running in folders worked, along with the site, but the umbraco backend gave the above error. If i had enough karma i would have up-voted your solution instead of making this reply.
If the answer David provided fixed the issue you had you can mark his post as the solution so others who come across this can jump straight to the solution and benefit as well. The solution checkmark is somewhere around the avatar - This does not require a certain amount of karma :)
I was not the original poster, and i assume that is why i don't have anything to click on to mark that reply as the answer. Or, as my wife always tells me, i'm just not looking hard enough...
Hi @David, Sub application working fine after added the webconfig changes but, now Main application ajax functionality is not working, its showing
500 - Internal server error.
There is a problem with the resource you are looking for, and it cannot be displayed.
Umbraco 7 with child web-api application, unable to access CMS
Morning all,
With umbraco 6. I've been able to add child applications under an Umbraoc install. The inheritance of the parent web config details has been prevented by wrapping <system.web>, <system.webserver> and <system.web.webPages.razor> with the <location path="." inheritInChildApplications="false" > element.
I've applied the same principles to an Umbraco 7.2.1 install framework 4.5 (IIS 7). Wrapping the <system.web>, <system.webserver> with the <location> element. The child application is a web-api project framework 4.5.
The Umbraco site works, the child application works. When I access the CMS, I get the folowing error:
HTTP Error 500.22 - Internal Server Error
An ASP.NET setting has been detected that does not apply in Integrated managed pipeline mode.
It mentions several steps to try. The http modules section is in <system.web> and <system.webserver>. The validation validateIntegratedModeConfiguration attribute is set to false.
Has anybody come across this before? Is this the correct way to allow a child application to exist under an Umbraco application?
Thanks in advance
I've fixed this issue. The solution is to comment out the content of <httpModules> section in <system.web>. The same modules are mapped in the <system.webserver> section.
Hi,
I just wanted to get on the record here and say that I've spent a ton of time on this.
Instead of removing the <httpModules> section, move the <validation> tag out of the <location> and in to the more-global space (probably <configuration>).
Worked perfectly for our current project. Thanks David.
David,
Thanks for your answer. It worked perfect. I just upgraded 7.1.4 to 7.2.4 and my applications running in folders worked, along with the site, but the umbraco backend gave the above error. If i had enough karma i would have up-voted your solution instead of making this reply.
Well done, and thanks.
Hi Cole
If the answer David provided fixed the issue you had you can mark his post as the solution so others who come across this can jump straight to the solution and benefit as well. The solution checkmark is somewhere around the avatar - This does not require a certain amount of karma :)
/Jan
Hi Jan
I was not the original poster, and i assume that is why i don't have anything to click on to mark that reply as the answer. Or, as my wife always tells me, i'm just not looking hard enough...
Cole
Hi Cole
Aaah, sorry! You're absolutely right about that - Silly me :)
Well I High fived David for his answer at least - Hopefully the karma limit will be removed once these forums are relaunched.
/Jan
Hi @David, Sub application working fine after added the webconfig changes but, now Main application ajax functionality is not working, its showing 500 - Internal server error. There is a problem with the resource you are looking for, and it cannot be displayed.
https://example.com/umbraco/Surface/Home/CheckUserAvailability?userName=RobertNelson&[email protected]
Good day,
I am also experiencing the same issue but on my side it does not give a any error massage, It just returns a blank browser page,
When I go check my last Log in to Umbraco it shows the field that I have Logged in but the issue it does not show anything on the browser
Please kindly assist,
Kind regards
is working on a reply...