Please Help!!!We have never been able to get the printing to work on any of our reportsusing 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.I read a few some postsaboutuninstallthe old ActiveX control used for printing, so I did this and installed the new one but that didn't help either.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 report2) Click the print button3) Select a printer and press ok4) "Printing Now..." dialog box appears5) "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. We are printing to network printers from IE6 and IE7.Since this is on a server, we do not have a local printer to this server computer to try to print to.Even if it worked on a local printer, this is supposed to be an enterprise solution. Almost allof our employees print to network printers.I am logged into my machine as a domain admin. I have no printing problems in any program printing to any printer, except when using Reporting Services. We are trying to print from an ASP web application which runs the reports in an iframe using URL access. We are able to print the same reports on all of our development environments using the same ASP web application and RDL. Again, Please help!!!

I am also facing a very similar problem... Printing to a real printer or export to pdf shows "Printing Now..." and w3wp.exe service on server starts consuming 100% CPU!!!I tired to run/print the same report from VS2005 and RSReportHost.exe dies while printing. After further analysis, we found that there was a field in a subreport that was extremely long... so long that it was spilling over a page's height.It seems like a bug in Reporting Service printing routine when there is a subreport with large fields, it freaks out...

No - this is not the same issue - none of the fields are very long (all less than 40 characters). And it happens when I printany of the reports. Any other ideas?

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- nowexactly 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 report2) Click the print button3) Select a printer and press ok4) "Printing Now..." dialog box appears5) "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! Hereit is... *** <HTML> <BODY onload="Print()"> <OBJECT ID="RSClientPrint" CLASSID="CLSID:FA91DF8D-53AB-455D-AB20-F2F023E498D3" CODEBASE="/Reports/Reserved.ReportViewerWebControl.axd? ReportSession=1fkaywuhrsf0nx3xffaqfs55&amp;ControlID=66deb65aa11844df954e9e62fcc1feec&amp;Culture=1033&amp;UICulture=9&amp;ReportStack=1&amp;OpType=PrintCab#Version=2005,090,3042,00" VIEWASTEXT></OBJECT> <script language="javascript"> function Print() { if (typeof RSClientPrint.Print == "undefined") { alert("Unable to load client print control."); return; } RSClientPrint.MarginLeft = 25.4; RSClientPrint.MarginTop = 25.4; RSClientPrint.MarginRight = 25.4; RSClientPrint.MarginBottom = 25.4; RSClientPrint.PageHeight = 279.4; RSClientPrint.PageWidth = 215.9; RSClientPrint.Culture = 1033; RSClientPrint.UICulture = 9; RSClientPrint.UseEmfPlus = true; *** The Debugger has the line below marked( in Yellow - with an Exception has Occured... *** RSClientPrint.Print("/Reports/Reserved.ReportViewerWebControl.axd", ReportSession=1fkaywuhrsf0nx3xffaqfs55&ControlID=66deb65aa11844df954e9e62fcc1feec&Culture=1033&UICulture=9&ReportStack=1&OpType=PrintRequest", "StkGainers") *** The line above is the exception point... } </script> </BODY> </HTML> *** More Details: when problem started i was onSql2005 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 toconfigure the browser for RsClientPrint" RsClientPrint is downloaded, installedand 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 File name File version File size Date Time Platform Microsoft.reportingservices.diagnostics.dll 9.0.3152.0 800,112 03-Mar-2007 07:53 x86 Msmdlocal.dll 9.0.3152.0 15,930,224 03-Mar-2007 07:53 x86 Msmgdsrv.dll 9.0.3152.0 6,041,456 03-Mar-2007 07:53 x86 Reportingservicesservice.exe 9.0.3152.0 17,264 03-Mar-2007 07:53 x86 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: LPCset quoted_identifier onset arithabort offset numeric_roundabort offset ansi_warnings onset ansi_padding onset ansi_nulls onset concat_null_yields_null onset cursor_close_on_commit offset implicit_transactions offset language us_englishset dateformat mdyset datefirst 7set 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' execDeletePersistedStreams @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 box1using 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: 'aspnet_wp.exe': Loaded 'C:\WINDOWS\assembly\GAC_32\System.Transactions\2.0.0.0__b77a5c561934e089\System.Transactions.dll', No symbols loaded. 'aspnet_wp.exe': Loaded 'C:\WINDOWS\system32\schannel.dll', No symbols loaded. 'aspnet_wp.exe': Loaded 'C:\WINDOWS\system32\kerberos.dll', No symbols loaded. 'aspnet_wp.exe': Loaded 'C:\WINDOWS\system32\cryptdll.dll', No symbols loaded. 'aspnet_wp.exe': Loaded 'C:\Program Files\Microsoft SQL Server\90\Shared\instapi.dll', No symbols loaded. 'aspnet_wp.exe': Loaded 'C:\WINDOWS\system32\dssenh.dll', No symbols loaded. 'aspnet_wp.exe': Loaded 'C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer\bin\ReportingServicesCompression.dll', No symbols loaded. 'aspnet_wp.exe': Loaded 'C:\WINDOWS\system32\mpr.dll', No symbols loaded. 'aspnet_wp.exe': Loaded 'C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\diasymreader.dll', No symbols loaded. 'aspnet_wp.exe': Loaded 'C:\WINDOWS\system32\msi.dll', No symbols loaded. 'aspnet_wp.exe': Loaded 'C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\fusion.dll', No symbols loaded. 'aspnet_wp.exe': Loaded 'C:\WINDOWS\assembly\NativeImages_v2.0.50727_32\System.Data.OracleC#\adae7ace96e282857121352c506ff359\System.Data.OracleClient.ni.dll', No symbols loaded. 'aspnet_wp.exe': Loaded 'C:\WINDOWS\assembly\GAC_32\System.Data.OracleClient\2.0.0.0__b77a5c561934e089\System.Data.OracleClient.dll', No symbols loaded. The thread 'Win32 Thread' (0xc0c) has exited with code 0 (0x0). aspnet_wp!library!8!10/9/2007-13:04:11:: i INFO: Cleaned -1 batch records, -1 policies, 0 sessions, -1 cache entries, 0 snapshots, 0 chunks, -1 running jobs, -1 persisted streams First-chance exception at 0x7c812a7b in aspnet_wp.exe: 0xE0434F4E: 0xe0434f4e. First-chance exception at 0x7c812a7b in aspnet_wp.exe: 0xE0434F4D: 0xe0434f4d. First-chance exception at 0x7c812a7b in aspnet_wp.exe: 0xE0434F4D: 0xe0434f4d. aspnet_wp!ui!6!10/9/2007-13:07:22:: Unhandled exception: System.OperationCanceledException: The operation was canceled. at Microsoft.Reporting.WebForms.ServerReport.ServerUrlRequest(Boolean isAbortable, String url, Stream outputStream, String& mimeType, String& fileNameExtension) at Microsoft.Reporting.WebForms.ServerReport.InternalRender(Boolean isAbortable, String format, String deviceInfo, NameValueCollection urlAccessParameters, Stream reportStream, String& mimeType, String& fileNameExtension) at Microsoft.Reporting.WebForms.ServerReportControlSource.RenderReport(String format, String deviceInfo, NameValueCollection additionalParams, String& mimeType, String& fileExtension) at Microsoft.Reporting.WebForms.PrintRequestOperation.PerformOperation(NameValueCollection urlQuery, HttpResponse response) at Microsoft.Reporting.WebForms.HttpHandler.ProcessRequest(HttpContext context) at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) First-chance exception at 0x7c812a7b in aspnet_wp.exe: 0xE0434F4D: 0xe0434f4d. The thread 'Win32 Thread' (0x228) has exited with code 0 (0x0). First-chance exception at 0x7c812a7b in aspnet_wp.exe: 0xE0434F4E: 0xe0434f4e. First-chance exception at 0x7c812a7b in aspnet_wp.exe: 0xE0434F4E: 0xe0434f4e. The thread 'Win32 Thread' (0x804) has exited with code 0 (0x0). aspnet_wp!library!9!10/9/2007-13:14:11:: i INFO: Cleaned -1 batch records, -1 policies, 0 sessions, -1 cache entries, 0 snapshots, 0 chunks, -1 running jobs, -1 persisted streams 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 reportsusing 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 isuspected. 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, Id suggest re-starting SQL Server and then testing your SRS print scenario again 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 ( yieldingdefault connection to Set NoCount On" (UserOption 512) cause i run a lot of reports to file and dont wantclients see rows effectedin reports i runand 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 changingthe defaults!) I was hopin it was some stupid nit that was causin the problem! I sure wouldnt a thunkit, but chalkup 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" intheir 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.

