views:

258

answers:

4

I've recently moved from [Windows 2003-32 bit, IIS 6 .NET 2.0] to [Windows 2008-64 bit, IIS 7 .NET 2.0].

Everything seems to be working fine except from the HTTP 500 error I am getting periodically and I also get timeouts in my database MSSQL 2005-randomly and on any on random stored procedures (DB is optimized and working fine-all stored procedures are working '0s' on the sql).

Any ideas how to resolve this error HTTP 500 error?

A: 

Work out what the error is for starters.

HTTP 500 is a status code for a server error. You will need to find out the details first.

Start with disabling 'View Friendly HTTP Errors' in Internet Explorer.

Wim Hollebrandse
+2  A: 

You need to find out more details from the server log: which 500 error are you getting? And take a look at the event viewer.

By default IIS7 runs in the new "Integrated Pipeline" mode, in which your ASP.NET application is running as part of IIS itself rather than through an external ISAPI plug-in. You may find that switching to "classic mode" gives you better stability while you find where the problem really lies.

(It may well be that you have some unmanaged resource, like a database connection, that isn't properly disposed. Check too the memory usage of the application to make sure your sessions aren't leaking.)

Jeremy McGee
How can I check this "Check too the memory usage of the application to make sure your sessions aren't leaking."? I have a load balancer and I am using ASP.NET STATE SERVER maybe it's something there...hmmm I am getting a lot of TIMEOUTS in DB connections as well. Although my SPs I running fine on the SQL when called via my web site I get randomly timeouts on any of my SPs-not on a specific one.
Argyris
A: 

First of all get error info. Error 500 is a common error for any unhandled error.

There are some common causes and concerning migration I'd try switching application pool to classical mode. If this helps, you need to migrate your web.config to support IIS7 pipeline (some info here).

terR0Q
Thanks for the info I already did this. Maybe is something with the DLLs that I am using in general on my site. Some of them I guess they are ready to run on 64 bit machine.
Argyris
You are correct...it's a common error. After playing around with IIS settings I managed to solve the prob.
Argyris
It was application-specific or configuration issue?
terR0Q
A: 

Turn on exception details, else IIS will always serve you a stupid HTTP 500 with no details on your crash.

Turn it off once you have fixed the issue.

leppie