CodeBetter.Com
Sign in | Join | Help
in Search
CodeBetter.Com
RSS 2.0 via Feedburner
           Do you Twitter? Follow us @CodeBetter

Peter's Gekko

public Blog MyNotepad : Imho { }

Fixing a broken asp.net installation. (The Web server reported the following error when attempting to create or open the Web project located at the following....)

After a failing installation of a VS.NET 2003 add-in, possibly because I  have Whidbey and 2003 running in parallel, I had quite a hard time to get everything working again. I found a lot of hits in support groups, a lot of solutions but nothing worked. The The Web server reported the following error when attempting to create or open the Web project located at the following .. (Internal Server error 500) message kept on hitting me whenever I tried to open or create a project.

What finally helped was taking a closer look at the aspnet_regiis utility. In many solutions you are advised to use this with the -s option to register asp.net with your webapps

 -s <path>  - Install scriptmaps for this version at the specified path,
              recursively. Existing scriptmaps of lower version are
              upgraded to this version.
              E.g. aspnet_regiis.exe -s W3SVC/1/ROOT/SampleApp1

What finally worked was using the -i option

 -i         - Install this version of ASP.NET and update scriptmaps
              at the IIS metabase root and for all scriptmaps below
              the root. Existing scriptmaps of lower version are
              upgraded to this version.

RTFcommand line !

<Update A summary and discussion of the many comments on this post can be found here. Read it !</Update>

blog on

Peter


Published Nov 20 2003, 07:50 PM by pvanooijen
Filed under:

Comments

Fritz Schenk said:

