SP2 Print Error -- sql server reporting services

SAcanuck
5/13/2005 4:11:02 PM

Im getting the same error. Never had the Beta installed and have checked my
security settings...

[quoted text, click to view]

Brian Welcker [MS]
5/14/2005 10:52:31 AM

Is this with all reports or just specific ones?

--
Brian Welcker
Group Program Manager
Microsoft SQL Server

This posting is provided "AS IS" with no warranties, and confers no rights.

[quoted text, click to view]

khonerka
5/16/2005 6:46:02 AM

I also never had the beta installed and believe my security settings are fine.
It is happening with all reports.
I finally just had to go through the hoops and turn the Client Side printing
off.
It would be nice to get it working, but due to a different fix in this
release I need to move SP2 to production as soon as possible.

[quoted text, click to view]

SAcanuck
5/16/2005 10:20:09 AM

We have two report servers... one works fine, the other has this issue. The
issue seems to be on the server because using the same client machine I get
the issue/or not depending which server i log on to.

[quoted text, click to view]

sblreporter
5/19/2005 3:13:14 PM

We too are having the same behavior
Same exact problem 'An error occurred during printing (hexvalue)"
As soon as we moved to SP2 , this error started appearing in reports that
are over !12 pages.
The problem is with both the 'Export' function and the 'Printer' icon
--
sbl reporter

[quoted text, click to view]

sblreporter
5/19/2005 3:15:01 PM

Don't know if this is relevant, but when I get the error mentioned in this
thread - I tried 'Export' to PDF and received the following

My guess is that there is some setting going out of bounds - because this
problem only shows for reports >~11 pages for us

Exception of type
Microsoft.ReportingServices.ReportRendering.ReportRenderingException was
thrown. (rrRenderingError) Get Online Help
Exception of type
Microsoft.ReportingServices.ReportRendering.ReportRenderingException was
thrown.
Index was out of range. Must be non-negative and less than the size of the
collection. Parameter name: index

--
sbl reporter

[quoted text, click to view]

SethD
6/1/2005 5:02:04 AM

Did anyone resolve this issue? I am dealing with the same problem. We are
using SP2, SQL server 2K, win 2k server, and IIS. I am going through a proxy,
but bypassing for local addresses.

This is a money report writer. Being able to print the reports would make it
that much better.

Any help is appreciated.
--
Seth

[quoted text, click to view]

cmay
6/7/2005 10:49:30 AM

I am having this same issue as well.

This is off a brand new machine, w/ a brand new install of SQL Reporting
Services.

For us, even the smallest 1/2 page reports produces this error, but the 1st
page of the report prints w/o any problem.

I can print it to other things, like the Microsoft Office Data Imaging and
it doesn't error, but when I try to send to a printer ... BAM!

Any ideas?

Chris

[quoted text, click to view]

Chris Kennedy
6/16/2005 12:48:02 PM

I'm having the same problem, but not all users. Some people can print a
report okay and others can't.

Chris Kennedy

[quoted text, click to view]

Brave
7/4/2005 1:35:02 PM

I have the same problem, some user get the Script error on the same report
with the same parameter. - Where is the problem?

"Chris Kennedy" schrieb:

[quoted text, click to view]

SethD
7/23/2005 7:25:01 AM

Can anyone please enlighten me on possible resolutions to this issue? It
appears that many people are experiencing the same problem. I just want to
print the report....this should be the ez part...right?
--
Seth

[quoted text, click to view]

Bruce L-C [MVP]
7/23/2005 11:52:24 AM

Depends. An activex control is being installed so it depends on how the
user's IE is configured (whether it allows this) and also it depends on what
the user's rights are on the PC. Do they have rights to install on the PC?

--
Bruce Loehle-Conger
MVP SQL Server Reporting Services

[quoted text, click to view]

SethD
7/23/2005 2:24:03 PM

Bruce, thanks for the reply. My user account is setup as a local admin on the
machine that I'm using to attempt printing. As for the IE configuration, I
setup the report server as a trusted site and set my security settings to
low. Is there anything i need to manually set or any security settings setup
check list that i could follow.

Thanks in advance.
--
Seth

[quoted text, click to view]

Bruce L-C [MVP]
7/23/2005 8:03:06 PM

Nothing else that I am aware of. One point to be sure of, did you ever use
this machine for the beta of SP2. If so you need to clear the machine out of
an old version of the control.

