Re: Latest patch parses 1.1 pages with 2.0

re:
!> That doesn't change the fact that there is a serious bug here.

Maybe; maybe not. You could also have a bad install.

Or, you could have a configuration element which you've configured/misconfigured
but now don't have any more access to, for whatever reason.

re:
!> 2.0 is parsing a config file while everything is reporting that 1.1 is the active framework.

How did you "uninstall" the .Net Framework 2.0 ?

I suspect that what you call an "active framework" is simply that you have reconfigured
your sites to run under 1.1, but that the .Net Framework 2.0 is still registered with IIS
and is, therefore, still active.

See below for the instructions to *uninstall* the .Net Framework 2.0

re:
!> I think at this point we have established that 1.1 is the registered framework. Agreed?

Nope. What we have established is that you have a number
of *sites* configured to run under the .Net Framework 1.1.

If you truly have no need for the .Net Framework 2.0, uninstall it by going to
the Windows Control Panel, opening the "Add or Remove Programs" tool,
finding the entry for the .Net Framework 2.0, selecting it and clicking the
"Change/Remove" button.

If you don't want to *physically* uninstall the .Net Framework 2.0, just run

aspnet_regiis -u

from :
drive:\WINDOWS\Microsoft.NET\Framework\v2.0.50727

That will uninstall the .Net Framework 2.0 from IIS's mappings, but will not delete the Framework's files.
That means that you could, later, reinstall it, but that it will not run under IIS until you reinstall it.

All existing scriptmaps mapped to the .Net Framework 2.0 will be remapped to the
highest remaining version of ASP.NET installed on the machine (1.1 in your case).

Once you've done that, *then* only the .Net Framework 1.1 will be active on that machine.

re:
!> Now I could fix the config file to run happily under 2.0, and then copy your identity.aspx file in.

What you're seeing is not a 2.0-specific feature.
The maxRequestLength default size is the same for both 1.1 and 2.0.

re:
!> maxRequestLength="500000000"

How did you ever end up with that number ?

maxRequestLength indicates the maximum file upload size supported by ASP.NET, in KB.
The default is 4096 (4 MB), both for the .Net Framework 1.1 and 2.0.

What's specified in your config file is that maxrequestLength is 500,000,000 KB = 500 GB!
I don't think you want to have people upload 500GB files to your server. :-)

Change that to a number which reflects the maximum size file upload you want to support.
If you want to support 8MB file uploads, change it to 8192. If 16MB, change it to 16384.

That will immediately allow you to run the identiy.aspx code I sent you.
Run it and post back the results.

Fiddling with configuration files without knowing what
a parameter does is the easiest way to wreck a server.

I recommend that you study, very carefully, configuration parameters before changing them.

....and don't forget to, at least, run aspnet_regiis -u
from the .Net Framework 2.0 directory, if you truly have no need to run 2.0 code.

Doing that will immediately end the 2.0 file processing you're seeing.





Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
======================================
"David Cameron" <DavidCameron@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C765420D-55D5-4C0D-8F1C-61676CB625BE@xxxxxxxxxxxxxxxx
If you do have it, please right-click "Web Sites", select "Properties" and
then the "ASP.NET" tab.
Jot down the ASP.NET version the ASP.NET tab reports...and post it.

It reports 1.1. Same as the aspnet_regiis -lk listing I posted.

Question for you : For your "1.1 sites", have you created IIS *web sites* or *ASP.NET applications* ?
It makes a lot of difference which one you've used.

I know. These are IIS web sites.

Now, back to the issues.

You are in luck, one of the sites is malfunctioning again, on one of the
test servers that I can play with. It is worth noting that this is a site
that was definitely registered to 1.1 prior to a reboot on the server.

The site in question is 2034039847.

Now the output of aspnet_regiis -lk in the 1.1 directory is:
W3SVC/ 1.1.4322.0
W3SVC/1370742412/root/ 1.1.4322.0
W3SVC/1453161142/root/ 1.1.4322.0
W3SVC/2034039847/root/ 1.1.4322.0
W3SVC/2080259255/root/ 1.1.4322.0
W3SVC/2116458577/root/ 1.1.4322.0
W3SVC/370149253/root/ 1.1.4322.0
W3SVC/384844167/root/ 1.1.4322.0
W3SVC/891393290/root/ 1.1.4322.0

The output of aspnet_regiis -lk in the 2.0 directory is:
W3SVC/ 1.1.4322.0
W3SVC/1370742412/root/ 1.1.4322.0
W3SVC/1453161142/root/ 1.1.4322.0
W3SVC/2034039847/root/ 1.1.4322.0
W3SVC/2080259255/root/ 1.1.4322.0
W3SVC/2116458577/root/ 1.1.4322.0
W3SVC/370149253/root/ 1.1.4322.0
W3SVC/384844167/root/ 1.1.4322.0
W3SVC/891393290/root/ 1.1.4322.0

(identical)

The properties for the root site in the MMC plugin show the .Net version as
1.1. The properties for the specific site in the MMC plugin show the .Net
version as 1.1.

I think at this point we have established that 1.1 is the registered
framework. Agreed?

I would copy in your identity file however the site is returning the same
configuration error as earlier:
Configuration Error
...
Parser Error Message: The value for the property 'maxRequestLength' is not
valid. The error is: The value must be inside the range 0-2097151.
...
Line 117: <httpRuntime
Line 118: executionTimeout="90"
Line 119: maxRequestLength="500000000"
Line 120: useFullyQualifiedRedirectUrl="false"
Line 121: minFreeThreads="8"
...
Source File: <path>\web.config Line: 119
Version Information: Microsoft .NET Framework Version:2.0.50727.832; ASP.NET
Version:2.0.50727.832

Just to be clear, I have removed the path in the code above and replaced it
with <path>.

Now I could fix the config file to run happily under 2.0, and then copy your
identity.aspx file in. That doesn't change the fact that there is a serious
bug here. 2.0 is parsing a config file while everything is reporting that 1.1
is the active framework.


.

Loading