framework version confusion

Hi

Hope someone can offer some input on this...

Running IIS6 with both ASP.NET 1.1 and 2.0 applications. Naturally
everything is seperated out by application pool.

When I run this script:
http://blog.crowe.co.nz/archive/2006/08/15/676.aspx

It warns me that one of my app pools (the one used by reporting
services) is using multiple versions of the framework. However - all
that app pool contains is the RS web site, and it's two virtual
directories. I have checked them in IIS Manager and they all say
v1.1.4332.

Any idea why that should be? Is the VBScript simply wrong? Or do I
have some metabase issue or something? Everything is pretty much
working as it should be, however we are getting intermittent errors on
our SharePoint portals (about ASP 2, which they do not use).

We used to get these errors all the time, and it was caused by a ASP 2
application trying to load in an ASP 1 application pool. Yesterday I
started up our report server for the first time in ages and boom, all
of a sudden I start getting reports of these errors returning.

Wonder if anyone can offer some insight of what might be going on?

Also - as a follow up question - in the "Properties" when I click on
"Web Sites" in IIS, the default ASP.NET version is 1.1.4322. However I
see the ASP.NET_2.0.50727.0 ISAPI filter loaded here. Is that normal?
Does this filter get executed in front of the ones on my actual web
sites? Again, any insight here would be very useful.

Thanks in advance,

Rich

Re: framework version confusion

As much as useful the script is, before using it I would understand exactly
what the script is doing and check the metabase for myself. (the script only
checks for .aspx, not full asp.net extensions for example). Although didn't
check the script with care, at first view seems a starting indicator of
where the ASP.NET versions are set.

Check for yourself by opening %systemroot%\system32\inetsrv\metabase.xml and
look into where Reporting services are installed and examine the script
mappings set. You can also do the same by using inetmgr.exe by pressing the
"Configuration" button on the WebSite or Virtual Directory tab of each of
the WebSites and VDirs you want to check.

If you understand what the script is doing, and you find the script maps are
set wrong, then assuming you have ASP.NET 1.1 and 2.0 running side by side
the best option is to install ASP.NET 2.0 by default. After that you set
ASP.NET 1.1 on the exceptions.

(uninstall v2)
> v2.0.50727\aspnet_regiis.exe -u
(uninstall v1.1)
> v1.1.4322\aspnet_regiis.exe -u
(install v2)
> v2.0.50727\aspnet_regiis.exe -i
(override the exceptions)
> v1.1.4322\aspnet_regiis.exe -s w3svc/1

Here "w3svc/1" would be the website where reporting services is installed
and would recursively set the script mappings of all ASP.NET extensions to
the ASP.NET 1.1 version.

NOTE: This assumes that all Reporting Services IIS resources are contained
in the same WebSite and use ASP.NET 1.1 only.

Tiago Halm

Re: framework version confusion

On 26 Sep, 18:06, "Tiago Halm" wrote:
> As much as useful the script is, before using it I would understand exactly
> what the script is doing and check the metabase for myself. (the script only
> checks for .aspx, not full asp.net extensions for example). Although didn't
> check the script with care, at first view seems a starting indicator of
> where the ASP.NET versions are set.
>
> Check for yourself by opening %systemroot%\system32\inetsrv\metabase.xml and
> look into where Reporting services are installed and examine the script
> mappings set. You can also do the same by using inetmgr.exe by pressing the
> "Configuration" button on the WebSite or Virtual Directory tab of each of
> the WebSites and VDirs you want to check.
>
> If you understand what the script is doing, and you find the script maps are
> set wrong, then assuming you have ASP.NET 1.1 and 2.0 running side by side
> the best option is to install ASP.NET 2.0 by default. After that you set
> ASP.NET 1.1 on the exceptions.
>
> (uninstall v2)> v2.0.50727\aspnet_regiis.exe -u
> (uninstall v1.1)
> > v1.1.4322\aspnet_regiis.exe -u
> (install v2)
> > v2.0.50727\aspnet_regiis.exe -i
>
> (override the exceptions)
>
> > v1.1.4322\aspnet_regiis.exe -s w3svc/1
>
> Here "w3svc/1" would be the website where reporting services is installed
> and would recursively set the script mappings of all ASP.NET extensions to
> the ASP.NET 1.1 version.
>
> NOTE: This assumes that all Reporting Services IIS resources are contained
> in the same WebSite and use ASP.NET 1.1 only.
>
> Tiago Halm

Hi Tiago

Thanks very much for the advice, I think this is exactly what I was
looking for.

I will give this a try next week when I am back at work.

Cheers!

Richard