Hi VPDJ,

I do not know what is wrong, but may have a way to help diagnose the problem. You can enable client side logging for client print. This will produce a log*.tmp file in your %temp% directory.

Once you have the print log file and the corresponding server log file, please send to me. I will try and see if I can figure out the problem from the logs. Bradsy@removememicrosoft.com

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL Server\80\Reporting Services]
"LogRSClientPrintInfo"=dword:00000001

Am having exactly the same problem as described - Report Services hangs on Print or Preview..

It used to work a few months ago - now exactly as described...

***

We can print to files without issue - only when we try to print to a real printer does it hang forever.
It doesn't matter how big the report is, 100 pages or 1/4 of a page, same problem.
We do the following:
1) Run the report
2) Click the print button
3) Select a printer and press ok
4) "Printing Now..." dialog box appears
5) "Print Error" dialog appears and never goes away - and nothing is printed out.
Have to close IE and crash the report session to get out of it.

This is the result on every client computer we have ever used in trying to access
the report server.
It also hangs in running a Print Preview for all reports.

***

Yep Exactly - Help Also!

WinXp Sp2+winupdate all current, vs2005sp1, sql2005sp2- all up to date! - Box is stable, smooth no problems except this RsClientPrint problem...if i enable script debugging and let it sit long enough to get the error dialog "An error occured during printing." I can attach the debugger though! Here it is...

***

***

More Details: when problem started i was on Sql2005 sp1 - i noticed sql2005sp2 was released so i applied it!

Everythin is "The Most Current", I followed How to enable Reporting Services Client printing, and how to configure the browser for RsClientPrint"

RsClientPrint is downloaded, installed and current - version 2005.90.3042 ( way current! 3/4/07)

*** And it used to work on this box!!! - lets see, what have i done since i know client printing worked - I allowed ie7 and .NetFramework 3.0 to be installed via WindowsUpdate - and an update to framework 2.0 - Hmmmm

I've uninstalled ie7 and back to ie6 most current... I'll try more debuggin, try to step into RsClientPrint.Print some more...

But surely, someone knows the FIX allready...

So Please Help!

R Lewis - MCSD - rplewis419@bellsouth.net

PS: *** I can let some one remote in to the problem if they like! But they gotta promise to fix it( I hope anyway)

Hmm...

Guess i'm not current (problems, problems...)

Cumulative hotfix package (build 3152) for SQL Server 2005 Service Pack 2 is available

SQL Server 2005 Reporting Services, 32-bit version

Oooo .3152... ( might as well try it!!!).

When you start printing, open up the sql profiler on the sql box and see whats going on in there. Is there any particular stored procedure which is executing over and over again, as if in a loop.

Check it with Profiler - Wow, Massive...

exec ObjectExists @Path=N'/RptStkGainers/StkGainers',@AuthType=1

exec sp_reset_connection

-- network protocol: LPC
set quoted_identifier on
set arithabort off
set numeric_roundabort off
set ansi_warnings on
set ansi_padding on
set ansi_nulls on
set concat_null_yields_null on
set cursor_close_on_commit off
set implicit_transactions off
set language us_english
set dateformat mdy
set datefirst 7
set transaction isolation level read committed

*** Then goes to constant and continuing loop of...

exec DeletePersistedStreams @SessionID='x3dm4u55unrjgr55lmqrfi55'

exec DeletePersistedStreams @SessionID='x3dm4u55unrjgr55lmqrfi55

'exec DeletePersistedStreams @SessionID='x3dm4u55unrjgr55lmqrfi55'

exec DeletePersistedStreams @SessionID='x3dm4u55unrjgr55lmqrfi55'

*** forever till end of trace (whatever that means.... No help here...)

( also from taskmgr - AspNet_wp.exe is just eating cpu time... seams to be dooing nothing).

Oh well - Every thing works ok EXCEPT STILL CANT PRINT or PREIVEW to a REAL PRINTER!!!

REAL BUMMER!!!

Please some one fix this!!!!

*** REALLY INTERESTING!!!

Had a extra dev box - Installed XpProSp2)(New,fresh,clean,new install) ran up all Microsoft updates, Installed Vs2005+sp1, Installed Sql2005 (noservice applied - same User, sql/rptservices service account setup), restored databases over to new box ), copied Rpt service solution/project - built/deployed -> And:

NO PROBLEM!!! - Local Print(RsClientPrint) from Report Manager WORKS LIKE A CHAMP!!!

Maybe, like the original poster says - Could be a real problem in SQL SERVICE PACK 2!!!

Now, Someone PLEASE! - whats wrong with the box with Sql2005 SP2 applied - Whats the secret