I am also having the same problem. One of my reports hangs during print or print preview when I scroll to a large grid which spans multiple pages. I have checked the NoCount option and it is off. The report is fine on screen and when exported to a pdf. We're using SQL Server 2005 SP2 on a server with clients over a network. The grid that hangs is a group in a report, with both rows and columns going to the next page. Any other ideas what could be causing this? A consultant who has leftwrote this report, and I haven't done reports for SQL Server before, so any help is appreciated!

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.

This report is an 11 page report and it hangs when clicking Next from the 3rd to 4th page on Print Preview. It is trying to show the next group in the report which is large - it spans 3 pages, with both rows and columns continuing on the next pages. I have not left it on overnight, I have left it running for at least a half hour. configuration I have is as follows: ReportServer Database is one server ReportServer web site is on another server, along with my web site I have checked the ReportServer logs for errors on the Report Server db machine and have not found any errors for when the report is run. I do see an error for when the Report Server starts: "Throwing Microsoft.ReportingServices.Diagnostics.Utilities.InvalidReportServerDatabaseException: The version of the report server database is either in a format that is not valid, or it cannot be read. The found version is 'C.0.8.54'. The expected version is 'C.0.8.43'. To continue, update the version of the report server database and verify access rights." On the ReportServer log of the web site machine, Isee the report starting to render and then no errors or other messages: w3wp!library!6!10/19/2007-10:26:07:: i INFO: Call to RenderFirst( '/DataBus Coordinator Reports/Application Matrix' )w3wp!library!5!10/19/2007-10:26:19:: Using folder C:\Program Files\Microsoft SQL Server\MSSQL.1\Reporting Services\RSTempFiles for temporary files.w3wp!library!6!10/19/2007-10:26:49:: i INFO: Call to RenderNext( '/DataBus Coordinator Reports/Application Matrix' )w3wp!webserver!5!10/19/2007-10:26:50:: i INFO: Processed report. Report='/DataBus Coordinator Reports/Application Matrix', Stream=''w3wp!cache!6!10/19/2007-10:26:50:: i INFO: Session live: /DataBus Coordinator Reports/Application Matrixw3wp!library!7!10/19/2007-10:36:00:: i INFO: Cleaned 0 batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0 chunks, 0 running jobs, 0 persisted streams I have two sets of machines configured the same as above and it does the same thing on both. I have another machine that has the database and the report server website on the same machine and there it works properly. I'm using the same client to access the three sets of servers. I cannot run the print preview the report on the servers directly since they don't have printers installed, as they are server machines. I cannot find the registry key you mentioned (LogRSClientPrintInfo). Would this be on the web site machine or the database machine? I don't see it in the registry in either one. The database machine registry has a Microsoft SQL Server tag withthe following configuration: HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL Server\90\Tools\Shell There is no ReportingServices key in there. The web site machine does not have a Microsoft SQL Server tag Thanks for your help.