I am still getting the 500 error after executing aspnet_regiis -i. The error occurs only when I create a new project (C# or VB). The error is ---------------------------
Microsoft Development Environment
---------------------------
The Web server reported the following error when attempting to create or open the Web project located at the following URL: 'http://colombia720/testWeb'. 'HTTP/1.1 500 Internal Server Error'.
---------------------------
OK Help
---------------------------


Hopefully you can shed som light into this problem. None of the forums have helped.

Please respond to fritz_schenk@countrywi.com and
intrader@attglobal.net
# February 9, 2004 4:31 PM

Peter van Ooijen said:

There are still a lot of other settings which can be wrong. I don't think this will fix all 500 issues.
# February 11, 2004 2:45 AM

Gayatri said:

Even i am facing this issue:
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'.

If i create another WebSite i am able to work.But i want to work on the default website.
Thanks
# March 8, 2004 12:45 AM

Peter van Ooijen said:

When your problem is specific to one website I would check things like the web.config of that app.
# March 8, 2004 2:44 AM

Lois Consiglio said:

I had the same problem. I finally started with a clean slate which included uninstalling and reinstalling IIS on my Win 2000 box and reloading VS.NET. The last step was to run aspnet_regiis -i. We are up and running now.
# March 11, 2004 9:56 PM

Eric Schmucker said:

I tried running 'aspnet_regiis -i' also without success. Then I found an article that said to delete the ASPNET account first. Once I did that, running 'aspnet_regiis -i' recreated it and everything now works fine.
# March 16, 2004 11:44 PM

M Ruminer said:

That last comment worked for me as well. Deleted the acct and ran aspnet_regiis -i all is good now.
# March 18, 2004 7:19 AM

Chester said:

Where do you run aspnet_regiis -i from the command prompt?
# March 23, 2004 11:24 AM

Peter van Ooijen said:

Use the visual studio command prompt and aspnet_regiis will be in the path
# March 24, 2004 12:31 AM

Steve M said:

I had this problem, but aspnet_regiis did not help. It was caused because I had changed the password in the machine.config processModel tag trying to synchronize it w/ another server.

Here's a test. Try to view you aspx page within the browser (not through VS). This will tell you if aspnet.exe is running. If you get the Server Application Unavailable message, aspnet is not running. This could be because of permission or a change in your machine.config.

My solution was to edit machine.config. Search for processModel tag. You can either resynchronize the passwords or set the password attribute back to autogenerate, UserName can be set to machine.

Save it and you must restart IIS after modifying machine.config.

The link here may help understand the asp.net process identity.
# April 1, 2004 5:30 AM

Chuck Bryan said:

Just solved my problem with this. I had killed my closing tag in my appSettings section of the web.config file. All of a sudden, I could not open the project anymore. Did not realize that I had deleted it. Tried everything, chased my tail and then saw it (I was chasing for a long time, however).

So, replace your current web.config with a clean, slick one, and see if you can reopen your project. Then, if it works, find the problem in your original.

HTH

# April 2, 2004 11:33 AM

Peter van Ooijen said:

Oh yeah, messing up your web.config can be a nightmare : http://dotnetjunkies.com/WebLog/petergekko/archive/2004/03/23/9775.aspx
# April 2, 2004 12:37 PM

Adnan Khan said:

Running these commands solved the problem for me.

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 "----------------------"

# April 5, 2004 3:08 PM

Peter van Ooijen said:

That's a nice script. Is it the ultimate one ? I do hope so.
# April 6, 2004 2:03 AM

Bill Winder said:

I tried everything indicated on this web page to no avail. In the end I had to get the Windows XP cd and run a repair installation of the system and this worked.
# April 7, 2004 5:37 AM

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 fixed it for me,

hope it works for you guys as well
# April 10, 2004 12:28 PM

roy melzer said:

Adnan Khan,
The script worked like a swiss clock.
Thank you very much.
# April 11, 2004 6:05 AM

Daniel Gormley said:

Ok!!! I think i have an answer to the problem but no fix. If you have a server running several sites all on the same ip and use Host Headers, then when you try to create a new project at a site using host headers, it errors. If you create a new web project on the main site not using host headers, it works.. now for a fix... :(
# April 12, 2004 10:43 AM

Mark said:

I fixed this error today. I enabled "Automatically detect settings" in IE Options > Connections > LAN Settings. I've pulled most of my hair out. But I still have some!
# April 13, 2004 3:39 PM

Rafael said:

That's a sweet script, baby! Thanks for sharing.
# April 14, 2004 10:22 PM

Matt said:

Having spent half a day trying to sort out this 'issue', I was quite happy to try the script twice - worked second time. (I also shut every app down first)

Thank you very much... The script was a great help!!!
# April 20, 2004 10:50 AM

Technical Ali said:

Hmmm, script worked in that 500 error no longer occurs. Now getting 403, but that's permissions so I think I'll correct that soon enough...
Thanks guys.
# April 21, 2004 5:47 PM

Lex Qian said:

Thanks a lot to Ronan Dom. After I fllowed his instructions, my problem is sloved.

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"

If Dom doesn't mind, I want to ask you a question. How did you find the solution. Did you any professional articles? If so, please do name them.
# April 22, 2004 2:30 PM

Cedric said:

Hi,
I had the same problem, this fixed it:
In IE, Tools | Internet Options
Connections Tab and click the LAN Settings button.
Under the Proxy Section check Bypass proxy server for local addresses.
This allow you to create asp.net applications locally.

# April 23, 2004 5:48 AM

Prasanth said:

I am getting the following error.
The web server reported the following error when attempting to create or open the web project located at the following URL: 'http://localhost/myappl'. 'HTTP/1.0 403 Forbidden'.

I checked the permissions in IIS ... and everything seems to be normal. Do throw some light on this :(
# April 26, 2004 4:25 AM

Peter's Gekko said:

Wikis on the dotnetjunkies ?
# April 26, 2004 10:10 AM

Stoney said:

I've done everything suggested here. No solution. When I try to create a new ASP.NET project (any language), I get 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'" message. The fun part is clicking on the help button to get "Topic Not Found". Does anybody at Microsoft really know how this is supposed to work? Why isn't there a KB article on this? Obviously, it is a COMMON problem.
# April 26, 2004 11:02 AM

El Rápido said:

This is my umpteenth vs.net installation, and I've got it for the first time now. The batch script didn't work for me, trying the 'Start DTC and reinstall IIS' option now.

I seriously doubt any of those Internet Options solutions work though...but whatever floats your boat I suppose....
# April 27, 2004 3:13 AM

El Rápido said:

It worked! Looking at the differences, I think it was the line:

regsvr32 aspnet_isapi.dll

The rest looks the same, and I fail to see what the DTC could do in this situation. But I'm really glad it works now, so thanks to everyone!!
# April 27, 2004 3:28 AM

Mac said:

I had the problem on Win2003 server and had to play around with a couple of these options to get it working. Pitty MS has not made this information available on the MSDN or as a KB article.
Also, the .tmp MIME error took some doing to get resolved. One would have thought that VS.NET 2003 and Win 2003 would be an easy platform to configure?
Anyway, thanks for all the help guys.

- Mac
# April 28, 2004 4:43 AM

Joshua said:

Thank you guy. This solved the problem
# April 28, 2004 2:25 PM

Pablo said:

Steve M thanks 4 ur help, it worked! :D
# April 28, 2004 2:35 PM

Daria said:

The above (of 4/5/2004 7:08 PM Adnan Khan) script didn't work for me. Or I probably should say it didn't work alone.
After I ran the script and had no results
I added ASPNET user to INETPUB folder's users (Security tab in Properties) and granted it full control. It worked.

All the best
# April 28, 2004 3:06 PM

Ronan Dom said:

I went looking for IIS problems regarding ASP.NET and found "my" solution (Make sure the "Distributed Transaction Coordinator" service is running and reinstall ISS) at

http://www.experts-exchange.com/Web/Web_Servers/IIS/Q_20730661.html

greetz

# April 29, 2004 4:10 AM

Tiffany said:

I think the problem was with the fact that I had both versions of the Framework because I had a similar problem with my PC at home. I did everything that I saw on this page to no avail. I finally uninstalled everything (Framework 1.0, Framewrok 1.1, IIS, VisualStudio and anything else related) and reloaded it then ran "aspnet_regiis.exe -i" and it works fine now. Thank you all for the insight.
# May 5, 2004 9:48 AM

Peter van Ooijen said:

For me my original solution worked for a machine with framework 1.0, 1.1 and 1.2 (PDC Whidbey build) installed....

# May 6, 2004 9:04 AM

ChesterC said:

So when you load the address http://localhost into IE you should not get a 500 server error if ISS is working properly, correct? I'm getting that. To my extreme sadness I've tried every suggestion here to no avail.

I'm running WinXP on fat32 but to my knowledge this only poses a security risk but should not keep me from developing on this machine.

I have no problem creating and editing asp.net projects on remote servers but trying to develop locally has proven to be impossible for me thus far.
# May 10, 2004 3:08 AM

Peter van Ooijen said:

The way to check if ISS itself is running is try to open a plain htm file. Like //localhost/MyPage.htm.
# May 10, 2004 6:43 AM

ChesterC said:

I'm able to open a plain html file in a directory I made under wwwroot. So I suppose ISS is working ok. Might I be missing something else? Do you have to make a virtual directory priror to creating a new asp.net project locally... or should I just be able to create a new project using http://localhost/some-random-name as the location ?
# May 10, 2004 1:04 PM

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.
# May 11, 2004 12:15 AM

Mark said:

The fix below is for Asp.net new web apps not opening and receiving the 'HTTP/1.1 500 Internal Server Error'
Check the following:

“My_Computer_Zone code group” value on the Web server? To achieve that, you should do the following:
- Go to “Administrative Tools”
- Open “Microsoft .Net 1.1 Configuration”
- In the new window, expand the “Runtime Security Policy”
- Expand “Machine”, then “Code Groups”, then “All_Code”.
- Right-Click on “My_Computer_Zone” and select properties.
- On the “Permission Set” tab, the selected value should be “Full Trust”
- If it is not, you should change the value to “Full Trust”.
- You can test again creating a new ASP.NET Web application
# May 11, 2004 6:04 AM

Mark said:

Sorry, forgot to add on the above that you must restart IIS after changing this setting.
# May 11, 2004 6:11 AM

Mark said:

Another easier way to fix is, open .net dos box and type "caspol -s off" and restart iis and all should be fine.
# May 11, 2004 6:20 AM

Peter van Ooijen said:

Thanks Mark, that makes a lot of sense.

The many full installation scripts popping up here (Chester you forgot : reinstall Windows :>) are typically something you would do in great despair. Missed many a night of sleep myself, finding out it didn't work after staring for hours at a "please wait" message. In the end the only sensible thing the script did will be something like updating one essential security setting.

Security is good but it can really backfire.
# May 11, 2004 6:21 AM

mythx said:

this works for me, hope it helps

go to IIS, select your website, right click to all task and then permission wizard. keep your current permission intact and then add the new
recommended permission. voila
# May 12, 2004 11:24 PM

Bret said:

I tried everything on this page. I have had this problem at home and have pulled out most of my hair. After installing VS.NET 2003 I now have the problem here at work !!!! nothing on this page worked. What I did to fix this problem was go into IIS select the website (Default Web Site) in my case and right click --> go to Home Directory and click the CREATE button. This fixed everything... who knew??? I now have time to start taping my hair back....

# May 17, 2004 12:05 PM

VK said:

Bret! pls?

ISS/DefaultWebSite/Property/HomeDirectory...
Where is CREATE button?
# May 27, 2004 10:48 AM

Scewdotnet! said:

OK guys I tried everthing on this page (except uninstall) even I remove and create a new application! still no luck! is there anyone out there to get the root of this problem so we all can understand what the hell is going on behind the scene?
# May 27, 2004 3:52 PM

Peter van Ooijen said:

Behind the scenes 50% will be a security issue, 50% registration settings and 50% gremlins. I don't think there is just 1 core problem.
# May 29, 2004 1:50 PM

Vijay said:

The batch script worked fine for my problem.

Thanks.
# June 1, 2004 11:56 PM

Turing said:

I tried many things, including a complete reinstall of VS, only to discover that the culprit is my ZoneAlarm firewall. Apparently version 4.5 worked fine, but the *new* version 5.0 causes problems with IIS. Reinstalling the old version took care of it.
# June 7, 2004 11:23 PM

Peter van Ooijen said:

Security hits back :

http://dotnetjunkies.com/WebLog/petergekko/archive/2004/06/08/15757.aspx
# June 8, 2004 4:30 AM

Rich C said:

Had the same problem and reverted to version 4.5. ZoneLabs had some suggestions... most of which I had already done (stop/start IIS, add 127.0.0.1 to safe zone, etc.)

I'll be waiting a bit before trying ZA 5.x again. Find more at:

http://richhubbins.theclaussens.com/PermaLink.aspx?guid=cb5763b8-207a-4ef9-ac6c-caadfa8a51e6
# June 8, 2004 8:39 AM

JBot said:

Getting this error (or similar) ?...

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 Server Error'.

Try turning your personal firewall completely off. Like totally unload the mofo.

Just a thought.
# June 12, 2004 8:56 PM

Peter's Gekko said:

ASP.NET not working ? Flame you firewall !
# June 14, 2004 1:55 AM

James said:

hi,

I've tried everything that was suggested as well, out of all, Lex Qian's suggestion worked. Thank you.

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"


James
# June 15, 2004 8:10 AM

Daniela said:

I am getting crazy! I have tried all of this and am still getting the same error!

Now maybe it has something to do with the permission levels, does anyone know how that can be fixed?
# June 15, 2004 8:53 AM

anonymouse said:

Removing the framework through Add/Remove programs then reinstalling the framework didn't work for me.

Neither did stopping IIS, removing the aspnet worker process account, then reinstalling asp.net and reregistering the "isapi" filter.

However, when inspecting the properties of the default web site, I noticed (as mentioned above) that there was no default application defined. Creating one fixed the problem.

This is XP SP2 RC1 and RC2 by the way.

Frustrating. I kind of agree with Peter though: It's either a problem to do with the setup of the framework, a security issue (the firewall is an annoying one:-) or an issue with configuration settings on the web you are trying to create projects in.

HTH.
# June 15, 2004 7:00 PM

Alan Sweet said:

OK I have finally gotten the Problem fixed. I'll share this with everyone
so if it happens to you.

I was not able to access or run web pages I had developed under .NET 2002.

I kept getting a number of errors saying the server was not accessible or
Internal Server Error. Most of the time if you go to the event viewer you
will see an error message...

aspnet_wp.exe could not be started. The error code for the failure is
80004005. This error can be caused when the worker process account has
insufficient rights to read the .NET Framework files. Please ensure that the
.NET Framework is correctly installed and that the ACLs on the installation
directory allow access to the configured account.

It will happen if,...

Your development machine is an XP Pro (some have said that they have gotten
the problem on Windows 2000 and Windows server 2003)

You have installed .NET Framework 2003

You have installed IIS V5.1

You have installed ASP.NET V1.1 or V1.0

You have applied the patch MS03-32 Security Update for Internet Explorer
security patch

According to MS it can only happen with ASP.NET V1.0 and it can not happen
ASP.NET V1.1...bull pat-too-ie

According to MS..

The symptom of this issue is that after installing the patch, all requests
to ASP.NET result in an error message saying "Server Application
Unavailable".

This issue only impacts installations running ASP.NET V1.0 on Windows XP
Professional. It does not impact machines running Windows 2000 or Windows
Server 2003. It also does not impact machines running Windows XP with
ASP.NET v1.1 installed.

We are working hard on a permanent solution for this issue. In the meantime,
you can visit this page to learn about the problem as well as a safe
workaround you can apply immediately to fix the issue:

http://www.asp.net/faq/ms03-32-issue.aspx



If you run the patch on a machine with ASP.NET V1.0, it works fine. It
corrects the defect..



It, however, will not run on a machine with ASP.NET V1.1.



In the downloaded batch file "fixup" - make the following changes


REM if exist %SystemRoot%\microsoft.net\framework\v1.1.4322\mscorlib.dll
goto v11_installed

REM "Changing to the Framework install directory"
cd /d %SystemRoot%\microsoft.net\framework\v1.1.4322

and then run it again. This should fix the issue.



It works. I can now access and create ASP.NET projects without problems.



Hope this helps some one so they do not lose 3 days like I did.


If anyone wants me too I'll copy the whole modified batch file text here for
you to look at.


Alan
# June 20, 2004 12:21 PM

Derek Calder said:

I tried everything up to Daria's post, but Daria's method is what finally worked for me. It may have been a combination of things, but that's what made it click.

>I added ASPNET user to INETPUB folder's users (Security tab in Properties) and granted it full control. It worked.

Derek
# June 22, 2004 2:46 PM

Serge said:

After reading "5/17/2004 4:05 PM Bret"

this is exactly what did work.
so my guess will be next:

1)Make sure the "Distributed Transaction Coordinator" service is running (!)
2) stop ISS
3) run "aspnet_regiis.exe -i"
4) run "regsvr32 aspnet_isapi.dll"
5) start IIS
6) make sure ASP.NET user has rights on Inetpub
7) Go to HomeDirectory under Web-site properties in IIS Management console
8) If you see Remove button next to Application Name Edit box, click Remove. If button is Create go to next step
9)then after "Create" appear click it
10) Enjoy... Oh, if you installed XP SP2, make sure you do not block yourself. firewall by default is On and HTTP is not allowed
# June 23, 2004 4:04 AM

