Post here for help with installing or upgrading mojoPortal pre-compiled release packages. When posting in this forum, please provide all relevant details. You may also want to review the installation or upgrading documentation.
If you have questions about using the source code or working with mojoPortal in Visual Studio, please post in the Developer forum.
When posting in this forum, please try to provide as many relevant details as possible. Particularly the following:
You may also want to review the installation or upgrading documentation.
These kinds of web.config conflicts can occur when you have more than one .NET app and one is running in the root and one is running in a folder beneath the root.
http://www.mojoportal.com/developer-faq.aspx
You can learn how to mitigate these issues by reading the links in the FAQ.
Hope it helps,
Joe
Hi Joe,
Thanks for that. I have read the FAQ and I also don't have 2 .NET applications running. At least there is only one website running under IIS.
I have also seen your post about getting around it with a location tag, but I can't see an example in the thread and I can't find one by Googling - possibly because I don't know what words to Google to get what I need.
Could you please point me in the right direction (e.g. Google link).
Cheers,
Shao
Okay, I have added the location tag now.
I only have one application and it is the root application.
I am still getting the error message.
What else could it be?
Thanks.
Okay, I think I've got it working.
In IIS 7.5 I didn't enable ASP.NET.
Once I enabled ASP.NET it corrupted the .NET framework, so you have to apply this:
http://www.gotknowhow.com/articles/fix-bad-module-managedpipelinehandler-in-iis7
%windir%\Microsoft.NET\Framework\v4.0.30319\SetupCache\Client\setup.exe /repair /x86 /x64 /ia64 /parameterfolder Client /q /norestart
Once you've done that, it may create new Application Pools and will disable your own Application Pools, so you need to enable them.
After that it works.