This is good that you know that this is a general error. I appreciate this understanding. But if you understand this, you should understand that in this case you can get only the general answer. Something like this:
The IIS7 HTTP server could encounter an error caused by your MVC3 application. You need to fix an internal error in your application.
I understand, it's not very informative, but this is all one can possibly see from the information you provided.
So, the major problem here is that you need to retrieve relevant information on the problem. So, very general advice:
Catch all exceptions in the top of the stack of every thread and output comprehensive exception information, including
Exception.Stack and all
Exception.InnnerException, recursively. Of course, you should make sure that you do not block exception propagation in between; this is a big mistake many beginners do; the best exception handling, as a rule of thumb, is not catching any exceptions except on top of the stack; another place is the main event loop of the UI.
Please see my past answers on exception handling for more ideas:
How do i make a loop that will stop when a scrollbar reaches the bottom[
^],
When i run an application an exception is caught how to handle this?[
^],
throw . .then ... rethrowing[
^],
Error Logging and Screen Shot.[
^],
Catching an Exception[
^],
Handling exceptions in class library (dll)[
^].
Add logging to check up if the code passes all points of your application logic. Please see this past answer:
User Log should be Maintained in Web Application[
^].
—SA
Submit an article or tip