Avinash said:

Adnan Khan, Your script finally worked. I was about to reinstall everything after trying all solutions and then i tried ur script as a last try and it worked. Thanks a lot
# June 24, 2004 11:11 AM

Manan said:

aspnet_regiis -i and restarting IIS as mentioned above did the trick for me. Thanks all.
# July 1, 2004 12:50 PM

Goksel Misirli said:

This link helped me to solve my problem.
http://www.tek-tips.com/gviewthread.cfm/pid/787/qid/758414

After checking that ASP.NET is not working, I wanted to look if the ASP pages are working or not. But they didn't as well. they gave me the same internal server error message but more meaningfull error messages regarding IWAM user in the event logs. Then I realized something wrong with COM+. as it is stated in the link above
*I reregistered the ole32.dll and oleaut32.dll
*Then reinstalled COM+ (I also checked the COM+ System Application service from the services. I could not start it before the reinstall process.) I applied the steps looking http://www.jsiinc.com/SUBN/tip6900/rh6951.htm
*Then I reinstalled the IIS

It then started to work perfectly

After spending hours, at least it is solved :)
# July 15, 2004 5:21 PM

Goit said:

Hi all, though so many solutions have been proposed by such helpful professionals, I couldn't find much info regarding the cause of the problem.
The problem has occured suddenly in the middle of jumping from a page to another page when I was testing a c# asp.net project on XP os, and IIS 5.1 MS Visual studio 2003.
For the first time is says it couldn't display a page because it can't get a reference to an object of code behind class for some requested page. Then I thought it could be my code problem and tried to figure out the problem and I did find nothing, but the next time when I run the application
The Web server reported the following error when attempting to create or open the Web project located at the following URL: aaaaaaa. 'HTTP/1.1 500 Internal Server Error' I then waste some minutes to try with new apps, other existing apps and that problem still continues showing up. I restarted nothing... then googling I found this site but i read most of the solutions here but I tried nothing because I don't see a solution that works for evey one or may be the nature of the cause of the problem differs from one to another then I went to MS site and I found the follwing site http://support.microsoft.com/default.aspx?scid=kb;en-us;822319 eventhough the solution is targeted for Microsoft Windows Server 2003-based computer I tried only a couple of things suggested there