--
Bruce Loehle-Conger
MVP SQL Server Reporting Services

[quoted text, click to view]

graylandworthey NO[at]SPAM yahoo.com
8/5/2005 10:40:23 AM

I am having the same issue. has anyone been able to solve this problem
yet?

[quoted text, click to view]

Dana Forsberg
10/14/2005 8:12:36 AM

In our case, we installed SP2, and for a couple of days the (0x80004005)
error did not occur. Now the error is indeed occurring.

It occurs in printing, print-preview, and in export to PDF at least. It may
occur in other export formats I haven't tried. It is clearly server-side, or
triggered server-side, since it is occurring for us in 2 locations remote
from each other, both referencing the same web-server in a third location,
over the internet.

It seems clear from earlier posts that the "smoking gun" here is *not* a
beta version of Reporting Services, nor browser settings. In our case, no
beta is involved, and in other, earlier installs of Reporting services, the
very same browser with the same settings I use now had no difficulty.

Please, Microsoft folks, clearly this is not an isolated incident -- and the
first post is in May(!) over 5 months ago -- I would very much appreciate an
answer with substance, taking into consideration all the symptoms listed this
post -- and all other posts in this thread. Will re-installing SP2 help? Any
other work arounds? This is impacting a production, customer site. Thank
you for your attention.

[quoted text, click to view]

Keenan Chadwick
10/24/2005 1:00:03 PM

Our organization also has servers that are being affected by this bug. Help

cmay
10/27/2005 1:06:38 PM

We are still seeing this problem.

We recently rebuilt our sql server and still have this problem.

GrandeApps
11/4/2005 6:32:01 AM

We installed Reporting Services and SP2 on our customer portal for
reporting of their test results. This determines how our customers are
paid and is of extreme importance to them. We developed Reporting Services
reports and deployed them just this past week.

The reports look great and have been well received. However, there are
two glaring problems. First, whenever they attempt to print the report using
the print icon, the first page of the report prints and the following error
pops up
in a message box "An error occurred during printing. (0x80004005)". Second,
when we attempt to export the reports to PDF format and print them, every
other
page is a blank page.

Having read numerous posts about these problems, its clear that these are
issues that effect many installations of Reporting Services. Please, this
is clearly
not an isolated incident -- and the first post was in May over 6 months ago.

We would very much appreciate a resolution to this issue! It has a tremendous
impact on customer satisfaction with our production reports.

Thank you in advance for your prompt attention in this manner!
--
Grande Applications

[quoted text, click to view]

Bruce L-C [MVP]
11/4/2005 8:44:48 AM

The PDF issue is usually a mismatch between your page layout and your
report. However, I have had one case where no matter what I did I would get
the blank page. In my case I think the issue was a subreport. Note that I
really did barely fit on the page anyway so it would take very little to
cause it to spill over to another page.

I suggest posting a question specifically on the PDF. You should get good
suggestions from the forum. I don't do a whole lot with PDF but others here
do.

As far as your error. Have your registered for the managed newsgroups (based
on your email it looks to me like you have). If you have, one thing you
might not realize is that your posting has to be the first posting for MS to
notice and monitor it. So, if you do have a managed newsgroup registered
address then re-post so you have done the first post and then MS should
respond.

--
Bruce Loehle-Conger
MVP SQL Server Reporting Services

[quoted text, click to view]

cmay
11/11/2005 8:41:41 AM

Bruce,

Any chance you could expand on the "managed newsgroups" thing?

I posted a new topic in:
microsoft.public.sqlserver.reportingsvcs

on Oct 27th with no response by anyone...

URL:
http://groups.google.com/group/microsoft.public.sqlserver.reportingsvcs/browse_frm/thread/866af77968baa740/04852578dfeea728?lnk=st&q=cmay&rnum=1#04852578dfeea728

The ability to print was a big reason for us to move to this product,
and it we have never been able to get ours to work... we have built 2
SQL Reporting machines, and rebuilt one of them 1 time, w/ the same
result... printing never works.

Bruce L-C [MVP]
11/11/2005 11:45:10 AM

If you have an msdn subscription you can register a special/fake email
address. That address is monitored by MS and they guarantee a response. To
get a response you have to be the one who initiated the thread. Go to
MSDN.microsoft.com, click on subscriptions and log on. Once you do that you
will see a link for managed newsgroups. I believe you can use a web based UI
to enter your questions but it goes to this newsgroup anyway, you can post
with however you do today as long as you have set up the posting account
correctly.

