how to configure RS2000 to use .Net framework 1.1 from 2.0?

Good morning,
This is a continuation post about a problem I am having where I can't open
Report Manager. Here is my scenario - win2003 server running Sql Server 2000
Sp4, RS2000. We were on .Net framework 1.1 but upgraded this last year to
.Net framework 2.0 so we could use Visual Studio 2005. We still have Visual
Studio 2003 so that we can use RS2000 designer. I can deploy reports OK, but
I can't open Report manager - keep gettting varoius HTTP errors, 401, 403. I
got one error that said the Webpage (for Report Manager) was looking for .Net
Framework 1.1 and couldn't find it).
I looked at IIS at the Reports Virtual Dir and the VirtualDir
tabl/Configuration dialog - the application extensions window has all the
extensions looing at .Net Framwork 1.1 which I presume is why I can still
deploy reports. But on the ReportServer virtual dir in the configuration
dialog - the application extensions window is empty, but the Wildcard
Application Extension window has this path:
C:\Windows\Microsoft.Net\Framework\v1.1.4322\aspnet_isapi.dll
In the Reports virtual dir/configuration/application extensions window, the
.aspx extension points to the same path as above. Do I need to add an
extension as above to the the application Extensions window in the
configuration dialog for the ReportServer virtual dir so that Report Manger
page can run correctly?
Thanks,
RichHere is something interesting:
On the server I typed http://localhost/reportserver
and I got a directory listing of all the dirs on the report server and was
able to invoke reports directly from here. But when I type
http://localhost/reports
I get the message that the website declined to show this webpage - http
error 403 - IE can connect to the website but doesn't have permission to view
the page. Does anyone know what the difference is between the ReportServer
virtual dir and the Reports Virtual dir?
"Rich" wrote:
> Good morning,
> This is a continuation post about a problem I am having where I can't open
> Report Manager. Here is my scenario - win2003 server running Sql Server 2000
> Sp4, RS2000. We were on .Net framework 1.1 but upgraded this last year to
> .Net framework 2.0 so we could use Visual Studio 2005. We still have Visual
> Studio 2003 so that we can use RS2000 designer. I can deploy reports OK, but
> I can't open Report manager - keep gettting varoius HTTP errors, 401, 403. I
> got one error that said the Webpage (for Report Manager) was looking for .Net
> Framework 1.1 and couldn't find it).
> I looked at IIS at the Reports Virtual Dir and the VirtualDir
> tabl/Configuration dialog - the application extensions window has all the
> extensions looing at .Net Framwork 1.1 which I presume is why I can still
> deploy reports. But on the ReportServer virtual dir in the configuration
> dialog - the application extensions window is empty, but the Wildcard
> Application Extension window has this path:
> C:\Windows\Microsoft.Net\Framework\v1.1.4322\aspnet_isapi.dll
> In the Reports virtual dir/configuration/application extensions window, the
> .aspx extension points to the same path as above. Do I need to add an
> extension as above to the the application Extensions window in the
> configuration dialog for the ReportServer virtual dir so that Report Manger
> page can run correctly?
> Thanks,
> Rich
>|||As I mentioned in one of my last postings to you, I thought it was weird
that you could deploy. My thought being that reportserver website might be
at 1.1 and reports being at 2.0 framework.
Report Manager (reports website) is a portal to Reporting Services. It is
just an asp.net application that integrates with ReportServer website/app.
Some people do their own front ends and do not even use Report Manager. In
RS 2000 Report Manager integrates using URL integration with ReportServer.
In RS 2005 it uses webservices to integrate.
On your server open up IIS Manager. Click on each website, right mouse
click, properties, ASP.Net tab. See if 1.1 or 2.0 and make sure both Reports
and ReportServer are 1.1
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Rich" <Rich@.discussions.microsoft.com> wrote in message
news:177B4114-7F1A-459A-ACEE-8BF497DE2BD5@.microsoft.com...
> Here is something interesting:
> On the server I typed http://localhost/reportserver
> and I got a directory listing of all the dirs on the report server and was
> able to invoke reports directly from here. But when I type
> http://localhost/reports
> I get the message that the website declined to show this webpage - http
> error 403 - IE can connect to the website but doesn't have permission to
> view
> the page. Does anyone know what the difference is between the
> ReportServer
> virtual dir and the Reports Virtual dir?
> "Rich" wrote:
>> Good morning,
>> This is a continuation post about a problem I am having where I can't
>> open
>> Report Manager. Here is my scenario - win2003 server running Sql Server
>> 2000
>> Sp4, RS2000. We were on .Net framework 1.1 but upgraded this last year
>> to
>> .Net framework 2.0 so we could use Visual Studio 2005. We still have
>> Visual
>> Studio 2003 so that we can use RS2000 designer. I can deploy reports OK,
>> but
>> I can't open Report manager - keep gettting varoius HTTP errors, 401,
>> 403. I
>> got one error that said the Webpage (for Report Manager) was looking for
>> .Net
>> Framework 1.1 and couldn't find it).
>> I looked at IIS at the Reports Virtual Dir and the VirtualDir
>> tabl/Configuration dialog - the application extensions window has all the
>> extensions looing at .Net Framwork 1.1 which I presume is why I can still
>> deploy reports. But on the ReportServer virtual dir in the configuration
>> dialog - the application extensions window is empty, but the Wildcard
>> Application Extension window has this path:
>> C:\Windows\Microsoft.Net\Framework\v1.1.4322\aspnet_isapi.dll
>> In the Reports virtual dir/configuration/application extensions window,
>> the
>> .aspx extension points to the same path as above. Do I need to add an
>> extension as above to the the application Extensions window in the
>> configuration dialog for the ReportServer virtual dir so that Report
>> Manger
>> page can run correctly?
>> Thanks,
>> Rich|||Hi Bruce,
Thank you again for getting back to me on this (and I appologize in advance
for being a bonehead, but unfortunately I am one - right now). When I open
up IIS Manager I go to Websites/Default Website/Reports. I right click on
Reports/select properties. In this dialog I have 5 tabs - Virtual Directory,
Documents, Directory Security, HTTP Headers, Custom Errors. I clicked around
looking for a tab/button for ASP.Net, but did not locate anything.
Quick note: from my workstation if I type http://myserver/reportserver --
I can get a directory listing of all the dirs on the report server, I can
even run reports directly from that page. But if I type
http://myserver/Reports -- now I get a message that content listing is not
permitted from this site. It must be a configuration thing. What I lack in
braincells I compenste for with perseverence. What to configure?
Thank you for your patience and helping me out.
Rich
"Bruce L-C [MVP]" wrote:
> As I mentioned in one of my last postings to you, I thought it was weird
> that you could deploy. My thought being that reportserver website might be
> at 1.1 and reports being at 2.0 framework.
> Report Manager (reports website) is a portal to Reporting Services. It is
> just an asp.net application that integrates with ReportServer website/app.
> Some people do their own front ends and do not even use Report Manager. In
> RS 2000 Report Manager integrates using URL integration with ReportServer.
> In RS 2005 it uses webservices to integrate.
> On your server open up IIS Manager. Click on each website, right mouse
> click, properties, ASP.Net tab. See if 1.1 or 2.0 and make sure both Reports
> and ReportServer are 1.1
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Rich" <Rich@.discussions.microsoft.com> wrote in message
> news:177B4114-7F1A-459A-ACEE-8BF497DE2BD5@.microsoft.com...
> > Here is something interesting:
> >
> > On the server I typed http://localhost/reportserver
> >
> > and I got a directory listing of all the dirs on the report server and was
> > able to invoke reports directly from here. But when I type
> > http://localhost/reports
> >
> > I get the message that the website declined to show this webpage - http
> > error 403 - IE can connect to the website but doesn't have permission to
> > view
> > the page. Does anyone know what the difference is between the
> > ReportServer
> > virtual dir and the Reports Virtual dir?
> >
> > "Rich" wrote:
> >
> >> Good morning,
> >>
> >> This is a continuation post about a problem I am having where I can't
> >> open
> >> Report Manager. Here is my scenario - win2003 server running Sql Server
> >> 2000
> >> Sp4, RS2000. We were on .Net framework 1.1 but upgraded this last year
> >> to
> >> .Net framework 2.0 so we could use Visual Studio 2005. We still have
> >> Visual
> >> Studio 2003 so that we can use RS2000 designer. I can deploy reports OK,
> >> but
> >> I can't open Report manager - keep gettting varoius HTTP errors, 401,
> >> 403. I
> >> got one error that said the Webpage (for Report Manager) was looking for
> >> .Net
> >> Framework 1.1 and couldn't find it).
> >>
> >> I looked at IIS at the Reports Virtual Dir and the VirtualDir
> >> tabl/Configuration dialog - the application extensions window has all the
> >> extensions looing at .Net Framwork 1.1 which I presume is why I can still
> >> deploy reports. But on the ReportServer virtual dir in the configuration
> >> dialog - the application extensions window is empty, but the Wildcard
> >> Application Extension window has this path:
> >>
> >> C:\Windows\Microsoft.Net\Framework\v1.1.4322\aspnet_isapi.dll
> >>
> >> In the Reports virtual dir/configuration/application extensions window,
> >> the
> >> .aspx extension points to the same path as above. Do I need to add an
> >> extension as above to the the application Extensions window in the
> >> configuration dialog for the ReportServer virtual dir so that Report
> >> Manger
> >> page can run correctly?
> >>
> >> Thanks,
> >> Rich
> >>
>
>|||Don't know if this is of any consequence, but I was looking at Global.asax,
web.config... for each of the directories - Reports and ReportServer from
IIS. I was able to browse all the config files in ReportServer dir, but I
was not able to browse any of the config files or home.aspx from the Reports
dir. Would this have any bearing on anthing?
"Rich" wrote:
> Hi Bruce,
> Thank you again for getting back to me on this (and I appologize in advance
> for being a bonehead, but unfortunately I am one - right now). When I open
> up IIS Manager I go to Websites/Default Website/Reports. I right click on
> Reports/select properties. In this dialog I have 5 tabs - Virtual Directory,
> Documents, Directory Security, HTTP Headers, Custom Errors. I clicked around
> looking for a tab/button for ASP.Net, but did not locate anything.
> Quick note: from my workstation if I type http://myserver/reportserver --
> I can get a directory listing of all the dirs on the report server, I can
> even run reports directly from that page. But if I type
> http://myserver/Reports -- now I get a message that content listing is not
> permitted from this site. It must be a configuration thing. What I lack in
> braincells I compenste for with perseverence. What to configure?
> Thank you for your patience and helping me out.
> Rich
> "Bruce L-C [MVP]" wrote:
> > As I mentioned in one of my last postings to you, I thought it was weird
> > that you could deploy. My thought being that reportserver website might be
> > at 1.1 and reports being at 2.0 framework.
> >
> > Report Manager (reports website) is a portal to Reporting Services. It is
> > just an asp.net application that integrates with ReportServer website/app.
> > Some people do their own front ends and do not even use Report Manager. In
> > RS 2000 Report Manager integrates using URL integration with ReportServer.
> > In RS 2005 it uses webservices to integrate.
> >
> > On your server open up IIS Manager. Click on each website, right mouse
> > click, properties, ASP.Net tab. See if 1.1 or 2.0 and make sure both Reports
> > and ReportServer are 1.1
> >
> >
> > --
> > Bruce Loehle-Conger
> > MVP SQL Server Reporting Services
> >
> > "Rich" <Rich@.discussions.microsoft.com> wrote in message
> > news:177B4114-7F1A-459A-ACEE-8BF497DE2BD5@.microsoft.com...
> > > Here is something interesting:
> > >
> > > On the server I typed http://localhost/reportserver
> > >
> > > and I got a directory listing of all the dirs on the report server and was
> > > able to invoke reports directly from here. But when I type
> > > http://localhost/reports
> > >
> > > I get the message that the website declined to show this webpage - http
> > > error 403 - IE can connect to the website but doesn't have permission to
> > > view
> > > the page. Does anyone know what the difference is between the
> > > ReportServer
> > > virtual dir and the Reports Virtual dir?
> > >
> > > "Rich" wrote:
> > >
> > >> Good morning,
> > >>
> > >> This is a continuation post about a problem I am having where I can't
> > >> open
> > >> Report Manager. Here is my scenario - win2003 server running Sql Server
> > >> 2000
> > >> Sp4, RS2000. We were on .Net framework 1.1 but upgraded this last year
> > >> to
> > >> .Net framework 2.0 so we could use Visual Studio 2005. We still have
> > >> Visual
> > >> Studio 2003 so that we can use RS2000 designer. I can deploy reports OK,
> > >> but
> > >> I can't open Report manager - keep gettting varoius HTTP errors, 401,
> > >> 403. I
> > >> got one error that said the Webpage (for Report Manager) was looking for
> > >> .Net
> > >> Framework 1.1 and couldn't find it).
> > >>
> > >> I looked at IIS at the Reports Virtual Dir and the VirtualDir
> > >> tabl/Configuration dialog - the application extensions window has all the
> > >> extensions looing at .Net Framwork 1.1 which I presume is why I can still
> > >> deploy reports. But on the ReportServer virtual dir in the configuration
> > >> dialog - the application extensions window is empty, but the Wildcard
> > >> Application Extension window has this path:
> > >>
> > >> C:\Windows\Microsoft.Net\Framework\v1.1.4322\aspnet_isapi.dll
> > >>
> > >> In the Reports virtual dir/configuration/application extensions window,
> > >> the
> > >> .aspx extension points to the same path as above. Do I need to add an
> > >> extension as above to the the application Extensions window in the
> > >> configuration dialog for the ReportServer virtual dir so that Report
> > >> Manger
> > >> page can run correctly?
> > >>
> > >> Thanks,
> > >> Rich
> > >>
> >
> >
> >|||My stress factor has just increased a few points. From IIS
Manager/Help/About it says that I have version 6 also. But I only see 5 tabs
when I right-click on a virtual directory/properties. I guess I am on my
own. Something was obviously not configured during the install of this
server (win2003/IIS/RS...), and I am not quite at the network admin level at
this time to figure this stuff out. Hmmm :(
Well, I have learned a few things, about things that are wrong/incorrect
with my system. And I thank you for mentoring me. I will give this my best
shot and post back if I get any positive results.
Rich
"Bruce L-C [MVP]" wrote:
> I don't know what to tell you. I have 6 tabs, not 5. The 5 you mention and
> then asp.net. My IIS version is version 6.
> I'm afraid you might have more than one thing going on.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Rich" <Rich@.discussions.microsoft.com> wrote in message
> news:351DE8CA-E510-4D78-A8DB-3950BD317190@.microsoft.com...
> > Hi Bruce,
> >
> > Thank you again for getting back to me on this (and I appologize in
> > advance
> > for being a bonehead, but unfortunately I am one - right now). When I
> > open
> > up IIS Manager I go to Websites/Default Website/Reports. I right click on
> > Reports/select properties. In this dialog I have 5 tabs - Virtual
> > Directory,
> > Documents, Directory Security, HTTP Headers, Custom Errors. I clicked
> > around
> > looking for a tab/button for ASP.Net, but did not locate anything.
> >
> > Quick note: from my workstation if I type
> > http://myserver/reportserver --
> > I can get a directory listing of all the dirs on the report server, I can
> > even run reports directly from that page. But if I type
> > http://myserver/Reports -- now I get a message that content listing is
> > not
> > permitted from this site. It must be a configuration thing. What I lack
> > in
> > braincells I compenste for with perseverence. What to configure?
> >
> > Thank you for your patience and helping me out.
> >
> > Rich
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> As I mentioned in one of my last postings to you, I thought it was weird
> >> that you could deploy. My thought being that reportserver website might
> >> be
> >> at 1.1 and reports being at 2.0 framework.
> >>
> >> Report Manager (reports website) is a portal to Reporting Services. It is
> >> just an asp.net application that integrates with ReportServer
> >> website/app.
> >> Some people do their own front ends and do not even use Report Manager.
> >> In
> >> RS 2000 Report Manager integrates using URL integration with
> >> ReportServer.
> >> In RS 2005 it uses webservices to integrate.
> >>
> >> On your server open up IIS Manager. Click on each website, right mouse
> >> click, properties, ASP.Net tab. See if 1.1 or 2.0 and make sure both
> >> Reports
> >> and ReportServer are 1.1
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "Rich" <Rich@.discussions.microsoft.com> wrote in message
> >> news:177B4114-7F1A-459A-ACEE-8BF497DE2BD5@.microsoft.com...
> >> > Here is something interesting:
> >> >
> >> > On the server I typed http://localhost/reportserver
> >> >
> >> > and I got a directory listing of all the dirs on the report server and
> >> > was
> >> > able to invoke reports directly from here. But when I type
> >> > http://localhost/reports
> >> >
> >> > I get the message that the website declined to show this webpage - http
> >> > error 403 - IE can connect to the website but doesn't have permission
> >> > to
> >> > view
> >> > the page. Does anyone know what the difference is between the
> >> > ReportServer
> >> > virtual dir and the Reports Virtual dir?
> >> >
> >> > "Rich" wrote:
> >> >
> >> >> Good morning,
> >> >>
> >> >> This is a continuation post about a problem I am having where I can't
> >> >> open
> >> >> Report Manager. Here is my scenario - win2003 server running Sql
> >> >> Server
> >> >> 2000
> >> >> Sp4, RS2000. We were on .Net framework 1.1 but upgraded this last
> >> >> year
> >> >> to
> >> >> .Net framework 2.0 so we could use Visual Studio 2005. We still have
> >> >> Visual
> >> >> Studio 2003 so that we can use RS2000 designer. I can deploy reports
> >> >> OK,
> >> >> but
> >> >> I can't open Report manager - keep gettting varoius HTTP errors, 401,
> >> >> 403. I
> >> >> got one error that said the Webpage (for Report Manager) was looking
> >> >> for
> >> >> .Net
> >> >> Framework 1.1 and couldn't find it).
> >> >>
> >> >> I looked at IIS at the Reports Virtual Dir and the VirtualDir
> >> >> tabl/Configuration dialog - the application extensions window has all
> >> >> the
> >> >> extensions looing at .Net Framwork 1.1 which I presume is why I can
> >> >> still
> >> >> deploy reports. But on the ReportServer virtual dir in the
> >> >> configuration
> >> >> dialog - the application extensions window is empty, but the Wildcard
> >> >> Application Extension window has this path:
> >> >>
> >> >> C:\Windows\Microsoft.Net\Framework\v1.1.4322\aspnet_isapi.dll
> >> >>
> >> >> In the Reports virtual dir/configuration/application extensions
> >> >> window,
> >> >> the
> >> >> .aspx extension points to the same path as above. Do I need to add an
> >> >> extension as above to the the application Extensions window in the
> >> >> configuration dialog for the ReportServer virtual dir so that Report
> >> >> Manger
> >> >> page can run correctly?
> >> >>
> >> >> Thanks,
> >> >> Rich
> >> >>
> >>
> >>
> >>
>
>