Take the 2-minute tour ×
Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It's 100% free, no registration required.

We have SSRS 2005 that publishes reports. The reports are often as big as 1000-3000 pages. So the problem is that when the users try to print the report, it prints some of the pages and stops. And this happens randomly. For instance, 10 people can print at the approximately the same time and 4 could face the problem. When I look at the even log it shows an ASP.Net warning that says:

'The report execution <'session ID'> has expired or cannot be found. (rsExecutionNotFound)'.

In a development setting, I tried upgrading it to SSRS 2012 and moved all the reports. But I got the same error message:

An error occurred during printing. (0x80004005)`.

And the error log is:

'The report execution <'session ID'> has expired or cannot be found. (rsExecutionNotFound)'.

What I have already done is make changes to the config file and set EnableAuthPersistance to FALSE and CleanupCycleMinutes to 30 on the SSRS 2012. I have already ruled out network and hardware related issues by trying it on different servers.

Do you know why this is happening and why it is happening so randomly?

share|improve this question
2  
I'm going out on a limb here and guessing your reporting session times out because you are attempting to print 1000 to 3000 pages. RS needs to generate all the data, stream it across the network, the client must receive that data and then stream it to a printer. Throw some graphics in there and you're really going to congest your network. Try having them Export to PDF and then print the PDF if it's more than X pages. The content will be the same but and you can eliminate part of the network from the equation. And eliminate part of the rain forest –  billinkc Sep 12 '13 at 17:56
    
Why are you killing so many trees by printing 1-3k pages? Waste of paper! –  bluefeet Sep 12 '13 at 18:10
    
@bluefeet IIRC There have been more trees replaced than are being cut down for printing. So print away! –  Kermit Sep 12 '13 at 18:20
    
Is it possible that what's happening is that your printer lacks the required memory necessary to print that large of a document. Try Exporting to a PDF and then printing that. My assumtion is that will not work as well. –  Zane Sep 12 '13 at 18:20
    
Is this being printed on a dot-matrix printer? –  Kermit Sep 12 '13 at 18:21
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.