What I do is I have two accounts setup in OE. One I use normally and one
when I need a question answered. They guarantee a response in 2 business
days.

--
Bruce Loehle-Conger
MVP SQL Server Reporting Services

[quoted text, click to view]

cmay
11/14/2005 1:01:43 PM

OK sweet, I will do this and see how it goes.

Bartosz Gorzynski
11/22/2005 12:00:00 AM

We have have this same problem - on 1 machine (production - win2003 SQL
Server RS SP2) we have "problem (0x80004005) " and on developer machine
(this same configuration except windxp as OS ) we don't have problems.
Printing will be triggered on one from our workstations (this same - not
one from above listed). However PDF export is fine and (this is most
strange) client printing from production server had work earlier for
long time without any problems

Dana Forsberg napisa³(a):
[quoted text, click to view]

cmay
11/28/2005 11:15:43 AM

Just to keep anyone reading this updated with my progress, or lack
thereof:

I posted with the email address that we have our MSDN though, which
Bruce suggested would get a response.

Someone did write back, asking if I was using IE and printing to a
local printer.

The answer is Yes and No. When I DO try to print to a local printer
the first page comes out, but nothing after that, and I still get the
same 0x80004005 error.

I am pretty amazed that there is nothing from MS indicating that they
are aware of this problem, or know what causes it, or what we can do
about it.

Bruce L-C [MVP]
11/28/2005 1:24:22 PM

Sorry, that isn't how you do a managed account. You have to go to MSDN, log
in, and then setup an alias that is used when you submit a posting. Then MS
tracks it. If you have your email address for MSDN the only thing that will
happen is that spam will start coming to that email account. That is why MS
has you create and register a fake email address (not a real one) so that
you don't have to worry about spam.

--
Bruce Loehle-Conger
MVP SQL Server Reporting Services

[quoted text, click to view]

cmay
11/29/2005 2:38:10 PM

Bruce,

I believe that I did what you are describing.

You just replied to my post, "msmolarek@community.nospa=ADm" is the
name I created.

I will continue this in the thread that MS should be tracking.

Bruce L-C [MVP]
11/29/2005 5:03:13 PM

OK, the other thing to make sure is that initiate the thread (first
posting). They don't track any replies. If you haven't been responded to
then send me an email (you have to take out the nospam) and I'll ding MS
that your thread hasn't been answered.

Also, it is not the name that needs to be the special address, it is your
email address when you setup your newsgroup access. In Outlook Express click
on the properties for the newsgroup and make sure your email address is set
to that. If it isn't then set it to the special address and then try a new
posting.

It isn't the most intuitive thing to setup.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services

[quoted text, click to view]
Bruce,

I believe that I did what you are describing.

You just replied to my post, "msmolarek@community.nospam" is the
name I created.

I will continue this in the thread that MS should be tracking.

cmay
12/2/2005 5:17:47 AM

Bruce,

Thanks for all your help on this.

I agree, intuitive it is not.

I have been using the web client through microsoft, not a traditional
news reader.

Will that still trigger the response from MS?
If there is anyway to check if I did it right, my initial post can be
found quickly through http://msdn.microsoft.com/newsgroups and search
for "msmolarek". Only 2 threads come back... this one, and the one I
started in hopes of getting a response from MS.

Chris

mamo
4/27/2007 7:40:29 AM

I tried searching for this thread but nothing came back. Any further progress?

From http://developmentnow.com/g/115_2005_5_0_0_518366/SP2-Print-Error.htm

Posted via DevelopmentNow.com Groups

Jay
5/10/2007 9:57:56 PM

There are two methods indicated for solving this problem:

1) Microsoft has a hotfix that you have to call them to obtain. They indicate that it has not been regression tested and that the final fix will be in some future SP.

http://support.microsoft.com/kb/907010

2) Some people have reported that the server makes use of GDI functions and that you should remove the servers print drivers and not elect to reload them as startup. When the server user basic Microsoft Windows video drivers the exception goes away.

Neither of these solutions appears to be ideal or 100% reliable.

From http://developmentnow.com/g/115_2005_5_0_0_518366/SP2-Print-Error.htm

Posted via DevelopmentNow.com Groups

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages about sql server reporting services

sql server reporting services : SP2 Print Error