R
Rod
I have been working with ASP.NET 1.1 for quite a while now. For some
reason, opening some ASP.NET applications we wrote is producing the
following error message:
"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'."
I am working on a Windows XP Professional machine. I had opened and edited
the same ASP.NET application no more than 2 weeks ago; now I cannot open it
at all without getting this error message.
I have tried looking at MSDN and the one article I found that which
described this situation is article 822319, but that is for Windows 2003
Server, which I am not using.
I have also tried running aspnet_regiis for .NET 1.1, but that didn't help.
I have to suspect that this is a result of one of Microsoft's recent
critical updates, as nothing else has gone onto my machine since working on
the ASP.NET applications a couple of weeks ago. Also, other developers who
work for me are experiencing the same problem (we all have Windows XP Pro
installed, with SP 1 for XP applied).
Any suggestions/recommendations please?
Rod
reason, opening some ASP.NET applications we wrote is producing the
following error message:
"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'."
I am working on a Windows XP Professional machine. I had opened and edited
the same ASP.NET application no more than 2 weeks ago; now I cannot open it
at all without getting this error message.
I have tried looking at MSDN and the one article I found that which
described this situation is article 822319, but that is for Windows 2003
Server, which I am not using.
I have also tried running aspnet_regiis for .NET 1.1, but that didn't help.
I have to suspect that this is a result of one of Microsoft's recent
critical updates, as nothing else has gone onto my machine since working on
the ASP.NET applications a couple of weeks ago. Also, other developers who
work for me are experiencing the same problem (we all have Windows XP Pro
installed, with SP 1 for XP applied).
Any suggestions/recommendations please?
Rod