Home/ Questions/Q 7074095
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-28T06:00:35+00:00

I am bin deploying a MVC 3 site… it works fine on our ‘Staging’

  • 0

I am bin deploying a MVC 3 site… it works fine on our ‘Staging’ server, which “theoretically” mirrors our “QA” server. However, when deployed to QA, it just gives a 500 error when trying to access it from the web browser. We’ve turned detailed errors on in the web.config, turning off friendly http errors in IE, but nothing.

Any suggestions on what we might check for? I’ve already verified that .NET 4 Client & .NET 4 Extended are installed on the server. I need to compile a checklist of possibilities. Scratching my head hard on this one…

UPDATE:

I noticed one oddity here, running the powershell command:

test-path "$<Env:ProgramFiles(x86)>\Microsoft ASP.NET"

returns false. As I said before, .NET 4 (Client & Extended) are installed, but nothing else. I find this a little suspect…

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Log into the server’s desktop and open the web-site from the browser there. You should then see the actual exception details.

    • 0