I just tried installing the https redirect module on an installation of 6.16 and ran into a bit of a problem. After the install, I selected the option to add https redirect to the dashboard. Then, my whole site (front end and back office) crashed with a 500.22 error. I switched my application pool from integrated to "classic" mode which brought everything back. However, after I uninstalled, I still cannot switch back to integrated mode. If I switch it, I still get the 500.22 error, so I suspect there may be something added to a config file somewhere that isn't compatible with integrated mode, that was not removed during the uninstall. Any ideas where I should look?
That's really odd - I know that there is a key added in the web.config file - But can't remember if anything else is added though. Does it help to remove the key?
That article is what I referred to when I changed to classic pipeline mode. Based on the article, it appears to be an issue with the config file. However, other than installing and uninstalling this module, I have not modified any config files in any other way.
config file issue with 6.16
I just tried installing the https redirect module on an installation of 6.16 and ran into a bit of a problem. After the install, I selected the option to add https redirect to the dashboard. Then, my whole site (front end and back office) crashed with a 500.22 error. I switched my application pool from integrated to "classic" mode which brought everything back. However, after I uninstalled, I still cannot switch back to integrated mode. If I switch it, I still get the 500.22 error, so I suspect there may be something added to a config file somewhere that isn't compatible with integrated mode, that was not removed during the uninstall. Any ideas where I should look?
Hi Steve
That's really odd - I know that there is a key added in the web.config file - But can't remember if anything else is added though. Does it help to remove the key?
/Jan
In web.config? do you happen to know what the key is called? I will try removing it if I can identify which key it is
Yes, there should be an
Hope this helps.
/Jan
the only key I saw that I thought might be related was this one: <add key="umbracoUseSSL" value="false" />
I tried removing it and still had the same issue.
Hi Steve
Hmm ok, that key should not be removed since it's an Umbraco key.
The key I'm thinking about has probably been removed by the uninstall then.
Don't know if you could try doing some of the suggested here http://stackoverflow.com/questions/7370513/http-error-500-22-internal-server-error-an-asp-net-setting-has-been-detected ?
/Jan
ok, I had already put that umbraco key back in.
That article is what I referred to when I changed to classic pipeline mode. Based on the article, it appears to be an issue with the config file. However, other than installing and uninstalling this module, I have not modified any config files in any other way.
I followed the link in there to this page - http://www.iis.net/learn/application-frameworks/building-and-running-aspnet-applications/aspnet-20-breaking-changes-on-iis - and ended up running "appcmd migrate config", and I was able to put the app pool back into integrated mode. No idea what happened to the config file. Oh well!
is working on a reply...