First of all the problem you are seeing is not a printing problem. The error occurs when you click from page 3 to page 4, like you say. That being said, LogRSClientPrintInfo is not going to be useful here. From the error msg, it looks like the SRS binaries and the database are not in sync. What build of SRS are you running? Can be found by browsing http://<servername>/reportserver or checking the srs log, at the very top. When SRS web server and DB server are on different machines the service pack upgrade may not update both the SRS DBs and the SRS binaries correctly. Which seems to be the case. The latest build for SQL is Service pack 3 Cumulative update 4.Upgrade both theservers in question correctly and ensure by checking theSQL Setup logs. The best way is to install the service pack on the web server and that shouldinturn go ahead and update the DBalso. If that does not work, upgrade both servers individually. Basically, ensure that the build on the SQL serverand the web server are exactly the same.

!!!!CORRECTION!!!! The latest build for SQL is Service pack2 Cumulative update 4

Sorry I didn't get back to this earlier. (Was out for training last week.) I checked the versions on both the Reporting Server and the db and they both match at 9.00.3042.00. I see that there is another hotfix out: Build 3152. Is that the cummulative update 4? Do you recommend upgrading to that build on both machines? I did see in the setup logs for SP2 on the database server that an error 3010 was returned for the Reporting Services component (reboot required). I don't know if a reboot was ever done after the install on that machine. I will try to get that done now. Thanks again for all your help!

