.Net Framework 2.0 and Reporting Services

When I installed 2.0 on the Web Server Reporting Services stopped working
properly. Is it possible to run them side by side. The server also has 1.1
running.
ThanksOn Fri, 25 Mar 2005 04:59:02 -0800, DJONES
<DJONES@.discussions.microsoft.com> wrote:
>When I installed 2.0 on the Web Server Reporting Services stopped working
>properly. Is it possible to run them side by side. The server also has 1.1
>running.
>Thanks
In theory,
When .NET Framework 2.0 reaches RTM it is supposed to be possible to
run them side by side without problem.
In practice, in the short term, there are assorted issues.
Why do you have .NET Framework 2.0 on your Web server? Which build?
Andrew Watt
MVP - InfoPath|||Thanks for the reply...
I'm working on the Proof of Concept phase of a project using 2.0. I wonder
if it would work with VS loaded on the Web Server instead...
"Andrew Watt [MVP - InfoPath]" wrote:
> On Fri, 25 Mar 2005 04:59:02 -0800, DJONES
> <DJONES@.discussions.microsoft.com> wrote:
> >When I installed 2.0 on the Web Server Reporting Services stopped working
> >properly. Is it possible to run them side by side. The server also has 1.1
> >running.
> >
> >Thanks
> In theory,
> When .NET Framework 2.0 reaches RTM it is supposed to be possible to
> run them side by side without problem.
> In practice, in the short term, there are assorted issues.
> Why do you have .NET Framework 2.0 on your Web server? Which build?
> Andrew Watt
> MVP - InfoPath
>|||I would suggest that the best thing is to ask your question (with a
more detailed description of your situation) on the Reporting Services
2005 NG. It's called microsoft.private.sqlserver2005.reportingsvcs.
Despite its name it's public.
You will see me there too. But I like to leave the pain of version
incompatibilities to others - so at this stage I only install one
version of SQL Server 2005 on a machine. Some of the others on that
group may have a solution to your situation though.
I would expect Visual Studio 2005 to cause you the same problem -
since it too will install .NET Framework 2.0.
Andrew Watt
MVP - InfoPath
On Fri, 25 Mar 2005 07:15:03 -0800, DJONES
<DJONES@.discussions.microsoft.com> wrote:
>Thanks for the reply...
>I'm working on the Proof of Concept phase of a project using 2.0. I wonder
>if it would work with VS loaded on the Web Server instead...
>"Andrew Watt [MVP - InfoPath]" wrote:
>> On Fri, 25 Mar 2005 04:59:02 -0800, DJONES
>> <DJONES@.discussions.microsoft.com> wrote:
>> >When I installed 2.0 on the Web Server Reporting Services stopped working
>> >properly. Is it possible to run them side by side. The server also has 1.1
>> >running.
>> >
>> >Thanks
>> In theory,
>> When .NET Framework 2.0 reaches RTM it is supposed to be possible to
>> run them side by side without problem.
>> In practice, in the short term, there are assorted issues.
>> Why do you have .NET Framework 2.0 on your Web server? Which build?
>> Andrew Watt
>> MVP - InfoPath|||We have similar situation - fix was two-fold, all done in IIS.
First, create an applicaton pool specifically for the two reporting
services applications, then set the properties of each application to
use that pool. Applications using different frameworks cannot "swim in
the same pool".
Second, ensure that the reporting services applications are configured
to use the 1.1 framework and not the 2.0 - the tedious way is to check
(and change, if needed) every mapping through the IIS properties pages.
The faster way is to use the command line applications to do this
configuration - but I think injudicious use of the command line can
remap all the applications at once - which could be what happened when
you installed the 2.0 framework.|||The command line tool aspnet_regiis has options to check the current script
mappings and to install certain versions for a particular virtual root only
rather than all virtual roots:
aspnet_regiis -lk
aspnet_regiis -s <path>
Make sure to run the aspnet_regiis.exe from the correct version directory
under \Windows\Microsoft.Net\Framework
-- Robert
This posting is provided "AS IS" with no warranties, and confers no rights.
"Parker" <psmith@.iquest.net> wrote in message
news:1112015101.606172.149480@.g14g2000cwa.googlegroups.com...
> We have similar situation - fix was two-fold, all done in IIS.
> First, create an applicaton pool specifically for the two reporting
> services applications, then set the properties of each application to
> use that pool. Applications using different frameworks cannot "swim in
> the same pool".
> Second, ensure that the reporting services applications are configured
> to use the 1.1 framework and not the 2.0 - the tedious way is to check
> (and change, if needed) every mapping through the IIS properties pages.
> The faster way is to use the command line applications to do this
> configuration - but I think injudicious use of the command line can
> remap all the applications at once - which could be what happened when
> you installed the 2.0 framework.
>