Re: Missing ASP.Net tab in IIS

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

I believe I already checked these keys (no errant entries.) Guess I'll have to try the other prolonged steps as indicated in the comments for this bug.
"Juan T. Llibre" <nomailreplies@xxxxxxxxxxx> wrote in message news:uMhT6wCeGHA.1204@xxxxxxxxxxxxxxxxxxxxxxx
See if any of the workarounds listed in my bug report help you get it back :

http://lab.msdn.microsoft.com/productfeedback/viewfeedback.aspx?feedbackid=f697a7d8-52a0-4c79-bc57-767b6d7d750a

Look closely at these entries :

> Same with VS.Net 2005 Version 8.0.50727.42(RTM.050727-4200)
> [FIX] This works for me ( it suggests a different solution )

FDBK21319#2: Remove Registry Entries that cause the problem
Thanks to Chris Adams:
http://www.eggheadcafe.com/forums/ForumPost.asp?ID=20592&INTID=6

To fix, check the following 3 regkeys :
HKEY_CLASSES_ROOT\CLSID\{7D23CCC6-A390-406E-AB67-2F8B7558F6F6}\InprocServer32
HKEY_CLASSES_ROOT\CLSID\{FD5CD8B1-6FE0-44F3-BBFB-65E3655B096E} \InprocServer32
HKEY_CLASSES_ROOT\CLSID\{FEDB2179-2335-48F0-AA28-5CDA35A2B36D}\InprocServer32

Under (expand) InProcServer32, look for the presence of a non-2.0.0.0 (example 2.0.36.0) and remove it.
It has a reference that causes this to break.

If you do not have this MMC interface, you can use aspnet_regiis.exe
aspnet_regiis -s <path>
where path equals the location in the metabase where you want the mappings to change.





Juan T. Llibre, asp.net MVP
aspnetfaq.com : http://www.aspnetfaq.com/
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
"Mike Lowery" <selfspam@xxxxxxxxxxxxxxxx> wrote in message
news:OfGGZoCeGHA.3888@xxxxxxxxxxxxxxxxxxxxxxx
> I'm running Win2003 Standard Edition and have installed both IIS and Framework 2.0. For some
> reason I do not have an ASP.Net tab when configuring websites. I've tried running aspnet_regiis -i
> and even reinstalling Framework 2.0 to no avail. I've seen posts talking about this being a
> problem when upgrading from a beta, but that's not what I'm doing.
>
> Can someone help? My next step would be to reinstall IIS but that's rather drastic.


Relevant Pages