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.
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.
Hi I'm looking for help with the following issue:
In TFS on our SSRS report server whenever I run any of the out the box Sprint Burndown reports the report seems to run successfully but I get the following error in the bottom right hand corner:
Through some research I found that the issue was due to the field definitions in that particular Collection not matching the other collections that we have in TFS. Simple...
In order to determine which field definition in the collection was the issue I used the witadmin command listfields for all of my collections:
witadmin listfields /collection:Collection /n:Microsoft.VSTS.Common.ReviewedBy
This led me to find that the Synchronizes Identity Name Changes definition in the collection mentioned in the TF293000 error was set to a value of true, while it is false in all of my other collections. Issue Found! Should be easy from here...wrong.
The following command should solve my problem:
witadmin changefield /collection:Collection /n:Microsoft.VSTS.Common.ReviewedBy /syncnamechanges:false
*of course with the proper collection url subbed in for the word Collection
However when run and after I confirm that I want to make the change I get the following error:
TF401327: The operation is not supported. The feature is obselete.
I look the error up and it takes me to this page TFS Known Issue which tells me it's a known issue but was resolved in update 1 ... we have update 3.
I then attempted to simply edit the WIT .xml file and update the attribute for that WIT on that collection with false, but when I import the change to the server it tells me it has imported successfully however when I export it I see that the file has not changed.
I have also tried copying the the .xml file from the same WIT in another collection and uploading that to the offending collection and that will not work. I've never had an issue with uploading a WIT as we've made several changes to our TFS workflow before. I'm pretty stuck at this point and just wondering if anyone else has experienced this issue before, thanks!
According to the error info, seems there is a conflict in the TFS Data warehouse and this because 2 fields in different collection has different attributes in the data warehouse as it’s only one data warehouse. To avoid schema conflicts when you export and process data to the data warehouse databases, you must assign the same values to these attributes across all collections:
Field type (the value for this field cannot be changed for an
existing field).
Reporting type.
Reporting name.
What you have done is the correct operation, change/update the attribute for the field in one project collection to match the assignments that are made in other project collections.
You could try to narrow the issue, if this issue only happened on that specific field in the team project collection. All other work item filed working correctly? Also give a try with other collections, such as change the syncnamechanges=true, then set it back to syncnamechanges=false, to see if any issue occurs.
Run the command line on TFS sever machine instead of your develop machine. Clear TFS cahce. And if the filed is not use for reporting about those project collections, you could also try to mark it as non-reportable. More details please refer below links:
Resolve data warehouse schema conflicts
Change a reportable attribute for a work item field
I have a SSRS 2008 project with some reports, and recently we update the version, now I open the project with the SQL Server Data Tools 2015, and all is fine, I can deploy, edit, update all fine.
The problem comes when I want to create a new report, when I add a DataSet to the report, the preview tab says:
An error occurred during local report processing
The definition of the report 'Report Name' is invalid
and nothing more happens, I can't preview the report anymore.
Does anyone know if it is a issue of upgrade/open a SSRS 2008 solution with SSDT 2015?
After some research... I couldn't find anything.
So I tried to create the report in Reporting Services 2008, and when trying to preview the report after adding a DataSet it show me the same error:
An error occurred during local report processing
The definition of the report 'Report Name' is invalid
But now, it has an aditional line:
The shared dataset definition is not valid. details the required
attribute 'name' is missing
And after enter the first search result in Google, it looks like the problem was that my DataSet was a Shared DataSet, JoannaK found the same problem and also found a workaround:
Found a workaround for now: Create the data set as embedded> Convert
to Shared Data set Looks like the Name property is set when you start
with embedded. report runs and can data sets can be uploaded to the
report server
This solves my problem. Hope it helps someone in the future.
Source: JoannaK from SQL Server Data Tools Preview update for April 2016
SSDT is generating a broken dataset definition. To fix it:
Open up the shared dataset's .rsd file in a text editor.
In the xml therein find the <DataSet> opening tag.
Add the attribute Name (case-sensitive) to that tag, e.g: <DataSet Name="SomeDataSet">
Probably should set the Name to be the same as the filename but doesn't seem to make any difference as far as I can see.
Thanks to the existing answer as without that I never would have got it to work at all.
VS2015 / SSRS2012
I experienced similar error. It mostly occurs as of change in 'SHARED DATASET'.
Check for query fields in 'Shared Database Properties', if no fields are there , simply add fields you have included in your query.
Check for database connection
Check for 'Stored Procedure' and it's result if you have used stored procedure.
One can delete old dataset and re-create with same name.
As a last option, one can create 'New Dataset' (another one) and bind the new one with the report(take care to map all fields again once you choose to create new dataset.
I am generating report everyday through SSRS. I am trying to get current date as file name when ever the job runs and file created.
Like this ID_report_03-31-2014
I have tried echo %date% %time% and #ExecutionTime but it doesn't work
The main option with a file share subscription is to add #timestamp to the file name.
From File Share Delivery in Reporting Services:
An alternative approach to creating unique files for every delivery is
to include a timestamp in the file name. To do this, add the
#timestamp variable to the file name (for example,
CompanySales#timestamp). With this approach, the file name is unique
by definition, so it will never be overwritten.
I don't know if this is exactly what you are after, since it will include a time component, but as far as a standard SSRS subscription goes your options are limited.
Edit after comment
You don't have a lot of control over the format here.
On the MS forums one of there support suggests using Data Driven Subscriptions to get more control:
Can we edit #timestamp variable in SSRS:
In this case, we can define the filename with timestamp in database
and then use Data-Driven Subscriptions to delivey the report.
But that seems a poor option to me, but is the only suggestion out there that I can see.
I have solved that problem using Data Driven Subscription.
I found the solution here.
I have this report when I deploy it it works. I come in the next day and under the Data Sources tab in properties I notice the report is pointing to our Dev environment. Now I know and double check that it is not coming from the solution as I have overwrite datasources equal to false, and there is only the one datasource in the project (named something completely different)
But what I also noted was when I change just the datasource on the report the Modified Date and Modified By does not change.
So it begs the question, is there anywhere on the SSRS site or database that I can capture who and when a datasource for a report is changed?
We are currently using SSRS 2005
Reportserver.dbo.Catalog has record of who first created and last modified any object on the server.