September 27, 2009 at 11:17 am
Hi,
I went through the below link and I have couple of questions:
http://blogs.msdn.com/brianhartman/archive/2008/11/05/client-print-fails-to-load-after-microsoft-update-956391.aspx
What do you need to download?
To get to a working state, you will need to do the following:
Update your report server to distribute the updated client print control.
Update your ReportViewer redistributable so that it references the new CLSID. The ReportViewer 2008 redistributable also includes an updated client print control for use in local mode.
Update Visual Studio. This is for the same reason as the redistributable. The ReportViewer is installed with Visual Studio for design time.
Update your Reporting Services SharePoint Add-In if you are using the report server in SharePoint integrated mode.
Below is a list of available updates (also available from MS08-052):
SQL Server 2000: http://www.microsoft.com/downloads/details.aspx?familyid=5F9E7F78-7439-414B-A9DC-A779B89427DB
SQL Server 2005: http://www.microsoft.com/downloads/details.aspx?familyid=5148B887-F323-4ADB-9721-61E1C0CFD213
Visual Studio 2005: http://www.microsoft.com/downloads/details.aspx?familyid=A7BF790B-3249-4EE8-9440-FA911EBBC08A
Visual Studio 2008: http://www.microsoft.com/downloads/details.aspx?familyid=A8C80B29-6D00-4949-A005-5D706122919A
Report Viewer 2005 Redistributable: http://www.microsoft.com/downloads/details.aspx?familyid=82833F27-081D-4B72-83EF-2836360A904D
Report Viewer 2008 Redistributable: http://www.microsoft.com/downloads/details.aspx?familyid=6AE0AA19-3E6C-474C-9D57-05B2347456B1
Visual Studio 2005: http://www.microsoft.com/downloads/details.aspx?familyid=A7BF790B-3249-4EE8-9440-FA911EBBC08A
Q: I have verified the Visual Studio version on My report server by going to add remove programs. It is as below
Microsoft Visual Studio 2005 premier partner edition -ENU
That means, Do I need to install Visual Studio 2005 Service Pack 1 GDIPLUS.DLL Security Update on My Report Server?? OR
Do we required to have Visual studio on each user's machine & then apply Visual Studio 2005 Service Pack 1 GDIPLUS.DLL Security Update??
Report Viewer 2005 Redistributable: http://www.microsoft.com/downloads/details.aspx?familyid=82833F27-081D-4B72-83EF-2836360A904D. Update Visual Studio. This is for the same reason as the redistributable. The ReportViewer is installed with Visual Studio for design time
Q:I have already installed Microsoft Report Viewer Redistributable 2005 Service Pack 1 on my Report server. We have SQL Server 2005 SSRS with SP3.
Having Reporting Services 2005 with SP3 also requires this Microsoft Report Viewer Redistributable 2005 Service Pack 1 update? OR
Do we need to install the Microsoft Report Viewer Redistributable 2005 Service Pack 1 on each individual user's machine??
please advice
September 27, 2009 at 11:44 am
gmamata7,
These are the links you need and per the blog you posted you need to install all three in your SSRS server, Web server if Asp.net application, if Winform the server running Winform. And your developers needs to run all three, if you are running SharePoint you also need to add the SharePoint version.
SQL Server 2005:
http://www.microsoft.com/downloads/details.aspx?familyid=5148B887-F323-4ADB-9721-61E1C0CFD213
Visual Studio 2005:
http://www.microsoft.com/downloads/details.aspx?familyid=A7BF790B-3249-4EE8-9440-FA911EBBC08A
Report Viewer 2005 Redistributable:
http://www.microsoft.com/downloads/details.aspx?familyid=82833F27-081D-4B72-83EF-2836360A904D
Kind regards,
Gift Peddie
September 28, 2009 at 12:48 pm
Thanks,
But why we do need to install Visual studio 2005 on a Report Server??
September 28, 2009 at 1:10 pm
gmamata7 (9/28/2009)
Thanks,But why we do need to install Visual studio 2005 on a Report Server??
I did not say that just that the dll is needed in all three places Visual Studio 2005 is what runs as BIDs so you need to install that dll for it. If your development is in another server then you need to install it in that server but the application running your reports needs to run reportviewer redist and the report server version of the dll.
Kind regards,
Gift Peddie
September 28, 2009 at 5:07 pm
I did not say that just that the dll is needed in all three places Visual Studio 2005 is what runs as BIDs so you need to install that dll for it. If your development is in another server then you need to install it in that server but the application running your reports needs to run reportviewer redist and the report server version of the dll.
thanks,
Our Reports were developed by some developer and later just the .rdl files are dropped into the Report Server via Report manager..In this case what should I do with the Visual Studio 2005 item?? The development machine used to create the reports is not in picture now????Still, If we install Visual Studio 2005 in that machine, how that going to effect the already deployed reports in Report Server? could you please explain me... OR
Do we required to have Visual studio on each user's machine & then apply Visual Studio 2005 Service Pack 1 GDIPLUS.DLL Security Update??
I already applied Report viewer redist SP1 on my Report Server after applying SQL Server 2005 SP3..
thanks much
September 28, 2009 at 5:42 pm
I already applied Report viewer redist SP1 on my Report Server after applying SQL Server 2005 SP3..
If the server running the application is different then you need to run both of the above in that server because both are needed for client printing to work as expected.
Kind regards,
Gift Peddie
September 28, 2009 at 9:54 pm
If the server running the application is different then you need to run both of the above in that server because both are needed for client printing to work as expected
Here I'm NOT touching the application Server..Let me give the details
1. Separate database engine with SQL Server 2005 x64 with SP3
2. Separate SQL Server 2005 Reporting Services with SP3
3. Separate Application Server. In the Application, we have a tab called Reports.
4. We have around 1000 users and from their machines, from the application URL, they are NOT able to PRINT the Reports.
So now you want me to install Visual Studio 2005 Service Pack 1 GDIPLUS.DLL Security Update & Report viewer redist SP1 on the Server where the APPLICATION IS INSTALLED??
OR anything we need to do on 1000 user's machines??
September 28, 2009 at 10:22 pm
1. Separate database engine with SQL Server 2005 x64 with SP3
2. Separate SQL Server 2005 Reporting Services with SP3
3. Separate Application Server. In the Application, we have a tab called Reports.
These are what you need to install because I don't know if SP3 installed what disables the control.
Kind regards,
Gift Peddie
September 28, 2009 at 11:21 pm
1. Separate database engine with SQL Server 2005 x64 with SP3
Why do we need to go back to SP2, if I already have SP3? I did not understand your point...
2. Separate SQL Server 2005 Reporting Services with SP3
Here also I have higher version SP3. So I think there is no point to go backup to SP2
3. Separate Application Server. In the Application, we have a tab called Reports.
These are what you need to install because I don't know if SP3 installed what disables the control.
Whats the point in installing these above 2 on Application server?
September 29, 2009 at 12:28 am
I also had a similar problem.
This is what that worked for me.
-SQL SERVER SP3 OR If KB953752 for SQL SERVER SP2
-Report viewer: http://www.microsoft.com/downloads/details.aspx?familyid=82833F27-081D-4B72-83EF-2836360A904D
Install the report viewer on web server also.
Regards,
[font="Verdana"]Sqlfrenzy[/font]
September 29, 2009 at 12:35 am
I just went through this link and looks like we need to apply CU1 for SP3 to resolve this print issue... I will try that & let you know...
Could you please clarify the below:
1. As I know ASP.NET ReportViewer control exist But I want to make sure is SSRS ReportViewer control also exists?
2.Is ASP.NET ReportViewer control & SSRS ReportViewer control same???
How can I know what Report viewer the application is using?? where can I check for this?
many thanks
September 29, 2009 at 4:24 am
I think that SSRS report viewer control doesn't exists.
please refer to the below links.
http://msdn.microsoft.com/en-us/library/ms251671(VS.80).aspx
and
Regards,
[font="Verdana"]Sqlfrenzy[/font]
September 29, 2009 at 8:09 am
Could you please clarify the below:
1. As I know ASP.NET ReportViewer control exist But I want to make sure is SSRS ReportViewer control also exists?
2.Is ASP.NET ReportViewer control & SSRS ReportViewer control same???
How can I know what Report viewer the application is using?? where can I check for this?
many thanks
Gmamata7,
I did not say Asp.net control Microsoft provides Reportviewer control it comes in both Winform and Webform so the Webform version is what you run in Asp.net applications. If your reports are in an application as you posted integrated into the application you may be running one of these controls if your reports are not running as web service.
If your reports are a web service then all you need is SP3 but if the reports are not web service you need to apply the report viewer fix.
2.Is ASP.NET ReportViewer control & SSRS ReportViewer control same???
Yes and check below for samples so you can understand what I am saying.
http://www.gotreportviewer.com/
Kind regards,
Gift Peddie
September 29, 2009 at 7:06 pm
Thanks Peddie,
If your reports are a web service then all you need is SP3 but if the reports are not web service you need to apply the report viewer fix
How to know your reports are a web service OR not web service?
If the reports are not web service you need to apply the report viewer fix. Where this report viewer fix should be applied? on
Application Server OR
Report Server OR
User's machine
Please see the attachment for what happening when we click PRINT...
many thanks
September 30, 2009 at 3:44 pm
Web Service is:
.ASMX page
Asp.net is:
.ASPX page
So if you are in web service then you don't need to add the reportviewer file and if you are in Asp.net then you add the reportviewer file.
Kind regards,
Gift Peddie
Viewing 15 posts - 16 through 30 (of 33 total)
You must be logged in to reply to this topic. Login to reply