how to configure virtual directory to use .Net v1.1 instea..

Hi Ken,

Thank you for your reply. I looked in the Application Pools/DefaultAppPool
and I saw the little gear shaped icon for the ReportServer virtual dir (named
"Report Server"which works OK) and I saw one for the Reports virtual dir
(named "Report Server Interface" - this is the one that is denying me access).

On the virtual dir Properties tab for the ReportServer virtual dir, in the
Application Pool dropdown box it shows "DefaultAppPool", Execute Permissions
"None", Application Name "Report Server". For the Reports virtual dir
properties, the application pool dropdown shows "DefaultAppPool", Execute
Permissions "Scripts and Executables", Application Name "Report Server
Interface".

Note: All of the extensions /paths aim at v1.1 already for the Reports
Virtual Dir in the configuration window. My problem is this: when I type
http://myservername/reportserver in IE, I get a directory listing of
everything on the Report Server. But when I type http://myservername/reports
I get a "Directory Listing Denied" message - "This Virtual Directory does
not allow contents to be listed."

What do I need to configure on IIS or the Reports Virtual dir so that it can
be accessed? I am guessing that something in the Reports Virtual dir is
still aiming at v2.0 framework. I don't have this ASPNet tab that supposedly
comes with IIS ver6.0 (which is what I am running). So how else can I set
what the Reports Virtual Dir is looking at for a framework? I tried
righ-clicking on the DefaultAppPool/Report Server Interface icon, but did not
get anything about properties.

Thank you again for getting back to me.

Rich


"Ken Schaefer" wrote:

> Hi,
>
> If you configure your Virtual Directory as an Application root (on the
> Virtual Directory tab), then you can use the "Configuration" button on that
> tab to configure .aspx (and any other extenstions) to point to the v1.1
> aspnet_isapi.dll rather than the v2.0 aspnet_isapi.dll file (each ASP.NET
> ISAPI .dll file lives in c:\windows\microsoft.net\framework\versionNumber\
> folder)
>
> By aware that you can only load one version of the .NET framework into each
> worker process, so you will need to run this virtual directory's application
> in its own web application pool (i.e. with it's own worker process), or put
> it into an existing web application pool that is already hosting v1.1
> applications.
>
> Cheers
> Ken
>
> "Rich" <Rich RemoveThis @discussions.microsoft.com> wrote in message
> news:7C25BBED-5B97-4DE6-A92F-3F6FE15F1FEF@microsoft.com...
> > Greetings,
> >
> > I am running IIS version 6.0 on win2003 server. On original install of
> > everything we were using .Net framework v1.1 with Sql Server 2000,
> > Reporting
> > Services 2000, Visual Studio 2003. I came into the picture after this
> > original install.
> >
> > Then we upgraded to .Net framework v2.0 and Visual Studio 2005. Still
> > using
> > Sql Server 2000 and Reporting services 2000. Now I cannot access Report
> > manager (which is a web service) for Reporting services 2000. So, while
> > combing the NGs for a solution to this problem, someone pointed out that
> > in
> > IIS 6.0, the properties dialog for a virtual directory is supposed to have
> > 6
> > tabs: Virtual Directory, Documents, Directory Security, HTTP Headers,
> > Custom
> > Errors, and ASPNET. I don't have the ASPnet tab. Is there something I
> > need
> > to do to or configure on IIS to get this tab?
> >
> > I can still deploy reports with RS2000, the ReportServer virtual dir
> > (which
> > functions correctly and I can access) is probably still configured to run
> > on
> > v1.1 while the Reports virtual dir (used by Report Manager) probably got
> > reconfigured and is looking at v2.0. The ASPNet tab has some options
> > where I
> > can configure the virtual directory to point to .Net framework v1.1. Is
> > there a way to do this without having the ASPNet tab?
> >
> > Thanks,
> > Rich
> >
> >
>
>
>
 >> Stay informed about: how to configure virtual directory to use .Net v1.1 instea..