I think I've been able to fix what I think is broadly the same issue.
First thing in the morning, if I go to our Report Server URL, it loads quick enough and I'm able to browse the menu straight away no problem. But as soon as I click on an actual report, there's that 2 minute wait before the report actually executes...
[Quick test... it was only 75 seconds for me this time, but it felt like longer!]
Running a report from a command line using the "RS" command seems to start up (wake up!) whetever part of the architecture isn't otherwise being started and the first report takes a normal amount of time to execute. I shall shedule that as a task and forget about it.
RS is a bit fiddly to use, since you need to script a bit of VBA to execute the report, but I already needed to work that part out for another job I had..
Edit: Added script below
I can't really take all the credit for this, nor cite references I'm afraid. It's cobbled together from 3 or 4 different resources already out there, and adapted to suit my needs (specifically, I wanted to generate a set of pdf exports for a range of inputs). And then simplified a little bit more for here:
Script file "RunReport.rss"
Public Sub Main()
Dim format as string = "PDF"
Dim fileName as String
' adapt the following variable for your report location
Dim reportPath as String = "/{my file path}/{my report name}"
Dim parameters(0) As ParameterValue
' Prepare Render arguments
Dim historyID as string = Nothing
Dim deviceInfo as string = Nothing
Dim extension as string = Nothing
Dim encoding as string
Dim mimeType as string
Dim warnings() AS Warning = Nothing
Dim streamIDs() as string = Nothing
Dim results() as Byte
rs.LoadReport(reportPath, historyID)
fileName = "output.pdf"
results = rs.Render(format, deviceInfo, extension, _
mimeType, encoding, warnings, streamIDs)
' Open a file stream and write out the report
Dim stream As FileStream = File.OpenWrite(fileName)
stream.Write(results, 0, results.Length)
stream.Close()
End Sub
Which is then executed from the command line with
rs -i RunReport.rss -s http://{my server name}/reportserver -t -e Exec2005
And in this case creates a file called "output.pdf"
Hopefully that may be of use?
Best Answer
What I have seen in a case like you ask about is you hit a report, and copy the url out and then try to hit it later. Reports have session state, especially if you change paramaters,etc. The url will look like a report url with some funky querystring data added to the end. You can't share that because SSRS can't take your "session state" and then find it later.