After I totally screwed the machine up last night, I have them reimage it. Today, when launching the management console for SQL 2005 it gave an error about C:\WINDOWS\Microsoft.NET\Framework\\mscorlib.tlb. (I thought the single instance of the double backslash was odd). Anyways, some quick research seemed to state that repairing the .NET installation could fix it. I repaired the x64 .NET 2.0 and the error went away.

Right now, I'm getting a 404 (can't find) error, and no longer the 403 (forbidden). I think that is improvment, but nothing jumped out at me why (e.g the files are there, permissions are set, etc).

I still think it's weird that you can't tell IIS which .NET you want to run for each website or application pool.

Brad

Thanks Mitch- I think you got me going in the right direction!

Basically, don't trust ANY of the images that are out there ;-) I went to register my x64 .NET and it promptly told me that it was running in 32-bit mode so that it couldn't register the 64-bit .NET. Well, to avoid further problems, I'm not even going to try to get IIS into 64-bit mode, but leaving it, uninstalling .NET x64 and reinstalling .NET x32. Then we'll see where I'm at.

Thanks so much to everyone who has commented - I'll update soon!

Brad

Thank you all so much!

I finally got all the kinks worked out of my installation. I wanted to try to recap here what I did:

Problem:

• Windows 2003 Server x64 virtual machine
• .NET 1.1
• .NET 2.0 x64
• .NET 2.0 x32 (showed up in IIS web extentions)
• Web errors: 403, 401

Solution:

• Uninstall all .NET (1.1 and 2.0 x64)
• Install Server 2003 x64 SP2 (not sure that this did anything)
• Install .NET 2.0 x64
• aspnet_regiis.exe -i
• <Denis Bauer's ASP.NET Version Switcher (aspnet_regiis.exe -s or -sn)
• Allow .NET 2.0

Works like a charm now! Thank you all for your input and help!

Brad