1 - Restart the IIS before you create a new ASP.NET 1.1 application. At the command prompt, type the following command:
iisreset

2 - start your application

works fine as it should be. But still remains what causes the problem unanswered? If any one interested for answer here are some info regarding my app, it creates threads inside other threads may be related to that? I don't know....you tell me
# July 18, 2004 12:24 AM

Carlito said:

Just another tip for anyone with this problem - I tried everything on the internet. I finally got it up and running after I:

1) uninstalled IIS
2) deleted (renamed) the inetpub directory <--important
3) reinstalled IIS
4) performed aspnet_regiis -i.

So try that if all else is failing.
# July 25, 2004 9:05 PM

zero303 said:

Just wanna say thanks to Adnan Khan for the script... worked a treat!
# July 27, 2004 6:31 AM

mOrrI said:

Heyas i'm getting this error...

and i've made the following steps:

iisreset
aspnet_regiis -i
reboot pc
and worked :D
this was on a windows 2000 server OS
# July 28, 2004 9:39 AM

oded said:

when i type the aspnet_regiis -i it says :
that the command isnt recognized
help
# July 28, 2004 3:58 PM

Jim said:

hello,

I was faced with this problem as well, after moving my development machine to winxp pro. It's frustrating to say the least.

I noticed this after I had installed the IIS 6.0 Admin pack.

