An error occurred during printing (0x8007F303)

Sometimes when I try to print a report from Report Manager using the ActiveX
print control, I get the following error message:
"An error occurred during printing (0x8007F303)"
I can't find any information on why I get the error or what it means.
Can anyone help?The client active-x control is corrupted. To Fix this
IE -> Tools -> InternetOption -> Settings -> View Objects -> Remove RS
Client Print object or do the update. Now click the icon from the report .
The Active-x control will be downloaded to install again freshly to get
working.
"Roberto Kohler" wrote:
> Sometimes when I try to print a report from Report Manager using the ActiveX
> print control, I get the following error message:
> "An error occurred during printing (0x8007F303)"
> I can't find any information on why I get the error or what it means.
> Can anyone help?
>
>|||Hi,
Thanks for your help.
I tried updating the active-x control as you suggested.
When I do, I get the following error message:
Internet Explorer - Security Warning
Windows has found a problem with this file.
Name: GetImage=8.00.1038.00rsclientprint.cab
Publisher: Unknown Publisher
This file was blocked because it does not have a valid digital signature
that verifies its publisher.
Then when I finish installing the RS Client Print object, and I try printing
the report, I get the same error "An error occurred during printing
(0x8007F303)"
I also tried this by removing the active-x control and the same thing
happens.

An Error Occured During Printing (0X80070003)

we r using the report viewer control of the reporting service 2000 , and it works fine

but when there is a huge report (around 1000 page) it gives the above error "An Error Occured During Printing (0X80070003)" after spoling of around half of the report around 500 page, and stops spoling the rest of the report

is it a problem with the reporting service or the server hardware ?

The problem is that your report is too large for the amount of RAM you have available on the server. Take a look at breaking the report down into a series of smaller reports. Here is a KB article that discusses the problem: http://support.microsoft.com/kb/909678

Larry

Am I a sysadmin member?

Hi,

I want to check if the currently connected user is a sysadmin(or securityadmin) member. Could I only check whether the user has the CONTROL SERVER permission or not? Is there a straight way to test it?

Try using

SELECT IS_SRVROLEMEMBER( 'sysadmin', 'UserName' )

Returns 1 for true, 0 for false.

|||Thanks

Alternative to Microsoft?

Andreas,
there are axtiveX controls to control the execution of=20
the various agents. Have a look at this for more detail:
http://www.windowsitpro.com/Articles/Index.cfm?
ArticleID=3D39079&DisplayTab=3DArticle
As for general options, there are alternatives out there.=20
I recently looked at SQL DataCompare, which could be used=20
in a similar way. Some of these alternatives are also=20
significantly faster. However, consider that merge has a=20
huge amount of inbuilt versatility. Merge has automatic=20
range management, a rich set of conflict resolution=20
techniques and assign priorities, the option to=20
dynamically filter data and prefilter snapshots, the=20
ability to configure unidirectional replication (in=20
either direction), the ability to control the batch size.=20
Along with other replication methods, we have subscriber=20
timeouts and inbuild alerts. The list of extras is huge=20
and the price of this functionality is the increased=20
complexity behind the scenes.
is designed for high autonomy.
>--Original Message--
>I have to implement a simple Merge-Replication, using=20
the MSDE.=20
>That means, I can=B4t using Enterprice-Manager.=20
>I don=B4t want using SQLDMO because of redistribution-
problems.=20
>Using T-SQL, it is quite difficult to implement Merge-
Replication.=20
>Are the thrid-pary-products, ActiveX-Controls,=20
Libraries, assembly,
>etc. that manage SQL-Server-Replication very well?
>What do you think about writing your own merge-
replication tool? I
>just wrote a prototyp, and it seems to be very easy.
>pro:
> - no limitations on changing data strukturs while=20
publishing tables
>!!!
> - using a connection in ONE direction (no re-connect=20
from subscriber
>to distritubor necessary, ideal for replication into=20
internet !! )
> - high level of transparency, you can debug each step,=20
you can log
>each SQL-Statement
> - if you want to use a single-sided replication (like=20
transactional
>replication) the subscriber database need not implement=20
anything (no
>table, no trigger, nothing!!)
> - few overhead: just adding 3 triggers per table (like
>MS-merge-replication does) and 2 or 3 system-tables
> - very simple code to switch on replication (just=20
adding the 3
>triggers to each table, independent on data strukture)
>contra:
> - replication-process itself is not tested, each=20
possible event have
>to be implemented and well tested
>I would be happy if someone would like to diskuss this=20
with me, or if
>someone has just written a tool like this, or have=20
another good idea.
>Andreas Lauffer, Germany
>.
>
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message news:<086e01c51813$bebd2800$a501280a@.phx.gbl>...

> there are axtiveX controls to control the execution of=20
> the various agents. Have a look at this for more detail:
> http://www.windowsitpro.com/Articles...yTab=3DArticle
OK, I tested these controls. There are not bad, but fare away from
beeing perfect. Sometimes the error messages arent detailed enough,
you dont know why replication doesnt work.
In addition, the controls covers only a part of the whole replication
process.

> As for general options, there are alternatives out there.=20
> I recently looked at SQL DataCompare, which could be used=20
> in a similar way. Some of these alternatives are also=20
> significantly faster.
SQL DataCompare looks very nice, but it seems so that it cannot merge
Datasets. You have to tell the tool, wheater to change the Database B
with the changes from A or vise versa.
Maybe there is a possibilty with C#, if you compare all the changes
from Database A and B and generate SQL-Scripts manually.

> However, consider that merge has a=20
> huge amount of inbuilt versatility. Merge has automatic=20
> range management, a rich set of conflict resolution=20
> techniques and assign priorities, the option to=20
> dynamically filter data and prefilter snapshots, the=20
> ability to configure unidirectional replication (in=20
> either direction), the ability to control the batch size.=20
> Along with other replication methods, we have subscriber=20
> timeouts and inbuild alerts. The list of extras is huge=20
> and the price of this functionality is the increased=20
> complexity behind the scenes.
I dont need range management, assign priorities, Data filters, etc.
Comflict management is even much much simpler and comfortable if you
implement this inside your code.
[vbcol=seagreen]
>
>
> is designed for high autonomy.
> the MSDE.=20
> problems.=20
> Replication.=20
> Libraries, assembly,
> replication tool? I
> publishing tables
> from subscriber
> internet !! )
> you can log
> transactional
> anything (no
> adding the 3
> possible event have
> with me, or if
> another good idea.