Unfortunately, Microsoft only tells you how fun and easy their development products are, and only after the fact do you find out about all these permissions gliches. Why can't they tell you what to do under the "Visual Studio installation prerequisites"?

That said, I combed through all these comments and tried most of them at least once, but without results. On a late-night whim, I know not why (does anyone believe in inspiration when you're on the verge of a nervous breakdown?), I logged off and logged in as administrator; created a project and ran it without problems; then logged back in under my normal account and added a password (I used no password previously); and wonder of wonders, I was able to run the project forever after without problems. I don't know if it was the act of creating it under the administrator account or changing the regular account password. Hope this helps someone.

I have a friend who is an ex-Microsoft research employee (turned university professor) who says that Vista is supposed to address a lot of these issues of development security and permissions. Thanks a lot; it's about time. Just seems so weird that you don't have control over these things on your own machine.

I got this error message when I changed the ASP.NET version from 1.4 to 2.0 in IIS Admin console. This happened since my app developed using ver 1.4. I switched back to 1.4 but I was still getting same error message. When I started my app without debugging, I noticed that the app was getting directives from the web.config file in inetpub\wwwroot. Aparently when I changed from ASP.NET 1.4 to 2.0 it put this file there and directed the IIS server to use ASP.NET 2.0. But it did not delete this file when I changed back to ASP.NET 1.4. When I deleted this file  everything started working (for safety backup this file to some other directory).

Note: I am using VS 2003 and Windows 2000 (IIS 5.0)

Thanks Adnan Khan.... That script was very very useful....

After you go through all of this and bang your head against the wall numerous times, go to the IIS manager and make sure that the default web site is running under .NET 1.4, not 2.0.  Using VS2003 and VS2005 on the same machine is a pain and I would not recommend it.  Unfortunately, I was at a client site and given a machine to work on that was hacked up with VS2005 and VS2003.  Gotta love it...

Correction...  I meant to say 1.1, not 1.4...

I did Adnan Khan' post Ronan Dom' (Distributed Transaction Coordinator) post, Daria' post then Mark' (caspol -s off) post and it worked. Thank you guys! In summary ...

Open and CMD window, go to C:\WINNT\Microsoft.NET\Framework\v1.1*

then do

iisreset /stop

net user ASPNET /delete

aspnet_regiis –I

regsvr32 aspnet_isapi.dll

iisreset /start

Then do iis reset from “Computer Management” in Administrative tools.

Then back to your CMD window and do ...

caspol -s off

Microsoft can you please document your stuff and save us all the many hours spent on this :-)

I solve this problem by following line

first click start menu ,click run and write cmd and open it

then go to the

c://windows/microsoft.net/framework/v1.1.4332

choose above path and then first type (at that path)

iisreset/stop (after then)

net user ASPNET/delete (then)

aspnet_regiis -i and then

iisreset /start

by this i slove my problem of HTTP://1.1 500 Internal Server Error

Thanks Guy hope u also solve your prob by this. bye and keep in touch

Hi.

This post is great and saved me a lot of time.

The replay that solved my problem was that of "Adnan Khan".

search it on this page (from the top).

Thanks.

You have to create the ASP.net machine account. and the again use aspnet_regiis -i and it will work .

Thankyou for leaving your comments. I tried everything else, deleting ASPNET user and recreating via ADNAN's script, reinstalling .NET etc and nothing worked.

The only solution that worked was the one below

1) uninstalled IIS

2) deleted (renamed) the inetpub directory <--important

3) reinstalled IIS

4) performed aspnet_regiis -i

----------<Quoted Directly from above>

the renaming of the inetpub directory was crucial.

Good luck, to anyone else with this problem

Hey! That fixed my problems! Thanks!

<<

Ronan Dom said:

I have been stuggeling with this problem for days as well and finally got it working:

1) Make sure the "Distributed Transaction Coordinator" service is running (!)

2) reinstall ISS

3) run "aspnet_regiis.exe -i"

4) run "regsvr32 aspnet_isapi.dll"

>>

This one fixed it for me!  Thanks!

It may not matter at all, but I ran the cmd line stuff from the Visual Studio cmd prompt, rather than the std cmd prompt.

Though since it's pretty typical of Microsoft to have about 80 billion ways of generating the exact same error msg, I've made note of the other solutions for future reference.  :-)

Some times we get this error when we create a new web application or open an existing application in

I renamed INETPUB wwwroot directory and also uninstalled .net framework 2.0, this worked after trying most of the other postings here.

To Ronan Dom: you are a god among techies. Thanks to your now three-year old comment, I can finally START my homework for my online class.

I've been searching Google for two days (about 6 hours of so between them), getting my error to change all the time but never go away. Then yours actually works. Hats off to ya!

I was wondering if you could help me with a little problem recently i installed VS 2005 from VS 2003, i get this error all the time, i have upgraded to asp.net 2.0... I dont get this problem with .net 1.4 with VS2005. Im not sure if i have to built the project again. any ideas on how to avoid this?

When i try and create a web app i cant..

Please forgive me when this appears a little rude, but I just have to get this of my chest. I do answer

I have solved the problem with the solution from ADNAN, but came across something new now I get this error I have installed VS2005. And migrated my VS2003 application to VS2005. After resolving all the errors I get the following error when press F5 fordebugging. "unabletostartdebugger on thewebserver. the microsoft visual studio remotedebuggingmonitor ( MSVSMON.EXE)does not appear to be running on the remote computer . Please see help for assistance."