To solve the problem, after going through many steps, was that I noticed I had changed the default password in the process model for machine.config. Changing it back to auto generate and restarting IIS did the trick for me.

Thanks guys for all your help!
# July 31, 2004 7:29 AM

Suzanne said:

I have a same problem here and I have tried all the solution that you guys provide. But it still can't solve my problem. After checking my event log I found out this error message:

The server failed to load application '/LM/W3SVC'. The error was 'The specified metadata was not found.
'.

I even try to repair my Com+ Application under the component service. But I got problem during the reinstallation of Com+ Application. Window give me this error message:

sub-component COM+ raised an exception while processing the OC_COMPLETE_INSTALLATION setup message.
d:\nt\com1x\src\complussetup\comsetup\ccompluscore.cpp (line565)
Error code: 0x80040155

interface not registered
the Com+ event classes could not be registered

Does any one here has any idea how to solve this?
# August 6, 2004 10:10 AM

Peter van Ooijen said:

An oversimplified opinion from a distance :
- Your IIS metabase has gone (corrupt)
http://www.winnetmag.com/Article/ArticleID/16179/16179.html
- Your COM+ app uses another COM(+) app which is not registered/installed

Does that make any sense ?
# August 6, 2004 11:20 AM

goit said:

this is to oded for the problem
(when i type the aspnet_regiis -i it says :
that the command isnt recognized
help )
it seesms you are not in the right path, open the visual studio .net command prompt from the visual studio .net tools menu and type the aspnet_regiis ...
# August 7, 2004 9:07 AM

