Continual problem with "HTTP/1.1 500 Internal Server Error"
Hi experts,
I've just about had it with ASP.NET! Lately, I've been experiencing problems with
trying to create or even open existing projects in VS.NET 2003! I began experiencing
trouble first about 3 weeks ago. I did find a solution that worked to solve the problem,
at least for the duration I was using the machine. On the next bootup or the second
bootup after implementing the fix, I'd be straight back to this error again!
Does anyone have a permanent cure out there that will fix the situation? I did
read something about needing to setup an application pool, but I am using
IIS 5 which I do not believe has support for this (only an IIS 6 thing?).
The messagebox with the error says the following when trying to create a new
web application:
"The web server reported the following error when attempting to create or open the
web project located at the following URL: 'http://localhost/WebApplication1'.
HTTP/1.1 500 Internal Server Error'".
The fix I tried that worked includes the following:
- Un-Install IIS
- Delete or rename the existing inetpub folder
- Make sure the Distributed Transaction Coordinator (DTC) service is running.
- Re-Install IIS
From \%installroot%\v1.1.4322 (where installroot = .net framework installation folder):
- regsvr32 aspnet_isapi.dll
- aspnet_regiis.exe -i
I've since found another work-around which does not require re-installation
of IIS but again, the effect is only temporarily (until the next couple of boot-ups).
- Delete ASPNET account
- Recreate ASPNET account by doing ASPNET_REGIIS -i
- Restart IIS using IISRESET command.
Why does the act of deleting the ASPNET account temporarily fix the issue? Is
there a PERMANENT workaround to this problem?
Any illumination on this most persistent error would be GREATLY appreciated!!!
TIA,
~Shar
I've just about had it with ASP.NET! Lately, I've been experiencing problems with
trying to create or even open existing projects in VS.NET 2003! I began experiencing
trouble first about 3 weeks ago. I did find a solution that worked to solve the problem,
at least for the duration I was using the machine. On the next bootup or the second
bootup after implementing the fix, I'd be straight back to this error again!
Does anyone have a permanent cure out there that will fix the situation? I did
read something about needing to setup an application pool, but I am using
IIS 5 which I do not believe has support for this (only an IIS 6 thing?).
The messagebox with the error says the following when trying to create a new
web application:
"The web server reported the following error when attempting to create or open the
web project located at the following URL: 'http://localhost/WebApplication1'.
HTTP/1.1 500 Internal Server Error'".
The fix I tried that worked includes the following:
- Un-Install IIS
- Delete or rename the existing inetpub folder
- Make sure the Distributed Transaction Coordinator (DTC) service is running.
- Re-Install IIS
From \%installroot%\v1.1.4322 (where installroot = .net framework installation folder):
- regsvr32 aspnet_isapi.dll
- aspnet_regiis.exe -i
I've since found another work-around which does not require re-installation
of IIS but again, the effect is only temporarily (until the next couple of boot-ups).
- Delete ASPNET account
- Recreate ASPNET account by doing ASPNET_REGIIS -i
- Restart IIS using IISRESET command.
Why does the act of deleting the ASPNET account temporarily fix the issue? Is
there a PERMANENT workaround to this problem?
Any illumination on this most persistent error would be GREATLY appreciated!!!
TIA,
~Shar
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
did u install SP for .Net
ASKER
Hi there. The framework installation reports that SP1 is installed,
version: v1.1.4322. The development environment does not report
as having a service pack and is at v7.1.3088.
I searched the link you gave me and so far, I've been unable to
find anything meaningful one way or the other as to a permanent
fix. I'm still looking through it though as I've had the time to
try and find a solution.
version: v1.1.4322. The development environment does not report
as having a service pack and is at v7.1.3088.
I searched the link you gave me and so far, I've been unable to
find anything meaningful one way or the other as to a permanent
fix. I'm still looking through it though as I've had the time to
try and find a solution.
ASKER
I haven't been able to find a permanent fix to this solution and do not know if there is one.
Although my question was not answered, I will give the points with a grade of B
since I had to do quite a bit of digging for a work-around (but not permanent) solution.
Thanks for trying.
Although my question was not answered, I will give the points with a grade of B
since I had to do quite a bit of digging for a work-around (but not permanent) solution.
Thanks for trying.
Uninstalling Exchange Update 926666 http://support.microsoft.com/kb/926666/ solved the problem for us.
I just had this problem and this above sorted it. just for those who might get stuck with the same.
I just had this problem and this above sorted it. just for those who might get stuck with the same.