I found the problem. One of the system admins had cloned the original production site intending for it to be used for the production beta, which was what I was setting up. Of course there was no communication as to what was needed to be kept in the copied site. Well it turns out there was a web.config in the original code that was doing a redirect to another location. Thus none of the new site configs were even being accessed. I removed all of the old code and it started working.
Local IIS 7 Returns 500 Error. Can't get details
-
22-07-2023 - |
Vra
I have tried all of the solution out there and have resolved nothing. It's a MVC 4 site on IIS 7 that I'm tryuing to get set up. Local browsing of the site won't display detail error information. Does anyone have any other suggestions?
So far I have done...
- Checked MachineConfig for for .net 4 both 32 and 64 bit. It was not there so it shouldn't interfere.
- Set customErrors mode="Off" in all config files.
- Changed settings for DefaultErrorPages in the Site Settings to always display details.
- Conducted an IISReset
- Enabled failed request logging. Nothing was logged.
- Checked the site error logs.=. Nothing indicated an error.
- Checked Windows Logs. No errors logged under the IIS section.
- Checked that the App Pool was running under .Net 4 and that it was set to integrated mode.
- Turned off friendly errors in the setting for the browser
PS this is a production web server running Windows 2008R2 and IIS 7.0
Oplossing
Gelisensieer onder: CC-BY-SA met toeskrywing
Nie verbonde aan StackOverflow