Update: I installed the latest hotfix cummulative upgrade 9.00.3152.00 to both db server and report server machine and I still have the same problem. I let the preview window stay up for a while longer, and about 2hrs later, I get a message in the preview "Error rendering report, error number 0x800C000B". This leads me to think that the versions are ok, but perhaps it is running out of memory? Or hitting a timeout? Any ideas?

I've got a print issue too. When I hit the print button the print dialogue opens, when I hit OK I get a message saying that "an error occure while printing" followed bya Javascript message box whichasks if I want to debug. The line of code it's breaking on is RSClientPrint.Print(http://<sitename>:80/Reserved.ReportViewerWebControl.axd..., Sinceour site is HTTPS I tried changing theurl to https and running the command. This opened the print dialogue, I clicked OK and the report printed fine. Does anybody know if there is a config setting or some code I can use which will pass https instead of http to the print method?

Did you check the rsreportserver.config file and set the urlroot tag?

I'm having another variation on the existing theme. We have an instance of SSRS 2005 RTMrunningon a SQL Server 2000 SP4database server (was like that when I was hired, don't ask me why). Most reports print with no problems. However, we have a couple of reports that some people can print and others cannot. The ones who cannot get the Printing Now... dialog that pops up and just freezes their IE window. I've tried to isolate windows versions and IE versions but it appears that there are some with IE6 that do work and others that do not. Same with IE7. I can print the report from the server without any problems. Thinking that it may have been related to the AD account/script, I logged intoa workstation that could printwith my account and printed with no problem butcouldn't print with my account on my laptop. Also tried removing RSClientPrint and having it re-install from the server but that did no good. Still get the Printing Now dialog. I did not find the registry key which was posted earlier to dump the client print out to a file so I added the key. But I do not get any file in my "%USERPROFILE%\Local Settings\Temp" folder. I know having the RTM build probably complicates the troubleshooting but I would like to fix these reports in place without having to apply any service packs. We're building a new SSRS server and will begin migrating things over in another month or so but we would like to figure out these two reports prior to that. Thanks!

After leaving the Printing Now dialog box open while I went to lunch, I came back and found this error: Print Error An Error occured during the printing. (0x800C00B). if that helps at all. I wasn't able to find a particular KB article referencing that error.

To add to the mystery, I've found that a laptop which cannot print the report at a remote office can print the report at the main office. And I've verified this on two separate machines. Same logins were used on each laptop. I do know that the login script does manipulate the My Documents folder depending on the location from where you login. So it basically "roams". Could that have anything to do with not being able to print an SSRS report? I'm really leaning in that direction but I don't know how I can prove it. I wish I knew of a way to turn on some kind of more detailed system logging. Because the event log is not giving me enough information. Any information that would help be solve issue would be appreciated. Thanks.

In case someone else stumbles onto this issue in the future, we did get it resolved. It turned out that Cisco Secureworks was blocking the traffic b/c it appeared to have an embedded metafile that was being marked as malicious. And since Secureworks would not filter anything within the home office it would print fine there but not out in the branches. So the SSRS server was added to the exclusion list and presto! It works now in all of the branches.

Hi Lukasz, I am also having the same problem, but i didnot get the solution. please let me know in detail what i have to do on the server. no one in the client mechine were able to print the report. thanks, kamal Thanks, Kamal

This works for me Internet Explorer Tools Internet Options Advanced Check Use HTTP 1.1 Uncheck Use HTTP 1.1 through proxy connections The idea came to me while eating a tuna club sandwich I would prefer from now on :P

This is the solution we found to our server: In our server properties, under connections we had the default connection set nocount ON. In order to work properly, Reporting Services 2005 requires that option to be OFF. Note that that option sets the default for the entire server, so make sure you don't have other applications on that SQL server that expect that setting to be ON if you're planning to change those settings. Since in our case we couldn't set that option to OFF (because it broke other applications), the solution was to modify the SSRS procedures that were being called infinite times by Reporting Services with SET NOCOUNT OFF. You can find the offending procedures by running SQL Profiler. To solve the specific problem with the print button, we modified the stored procedure DeletePersistedStreams on the ReportingServer$ServerName database, adding the clause SET NOCOUNT OFF at the beginning of the procedure. I found that in the past we also had problems trying to delete reports through Report Manager, and the same thing was done with the procedure DeleteObject.