Client Printing Support in SQL Server Reporting Using SOAP
page 2 of 3
by vikas chaudhary
Average Rating: 
Views (Total / Last 10 Days): 18571/ 28

Tackling Errors

One may get some problems implementing this. The most common are listed below.

You may get an error as "Error loading resource library. (0x80004002)."

For this you need to install the ActiveX control explicitly once before using the object. To resolve this you need to run the report from report manager and install the ActiveX provided from the toolbar of the Report Server. Additionally your client browser should allow ActiveX to permit download.

Another problem that can occur during execution is an unhandled exception of type "System.InvalidCastException" occurred in CoMALite.exe.

To resolve this you need to check your version of the downloaded control that can be done by checking the downloaded control itself. For that, go to path C: or your windows drive and check %windir% folder generally C:\windows. Then in "\Downloaded Program Files," you will see RSClientPrint Class as a downloaded ActiveX and it will be shown along with status(installed), size, date and version. If the problem persists, try deleting this and again installing the control.

This makes the client printing easy and almost effortless if the application uses the web method for rendering reports and without using the ReportViewer control that is extensively used in Visual Studio 2005.

View Entire Article

User Comments

No comments posted yet.

Community Advice: ASP | SQL | XML | Regular Expressions | Windows

©Copyright 1998-2024  |  Page Processed at 2024-04-19 3:36:46 PM  AspAlliance Recent Articles RSS Feed
About ASPAlliance | Newsgroups | Advertise | Authors | Email Lists | Feedback | Link To Us | Privacy | Search