BugNET

Open source issue tracking & project management

Forums

HomeHomeSupportSupportInstalling BugN...Installing BugN...CanCan't make site use .NET version 2.0
Previous
 
Next
New Post
6/10/2008 4:25 PM
 

The problem is that I have the site running as a 1.1 application, which it chose by default, and not reflecting the IIS changes when I modify it to version 2.0.  The site is generating an error when I access it on line 17 with a configuration error of "Parser Error Message: Unrecognized attribute 'type'." I see the 1.1 .NET version info at the bottom of the page:

Version Information: Microsoft .NET Framework Version:1.1.4322.2407; ASP.NET Version:1.1.4322.2407 

Here is what I know:

- The server is hosting both 1.1 and 2.0 sites that I personally checked are both working.
- The troublesome site, that I would beat mercilessly if I could, was created as a virtual directory under the default web site using the same IP and port (80), but with a host header.
- I have no less than 3 other sites running under the same IP with host headers and they run fine (as 1.1 apps)
- I didn't receive any errors when creating the site and everything looks normal in IIS
- I can open the properties of the site and change the ASP version and application pool to .NET 2.0
- After changing the properties and closing and then re-opening the properties the ASP version and app pool are still set to .NET 2.0
- The site has never successfully run as a .NET 2.0 app, I always get the same message with .NET 1.1xxx at the bottom
- I am testing the site on the server locally and verified that the other sites using the same IP successfully run locally
- I tried stopping/starting the default web site and restarting IIS (Nada, same error, someone please get me a beer)
- I was able to get the site up and running on my local laptop running Vista and II7 (but not on my server!!!)

I feel I have my due diligence of hours of troubleshooting and am now about to shave my head.  Lay it on me and enjoy basking in the glow of my earnestly given gratitude.

 
New Post
6/11/2008 5:59 AM
 

I can certainly understand your fustration.

If you haven't already, you could try running the Aspnet_regiis.exe tool manually against your virtual directory to set the asp.net script mappings. See here for details on how to use this tool and make sure you run the one under the C:\windows\microsoft.net\framework\v2.0* directory.

http://msdn.microsoft.com/en-us/library/k6h9cz8h(VS.80).aspx


Davin Dubeau

follow us on twitter facebook users group google plus
 
New Post
6/11/2008 2:50 PM
 

Thanks for the suggestion, and before I forget, despite the difficulties I think it's a great app.

I ran aspnet_regiis -ir which ran fine then I ran aspnet_regiis -s <path> to set the script mapping, but I didn't receive any success message, it just listed out the options as if I had run it with -? and when I checked the site it was still 1.1.

Ideas?

 
New Post
6/11/2008 10:42 PM
 

OK, a little progress...  ran aspnet_regiis -i and then the 2.0 setting took, however now I am getting the infamous configuration error:

It is an error to use a section registered as allowDefinition='MachineToApplication' beyond application level.  This error can be caused by a virtual directory not being configured as an application in IIS.

The IIS properties window already has it as an application as there is no create button.  How else can I verify that the virtual directory is an application or manually do it myself?

Thanks!

 
New Post
6/11/2008 11:17 PM
 

Could it be the version of windows I am on? 2003?  I am still in shock that I had this up and running in 15 minutes on my local pc running vista and sql2005, but some 6 hours later I am still working on this...

 
Previous
 
Next
HomeHomeSupportSupportInstalling BugN...Installing BugN...CanCan't make site use .NET version 2.0


Forum Policy

These Discussion Forums are dedicated to the discussion of the BugNET issue tracker.

For the benefit of the community and to protect the integrity of the project, please observe the following posting guidelines:
1. No Advertising.
2. No Flaming or Trolling.
3. No Profanity, Racism, or Prejudice.
4. Site Moderators have the final word on approving/removing a thread or post or comment.
5. English language posting only, please.