Build error after installing SQLRS2005

Since installing the latest version of Reporting Services side-by-side with
the 2000 version I can't build any of my extensions with the following
error:
fatal error CS0009: Metadata file 'c:\Program Files\Microsoft SQL
Server\90\SDK\Assemblies\Microsoft.ReportingServices.Interfaces.dll' could
not be opened -- 'Version 2.0 is not a compatible version.'
This is not the assembly I have referenced in the project so where is the
redirect happening?Hi James,
Thanks for your post.
From your descriptions, I understood you scenario as below
1. You have installed SQL Server 2000 Reporting Services before, it's OK to
build your extensions.
2. You have upgraded your SQL Server 2000 RS to SQL Server 2005 Reporting
Services, the assembly you refered was redirect to another one and report
the error message
If I have misunderstood your concern, please feel free to point it out.
1. Is it possible for you to complie the assembliy with VS.NET 2005 first?
2. Would you please clarify what is "side-by-side" in your words? Is it
possible for you to let me know the detailed steps?
3. Any more related logs in SQL/Reporting Error Logs?
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Michael,
> From your descriptions, I understood you scenario as below
> 1. You have installed SQL Server 2000 Reporting Services before, it's OK
> to
> build your extensions.
Yes.
> 2. You have upgraded your SQL Server 2000 RS to SQL Server 2005 Reporting
I have installed the Yukon RTM as a new instance called "Yukon" in addition
to the existing RS2000.
> Services, the assembly you refered was redirect to another one and report
> the error message
Yup, I was referring to the interfaces assembly in the RS2000 folder but it
was redirected to the one in the RS2005 SDK folder.
> If I have misunderstood your concern, please feel free to point it out.
> 1. Is it possible for you to complie the assembliy with VS.NET 2005 first?
After upgrading the project it does build in VS2005. However I need it to
build in 2003 because I need a .NET 1.1 assembly...
> 2. Would you please clarify what is "side-by-side" in your words? Is it
> possible for you to let me know the detailed steps?
Side-by-side really means I've installed a new instance of SQL2005 so I can
continue to develop on SQL2000.
> 3. Any more related logs in SQL/Reporting Error Logs?
Nope, this is a build problem not a runtime problem. The error message is
occuring because VS2003 is attempting to load a .NET 2.0 assembly.|||Sorry if this is double posted - the original didn't appear after an hour or
so...
Hi Michael,
> From your descriptions, I understood you scenario as below
> 1. You have installed SQL Server 2000 Reporting Services before, it's OK
> to
> build your extensions.
Yes.
> 2. You have upgraded your SQL Server 2000 RS to SQL Server 2005 Reporting
I have installed the Yukon RTM as a new instance called "Yukon" in addition
to the existing RS2000.
> Services, the assembly you refered was redirect to another one and report
> the error message
Yup, I was referring to the interfaces assembly in the RS2000 folder but it
was redirected to the one in the RS2005 SDK folder.
> If I have misunderstood your concern, please feel free to point it out.
> 1. Is it possible for you to complie the assembliy with VS.NET 2005 first?
After upgrading the project it does build in VS2005. However I need it to
build in 2003 because I need a .NET 1.1 assembly...
> 2. Would you please clarify what is "side-by-side" in your words? Is it
> possible for you to let me know the detailed steps?
Side-by-side really means I've installed a new instance of SQL2005 so I can
continue to develop on SQL2000.
> 3. Any more related logs in SQL/Reporting Error Logs?
Nope, this is a build problem not a runtime problem. The error message is
occuring because VS2003 is attempting to load a .NET 2.0 assembly.
Regards,
James Snape|||Hi James,
Please build the assembly in another machine that has VS.NET 2003 and .NET
1.1 only and then deploy the assembly in your SQL Server 2005 directly.
Make sure the machine has .NET 1.1 installed.
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Michael,
It's not my goal to build the assembly and install on SQL2005. I just have
to develop for both RS2000 and RS2005 which is why that are both installed
on my machine. The project in question is a VS2003 project, the output of
which will be installed in a RS2000 server. The VS2003 project will not
build in this configuration and I can't use 2.0 assemblies inside RS2000.
Regards,
James Snape
"Michael Cheng [MSFT]" <v-mingqc@.online.microsoft.com> wrote in message
news:djwX7pS4FHA.3936@.TK2MSFTNGXA01.phx.gbl...
> Hi James,
> Please build the assembly in another machine that has VS.NET 2003 and .NET
> 1.1 only and then deploy the assembly in your SQL Server 2005 directly.
> Make sure the machine has .NET 1.1 installed.
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||Hi James,
Yes, you cannot use .net 2.0 runtime assembies inside VS.NET 2003/RS2000;
You can only build .net 2.0 runtime with VS.NET 2005. If you want to build
the report with .net 1.1 runtime, you will have to use VS.NET 2003
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to all
Microsoft technology partners in the United States and Canada.
This and other support options are available here:
BCPS:
https://partner.microsoft.com/US/technicalsupport/supportoverview/40010469
Others: https://partner.microsoft.com/US/technicalsupport/supportoverview/
If you are outside the United States, please visit our International
Support page: http://support.microsoft.com/common/international.aspx
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Michael,
I completely agree, but the problem here is that since installing RS2005 my
old references to the RS2000 (1.1) assembly have been redirected to the new
RS2005 (2.0) assembly even though the project hint path points to the
correct (old) location. I just really want to know how to stop the redirect
and make it use the v1.1 assembly.
Regards,
James Snape
"Michael Cheng [MSFT]" <v-mingqc@.online.microsoft.com> wrote in message
news:O8PIC824FHA.1144@.TK2MSFTNGXA01.phx.gbl...
> Hi James,
> Yes, you cannot use .net 2.0 runtime assembies inside VS.NET 2003/RS2000;
> You can only build .net 2.0 runtime with VS.NET 2005. If you want to build
> the report with .net 1.1 runtime, you will have to use VS.NET 2003
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are always here to be of
> assistance!
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================> Business-Critical Phone Support (BCPS) provides you with technical phone
> support at no charge during critical LAN outages or "business down"
> situations. This benefit is available 24 hours a day, 7 days a week to all
> Microsoft technology partners in the United States and Canada.
> This and other support options are available here:
> BCPS:
> https://partner.microsoft.com/US/technicalsupport/supportoverview/40010469
> Others: https://partner.microsoft.com/US/technicalsupport/supportoverview/
> If you are outside the United States, please visit our International
> Support page: http://support.microsoft.com/common/international.aspx
> =====================================================> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||Hi James,
As for which verion of runtime library the .net framework application will
load, if differs according to how the .net managed code is hosted in the
application.
1. If the the application is a pure .net managed application, the CLR host
is the application process it self, then the application will prefer the
class library version which it built with. If that version not available on
target machine, it try loading the latest compatible one.
2. If the .net code is hosted as "Add-in" model, in other word, the
application it self is not a pure .net application, but it load the CLR as
part of its process to run some managed code. In such scenario, the process
by default will load the latest runtime and class library verison. This is
because in such scenario, the host could load multiple such assemblies
which may be built under different versions (so which version should the
application chose?). So for consistency consideration, the application will
load the latest framework no matter the which version the add-in assemblies
were built with.
Based on my understanding, the SQLserver reporting service is rely on the
"ReportingServicesService.exe" process which is a managed application. So
this application's built version also determine all the sequential
assemblies it will load into.
In addition, before your deploying the Reports, please make sure you have
deployed it to the right TargetServer:
Right Click the solution name;
Select Properties;
Make sure you are using SQL Server 2000 RS or SQL Server 2005 RS
Hope helps. Thanks,
Steven Cheng
Microsoft Online Support
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
| From: "James Snape" <jim_snape.at.hotmail.com@.online.nospam>
| References: <uEaHQ043FHA.476@.TK2MSFTNGP15.phx.gbl>
<rjcK#jD4FHA.3220@.TK2MSFTNGXA01.phx.gbl>
<O6QboiG4FHA.1416@.TK2MSFTNGP09.phx.gbl>
<djwX7pS4FHA.3936@.TK2MSFTNGXA01.phx.gbl>
<un6ygiT4FHA.3588@.TK2MSFTNGP15.phx.gbl>
<O8PIC824FHA.1144@.TK2MSFTNGXA01.phx.gbl>
| Subject: Re: Build error after installing SQLRS2005
| Date: Mon, 7 Nov 2005 17:22:31 -0000
| Lines: 51
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2900.2670
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670
| X-RFC2646: Format=Flowed; Original
| Message-ID: <e7V2r$74FHA.3136@.TK2MSFTNGP09.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.reportingsvcs
| NNTP-Posting-Host: ip-213-92-131-1.aramiska-arc.aramiska.net 213.92.131.1
| Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP09.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.reportingsvcs:55896
| X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
|
| Hi Michael,
|
| I completely agree, but the problem here is that since installing RS2005
my
| old references to the RS2000 (1.1) assembly have been redirected to the
new
| RS2005 (2.0) assembly even though the project hint path points to the
| correct (old) location. I just really want to know how to stop the
redirect
| and make it use the v1.1 assembly.
|
| Regards,
| James Snape
|
|
| "Michael Cheng [MSFT]" <v-mingqc@.online.microsoft.com> wrote in message
| news:O8PIC824FHA.1144@.TK2MSFTNGXA01.phx.gbl...
| > Hi James,
| >
| > Yes, you cannot use .net 2.0 runtime assembies inside VS.NET
2003/RS2000;
| > You can only build .net 2.0 runtime with VS.NET 2005. If you want to
build
| > the report with .net 1.1 runtime, you will have to use VS.NET 2003
| >
| > Thank you for your patience and cooperation. If you have any questions
or
| > concerns, don't hesitate to let me know. We are always here to be of
| > assistance!
| >
| >
| > Sincerely yours,
| >
| > Michael Cheng
| > Microsoft Online Partner Support
| >
| > When responding to posts, please "Reply to Group" via your newsreader so
| > that others may learn and benefit from your issue.
| > =====================================================| > Business-Critical Phone Support (BCPS) provides you with technical phone
| > support at no charge during critical LAN outages or "business down"
| > situations. This benefit is available 24 hours a day, 7 days a week to
all
| > Microsoft technology partners in the United States and Canada.
| >
| > This and other support options are available here:
| > BCPS:
| >
https://partner.microsoft.com/US/technicalsupport/supportoverview/40010469
| > Others:
https://partner.microsoft.com/US/technicalsupport/supportoverview/
| >
| > If you are outside the United States, please visit our International
| > Support page: http://support.microsoft.com/common/international.aspx
| > =====================================================| > This posting is provided "AS IS" with no warranties, and confers no
| > rights.
| >
|
|
||||Sorry guys, but you don't seem to get the problem I was trying to describe I
guess I haven't been explicit enough. As it turns out I have solved the
problem by not referencing the assembly in the ReportServer/bin folder but
instead copying it to my .csproj folder and referencing it there. The
redirect doesn't happen and I can now build successfully.
Many thanks
James Snape
"Steven Cheng[MSFT]" <stcheng@.online.microsoft.com> wrote in message
news:HLY6XHE5FHA.3904@.TK2MSFTNGXA01.phx.gbl...
> Hi James,
> As for which verion of runtime library the .net framework application
> will
> load, if differs according to how the .net managed code is hosted in the
> application.
> 1. If the the application is a pure .net managed application, the CLR host
> is the application process it self, then the application will prefer the
> class library version which it built with. If that version not available
> on
> target machine, it try loading the latest compatible one.
> 2. If the .net code is hosted as "Add-in" model, in other word, the
> application it self is not a pure .net application, but it load the CLR as
> part of its process to run some managed code. In such scenario, the
> process
> by default will load the latest runtime and class library verison. This
> is
> because in such scenario, the host could load multiple such assemblies
> which may be built under different versions (so which version should the
> application chose?). So for consistency consideration, the application
> will
> load the latest framework no matter the which version the add-in
> assemblies
> were built with.
> Based on my understanding, the SQLserver reporting service is rely on the
> "ReportingServicesService.exe" process which is a managed application. So
> this application's built version also determine all the sequential
> assemblies it will load into.
>
> In addition, before your deploying the Reports, please make sure you have
> deployed it to the right TargetServer:
> Right Click the solution name;
> Select Properties;
> Make sure you are using SQL Server 2000 RS or SQL Server 2005 RS
> Hope helps. Thanks,
> Steven Cheng
> Microsoft Online Support
> Get Secure! www.microsoft.com/security
> (This posting is provided "AS IS", with no warranties, and confers no
> rights.)
>
>
> --
> | From: "James Snape" <jim_snape.at.hotmail.com@.online.nospam>
> | References: <uEaHQ043FHA.476@.TK2MSFTNGP15.phx.gbl>
> <rjcK#jD4FHA.3220@.TK2MSFTNGXA01.phx.gbl>
> <O6QboiG4FHA.1416@.TK2MSFTNGP09.phx.gbl>
> <djwX7pS4FHA.3936@.TK2MSFTNGXA01.phx.gbl>
> <un6ygiT4FHA.3588@.TK2MSFTNGP15.phx.gbl>
> <O8PIC824FHA.1144@.TK2MSFTNGXA01.phx.gbl>
> | Subject: Re: Build error after installing SQLRS2005
> | Date: Mon, 7 Nov 2005 17:22:31 -0000
> | Lines: 51
> | X-Priority: 3
> | X-MSMail-Priority: Normal
> | X-Newsreader: Microsoft Outlook Express 6.00.2900.2670
> | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670
> | X-RFC2646: Format=Flowed; Original
> | Message-ID: <e7V2r$74FHA.3136@.TK2MSFTNGP09.phx.gbl>
> | Newsgroups: microsoft.public.sqlserver.reportingsvcs
> | NNTP-Posting-Host: ip-213-92-131-1.aramiska-arc.aramiska.net
> 213.92.131.1
> | Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP09.phx.gbl
> | Xref: TK2MSFTNGXA01.phx.gbl
> microsoft.public.sqlserver.reportingsvcs:55896
> | X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
> |
> | Hi Michael,
> |
> | I completely agree, but the problem here is that since installing RS2005
> my
> | old references to the RS2000 (1.1) assembly have been redirected to the
> new
> | RS2005 (2.0) assembly even though the project hint path points to the
> | correct (old) location. I just really want to know how to stop the
> redirect
> | and make it use the v1.1 assembly.
> |
> | Regards,
> | James Snape
> |
> |
> | "Michael Cheng [MSFT]" <v-mingqc@.online.microsoft.com> wrote in message
> | news:O8PIC824FHA.1144@.TK2MSFTNGXA01.phx.gbl...
> | > Hi James,
> | >
> | > Yes, you cannot use .net 2.0 runtime assembies inside VS.NET
> 2003/RS2000;
> | > You can only build .net 2.0 runtime with VS.NET 2005. If you want to
> build
> | > the report with .net 1.1 runtime, you will have to use VS.NET 2003
> | >
> | > Thank you for your patience and cooperation. If you have any questions
> or
> | > concerns, don't hesitate to let me know. We are always here to be of
> | > assistance!
> | >
> | >
> | > Sincerely yours,
> | >
> | > Michael Cheng
> | > Microsoft Online Partner Support
> | >
> | > When responding to posts, please "Reply to Group" via your newsreader
> so
> | > that others may learn and benefit from your issue.
> | > =====================================================> | > Business-Critical Phone Support (BCPS) provides you with technical
> phone
> | > support at no charge during critical LAN outages or "business down"
> | > situations. This benefit is available 24 hours a day, 7 days a week to
> all
> | > Microsoft technology partners in the United States and Canada.
> | >
> | > This and other support options are available here:
> | > BCPS:
> | >
> https://partner.microsoft.com/US/technicalsupport/supportoverview/40010469
> | > Others:
> https://partner.microsoft.com/US/technicalsupport/supportoverview/
> | >
> | > If you are outside the United States, please visit our International
> | > Support page: http://support.microsoft.com/common/international.aspx
> | > =====================================================> | > This posting is provided "AS IS" with no warranties, and confers no
> | > rights.
> | >
> |
> |
> |
>|||Hi James,
Sorry for the misunderstanding and it's great to hear you have resolved it
by copying the assembly to your project folder.
Anyway, thanks so much for sharing this with us.
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.