Thanks, R Lewis, MCSD - rplewis419@bellsouth.net

Edit1:

Applied sql2005 sp1 - all OK!!!

Think i'd be a fool to apply Sql2005sp2 and the have 2 boxes busted!!

Will try accessing Rpts from box1 using the RsClientPrint on box2... or somethin like that.

Unless someone has a better idea

Edit2: *** BIG WOW! -- Sql2005sp2 is (IMHO) at the bottom of This problem!!!!

Consider:

Box1 - XpSp2-Sql2005sp2 wRs - standalone - Cant local print from ReportManager

Box2 - XpSp2-Sql2005sp1 wRs - standalone - CAN local print from ReportManager

Now run ReportManager by reaching thru local Intranet to the other box....

from box2: run http:\\box1\Reports - select report, view(ok) try local print(RsClientPrint) ---- Hang(Bombo!!!)

from box1: run http:\\box2\Reports - select report, view(ok) try local print(RsClientPrint) ---- NO Problem!!!!

Interesting! Definitely something to do with sql sp2 - and AspNet_wp.exe!

The Problem is somewhere in SqlSp2 and new .NetFrame 2.0!

from TaskMgr - AspNet_wp process is just burning cpu time - attach debugger to it and:

Oops - Unhandled exceptions!!!! ( Give me a good ole kernal debugger & symbols - but this is MS's Job)

Like the original poster said - and I now totally agree!

***

Please Help!!!

We have never been able to get the printing to work on any of our reports using SQL Server Reporting Services 2005 SP2 in our production environment. Without this feature of printing a report, we cannot go live with SSRS at all.

We have tried adding the SP2 after a clean install on a new server -- yet we still have this problem.

***

It sure is a problem! And Sql2005Sp2 is on Microsoft Update!!!!

Has ANYBODY applied sql Sp2 and gotten this to WORK

(or it could be in the updated Framework\v2.0.50727) ( im definitely gettin off the bleading edge)

What a bummer - i also still have this problem!

The profiler trace confirms what i suspected.

Please use following steps/ commands against the SQL Server:

1. sp_configure
a. Note the ¡®Run¡¯ value for ¡®user options¡¯

2. sp_configure 'user options', 0

3. RECONFIGURE

These commands ¡°Set NOCOUNT OFF¡± -- meaning we are asking SQL Server to send back the # of rows affected by statements like Delete, Insert, Update etc; -- This is the Default option on SQL anyway.

4. After the above change, I¡¯d suggest re-starting SQL Server and then testing your SRS print scenario again ¨C If it prints, do let me know.

5. After validating the findings, you could run another command to reset the user options to the value noted in step 1 a: (if you so wish)

sp_configure ¡®user options¡¯ <value from step 1a above>
RECONFIGURE

AMAZING! Who woulda Thunkit! ALL WORKED...

Yes, i had set the Server-Propertien-Connections- NoCount CHECKED ( yielding default connection to Set NoCount On" (UserOption 512) cause i run a lot of reports to file and dont want clients see rows effected in reports i run and print at home) Wowsa! That'll teach me to set options just for convienient appearance! ( of course i always set no count off in procs that to need to return the number of rows effected, but evidently one shouldn't be steppin on supermans cape and changing the defaults!)

I was hopin it was some stupid nit that was causin the problem!

I sure wouldnt a thunkit, but chalk up another step in savin the world!!!

Thanks Much!

ps: now whatdoya think about the original paster, who may or may not have ever gotten his Sql2005sp2 fixed

ps2: and maybe MS should put "Set NoCount Off" in their procs/queries that require it so stupid users like me dont step on it like i did! But no problem, I was the one that shot myself in the foot!

;-) Nice to see that this now works for you. Sorry.. i dint get that original poster question... this should now work with any SP of sql2005, is that what you wanted to ask

Also, this sure looks like anomalous behavior [can be read as buggy ;-)] so i would encourage you to post this on https://connect.microsoft.com/ as a bug. The more tech details you provide, [like repro steps etc] more chances of this getting to Microsofts attention and being actually fixed.

I personally have seen very rare occurances of this, just 2, to be precise.

If only one of your report hangs, you are facing a different problem for sure. What is special about this report Is it a very large report How many pages What if you leave it on overnight Any error messages in the reporting services error logs when you start printing the report Do you see the hang from any one particular machine Does this happen on the server as well as the client machine

You should probably try the LogRSClientPrintInfo registry key entry as mentioned by Brad Syputa earlier in this post. In the log, you should be able to spot a URL which is actually the report URL used to render the report for printing. See if you can put that in the browser and get a report rendered.