herman ballinger said:

whhen i try to read my email i get an internal error report
# August 21, 2004 1:52 PM

Eckey said:

ok guys I found a solution to this problem after trying all these tips and still nothing I found out that the proper way is to be on a network (router) so that your ip is something like 192.168.x.x I know this sounds stupid but it worked for me. i figured this out because everytime i brought my PC into work and put it on their network it would work but as soon as i got home and put in on my satice ip from my isp i would get the error.So try it out, let me know if this helped you. eckey@rogers.com
# August 21, 2004 2:16 PM

Peter van 0oijen said:

Eckey, that's "coincidence". This would mean that you could not run an ASP.NET server on the internet. Too many sites proves the contrary.

Herman, I miss the remark/question.
# August 21, 2004 3:26 PM

Otto said:

hi,

Got it working with Ronan Dom Solution (Below) ...Awesome.
Pretty wak having to do all this to get it up and running

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"

Cheers

-Otto
# August 26, 2004 11:39 PM

Drazen Soronda said:

BINGO...LOTTO
I make it works :)

Ok
Solution is just copy/paste from upper post:
1) uninstalled IIS
2) deleted (renamed) the inetpub directory <--important
3) reinstalled IIS
4) performed aspnet_regiis -i.
I tried everything else and no success.
It is not firewall !!(Turned ON on my machine)
It is not COM+... ( i disabled them in services:)
oh btw. I'm running WIN XP + SP2 (final) + DOT.NET 2003 (1.1 framework).

I belive the problem is in ASP.NET user permisions. so just "DELETE ALL FILES IN INETPUB dir" reinstall IIS. (fixes that HTTP 500 error). AND aspnet_regiis -i fixes error for ASP.NET 1.1 request.

Now i can go to slee, peacefully. :)
# September 3, 2004 2:03 PM

Peter's Gekko said:

Fixing a broken asp.net installation. (The Web server reported the following error when attempting to create or open the Web project located at the following....) revisited
# September 7, 2004 11:54 PM

RB said:

IE >> Internet Options >> Connections >> Lan Settings just uncheck the "Automatically detect settings".
It worked for me.

Cheers,
RB
# September 10, 2004 9:31 PM

Dave Jones said:

I fixed my problem with HTTP/1.1 500 error! After fooling with this for a couple of hours, it turned out to be that permissions had not properly been propigated to my physical folder where my site was. As soon as I put 'Everyone' in the security settings with re/L/R rights, it worked! Take a look at your settings before trying anything else invasive.

D-
# September 12, 2004 3:17 PM

Peter van 0oijen said:

How very right. It's all about permissions.
http://dotnetjunkies.com/WebLog/petergekko/archive/2004/09/08/24756.aspx
# September 13, 2004 11:06 AM

kiran said: