I'm trying to get a Data-Driven subscription to output a file but cannot get it do so.
The job runs but nothing is generated
Oct 24, 2019 10:01:03 AM
Processing: 0 processed of 10 total; 0 errors.
Data is populated to the event and the Active Subscriptions table is being populated, but no files are ever generated.
My query validates successfully. The report has a single parameter and I verified that data is being populated when the report is run manually.
I have the following settings but I am still not sure what is going on. Also, the user has read-write permissions to the folder.
Any help is greatly appreciated! Thanks!
Permissions issue on share. Went to advanced sharing and added user. Everything works as expected.
Related
I have an ssrs server that is not allowing me to create subscriptions for some reports. There are 20+ reports in a folder which all use the same data source: /Data Sources/MyDataSource. The credentials are stored in the data source. I can add subscriptions to most of the reports, but there are a few which throw the following error:
An Error Has Occurred:
Subscription can't be created or edited because
the credentials used to run the report are not stored, or if a linked
report, the link is no longer valid.
I have tried deleting the report and re-uploading them, deploying the whole bit from the project and adding another data source with the same stored credentials. However, I still get the same warning triangle on the subscription button. There are a batch of new reports I have added, some have this issue and others do not. Restarting the SSRS service did not help.
Any other ideas for troubleshooting this?
Bonkers! Looks like the issue was a case sensitivity one. In the project, all of the reports referred to a shared data source. However, sometimes the reference to the shared data source was spelled "mySharedDataSource" instead of "MySharedDataSource"
I found a hint of this in the logs, which complained about the first version of the spelling which did not exist on the report server. Fixing that and deploying the report corrected the issue and now I can create subscriptions.
Might be a 2017 thing, I have these reports both on a 2016 and 2019 instance and they have not complained.
My error is below:
The report server cannot process the report or shared dataset.
The shared data source 'XXX' for the report server or SharePoint site is not valid.
Browse to the server or site and select a shared data source. (rsInvalidDataSourceReference)
Right. I've checked all 3 data sources and they connect fine. I've deleted the report and data sources and deployed them again but still the error. I've used Notepad++ to check for the reference XXX in any of the files and still nothing.
These options are both checked.
Always run this report with the most recent data
Do not cache temporary copies of this report
Under Snapshot Options > Allow report history to be created manually I get a warning of Credentials used to run this report are not stored. Could this be a reason?
My data sources are setup like:
I have read other similar posts but no luck.
Thanks
A restart of report server resolved this particular issue for some annoyingly odd reason
Go to your Datasets and check the Data Source being used if it's pointing to the correct data source
I've created a shared dataset in both BIDS and Report Builder. The data source is set up to use a windows service account. I've also tried it with a sql user that is verified to work.
In both BIDS and Report Builder, data is returned. When I go to the report portal and try to preview the data, or try to add it is a dataset to a mobile report, it throws an error:
I've given permissions at the root folder level to NT Authority\Authenticated Users and to my department's AD group, with all rights granted.
I'm not really sure what else to do, or where to even check to see what the error actually is. Any help is appreciated.
So I figured it out - it actually had nothing to do with permissions. A fiddler trace showed a 422 and 500 errors.
422: the Dataset could not be processed. The 500 said
500: There was a problem getting data from the Report Server Web Service: System.Web.Services.Protocols.SoapException: The JSON SharedDataSet Table renderer cannot parse the supplied report...
This lead me to check the actual query coming back, which had a Geography data type coming back for one of the fields. When I removed this from the query, everything worked fine.
This is hopefully a simple yes/no question but I cant find anything definitive online.
If an SSRS subscription - on a once a day schedule - fails because a data source is deleted, if you rebuild the data source will the subscription run as normal the following day or do you need to alter the subscription to rebuild it?
Thanks in advance
if you rebuild the data source will the subscription run as normal the
following day or do you need to alter the subscription to rebuild it?
Short answers: No and No
First No
If the datasource has been deleted and you recreate it, then the DataSourceID property will be different.
So all the dependent items will have first to be "re-linked" to the datasource (reports, shared datasets).
Second No
Nothing will have to be changed in the Subscription though, because the Subscription is linked to a Report (or Linked Report), so once everything else is valid it will run as normal.
Assuming you are using a regular subscription and not a data driven subscription, as long as the published report's data source is set after the new data source was re-created. The subscription should work.
I am having this problem where the data being shown in report is different when I deploy it on server. So let's say if I am viewing report by pressing F5 (to debug) or by clicking on "Preview" button on the report in BI Studio the data shown is correct. But when I deploy the same report and when I run it from server such as http://myserver/reports then data shown is incorrect/missing.
For e.g. in some cases it is not showing data for a particular field and there are some number fields which are showing wrong data. I have cleaned the solution, deleted data cache files, rebuilt and deployed like 100 times but no luck.
When I deploy it shows some warning (which I guess I can ignore) but no errors.
I have checked the database by running queries and stored procedures directly and they all return correct data.
How do I fix this issue?
I went to report server and looked at the XML of one of the data set which was creating problem and found out that the new FIELD I have added is not there. Then I tried to deploy that data set and it said Overwrite Dataset property is set to False and that's why it was not deploying and I missed it in messages when it deploys a solution. So I simply set the property to True, deployed it and viola problem is solved.