Search

SQL 2008 R2 Nov CTP - Management Studio Reports Fail on Opening by Kurt Moskal

Closed
as Fixed Help for as Fixed

4
0
Sign in
 to vote
Type: Bug
ID: 523972
Opened: 1/8/2010 12:33:33 PM
Access Restriction: Public
1
Workaround(s)
3
User(s) can reproduce this bug
I installed SQL Server 2008 R2 Nov. CTP on a W2K8 R2 server. I then installed only the SQL Management Studio on another W2K8 R2 server. From both servers, when I try to run any Management Studio report, I receive a pop-up window stating "The file 'Microsoft.ReportViewer.WinForms, Version=9.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' cannot be opened. Do you want to remove the reference to it from the Recent list?

There are Yes/No buttons, regardless of which button I press nothing good happens.
Details (expand)
Product Language
English

Version

SQL Server 2008 R2 November CTP

Category

Tools (SSMS, Agent, Profiler, etc.)

Operating System

Windows Server 2008 R2
Operating System Language
US English
Steps to Reproduce
Install SQL Server 2008 R2 CTP (Nov) on a W2K8 server, Installed SQL Server database services and all the client tools. No Reporting Services, No Integration Services, No Analysis Services

Install only SQL Server 2008 R2 CTP (Nov) on a second W2K8 server. Installed only the client tools (Management Studio).

W2K8 is x64.
Actual Results
When I run any report from Management studio, I get the following message box with a Yes/No buttons.

"The file 'Microsoft.ReportViewer.WinForms, Version=9.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' cannot be opened. Do you want to remove the reference to it from the Recent list?"

This message box apears on both the server with the database engine and on the server with just the management tools
Expected Results
Reports should work.

Platform

X64
File Attachments
0 attachments
Sign in to post a comment.
Posted by CuckooSQL on 10/25/2011 at 8:36 AM
I have just upgraded my client tools (no server components) from SQL2008 RTM to SP3 and get the identical error. Since the problem was raised on this thread months ago, it is distressing that MS are careless to not fix in the SP3 (supposedly fully QA'ed). Bad Microsoft!
Posted by SheaButta on 3/25/2011 at 5:56 AM
Hi Microsoft:

What is the recommended workaround if you are at SQL Server 2008 SP2 and have no plans of upgrading to SQL 2008 R2 in the near future ? I just upgraded over 40 servers to SQL 2008 SP2 and I'm looking for the best and fastest option without any downtime.

Thanks.
Posted by Microsoft on 4/5/2010 at 12:31 PM
Hi Kurt,
    Just to let you know, this should be fixed with the SQL Server 2008 R2 final release.
Thank you,
Bill Ramos
Posted by DevilzOk on 1/22/2010 at 11:39 AM
Currently we are seeing the same issues in R1 - is there a fix that will be part of a CU or SP to resolve this issue?

We are running R1 SP1 CU 4.
Posted by Kurt Moskal on 1/11/2010 at 7:11 AM
Thanks for the workaround info. I do hope that this is fixed by RTM. I would be a fairly large issue having to install MSRS on all the database instances just to run reports.
Posted by Microsoft on 1/8/2010 at 9:53 PM
Hi There, this is a known issue that we expect to have fixed for RTM. In the mean time you can workaround this issue by downloading and installing the Reporting Services Report Viewer 9.0. You can download this package from the Microsoft Download Center or by using the following link: http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=6ae0aa19-3e6c-474c-9d57-05b2347456b1

Thanks,
Dan
Sign in to post a workaround.
Posted by AlunJ on 10/5/2010 at 1:39 AM
From MS

There, this is a known issue that we expect to have fixed for RTM. In the mean time you can workaround this issue by downloading and installing the Reporting Services Report Viewer 9.0. You can download this package from the Microsoft Download Center or by using the following link: http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=6ae0aa19-3e6c-474c-9d57-05b2347456b1

© 2013 Microsoft Corporation. All rights reserved. Microsoft Connect Terms of Use | Trademarks | Privacy Statement