http://www.teknikdesign.co.uk/VS05/vs05error2.JPG

Please advice the workaround

This is my third post with this title. What started as quick command line fix has grown into something

November last year I posted a story with this title . It was a fix for the error messgae above. I wasn&#39;t

I had Http1.1/500 problem for couple days, the following solution fixed the problem, i guess the step # 4 is the critical.

Wondering why microsoft do not have a KB on this issue.

1) Make sure the "Distributed Transaction Coordinator" service is running (!)

2) reinstall ISS

3) run "aspnet_regiis.exe -i"

4) run "regsvr32 aspnet_isapi.dll"

thanks for the help!!

--Venkat

I couldn't create a new web service project or a web application on my local machine. XP, IIS 5.1.

My first error message was:

"Visual Studio .NET has detected that the specified Web server is not running ASP.NET version 1.1. You will be unable to run ASP.NET Web applications or services"

I fixed this with :

c:\windows\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis.exe" -i

"The Web server reported the following error when attempting to create or open the Web project located at the following url ... Internal server error"

I tried to remove the aspnet user. Didn't work at all. Tried to set the ip-adress (instead of All Unassigned), didn't work.

The solution for me was to add my own username(with domain that is domain/username) and password in machine.config process model tag. It starts working

Hope this help you.

Thanks for all help!

After a day of uninstalling and installing iis and aspnet, with no results. I tried with ChesterC solution and it works!!!!!

Thanks

ChesterC said:

Well I have resolution at last.

For myself, what worked was:

1. Uninstall .NET framework AND manually delete the directory and everything inside.

2. Uninstall ISS and manually delete the 'Inetpub' directory or it's eqiuvalent.

3. Reinstall ISS with default options.

4. Install VS.NET prerequisites from the VS.NET installation.

At this point I was able to create asp.net web applications locally using my localhost directory.

Thankkssss!!! Solved my problem!!!

This is a great summary.  What worked for me was merely changing the username in the machine.cfg file to "system" per the wonderful Mr_Digital.  I'd love to know what happened to suddenly cause the problem ( I went to an earlier restore point), or how this fix works... but I WILL enjoy that drink now!!

Very very thanks to Ronan Dom. I solved my problem by executing;

echo "Stop IIS"

iisreset /stop

echo "----------------------"

echo "Deleting the ASPNET account."

net user ASPNET /delete

echo "----------------------"

echo "Reregistering ASP.NET and the ASPNET account."

aspnet_regiis -i

echo "----------------------"

echo "Registering ASPNET_ISAPI.DLL"

regsvr32 aspnet_isapi.dll

echo "----------------------"

echo "Restarting IIS."

iisreset /start

echo "----------------------"

codes. Now working fully.

I got a similar error. I would like everyone to check something before trying any of the above fixes. I noticed that the ASP.NET state service was stopped and was marked as Manual. I restarted the service, marked it automatic, restarted IIS and I was good to go.

I had the http://1.1 403 forbidden.  I went into IIS, right clicked the website, clicked Create next to the Application name in the Directory tab.  This resolved the issue.  This was with Visual Studio 2003 running on Windows 2003.

I was getting an error message like this:

"The Web server reported the following error when attempting to create or open the Web project located at the following URL: 'localhost/WebApplication1'. 'HTTP/1.0 400 Bad Request'. "

I found out the reason after spending the whole day on it..

- In the LAN settings, disable the proxy !!

Hope this post helps someone!!

Echo Stop IIS

iisreset /stop

echo "----------------------"

echo "Deleting the ASPNET account."

net user ASPNET /delete

echo "----------------------"

echo "Reregistering ASP.NET and the ASPNET account."

aspnet_regiis -i

echo "Restarting IIS."

iisreset /start

echo "----------------------"

The script worked for me. Thank you very much.

NON IS WORKING... I JUST LOST MY WHOLE DAY TO REPAIR THIS PROBLEM.. I HATE FORUM

None of the above comments are working.... I tried a lot for this problem..

The Web server reported the following error when attempting to create or open the Web project located at the following URL: 'localhost/WebApplication1'. 'HTTP/1.1 400 Bad Request'

M y problem doesnt comes under any of these. Iam using asp.net 1.1  . I can create new project and also open an existing one. But i cant debug it. i can start without debugging, the it displays the page. But when i debug it, it shows the message that " Unable to start debugging on webserver. You do not have the permission to debug.The url of the project is in the internet zone"  How can i rectify this problem. Plz help me out

I am facing a problem while creating and while viewing asp site in window server 2003 Can anyone help me with this. i am getting following error while creating Asp web application. "The web server reported the following error when attempting to create or open the web project located at the following URL: localhost/webapplication1.'HTTP/1.1 403 Forbidden'. "

whle opening a web application IE throws an error that Cannot view the webpage

The Web server reported the following error when attempting to create or open the Web project located at the following URL: 'localhost/WebApplication1'. 'HTTP/1.1 400 Bad Request'

Can anyone help me in finding why this error is coming while creating a ASP web app in visual studio 2003 on window server 2003

also i am not able to open any aspx page on this machine

hi guys ,here is the solution to your problem

if you are not able to create ASPWEBAPPLICATION  -:

when u create new webapplication project the Default url which come is localhost/webapplicationname where localhost points to port 80 just change it to localhost:portnumber  and then u should be able to create a webapplication.

if you are not able to open your existing site in server then there can be DNS mismatch  the ipaddress given in url will be of DNS IP just change it to localhost IP . Your web application should run fine

cheers

ankur

Very nice site!