I have a problem with Sql Server 2005 Reporting Server where people are receiving old versions of a report whenever the report is sent through a subscription.
I've added a date to the footer of the report, build and deployed it but subscribers still receive an older report.
I am not able to find any known issue or someone with a similar problem and could use some guidance on what to do.
Check Properties -> Execution. There are options there to have the report run based on a cached copy or from a snapshot. If these options are selected, the report will be run from older data in order to increase performance. Disable these to get the latest data.
Related
Our reports in SSRS stopped sending. The last report was sent 2 days ago, and was send successfully, but since then none of the reports are being sent.
If I look at the SSRS web page for each report, there is no error. Simply showing the last run time as 2 days ago, so seems it didn't even try send.
Yesterday we did make some changes. But only moving a database from the Express version, to the regular version. We did not do anything that would affect the SSRS metadata (or at least we don't think we did...)
Where should we start looking to see why the report subscriptions stopped? Is there a process that could have accidentally been disabled? Thank you!
The Report subscriptions are created as jobs for the SQL Agent. You should see a long list of jobs with GUIDs as the names. Make sure that the SQL agent jobs are running. Going through the Steps of the SQL Reporting Services Configuration tool will recreate these jobs if you were to move the Reporting Service installation to another server. (I don't recall which step recreates the subscriptions. Just go through each pane and click "Apply.")
Depending on how you move things, you may need to backup and restore encryption keys, and you can easily end up in a state where two copies of subscription exist and are executed ( on different servers.) But in your case, where you didn't move SSRS, I'd look at the SQL Agent properties on the original server (Express) to see that the SQL agent is enabled and running, and check the history of the SQL Agent jobs, to see if there are any problems.
Running into an issue where after upgrading SQL Server from 2008/R2 to 2012, SSRS report when rendered to PDF will display "Page x of 0" at the bottom (x = page number of report). This only occurs in PDF.
I open the reports, and the correct usage of the global parameters is there. If I re-deploy the report to the upgraded SSRS, it works fine.
It appears to be an upgrade issue. Applying the SQL Server 2012 SP1 doesn't help either.
Any ideas?
So we opened a ticket with MS. In a nutshell, when running an in-place upgrade, the RDL's stored in the ReportServer DB are "left alone". Because MS changed only the Globals!TotalPages to Globals!OverAllTotalPages and the RDL's are never touched during the upgrade process, the error occurs.
This also explains why when you take the un-modified original report and re-upload/deploy the report. It works.
This is fine if your just updating you local server. When you have 4500+ installations which can support up to N users, and 180+ reports. We get a trouble ticket in when a customer upgrades. That can be a lot of trouble tickets.
Not sure why MS just didn't "upgrade" the Globals!TotalPages to Globals!OverAllTotalPages. Didn't get an answer for that one.
I've recently copied an SSRS instance from SQL 2008 R2 to a new SQL 2012 instance. I performed a backup/restore on the report server DB and encryption key and have configured the service/execution accounts etc. I can run reports via report manager without incident and I can create new subscriptions the same way which run fine.
However, whenever one of the previously existing subscriptions (set up under R2) is due to run, it fails with the following error:
Microsoft.ReportingServices.Diagnostics.Utilities.AuthorizationExtensionException: An error occurred when invoking the authorization extension. ---> System.ArgumentNullException: SafeHandle cannot be null.
The suggestion seems to be that this is related to custom security components, but we don't have any. We do have a custom DLL for other purposes, but it isn't even being invoked when the subscriptions in question run, so it's highly unlikely it's that. CAS is configured for this DLL.
I'm really looking for suggestions on where to start looking to resolve this error, as I'm out of ideas on what to try!
I posted the same question on MSDN and got an answer suggesting it could be that the subscriptions that were copied over from the old server were created by local users that don't exist on the new server.
After some investigation, this turned out to be the case. It seems that SSRS needs the subscription creator (OwnerID field in the Subscriptions table in the Report Server DB) to be a valid account, as it must perform some sort of verification when it attempts to run the subscription.
Once I changed this to a valid domain account (a local account would work just as well), the subscriptions all work fine.
I have development, test, demo and production systems. They all need to have the same set of reports (easily deployed via Visual Studio, multiple reports at the same time if needed) and the same set of report subscriptions. At this time I have to manually go through the sequence of up to 7 steps in web UI for report manager to deploy or modify each subscription on each system.
Is there a way to automate/improve creation/modification of report subscriptions? I use SSRS 2008.
I've cheated in the past and manipulated the reporting database in SQL Server, you could dig around in there and see if you can figure out the records you need to add.
I'm having trouble figuring this out.
I stopped ALL of local SQL Services, e.g. SQL Server, SQL Agent, Reporting Services. Then using Report Builder 2.0 to create a report connecting to a remote SQL Server (No SSRS running) out in the farm. When I click on "Run" button, for some odd reasons, it still render the report.
I thought you must have SSRS running in the first place. Is SQL Reporting Services even required for Report Builder?
Img
alt text http://www.freeimagehosting.net/image.php?0bf8bb1f1d.jpg
When Reporting Services runs a report, it creates a data file of the data used in the report and, if nothing changes, it uses that data the next time the report runs instead of hitting the server again. You could be seeing the cached data.
Look where the report is kept. There will be a report file, say MyReport.rdl and also the data, MyReport.rdl.data. You could delete that data file otherwise simply changing the report parameters (if you have some) will generally cause the report to disregard the cached data and make a trip to the server again.
I'm answering my own question. Here's my observation after some googling and experimenting.
Report Builder is using a stand alone report control to render report. Visual Studio.NET is probably using the same thing when preview a report. SSRS is required when developers need to incorporate web-based reporting solution, e.g. ASP.NET, as well as to manage reports.
What's really bothering me is that to author reports in VS.NET, I must be using Business Intelligence Projects. In order to do that, I must install SQL Server 2005/2008 with SSRS. Why is so when SSRS is not even required in a LOCAL environment?