Cannot run SRS 2000 and WSS3 on same server

I have a single Win2k3 server that was running SQL2000, SQL Reporting
Services 2000, and Windows SharePoint Services 2.
I upgraded the WSS2 to WSS3. When I try to navigate to http://myserver/Reports
I get an error "Server Error in /Reports Application". With the error
message Unrecognized attribute 'Type'. The source error has this line
highlighted...
<sectionGroup name="System.Workflow.ComponentModel.WorkflowCompiler"
type="System.Workflow.ComponentModel.Compiler.WorkflowCompilerConfigurationSectionGroup,
System.Workflow.ComponentModel, Version=3.0.0.0, Culture=neutral,
PublicKeyToken=31bf3856ad364e35">
The source file identified in the error is c:\inetpub\wwwroot
\web.config
I assumed that the Reports application couldn't understand the
web.config entry because it now included Freamework v2 information.
The first thing that I tried was to change the ASP.Net settings in IIS
for Reports and ReportServer to v2.
Now when I navigate to http://myserver/Reports the reports I can see
the reports listed properly. But, when I try to execute a report I
get the following Reporting Services Error...
Failed to load expression host assembly. Details: StrongName cannot
have an empty string for the assembly name. (rsProcessingError)
>From looking at other postings it appears that this error is due to me
setting the Reports and ReportServer applications to ASP.Net v2.
So, I am stuck. If I set the applications to v2 I can see the site
but cannot run the reports. If I set te applications to v1.1 then I
cannot see the site at all.
Is there are way to allow Reporting Services 2000 to exist with WSS3?
Thanks for your help
IANI suggest you read through this article about "Troubleshooting a
Side-by-Side Installation of Reporting Services and Windows SharePoint
Services"
http://msdn2.microsoft.com/en-us/library/aa179370(SQL.80).aspx
It refers to RS 2000 and WSS 2.0, but it might give you some clues as how to
set it up. I'm not sure if you can exclude sites in WSS 3.0 though, so you
might have to move the RS virtual directories to their own web site, at
least to create a new web application, to make sure you can change which
.NET framework they use.
Hope this gives you something to work with.
Kaisa M. Lindahl Lervik
<iani4profit@.gmail.com> wrote in message
news:1173135063.253461.175400@.j27g2000cwj.googlegroups.com...
>I have a single Win2k3 server that was running SQL2000, SQL Reporting
> Services 2000, and Windows SharePoint Services 2.
> I upgraded the WSS2 to WSS3. When I try to navigate to
> http://myserver/Reports
> I get an error "Server Error in /Reports Application". With the error
> message Unrecognized attribute 'Type'. The source error has this line
> highlighted...
> <sectionGroup name="System.Workflow.ComponentModel.WorkflowCompiler"
> type="System.Workflow.ComponentModel.Compiler.WorkflowCompilerConfigurationSectionGroup,
> System.Workflow.ComponentModel, Version=3.0.0.0, Culture=neutral,
> PublicKeyToken=31bf3856ad364e35">
> The source file identified in the error is c:\inetpub\wwwroot
> \web.config
> I assumed that the Reports application couldn't understand the
> web.config entry because it now included Freamework v2 information.
> The first thing that I tried was to change the ASP.Net settings in IIS
> for Reports and ReportServer to v2.
> Now when I navigate to http://myserver/Reports the reports I can see
> the reports listed properly. But, when I try to execute a report I
> get the following Reporting Services Error...
> Failed to load expression host assembly. Details: StrongName cannot
> have an empty string for the assembly name. (rsProcessingError)
>>From looking at other postings it appears that this error is due to me
> setting the Reports and ReportServer applications to ASP.Net v2.
> So, I am stuck. If I set the applications to v2 I can see the site
> but cannot run the reports. If I set te applications to v1.1 then I
> cannot see the site at all.
> Is there are way to allow Reporting Services 2000 to exist with WSS3?
> Thanks for your help
> IAN
>|||WSS3 does not have the "exclude sites" functionality any more.
My short term (hopefully) solution is to host the report sites on a
new site that is unrelated to SharePoint. The bad part is that I will
need to update all of the links to the various reports throughout my
web sites, etc.
Thanks for your feedback.
IAN